Concept Design

Retail & e-commerce

For retailers selling through stores, marketplaces and fulfilment partners, where a change made in one channel can leave stock or customers exposed elsewhere.

Concept Design

Withdrawing a recalled product from every sales channel

Head office can block a SKU in the ERP while a franchise, marketplace listing or third-party warehouse continues to sell or dispatch it. A listing marked inactive does not tell the recall lead what happened to orders already picked.

System landscape

Source evidence comes from affected product notice. The proposed workflow sends the decision to recall lead.

Proposed architecture

Build a crosswalk from the supplier’s affected model or batch to retail SKUs, bundles, marketplace listings and fulfilment locations. Issue channel-specific holds and collect acknowledgements separately for listings, open orders and stock on hand.

Event sequence Select a step for details
  1. Source recordsAffected product notice
  2. ProcessingExpand to offers and bundles
  3. Decision ownerRecall lead
  4. Operational outputVerified channel withdrawal

Reliability and operating controls

Leave unknown batch identity on hold for the recall lead. Take unavailable marketplace APIs through a documented manual route. Keep customer contact attempts separate from confirmed remedies.

Illustrative operating scenario

A recalled charger is sold individually and bundled under a different SKU. The store listing comes down, but the bundle remains in the warehouse pick queue until its separate hold is accepted.

Delivery boundaries

Product and quality teams decide release, recall scope and permitted substitutions. The delivery scope covers channel and fulfilment data exchange.

Expected business impact

Reduce the time it takes to confirm affected products are held across listings, open orders and distribution.

Acceptance test and handover

Run a simulated withdrawal with an unreachable channel. Trace one affected unit from the supplier notice to each offer, location and customer remedy, and report the remaining unexplained units.

Industry evidence

The ACCC asks suppliers to monitor recall effectiveness, review progress and adjust their approach. ACCC Product Safety on tracking a recall

Concept Design

Making a packaging change reach the checkout and the warehouse together

A supplier changes the case quantity or formulation. The product department updates the catalogue while the warehouse still picks the previous carton and a marketplace keeps the previous consumer description.

System landscape

Source evidence comes from supplier change notice. The proposed workflow sends the decision to product data owner.

Proposed architecture

Create a release process for the item, trade unit and listing hierarchy. Map old and new product identifiers, effective dates, pack sizes and each channel’s acceptance response. Allow old and new stock to coexist explicitly.

Event sequence Select a step for details
  1. Source recordsSupplier change notice
  2. ProcessingVersion trade-unit mappings
  3. Decision ownerProduct data owner
  4. Operational outputCoordinated channel release

Reliability and operating controls

Product and quality owners decide how the identifier rules apply. Quarantine contradictory pack information and prevent an unverified substitution from reaching a purchase order or fulfilment instruction.

Illustrative operating scenario

The old case holds twelve units and the replacement holds eight. Existing stock remains sellable under its own mapping while the next inbound delivery is received against the new trade unit.

Delivery boundaries

Product and quality teams decide release, recall scope and permitted substitutions. The delivery scope covers channel and fulfilment data exchange.

Expected business impact

Reduce mis-picks and incorrect descriptions during the period old and new packaging coexist.

Acceptance test and handover

Test mixed stock, customer returns and a channel that rejects the update. Compare ordered, picked and charged unit counts through an actual test order.

Industry evidence

GS1 sets decision rules for trade-item identification when a product or its packaging changes. GS1 GTIN Management Standard

Concept Design

Tracing supplier lots through split deliveries and repacked stock

The retailer knows which distribution centre received a lot. It may lose that connection when cartons are split, labels change or stock transfers between stores after receipt. A supplier query can then force a wider hold than the evidence supports.

System landscape

Source evidence comes from goods receipts and labels. The proposed workflow sends the decision to quality manager.

Proposed architecture

Capture receipt, break-pack, transfer and dispatch events against location and lot. Map supplier identifiers to internal stock records and retain the original label alongside any replacement.

Event sequence Select a step for details
  1. Source recordsGoods receipts and labels
  2. ProcessingRebuild split and transfer events
  3. Decision ownerQuality manager
  4. Operational outputDefensible hold list

Reliability and operating controls

Do not invent a lot when a scan is missing. Show the last confirmed location and the wider population that cannot yet be excluded. A quality manager authorises narrowing or clearing a hold.

Illustrative operating scenario

A chilled delivery is divided between two stores, then part of one delivery is transferred again. The trace includes the later transfer and isolates the cartons with unreadable labels.

Delivery boundaries

Product and quality teams decide release, recall scope and permitted substitutions. The delivery scope covers channel and fulfilment data exchange.

Expected business impact

Narrow the withdrawal boundary to locations and lots the retailer can establish from evidence.

Acceptance test and handover

Conduct a timed forward and backward trace with receiving staff. Check quantities at each split and test stock that moved during the investigation.

Industry evidence

GS1 describes how businesses establish traceability across trading partners and their internal processes. GS1 Australia on implementing traceability

GS1 documents Australian export cartons rejected after shipping marks were missing or damaged, breaking the link to certification. GS1 Australia meat-export traceability case

Discuss a workflow All case studies