What Is a Master Production Schedule for Amazon FBA?
A master production schedule is the bridge between your demand forecast and your purchase orders. Most FBA sellers operate with a loose mental model of "order more when stock gets low." An MPS replaces that guesswork with a week-by-week plan showing exactly how many units of each SKU to order, when the PO must be placed, and when inventory will arrive at Amazon.
The master production schedule originated in manufacturing (it's a core input to MRP systems), but the concept translates directly to FBA. Your "production" is your supplier's factory run plus ocean freight plus prep plus FBA inbound receiving. Each of those stages has a lead time, and the MPS maps orders against those stages so inventory arrives before you stock out, but not so early that you burn cash on holding costs or blow through storage limits.
For sellers running 50+ SKUs across multiple suppliers, a master production schedule is the difference between proactive inventory management and constant firefighting.
Master Production Schedule Formula
The core MPS calculation for each time period (typically one week):
MPS Quantity = Forecasted Demand + Safety Stock Target − Projected On-Hand − Scheduled ReceiptsIf the result is positive, you need to place an order. If negative, you have excess inventory for that period.
Variables:
- Forecasted Demand: Expected unit sales for the period (from your demand forecast)
- Safety Stock Target: Minimum buffer you want on hand at the end of each period
- Projected On-Hand: Current inventory minus expected sales in prior periods
- Scheduled Receipts: Units already on order that will arrive in this period
The order must be placed N days before the target arrival, where N equals your total lead time (supplier + freight + prep + FBA receiving).
Worked Example: 12-Week MPS for an FBA SKU
You sell a yoga mat at $34.99 ASP, averaging 180 units/week. Your total lead time from PO to FBA-available is 80 days (55 days production + 25 days ocean freight/prep/receiving). Safety stock target: 360 units (2 weeks of cover). Current on-hand: 1,200 units. No open POs.
| Week | Forecast | Projected On-Hand (Start) | Scheduled Receipts | On-Hand (End) | MPS Order? |
|---|---|---|---|---|---|
| 1 | 180 | 1,200 | 0 | 1,020 | No |
| 2 | 180 | 1,020 | 0 | 840 | No |
| 3 | 180 | 840 | 0 | 660 | No |
| 4 | 180 | 660 | 0 | 480 | No |
| 5 | 180 | 480 | 0 | 300 | Below safety stock! |
By Week 5 you drop below your 360-unit safety stock target. Since your lead time is ~11.5 weeks (80 days), you actually needed to place that PO 11 weeks before Week 5. That means the order should have been placed 6 weeks ago. This is the entire point of an MPS: it reveals timing gaps that are invisible when you only look at current inventory levels.
The MPS-driven order: place a PO for 900 units (5 weeks of demand) immediately. At $6.20 landed cost per unit, that's a $5,580 purchase order arriving around Week 12.
FBA-Specific Context for Your Master Production Schedule
Textbook MPS examples assume one factory, one warehouse, deterministic lead times. FBA breaks all three assumptions:
Multi-stage lead time stacking: Your lead time isn't just "supplier days." It's supplier production + ocean freight + customs + prep center + Amazon's replenishment cycle receiving (which can take 3-21 days). Your master production schedule has to account for the full chain, not just the manufacturer's stated lead time.
Restock limit constraints: Your MPS might say "order 2,000 units in Week 5." But Amazon's restock limits may only allow 800 inbound at that time. Your MPS has to plan around capacity, often by routing excess to AWD or a 3PL.
Seasonal compression: For Q4 sellers, the MPS planning horizon must extend through January (post-holiday returns and aged inventory). Plan production in August for arrivals in October.
Common Mistakes
1. Using stated supplier lead time instead of total lead time. Your supplier says 45 days. Your master production schedule treats 45 days as the planning lead time. But by the time you add ocean freight (25 days), prep (5 days), and FBA receiving (10 days), you're at 85 days. Plan against 45 and you're chronically understocked.
2. Building the MPS once and never updating it. An MPS is a rolling plan. Each week, demand actuals come in, supplier confirmations land, and FBA inbound timelines shift. If you build the schedule in January and never touch it, by April it's fiction. Update weekly at minimum.
3. Ignoring supplier MOQ when calculating MPS quantities. Your MPS says "order 340 units." Your supplier MOQ is 1,000. You either order 1,000 (carrying excess) or skip the order and stock out. The MPS has to be reconciled against supplier minimums during planning, not at PO time.
Related Terms
Master Production Schedule FAQ
How far out should my master production schedule go for FBA?
Plan at least 90 days out when sourcing from Asia, and 120-150 days if you sell seasonal products. Your MPS horizon must cover your longest supplier lead time plus FBA receiving time plus a safety buffer. Anything shorter and you are reacting instead of planning.
Is a master production schedule the same as a reorder calendar?
No. A reorder calendar tells you when to place orders. A master production schedule tells you how many units to order in each time period, factoring in forecasted demand, current inventory, safety stock targets, and supplier constraints. The MPS is the plan; the reorder is the action.
How does seasonality affect a master production schedule?
Seasonality compresses your planning windows. If Q4 demand is 3x your baseline, your MPS needs to front-load production orders into August and September to account for ocean freight transit, FBA receiving delays, and the risk of capacity constraints at your supplier. Waiting until October means competing with every other seller for factory capacity.
Can I run a master production schedule with a spreadsheet?
You can start there. A basic MPS spreadsheet has columns for each week, rows for each SKU, and cells showing planned order quantities. It works for 10-20 SKUs. Past that, the manual updates become error-prone and you miss cascading impacts when one supplier slips.