Back to Details

amz-q4-restock-war-room

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Q4 Restock War Room

Q4补货作战室

Q4 is where the year is won or lost. October through December delivers 30-40% of annual revenue for most sellers. FBA receiving slows from 5 days to 14-21 days during peak. Container ports add another 7-10 days of unpredictability. The standard "30-day cover" restock model breaks every Q4. A war-room plan adds the right buffers and pre-stages FBM as a safety net. The cost of stocking out on Black Friday is not just lost sales, it is permanent BSR damage that takes 6-8 weeks to recover.
Q4是决定全年成败的关键时期。对于大多数卖家而言，10月至12月的营收占全年的30-40%。旺季期间，FBA收货时长从5天延长至14-21天。集装箱港口还会增加7-10天的不确定性。标准的"30天库存覆盖"补货模型在每个Q4都会失效。作战室计划会添加合适的缓冲时间，并预先准备FBM作为安全保障。黑五期间缺货的代价不仅是损失销售额，还会对BSR造成永久性损害，恢复需要6-8周时间。

When to use this

适用场景

  • August 1st, kicking off Q4 planning
  • October cover check, deciding emergency air-freight or FBM
  • A SKU is forecasted to peak 3x normal velocity in November
  • Multiple SKUs sharing a container with mixed Q4 demand profiles
  • 8月1日启动Q4规划时
  • 10月库存覆盖检查，决定紧急空运或启用FBM时
  • 预测某SKU在11月的销量峰值为平日3倍时
  • 多个SKU共用集装箱且Q4需求模式不同时

The framework. The Q4 War-Room Plan

框架：Q4作战室计划

Q4 demand = (Last-year peak monthly velocity x YoY growth x 1.4 peak buffer)
Order quantity = Q4 demand + lead time cover + inbound delay buffer
Q4需求 = (去年月度峰值销量 × 同比增长率 × 1.4峰值缓冲系数)
订购数量 = Q4需求 + 前置期库存覆盖 + 入库延迟缓冲

Inbound delay buffer by month received

按收货月份划分的入库延迟缓冲

Receiving monthBuffer days to add
August0
September7
October14
November14
Decembern/a (too late for FBA)
收货月份需添加的缓冲天数
8月0
9月7
10月14
11月14
12月不适用（FBA入库为时已晚）

FBM fallback triggers

FBM备用触发机制

If FBA cover drops below 14 days by Nov 20, activate FBM:
  • List FBM offer at +8% price (covers FBM fulfillment cost)
  • Pre-stage 30 days of inventory at 3PL or home
  • Switch buy box back to FBA when restock arrives
若11月20日前FBA库存覆盖天数降至14天以下，启动FBM：
  • 以高出8%的价格上架FBM报价（覆盖FBM履约成本）
  • 在第三方物流仓库或本地预先准备30天的库存
  • 补货入库后将购物车切换回FBA

Peak velocity multipliers (vs Q3 baseline)

峰值销量乘数（对比Q3基准值）

Event dates move every year. Confirm the current-year dates in Seller Central and map each multiplier to the right week.
EventVelocity multiplier
Prime Big Deal Days (early-to-mid October, confirm yearly)1.8x baseline for that week
Black Friday week2.5-3.5x baseline
Cyber Monday2.0x baseline
Early December (Christmas push)1.6x baseline
Late December (last-mile rush)0.9x (shipping cutoffs and carrier capacity throttle late-arriving orders)
活动日期每年都会变动。请在卖家平台确认当年日期，并为对应周匹配相应乘数。
活动销量乘数
Prime大促日（10月上旬至中旬，需确认当年日期）当周基准值的1.8倍
黑五周基准值的2.5-3.5倍
网络星期一基准值的2.0倍
12月上旬（圣诞促销）基准值的1.6倍
12月下旬（最后配送高峰）基准值的0.9倍（配送截止和 carrier 运力限制导致晚到订单减少）

Step by step

