Reorder Points

We ordered when the shelf was empty

A planner triggered POs when nettable hit zero, ignoring 14-week factory lead time. Reorder point (ROP) = expected demand during lead time plus safety stock. Ordering at zero guarantees stockouts.

Atlas Outdoor Gear is a direct-to-consumer (DTC) and wholesale outdoor apparel brand with global sourcing and the anchor company for OPS 202. Latest annual revenue is approximately $165M across 55% DTC and 45% wholesale, with roughly 2,400 active SKUs and 14-week average production lead time from purchase order release to ex-factory. COO Mei Lin, Logistics Director Carlos Ruiz, and Sourcing VP Priya Shah manage cut-and-sew in Vietnam and Bangladesh, trims in Taiwan, nearshore basics in Guatemala, fulfillment from Reno, Nevada (West DTC and wholesale) and Columbus, Ohio (East wholesale and overflow), and ocean FCL (full container load) from Asia, domestic LTL (less-than-truckload) to wholesale accounts, parcel carriers for DTC.

You met Atlas process fundamentals in OPS 201 (Operations and Process Management) process and capacity work on Atlas fulfillment lines. This course adds the supply network layer: how to design flows from supplier to customer, plan inventory under uncertainty, source ethically at scale, run logistics networks, manage global exposure, and build resilience when ports, weather, or demand surprise you.

ROP formula and continuous review

ROP = d × L + SS where d is demand rate and L is lead time. Continuous review triggers PO when inventory position (on-hand + on-order - allocations) ≤ ROP.

Inventory position versus on-hand

On-hand 5,000 with 20,000 on order looks healthy, but 22,000 allocated to wholesale leaves position 3,000 below ROP. Atlas ERP must show position, not only on-hand.

Periodic review alternative

Weekly S&OP review sets order-up-to levels for slow movers. Fast movers use ROP; C SKUs use periodic to reduce transaction costs.

Lead time clock start

Define whether L starts at PO release, supplier acceptance, or ex-factory. Misaligned clocks shift ROP by weeks.

Scenario: COO Mei Lin, Logistics Director Carlos Ruiz, and Sourcing VP Priya Shah must apply ROP for TrailShell sizes this quarter. Wholesale partners want higher fill rates before Q3 pre-fall wholesale bookings and Q4 holiday DTC; DTC marketing is scaling spend on hero jackets; finance caps inventory near $36M at cost.

Part A: ROP calc

d = 2,800/wk; L = 12 wks; SS = 6,500.

ROP = 2,800×12 + 6,500 = 40,100 units.

Check: demand during LT = 33,600 + SS 6,500 = 40,100 ✓

Part B: Trigger decision

Position 38,200 → below ROP → release PO 18,000 (container multiple). Next review in 3 days.

Part D: Managerial read

Do not wait for zero; position-based triggers protect 14-week pipeline.

Wholesale allocation reduces nettable for DTC. Atlas runs channel-specific ROP views on shared SKUs to avoid silent DTC starvation.

d=500/day, L=21 days, SS=4,000. ROP? If position=14,200, order?

Solution

Demand in LT = 500×21 = 10,500. ROP = 10,500+4,000 = 14,500. Position 14,200 < 14,500 → order now.

If on-hand 14,200 but allocated 2,000, position? Still order?

Solution

Position = 14,200 - 2,000 = 12,200 (assuming no on-order). 12,200 < 14,500 → urgent order; allocation worsened gap.

Key takeaways

• ROP covers lead time demand plus safety stock
• Inventory position includes on-order and allocations
• Match review policy to SKU velocity
• Lead time definition must match supplier contract clock
• Channel views prevent allocation blind spots

1. Re-read the worked examples and verify every check line in your OPS 202 workbook.
2. Apply one concept from Reorder Points to a real SKU or supplier decision at your organization.
3. Preview Service Levels and note which Atlas metrics should feed the next analysis.

Applying Reorder Points at Atlas scale

