theonline.mba
← Back to unit 1: Supply-Chain Foundations

OPS 202 · Unit 1 · Lesson 2 of 5

Supply-Chain Flows

Supply-Chain Foundations

Lesson

The ASN that never arrived

Reno DC planners saw zero on-hand for a fast-moving midlayer, but Carlos knew two containers were en route. The ASN (advance ship notice) sat in a supplier portal nobody monitored on weekends. Picking stopped, DTC promises slipped, and marketing paused ads on a hero SKU. The material existed; the information flow failed.

Supply-chain flows describe how product, data, and money move through nodes. Atlas managers who master flows diagnose stockouts that are really visibility problems and cash crunches that are really payment-term design problems.

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.

Material flow and pipeline inventory

Pipeline inventory is product not yet available to sell: in factory WIP (work in progress), on ocean, in customs, or in transit between DCs. Atlas carries roughly $25M in pipeline at peak. Planners who ignore pipeline double-order or cancel marketing prematurely.

Material flow speed depends on mode (ocean vs air), consolidation rules, and DC receiving capacity. Carlos caps weekly container receipts in Reno to protect putaway labor.

Information flow and event milestones

Critical events: PO acceptance, ex-factory, vessel departure, customs release, DC receipt, available-to-promise update. Each event should have an owner and SLA (service level agreement). Latency between physical movement and system update creates phantom stockouts.

Atlas targets 24-hour ASN posting from ex-factory for Tier-1 suppliers. Priya ties contract compliance to scorecards.

EventSystem recordDecision enabled
Ex-factoryASN + qtyUpdate ATP (available-to-promise)
Vessel departureContainer IDIn-transit inventory
Customs filedEntry numberDuty accrual
DC receiptGRN (goods receipt)Nettable on-hand

Cash flow and working capital

Suppliers often require deposit at PO, balance at ex-factory. Atlas pays ocean freight and duty before selling. Cash-to-cash cycle links material and cash flows. Finance wants lower inventory; sales wants higher service; sourcing negotiates terms that affect both.

Mei Lin presents flow diagrams with dollar days in pipeline, not only unit days, so the CFO sees tradeoffs.

Linking flows to customer promises

DTC two-day promise requires nettable inventory in Reno plus cut-off times. Wholesale in-full requires case integrity and label compliance before appointment. The same SKU may have different available quantities by channel depending on allocation rules.

Flow design asks where to hold inventory so both promises are feasible without duplicate safety stock everywhere.


Worked example: Supply-Chain Flows at Atlas Outdoor Gear

Scenario: COO Mei Lin, Logistics Director Carlos Ruiz, and Sourcing VP Priya Shah must apply information flow repair for midlayer SKU 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: Flow state table

LocationUnitsNettable?Source
Reno on-hand0YesERP
In transit ocean18,400No (no ASN)Missing
Vietnam factory6,000NoSupplier portal

After ASN fix: in-transit becomes visible; ATP shows Aug 9 customer ship.

Part B: Revenue at risk

DTC daily run rate: 620 units × $89 = $55.2K/day. Three-day promise miss ≈ $166K retail plus ad waste $22K. Fix cost: weekend monitoring rotation $4K + EDI (electronic data interchange) upgrade $35K one-time.

Part D: Managerial read

Fund EDI if expected phantom stockouts exceed $200K/year. Treat information flow as part of service design, not IT optional.


Worked example: Cash and material on one timeline

Draw one timeline for a PO: deposit out, production days, ex-factory cash, ocean days, sale, collection. Atlas finance uses this to size a revolving facility. Students should add payment terms to any flow map they build.


Common mistakes beginners make

MistakeReality
Equating on-hand with available inventoryPipeline and allocations change what you can promise
ASNs as paperwork onlyThey drive ATP and customer commits
Optimizing unit lead time ignoring cashWorking capital limits growth at Atlas scale
Single ERP view for all channelsWholesale and DTC allocation rules differ
No event ownerMilestones slip when everyone assumes someone else watches

Practice problem

Container holds 12,000 units; 8,000 pre-allocated to wholesale, 4,000 free for DTC. Reno shows 0 on-hand; ASN missing. DTC run rate 400/day. How many days of DTC sales are at risk if ASN delay is 5 days? What is the first operational fix?

Solution

At risk: 5 days × 400 = 2,000 units ($178K at $89). Wholesale allocation is not nettable until receipt anyway. First fix: post ASN and in-transit inventory; second, temporary DTC cap on ads; third, EDI enforcement on supplier. Check: 2,000 ≤ 4,000 DTC pool in container ✓.

Key takeaways

  • Pipeline inventory is real capital even if not nettable
  • Information latency causes avoidable stockouts
  • Cash flow timing belongs on the same map as material
  • Channel allocation rules define available-to-promise
  • Event owners and SLAs beat heroic weekend email

After this lesson

  1. Re-read the worked examples and verify every check line in your OPS 202 workbook.
  2. Apply one concept from Supply-Chain Flows to a real SKU or supplier decision at your organization.
  3. Preview Push, Pull, and Postponement and note which Atlas metrics should feed the next analysis.

Applying Supply-Chain Flows at Atlas scale

When Atlas Outdoor Gear evaluates supply-chain flows, 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 supply-chain foundations and end-to-end flow design 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 supply-chain flows 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 supply-chain foundations and end-to-end flow design 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 supply-chain flows. 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 supply-chain foundations and end-to-end flow design 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. Supply-Chain Flows 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 supply-chain flows, 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 supply-chain flows 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 Supply-Chain Flows to resilience and global exposure

Supply chains fail at interfaces: supplier to factory, factory to port, port to DC, DC to customer. Supply-Chain Flows 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 supply-chain flows 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 supply-chain foundations and end-to-end flow design 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 supply-chain flows, 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.

Applying Supply-Chain Flows at Atlas scale

When Atlas Outdoor Gear evaluates supply-chain flows, 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 supply-chain foundations and end-to-end flow design 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 supply-chain flows 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 supply-chain foundations and end-to-end flow design 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.

Lesson exercise

30 min

ASN and ATP fix memo

1. Complete pipeline vs on-hand practice cold. 2. Document material, information, cash events for one PO. 3. Propose ASN/EDI fix with cost and owner. 4. Define ATP rule for DTC vs wholesale on shared SKU.

Deliverable

Flow timeline + ATP rules table.

Rubric

  • Three flows represented
  • ATP distinguishes allocations
  • ASN latency cost estimated
  • Owner assigned