步骤说明

  1. Pull last year's Q4 sales by SKU by week. Business Reports. Note the weekly peak.
  2. Apply YoY growth assumption. Use trailing 90-day YoY for the same SKU. Default 1.15x if no data.
  3. Apply 1.4x peak buffer. Q4 is more volatile than Q3, undershoot kills.
  4. Calculate inbound delay buffer per month. Add to lead time per the table.
  5. Build the reorder calendar. Confirm the current-year event dates first, then place PO dates so units land at FBA with cover ahead of each event:
    • about 1 week before the fall Prime event (early-to-mid October, confirm yearly)
    • about 3 weeks before Black Friday
    • by late November for early-December coverage
  6. Set the FBM trigger thresholds. For each SKU, calculate the FBA-cover day count that triggers FBM activation. Pre-stage FBM inventory by Nov 1.
  7. Build the dashboard. Weekly check-in: FBA cover days, sell-through rate vs forecast, time-to-FBM-trigger.
  8. Run the quality check, then circulate to ops and finance.
  1. 提取去年Q4各SKU的周度销量数据。可从业务报告中获取，记录周度峰值。
  2. 应用同比增长假设。使用该SKU过去90天的同比增长率。若无数据，默认使用1.15倍。
  3. 应用1.4倍峰值缓冲系数。Q4的波动性高于Q3，低估需求会导致严重后果。
  4. 按月份计算入库延迟缓冲。根据表格将缓冲天数添加至前置期。
  5. 制定补货日历。先确认当年活动日期，再安排采购订单日期，确保库存在各活动前入库FBA：
    • 秋季Prime活动前约1周（10月上旬至中旬，需确认当年日期）
    • 黑五前约3周
    • 11月底前完成入库，保障12月上旬的库存覆盖
  6. 设置FBM触发阈值。为每个SKU计算触发FBM启用的FBA库存覆盖天数。11月1日前完成FBM库存预准备。
  7. 搭建监控仪表盘。每周检查：FBA库存覆盖天数、售罄率与预测值对比、距离FBM触发的剩余天数。
  8. 执行质量检查，然后将计划分发至运营和财务部门。

Output format

输出格式

undefined
undefined

Q4 War Room Plan. [Account]

Q4作战室计划. [账号名称]

Per-SKU summary SKU | Last-yr peak/wk | YoY growth | Buffered Q4 demand | FBM trigger day [rows]
Reorder calendar Week of [date] | SKU | Order qty | PO ship date | Expected receive date [rows for August through November]
FBM fallback inventory SKU | FBM units to pre-stage | Location | Activation trigger [rows]
Weekly check-in metrics
  • FBA cover days (target: >= 21)
  • Sell-through vs forecast (target: 90-110%)
  • Days to FBM trigger (alarm if <= 7)
undefined
SKU汇总表 SKU | 去年周度峰值 | 同比增长率 | 缓冲后Q4需求 | FBM触发天数 [数据行]
补货日历 [日期]当周 | SKU | 订购数量 | 采购订单发货日期 | 预计收货日期 [8月至11月的数据行]
FBM备用库存 SKU | 需预准备的FBM库存数量 | 存放地点 | 触发条件 [数据行]
每周检查指标
  • FBA库存覆盖天数（目标：≥21）
  • 售罄率与预测值对比（目标：90-110%）
  • 距离FBM触发的剩余天数（≤7天时触发警报）
undefined

Worked example

示例演算