When Atlas Outdoor Gear evaluates reorder points, the team starts from operational facts: $165M revenue, 2,400 SKUs, 14-week average factory lead time, and inventory near $36M at cost on the balance sheet. COO Mei Lin, Logistics Director Carlos Ruiz, and Sourcing VP Priya Shah align inventory planning, safety stock, and S&OP (sales and operations planning) with weekly S&OP cadence, monthly supplier scorecards, and quarterly network reviews. A lesson concept that sounds abstract becomes concrete when tied to purchase order releases, container milestones, and fill-rate dashboards.

Consider how a one-point change in wholesale fill rate affects Atlas. At 45% wholesale mix, a missed key-account delivery can trigger chargebacks and lost floor space for the next season. DTC promises two-day shipping on core sizes; a stockout on hero SKUs shows up in marketing return on ad spend within days. That is why reorder points is not an academic exercise for Mei Lin's operations org; it is how the company protects margin while scaling technical shells, midlayers, base layers, packs, and accessories.

The inventory planning, safety stock, and S&OP (sales and operations planning) workflow at Atlas deliberately separates structural decisions from firefighting. Priya Shah's sourcing team labels supplier risk tiers before PO placement. Carlos Ruiz's logistics team tracks in-transit positions separately from on-hand DC inventory. Mei Lin's S&OP forum forces sales, finance, and operations to reconcile demand plans before factories commit capacity. You should copy that separation habit: name the decision owner, the time horizon, and the metric that proves success before approving spend.

Document definitions alongside every KPI tile. Atlas fill rate specifies eligible lines, cancellation rules, and partial-shipment handling. Inventory turns use average cost inventory and cost of goods sold aligned to fiscal calendar. Lead time clocks start at PO acceptance, not email request. When definitions live in a shared dictionary, the company builds institutional memory instead of re-debating the same report every quarter.

Extended Atlas scenario: cross-functional read

Imagine Atlas's Q3 pre-fall wholesale bookings and Q4 holiday DTC review for reorder points. Finance asks whether expedited air freight on delayed containers is worth the margin hit. Merchandising asks whether to cancel a colorway or chase late units for wholesale commitments. IT asks whether a visibility pilot on Tier-1 suppliers should expand before peak. A weak inventory planning, safety stock, and S&OP (sales and operations planning) answer addresses only one function. A strong answer shows how evidence flows: supplier OTIF (on-time in-full) data explains root cause, inventory simulation quantifies service impact, and network options compare cost versus customer promise.

Work the arithmetic on a conservative example. Suppose Atlas sells roughly $37K at retail value per week across channels. A two-week delay on a container holding $420K at cost on high-velocity fleece SKUs could defer roughly $680K retail sales if substitutes are weak. Expedited split shipment might recover half the lost sales at $95K incremental freight and $18K handling. Mei Lin should compare recovered gross margin to expedite cost, not treat freight as purely operational overhead.

Stakeholder conflict is normal. Priya may push to dual-source a factory to reduce risk. Carlos may resist opening a third DC without volume proof. Wholesale sales may demand 98% fill while finance caps inventory at $36M. Reorder Points gives you language to negotiate those tensions with explicit service-cost tradeoffs rather than charisma. If data is incomplete, the decision is invest in visibility or accept uncertainty, not pretend last year's average lead time still holds.

Translate lessons to your own context by replacing Atlas names while keeping structure. Pick one supply decision you face this quarter. Write the customer promise, supplier constraint, inventory implication, and cash impact before approving a PO or network change. If you cannot write those elements, you are not ready to commit capacity regardless of how urgent the email thread feels.

Technical mechanics and checks (worked patterns)

For reorder points, Atlas analysts show work the way finance shows reconciliations. An inventory table prints SKU, on-hand units, average weekly demand, weeks of cover, and a check that extended value equals units times standard cost within rounding. A logistics lane table multiplies transit days, handling days, and order frequency to reconcile total pipeline days to supplier scorecard definitions. A sourcing TCO (total cost of ownership) table sums unit cost, freight, duty, quality fallout, and payment terms into comparable dollars per unit.

