Turn supplier delays into an actionable replenishment decision

A multistore footwear retailer reviews quarterly vendor performance for a core supplier (SUP-FOOT-09) that fulfilled 12 purchase orders (2,400 pairs ordered) over the last 90 days. In the ERP summary report, SUP-FOOT-09 shows an impressive 91.7% on-time delivery score (11 of 12 orders marked 'On Time'). Yet store managers complain of chronic size-run stockouts and emergency inter-store transfers. When the replenishment planner audits the underlying PO logs, the discrepancy becomes clear: on 4 of the 12 orders, the supplier emailed 48 hours before the due date to push delivery back by 6 to 9 days, and a buying coordinator updated the ERP Expected Delivery Date field to match the new promise. On two other orders, the supplier delivered on the original date but shipped only 75% of the ordered pairs, leaving 180 pairs backordered. And on the single order marked 'Late', the truck actually arrived on the promised Tuesday, but the receiving store refused the delivery because a local market holiday had closed the loading bay.

The operational decision for a procurement head and replenishment planner is how to structure supplier delivery reliability records so that changed promises, partial line availability, and merchant-caused receiving delays are separated cleanly—and translated into concrete adjustments to retail replenishment policy or supplier allocation (Shopify Help Center — Managing suppliers and purchase orders, Shopify Retail Blog — Open-to-buy (OTB) planning guide). By linking this control to retail replenishment policy parameters and customer preorder and backorder promise dates, procurement head and replenishment planner teams prevent downstream inventory and accounts-payable breaks before stock or cash moves.

Why single-date supplier scorecards distort replenishment decisions

