Confirm the Supplier Bottleneck Before You Switch
A repeating symptom can start in five places; only one is the supplier.
| Failure signal | Likely control point | Evidence that settles it | Where it is covered |
|---|---|---|---|
| Dispatch dates slip | Supplier scheduling | Confirmed vs. actual dispatch | This page |
| Units fail vs. sample | Quality or process | Inspection record, defect class | Quality control guide |
| Packaging mixed, wrong or damaged | Spec ownership, not supplier alone | Approved vs. pack-out | This page — specification lock |
| Stock or handoff breaks down | Fulfillment or 3PL handoff | Receiving record, stock ledger | Fulfillment and 3PL guide |
| Transit or tracking unstable | Route or carrier design | Tracking events, from label creation to first scan | Shipping routes guide |
Two rows pointing at different control points are two problems. If tracking is the signal, compare shipping routes from China.
Choose the Lane: Fix, Verify, Parallel-Test or Replace
Once you have named the lane, record the decision in writing.
- FIXIf the cause is your specification or packaging brief, fix the standard first.
- VERIFYIf the cause is the supplier but no alternative is confirmed, verify one first.
- PARALLELIf the replacement is verified but unproven, run a covering cohort.
- CUT OVERIf parallel results hold and responsibility has transferred in writing, move in stages.
- ROLLBACKIf evidence is refused or a stage produces no record, reverse.
Want the ASG team to check this step for your store?
Freeze the Product, Packaging and Acceptance Standard Before Comparison
A candidate is only comparable against a standard that isn't moving. Record the freeze as a SKU specification lock.
Lock 01 · ProductProduct specification
Freeze the approved sample, materials and tolerances, and have the freeze signed.
Lock 02 · PackagingPackaging approval
Use the approved file and matching pack-out photo.
Lock 03 · AcceptanceQuality acceptance
Apply the same criteria when you run a pre-shipment QC checklist.
Lock 04 · ChangeChange control
Log every post-freeze change on both routes.
Verify a Replacement Without Duplicating Supplier Vetting
before
volume
Before a candidate reaches a parallel test, verify a replacement supplier through identity, capability and a first-article sample — a sales deck verifies nothing.
- Record
Identity
Who the candidate is.
- Site
Capability
What it can make now.
- Sample
First-article sample
This SKU, this standard.


Build the Open-Order, Inventory and Responsibility Cutover Map
Before a single order moves, build an open-order ledger naming the inventory and the overlap owner.
| Item crossing freeze date | Owner before cutover | During overlap — handling | After cutover — condition |
|---|---|---|---|
| Orders placed before freeze | Current supplier | Tracked separately | Through delivery |
| In-transit inventory, safety stock | Supplier and route | Both routes, one ledger | Named in handoff |
| Reorder points, replenishment timing | Current supplier | Route owning SKU group | Once proven |
| Returns, after-sales on earlier orders | Current supplier | Regardless of route | Until closed |
| Product, packaging data files | Supplier's version | Both, checked vs. standard | Once drift-checked |
Warehouse and 3PL responsibilities sit inside this ledger. Where receiving and pick-pack change hands, compare China fulfillment and 3PL responsibilities before assuming the supplier owns it.
Want the ASG team to check this step for your store?
Run Current and Candidate Routes in Parallel by Order Cohort
A parallel test shows how a candidate performs on real orders rather than in a demo.
Current route
- Frozen spec
- Approved packaging
- Existing QC
- Named owner
Candidate route
- Same spec
- Same packaging
- Same QC
- Named owner
| Control point | Current route | Candidate route |
|---|---|---|
| Specification version | Frozen standard | Same, no substitutions |
| Packaging version | Approved version | Same, matched pack-out |
| QC criteria | Existing checklist | Same, same classes |
| Evidence source | Existing records | New, same cohort |
| Exception owner | Named contact | Confirmed before cohort |
Choose the cohort by coverage, not a fixed order count: every variant, lane and known exception type — otherwise the pilot has not tested the route that carries your real volume.
Current route keeps shippingThe existing supplier carries every order outside the cohort and stays the fallback.
Candidate runs the same cohortSame spec, same packaging, same QC criteria, a named owner.
Cut over one SKU group at a timeEach stage passes a dated review before more volume moves.
Complete the Responsibility Handoff for Specifications, QC and Data
Responsibility does not move because a contract implies it; it moves only when each function is named against a date and a record.
| Function | Current route until cutover | Candidate at cutover | Evidence of transfer |
|---|---|---|---|
| Specification, change control | Maintains file | Receives same file | Signed handoff |
| Packaging version control | Maintains version | Matches version | Version plus pack-out |
| QC, disposition authority | Current defect classes | Same classes | Record, new owner |
| Inventory, order mapping | Current ledger | Reconciled data | Export naming owner |
| Exceptions, escalation | Current owner | Named before cohort | Written rule |
A function without a record has not transferred; it has only changed who answers the phone.
- Contract says the new supplier owns it
- No dated record per function
- Exceptions go to whoever answers
- Each function named against a date
- Signed handoff, version and export on file
- Written escalation rule before the cohort

Ethan Santos
James A. Blackwood
Robert F. Underwood