Use plain-language decision statements before formulas. Example for safety stock: Atlas targets 96% fill on A SKUs; demand standard deviation over lead time drives buffer size. Still verify seasonality with year-over-year sell-through and document concurrent promotions that could inflate short-term demand. Spreadsheet or ERP replication should state grain first: SKU-location-week for inventory, container-shipment for in-transit, supplier-style for sourcing scorecards.

Common executive questions (and disciplined answers)

Executives ask short questions that require long disciplined answers. "How sure are we on delivery?" maps to OTIF distributions and confidence intervals on lead time, not vendor promises. "What is the dollar impact?" maps to lost margin from stockouts plus expedite cost minus recovery options. "Can we add SKUs?" maps to complexity cost in planning, picking, and supplier minimums. "Why not nearshore everything?" maps to unit economics, capacity, and product quality evidence, not slogans.

Atlas's credible answer format for reorder points is three bullets: recommendation, evidence strength (structural data versus anecdote), and next instrumentation step if uncertainty remains. A fourth bullet lists what would falsify the recommendation within sixty days. That discipline prevents the supply chain team from becoming either a bottleneck or a rubber stamp.

Linking Reorder Points to resilience and global exposure

Supply chains fail at interfaces: supplier to factory, factory to port, port to DC, DC to customer. Reorder Points at Atlas must be read alongside global trade and risk lessons later in OPS 202. A sourcing decision that ignores duty exposure or single-port dependence can look efficient on a spreadsheet until a weather event or policy change freezes inventory in transit.

Build a simple interface register for your own organization: node, owner, metric, escalation trigger. Atlas maintains one for Tier-1 cut-and-sew, ocean booking, customs clearance, and wholesale appointment scheduling. When reorder points improves one node, update the register and test downstream capacity. Local optimization without system view recreates the bullwhip effect Mei Lin warns about in S&OP.

Practice extension: workbook discipline

Carlos Ruiz requires every inventory planning, safety stock, and S&OP (sales and operations planning) recommendation to include a one-page workbook tab with four rows: baseline metric, proposed change, reconciliation check, and owner plus review date. Students should mirror that format even when homework uses simplified numbers. The habit trains you to catch unit errors (cartons versus units) and definition drift (calendar days versus business days) before they reach a CFO review.

For reorder points, add a fifth row: assumption you would monitor weekly if the recommendation is approved. Atlas examples use in-transit counts, supplier OTIF, DC pick rates, or wholesale cancel rates depending on lesson topic. If you cannot name a weekly monitor, the proposal is not operationalized.

Technical drill: Reorder Points formulas and checks at Atlas

Work the numbers the way Mei Lin expects in S&OP review. State inputs in blue, formulas in black, outputs in green if you replicate in Excel. For inventory lessons, grain is SKU-location-week; for logistics, shipment-container-day. Never mix cartons and eaches without a conversion row.

Example reconciliation habit: after computing safety stock or ROP, compare to last week's planner override and document why model and judgment differ. Overrides are allowed but must be labeled; silent overrides destroy trust in the planning system.

Atlas planners maintain a model vs override log for A SKUs during peak. If override frequency exceeds 30% of lines, the issue is data or formula, not "planner error." Fix definitions before blaming operators.

Spreadsheet replication steps (Reorder Points)

1. Export twelve weeks of demand for one Atlas hero SKU in Reno.
2. Compute mean, standard deviation, and seasonality index by week-of-year.
3. Apply lesson formula with documented z, L, and SS policy by segment.
4. Print inventory position including on-order and wholesale allocations.
5. Add check row: beginning + receipts − shipments = ending within 0.5%.

If check fails, stop. Mei Lin rejects models that do not reconcile when finance can recompute two cells independently.

Sensitivity table template