Most retail inventory systems store a single Expected Arrival Date on a purchase order header (see Shopify's supplier and purchase-order guide). Store operations and ecommerce customer-service teams need that field to reflect the latest realistic arrival date so they can manage dock staffing and customer preorder or backorder promises. Procurement and replenishment planners, however, need the original confirmed promise date to measure whether the supplier actually honors its contracted lead time.

When one date field tries to serve both purposes, editing the ETA to help the warehouse destroys the historical baseline needed for open-to-buy (OTB) planning and safety-stock calculation. Keep these four metrics distinct on every supplier review:

First-Promise On-Time Rate (%) = (Orders Received on or before Original Confirmed Date ÷ Total Supplier-Accountable Orders) × 100

Revised-Promise ETA Accuracy (%) = (Orders Received on or before Latest Approved Revised Date ÷ Total Orders) × 100

Line Unit Fill Rate on First Receipt (%) = (Accepted Units Received on First Drop ÷ Confirmed Ordered Units) × 100

Strict First-Promise OTIF (%) = (Orders On-Time vs Original Date AND ≥ Agreed Fill Threshold AND Zero Merchant Exception ÷ Total Supplier-Accountable Orders) × 100

By separating the immutable Original Confirmed Promise Date from the operational Revised Planning ETA and attaching a mandatory reason code to every variance, procurement and planning teams stop arguing with suppliers over corrupted spreadsheets and focus on real lead-time risk.

  <path d="M219 85 L248 85" stroke="#475569" stroke-width="1.8" marker-end="url(#arrow-r005)"/>

  <rect x="248" y="40" width="195" height="90" rx="8" fill="#fef9c3" stroke="#ca8a04" stroke-width="1.5"/>
  <text x="262" y="64" font-weight="700" fill="#854d0e">2. Log Receipt & Fill</text>
  <text x="262" y="84">12 POs (2,400 pairs ordered)</text>
  <text x="262" y="102">Compare GRN vs Date 1 & Date 2</text>
  <text x="262" y="118" font-size="11" fill="#475569">Measure 1st-drop unit fill</text>

  <path d="M443 85 L472 85" stroke="#475569" stroke-width="1.8" marker-end="url(#arrow-r005)"/>

  <rect x="472" y="40" width="195" height="90" rx="8" fill="#ffedd5" stroke="#ea580c" stroke-width="1.5"/>
  <text x="486" y="64" font-weight="700" fill="#9a3412">3. Classify Exceptions</text>
  <text x="486" y="84">4 POs: Vendor rescheduled late</text>
  <text x="486" y="102">2 POs: Short-shipped (-180 u)</text>
  <text x="486" y="118" font-size="11" fill="#475569">1 PO: Store closed (Merchant)</text>

  <path d="M667 85 L696 85" stroke="#475569" stroke-width="1.8" marker-end="url(#arrow-r005)"/>

  <rect x="696" y="40" width="200" height="90" rx="8" fill="#dcfce7" stroke="#16a34a" stroke-width="1.5"/>
  <text x="710" y="64" font-weight="700" fill="#166534">4. Trigger Action</text>
  <text x="710" y="84">True Vendor OTIF: 5/11 (45.5%)</text>
  <text x="710" y="102">Raise safety stock (+4 days LT)</text>
  <text x="710" y="118" font-size="11" fill="#475569">Fix store holiday calendar</text>

  <rect x="24" y="166" width="872" height="164" rx="8" fill="#ffffff" stroke="#cbd5e1" stroke-width="1.2"/>
  <text x="44" y="194" font-weight="700" font-size="13" fill="#0f172a">Governance rule: Updating an operational ETA never overwrites the original confirmed promise baseline</text>
  <text x="44" y="220" fill="#334155">• Gate A: Dual-date lock freezes Original Confirmed Promise Date at PO confirmation; only buyer-initiated deferments can re-anchor it.</text>
  <text x="44" y="246" fill="#334155">• Gate B: Reason-code audit separates supplier-caused delays and short shipments from merchant dock refusals and late GRN data entry.</text>
  <text x="44" y="272" fill="#334155">• Gate C: Replenishment feedback maps verified supplier lead-time mean and variance directly to reorder-point and OTB rules.</text>
  <text x="44" y="302" font-weight="600" fill="#0369a1">Outcome: Apparent 91.7% on-time score is revealed as 45.5% strict vendor OTIF (5 of 11 vendor-accountable POs), triggering a 4-day lead-time buffer update.</text>
</g>
<defs>
  <marker id="arrow-r005" viewBox="0 0 10 10" refX="8" refY="5" markerWidth="6" markerHeight="6" orient="auto-start-reverse">
    <path d="M 0 0 L 10 5 L 0 10 z" fill="#475569"/>
  </marker>
</defs>

Worked illustrative example: auditing 12 footwear purchase orders across two date baselines

Illustrative example (hypothetical scenario): Examine the 90-day quarterly review for footwear supplier SUP-FOOT-09 across 12 confirmed purchase orders (200 pairs per order = 2,400 pairs total ordered at ₹900 net landed cost per pair, total commitment ₹21,60,000). Contracted supplier lead time is 14 calendar days from PO confirmation, and the agreed line fill threshold for In-Full is ≥95% on first delivery (≥190 pairs per 200-pair PO).

Step 1: Establish the baseline operational and commercial parameters

• Cohort A (5 orders: PO-01, PO-02, PO-05, PO-08, PO-11 — Clean OTIF):
  • Delivered on or before Day 14 (Original Confirmed Date) with 100% fill (5 × 200 = 1,000 pairs received).
• Cohort B (4 orders: PO-03, PO-06, PO-09, PO-12 — Supplier Late Reschedules):
  • Supplier emailed before Day 14 to push delivery to Day 20, Day 21, Day 22, and Day 21 respectively (average delay +7.0 days, actual lead time 21.0 days). All 4 orders arrived on their revised ETA with 100% fill (4 × 200 = 800 pairs received). Because the coordinator overwrote the single ERP date field, the legacy report scored all 4 as 'On Time'.
• Cohort C (2 orders: PO-04, PO-10 — Supplier Partial / Short Shipments):
  • Arrived on Day 14 (On Time), but PO-04 delivered 150 of 200 pairs (-50 pairs) and PO-10 delivered 70 of 200 pairs (-130 pairs), for 220 pairs received out of 400 ordered (180 pairs short-shipped, or 55.0% first-drop fill rate).
• Cohort D (1 order: PO-07 — Store Dock Refusal on Local Holiday):
  • Carrier arrived at the store dock on Day 14 with all 200 pairs, backed by GPS and gate-log proof, but the store was closed for a municipal market shutdown. Redelivery occurred on Day 16 (200 pairs received).

Step 2: Reconcile packs, exceptions, and financial commitment

1. Remove the merchant-caused exception (PO-07) from the supplier fault denominator:
   • Out of 12 total orders, PO-07 was ready at the dock on Day 14 (200 pairs) and delayed solely by MER-DOCK-REFUSED. This leaves 11 supplier-accountable orders (2,200 pairs)—or if PO-07 is credited as supplier on-time and in-full at first tender, 6 of 12 orders (50.0%). Using the 11 supplier-accountable orders denominator:
2. Calculate separated performance metrics vs the corrupted legacy report:
   • Legacy overwritten report ('On Time vs Latest ETA'): 11 ÷ 12 = 91.67% (falsely scoring the 4 rescheduled orders and 2 partial orders as successes, while blaming the vendor for PO-07).
   • First-Promise On-Time Delivery Rate (Supplier Accountable): 7 on-time arrivals (5 in Cohort A + 2 in Cohort C) ÷ 11 supplier-accountable orders = 63.64% (with 4 orders in Cohort B late by an average of +7.0 days).
   • Revised-ETA Planning Accuracy: Once Cohort B orders were rescheduled, 4 ÷ 4 = 100.0% arrived on their revised ETA—useful to know that the supplier's second notice is reliable for dock scheduling, even though primary lead time failed.
   • First-Drop Unit Fill Rate (Supplier Accountable): (1,000 + 800 + 220) ÷ 2,200 ordered pairs = 2,020 ÷ 2,200 = 91.82% (or 2,220 ÷ 2,400 = 92.50% across all 12 POs), with 180 pairs (₹1,62,000 at cost) missing on first receipt.
   • Strict First-Promise OTIF (Supplier Accountable): Only the 5 orders in Cohort A were both on time against the original Day 14 promise and ≥95% in full: 5 ÷ 11 = 45.45% (or 6 ÷ 12 = 50.00% when PO-07 is credited as tendered OTIF).
3. Translate the decomposed scorecard into a replenishment parameter update:
   • Across the 11 supplier-accountable orders, weighted-average actual lead time was ((7 orders × 14 days) + (4 orders × 21 days)) ÷ 11 = (98 + 84) ÷ 11 = 182 ÷ 11 = 16.55 days (with a 90th-percentile lead time of 21 days). Leaving the ERP reorder calculation at 14 days guarantees a stockout on 36.36% (4 ÷ 11) of replenishment cycles.

Decomposing the 12 orders changes the operational response completely: instead of assuming SUP-FOOT-09 is a 91.67% reliable vendor, the planner updates the supplier's planning lead time from 14 days to 18 days (or adds a 4-day safety-stock buffer on core sizes), sets an automatic cancellation rule for unshipped backorder balances older than 7 days to free ₹1,62,000 of trapped OTB, and fixes the store receiving calendar so holiday closures are blocked at PO creation.

Workflow for turning delivery variance logs into buying actions

To connect supplier delivery tracking directly to replenishment and buying decisions, run a monthly four-step review:

1. Freeze Original Confirmed Promise Date upon order acceptance (Owner: Procurement Operations). When the supplier confirms the PO, lock the original due date and ordered line quantities. Allow operational coordinators to update Revised Expected Arrival Date (ETA) as often as needed for warehouse scheduling and customer backorder promises, provided every ETA edit logs a reason code.
2. Reconcile first-drop receipt lines against both dates within 24 hours of GRN (Owner: Receiving Lead + Inventory Analyst). Compare the physical GRN timestamp and accepted quantities against both the original promise and the latest ETA. If a delivery was refused at the gate or delayed by late data entry, attach the gate log and tag Merchant / Admin Cause so the vendor scorecard remains factual.
3. Segment supplier failures by operational mechanism (Owner: Category Buyer + Replenishment Planner). Distinguish between consistent lead-time drift (supplier always takes 21 days instead of 14, but ships 100% in full) and fill-rate attrition (supplier arrives on Day 14 but short-ships 25% of units). Lead-time drift is solved by updating the lead-time parameter in your retail replenishment policy; chronic short-shipping requires MOQ/allocation renegotiation or secondary sourcing.
4. Assign one time-bound corrective action per underperforming vendor (Owner: Procurement Head). Record the agreed action—such as revising ERP lead time from 14 to 18 days, requiring 72-hour pre-dispatch packing lists, or reallocating 30% of category OTB to a backup vendor—with a 60-day review date.

Choosing the right reporting approach: Start with a transparent two-date exception report extracted from your existing PO and GRN logs before building predictive lead-time models. Automated lead-time forecasting only adds value after Original Promise Date, Revised ETA, and Merchant vs Supplier Reason Codes are captured cleanly without manual overwrites.

Observable acceptance tests for your retail systems

Before relying on this workflow in production, execute three deterministic acceptance tests (ACT-R005-01 to ACT-R005-03) in your staging environment or controlled worksheet:

Starting a two-date supplier reliability review in your category

To turn noisy delivery complaints into an objective replenishment and vendor-management decision:

1. Audit your last 50 closed purchase orders in one high-stockout category and check whether your system retained the first confirmed promise date whenever an arrival ETA was pushed out.
2. Add Original Confirmed Promise Date and Delay Reason Code fields to your purchase-order log so warehouse teams can update live ETAs without erasing the supplier's baseline commitment.
3. Separate lead-time drift from short-shipment fill loss in your monthly buying review, updating ERP replenishment lead times for consistently slower vendors while cancelling aged backorder tails to free up open-to-buy budget.
4. Run acceptance tests ACT-R005-01 to ACT-R005-03 before your next quarterly vendor business review so every scorecard number traces to verified receipt and gate evidence.