SKU: pet brush, last-year Nov peak = 320 units/week. YoY growth = 1.22x. Peak buffer 1.4x. Q4 weekly peak forecast = 320 x 1.22 x 1.4 = 547 units/week. November total Q4 demand = 4 weeks x 547 = 2,188 units.
Lead time supplier ship to FBA = 35 days normal. November receiving buffer adds 14 days. Total lead time = 49 days. PO must ship by Sept 12 to land at FBA by Nov 1.
FBM trigger: at peak 547 units/week, 14-day cover = 1,094 units. When FBA inventory drops below 1,094 units after Nov 20, list FBM offer. Pre-stage 600 units (30 days FBM cover) at 3PL by Nov 1. Cost: 600 x $2.40 storage = $1,440 insurance against $0 stockout. Worth it.
Skipping this plan = stockout Nov 26 historical pattern = 4 days dark = 4 x 547 x $9 margin = $19,692 lost plus 6-8 weeks BSR recovery.
SKU：宠物梳，去年11月周度峰值=320件/周。同比增长率=1.22倍。峰值缓冲系数1.4倍。Q4周度峰值预测=320 × 1.22 × 1.4 = 547件/周。11月Q4总需求=4周 × 547 = 2188件。
供应商发货至FBA的常规前置期=35天。11月收货缓冲添加14天。总前置期=49天。采购订单需在9月12日发货，才能在11月1日前入库FBA。
FBM触发条件：按峰值547件/周计算，14天库存覆盖=1094件。11月20日后，若FBA库存降至1094件以下，上架FBM报价。11月1日前在第三方物流仓库预准备600件（30天FBM库存覆盖）。成本：600 × 2.40美元仓储费=1440美元，以此避免缺货损失。这笔投入是值得的。
若跳过该计划，会重蹈历史覆辙：11月26日缺货=4天无货=4 × 547 × 9美元利润=19692美元损失，外加6-8周的BSR恢复时间。

Quality check

质量检查要点

  • Last-year data is week-level, not month-level (smoothing hides peaks)
  • YoY growth uses trailing 90 days, not full-year average
  • Inbound buffer aligned to receive month, not ship month
  • FBM trigger numerically defined per SKU, not "we will watch it"
  • Reorder calendar shows PO ship dates, not just receive dates
  • 去年数据为周度数据，而非月度数据（月度平滑会掩盖峰值）
  • 同比增长率使用过去90天的数据，而非全年平均值
  • 入库缓冲与收货月份对齐，而非发货月份
  • FBM触发条件为每个SKU设定具体数值，而非“我们会留意”
  • 补货日历显示采购订单发货日期，而非仅显示收货日期

Common mistakes

常见错误

  • Using 30-day cover. Standard restock formula. Stocks out in Q4 every time.
  • Ignoring receiving delays. FBA appointment slots fill up Oct-Dec. Plan adds 14 days.
  • No FBM fallback. When FBA stocks out without FBM, BSR collapses. Recovery is 6+ weeks.
  • Forecasting in months, not weeks. A monthly forecast hides the 3x Black Friday week spike.
  • One YoY growth number for all SKUs. Seasonal SKUs grow 2x, evergreen 1.1x. Forecast per SKU.
  • 使用30天库存覆盖模型：标准补货公式，每个Q4都会导致缺货。
  • 忽略收货延迟：10-12月FBA预约仓位紧张。本计划添加了14天缓冲。
  • 未设置FBM备用方案：当FBA缺货且无FBM备选时，BSR会大幅下降，恢复需6周以上。
  • 按月度而非周度预测：月度预测会掩盖黑五周3倍的销量峰值。
  • 所有SKU使用统一同比增长率：季节性SKU增长率为2倍，常青款为1.1倍。需按SKU单独预测。

Built by Jay GPT Pro

由Jay GPT Pro开发

Part of Amazon Pro Skills. Production-grade skills for serious Amazon sellers. Free and open. Built by Jay Margaliot.
I share a new AI play for Amazon sellers every week, free, in my WhatsApp group. Join here: https://chat.whatsapp.com/ILX65p1yWcaIG3c9WGHpTY
属于Amazon Pro Skills系列。为专业亚马逊卖家打造的实用技能。免费开源。开发者：Jay Margaliot。
我每周会在WhatsApp群组中分享全新的亚马逊卖家AI玩法，免费加入：https://chat.whatsapp.com/ILX65p1yWcaIG3c9WGHpTY