Run low/base/high before approving PO changes. Atlas requires sensitivity on any request that increases inventory >$250K at cost.

Integration with Atlas S&OP cadence

Reorder Points outputs feed the monthly S&OP pack: one slide on service impact, one on inventory dollars, one on freight or capacity implications. Carlos adds logistics constraints; Priya adds supplier OTIF and capacity; finance adds cash and turns guardrails.

Without integration, reorder points stays a classroom exercise. With integration, it becomes the language Mei Lin uses to deny or approve promos, air freight, and wholesale allocations in the same meeting.

Applying Reorder Points at Atlas scale

When Atlas Outdoor Gear evaluates reorder points, the team starts from operational facts: $165M revenue, 2,400 SKUs, 14-week average factory lead time, and inventory near $36M at cost on the balance sheet. COO Mei Lin, Logistics Director Carlos Ruiz, and Sourcing VP Priya Shah align inventory planning, safety stock, and S&OP (sales and operations planning) with weekly S&OP cadence, monthly supplier scorecards, and quarterly network reviews. A lesson concept that sounds abstract becomes concrete when tied to purchase order releases, container milestones, and fill-rate dashboards.

Consider how a one-point change in wholesale fill rate affects Atlas. At 45% wholesale mix, a missed key-account delivery can trigger chargebacks and lost floor space for the next season. DTC promises two-day shipping on core sizes; a stockout on hero SKUs shows up in marketing return on ad spend within days. That is why reorder points is not an academic exercise for Mei Lin's operations org; it is how the company protects margin while scaling technical shells, midlayers, base layers, packs, and accessories.

The inventory planning, safety stock, and S&OP (sales and operations planning) workflow at Atlas deliberately separates structural decisions from firefighting. Priya Shah's sourcing team labels supplier risk tiers before PO placement. Carlos Ruiz's logistics team tracks in-transit positions separately from on-hand DC inventory. Mei Lin's S&OP forum forces sales, finance, and operations to reconcile demand plans before factories commit capacity. You should copy that separation habit: name the decision owner, the time horizon, and the metric that proves success before approving spend.

Document definitions alongside every KPI tile. Atlas fill rate specifies eligible lines, cancellation rules, and partial-shipment handling. Inventory turns use average cost inventory and cost of goods sold aligned to fiscal calendar. Lead time clocks start at PO acceptance, not email request. When definitions live in a shared dictionary, the company builds institutional memory instead of re-debating the same report every quarter.

Extended Atlas scenario: cross-functional read

Imagine Atlas's Q3 pre-fall wholesale bookings and Q4 holiday DTC review for reorder points. Finance asks whether expedited air freight on delayed containers is worth the margin hit. Merchandising asks whether to cancel a colorway or chase late units for wholesale commitments. IT asks whether a visibility pilot on Tier-1 suppliers should expand before peak. A weak inventory planning, safety stock, and S&OP (sales and operations planning) answer addresses only one function. A strong answer shows how evidence flows: supplier OTIF (on-time in-full) data explains root cause, inventory simulation quantifies service impact, and network options compare cost versus customer promise.

Work the arithmetic on a conservative example. Suppose Atlas sells roughly $37K at retail value per week across channels. A two-week delay on a container holding $420K at cost on high-velocity fleece SKUs could defer roughly $680K retail sales if substitutes are weak. Expedited split shipment might recover half the lost sales at $95K incremental freight and $18K handling. Mei Lin should compare recovered gross margin to expedite cost, not treat freight as purely operational overhead.

Stakeholder conflict is normal. Priya may push to dual-source a factory to reduce risk. Carlos may resist opening a third DC without volume proof. Wholesale sales may demand 98% fill while finance caps inventory at $36M. Reorder Points gives you language to negotiate those tensions with explicit service-cost tradeoffs rather than charisma. If data is incomplete, the decision is invest in visibility or accept uncertainty, not pretend last year's average lead time still holds.

Translate lessons to your own context by replacing Atlas names while keeping structure. Pick one supply decision you face this quarter. Write the customer promise, supplier constraint, inventory implication, and cash impact before approving a PO or network change. If you cannot write those elements, you are not ready to commit capacity regardless of how urgent the email thread feels.

Technical mechanics and checks (worked patterns)

For reorder points, Atlas analysts show work the way finance shows reconciliations. An inventory table prints SKU, on-hand units, average weekly demand, weeks of cover, and a check that extended value equals units times standard cost within rounding. A logistics lane table multiplies transit days, handling days, and order frequency to reconcile total pipeline days to supplier scorecard definitions. A sourcing TCO (total cost of ownership) table sums unit cost, freight, duty, quality fallout, and payment terms into comparable dollars per unit.

Use plain-language decision statements before formulas. Example for safety stock: Atlas targets 96% fill on A SKUs; demand standard deviation over lead time drives buffer size. Still verify seasonality with year-over-year sell-through and document concurrent promotions that could inflate short-term demand. Spreadsheet or ERP replication should state grain first: SKU-location-week for inventory, container-shipment for in-transit, supplier-style for sourcing scorecards.

Common executive questions (and disciplined answers)

Executives ask short questions that require long disciplined answers. "How sure are we on delivery?" maps to OTIF distributions and confidence intervals on lead time, not vendor promises. "What is the dollar impact?" maps to lost margin from stockouts plus expedite cost minus recovery options. "Can we add SKUs?" maps to complexity cost in planning, picking, and supplier minimums. "Why not nearshore everything?" maps to unit economics, capacity, and product quality evidence, not slogans.

Atlas's credible answer format for reorder points is three bullets: recommendation, evidence strength (structural data versus anecdote), and next instrumentation step if uncertainty remains. A fourth bullet lists what would falsify the recommendation within sixty days. That discipline prevents the supply chain team from becoming either a bottleneck or a rubber stamp.

Linking Reorder Points to resilience and global exposure

Supply chains fail at interfaces: supplier to factory, factory to port, port to DC, DC to customer. Reorder Points at Atlas must be read alongside global trade and risk lessons later in OPS 202. A sourcing decision that ignores duty exposure or single-port dependence can look efficient on a spreadsheet until a weather event or policy change freezes inventory in transit.

Build a simple interface register for your own organization: node, owner, metric, escalation trigger. Atlas maintains one for Tier-1 cut-and-sew, ocean booking, customs clearance, and wholesale appointment scheduling. When reorder points improves one node, update the register and test downstream capacity. Local optimization without system view recreates the bullwhip effect Mei Lin warns about in S&OP.

Practice extension: workbook discipline

Carlos Ruiz requires every inventory planning, safety stock, and S&OP (sales and operations planning) recommendation to include a one-page workbook tab with four rows: baseline metric, proposed change, reconciliation check, and owner plus review date. Students should mirror that format even when homework uses simplified numbers. The habit trains you to catch unit errors (cartons versus units) and definition drift (calendar days versus business days) before they reach a CFO review.

For reorder points, add a fifth row: assumption you would monitor weekly if the recommendation is approved. Atlas examples use in-transit counts, supplier OTIF, DC pick rates, or wholesale cancel rates depending on lesson topic. If you cannot name a weekly monitor, the proposal is not operationalized.

Technical drill: Reorder Points formulas and checks at Atlas

Work the numbers the way Mei Lin expects in S&OP review. State inputs in blue, formulas in black, outputs in green if you replicate in Excel. For inventory lessons, grain is SKU-location-week; for logistics, shipment-container-day. Never mix cartons and eaches without a conversion row.

Example reconciliation habit: after computing safety stock or ROP, compare to last week's planner override and document why model and judgment differ. Overrides are allowed but must be labeled; silent overrides destroy trust in the planning system.

Atlas planners maintain a model vs override log for A SKUs during peak. If override frequency exceeds 30% of lines, the issue is data or formula, not "planner error." Fix definitions before blaming operators.