Capability template for quality management
Batch distribution trace
When the quality lead needs to know where one production batch went, they get a map from the batch record to every recorded shipment: quantities, transfers and repacking links, with each gap in the trace written as a question. It decides no hold and contacts nobody.
Listed under
Add it to a workflow in the Fully Powered Planner, beside the teams and roles that will run it. Book a fit call
The outcome
Following one batch through a warehouse network usually means four exports open side by side and a lot of patience. This capability does that reading for you. It starts from the batch record and follows the batch location by location, then out through each dispatch line to the account that received it, and it keeps a running balance so you can see how much of the batch each location is recorded as holding.
Where the records stop agreeing, the map says so rather than smoothing it over. A batch that was received short, a transfer that moved more than the location held, a repacking record whose quantities differ, a dispatch line with no batch code, a line carrying two batch codes and a code that is nearly, but not exactly, the one you are tracing: each becomes a numbered gap with the quantity at stake and a question for a named role. Nothing is assigned by guesswork and no gap is filled.
An incomplete trace cannot show that no other stock is affected, and the map says that in plain words whenever a gap is open. It decides no scope, no hold, no recall and no regulatory question, and it contacts nobody. The quality lead confirms the scope. Operations verifies the matches before anyone acts.
Who starts the work, and when
The quality lead starts it, naming the batch code to trace, when a quality concern, a supplier or production-partner report, or a customer complaint points at one batch. It runs again when operations corrects a record or answers one of the questions.
Operations, usually the warehouse or logistics lead, checks the matches against carrier and retailer documents. The quality lead decides what the affected scope is and what happens next.
What they supply
- A batch record: the batch code, product, production date and quantity produced.
- A movement export for the batch: receipts, transfers between locations, returns and adjustments.
- Repacking records: any batch relabelled or re-boxed into a new batch code.
- Dispatch lines: what shipped, from which location, to which destination, with the retailer reference and the carrier reference.
- The settings: the batch code to trace, the unit, and the people to name in the questions.
It works from files you supply. It needs no connection to your warehouse or order systems and never asks for a password. If a column header does not match what it expects, it stops and asks.
What comes out
One trace in a fixed order:
- The batch. What was produced and what was recorded as received.
- Where it moved. Every movement in date order, with the recorded balance at each location after it.
- The batch-to-shipment map. One line for each dispatch, with its route and whether it traces cleanly.
- Repacking links. Each new batch code, its quantity compared with the quantity that went in, and its own shipments.
- Gaps in the trace. Each one numbered, with its type, the rows involved, the quantity at stake and a question.
- For the quality lead and operations. A tie-out line, what the records show by destination, what operations is asked to verify, and a closing statement that the trace is a reading of records and decides nothing.
Good looks like this: every number traces to a row in an export, no unresolved line is quietly counted in or out, and nowhere does the trace say a product is safe, unsafe or affected.
This is not a recall contact plan and not a stock count. Product recall customer contact plan starts after a recall has been issued and works from affected customers. Stock count reconciliation compares a physical count with the books. This capability only answers where the records say one batch went, and where they do not say.
An invented example
Illustrative example with invented data. Brand X, the retailers, the warehouses, the production partner and every code, reference and quantity below are invented. The quality lead has asked for a trace of batch B2611A, a chilli oil, after a production partner's note raised a question about it. The unit throughout is bottles.
What the person supplies
Batch record
batch_code,sku,product_name,production_date,quantity_produced,unit
B2611A,CO-250,Chilli oil 250 ml,2026-09-14,2400,bottle
Movement export (every row for B2611A)
movement_id,movement_date,batch_code,sku,from_location,to_location,quantity,unit,movement_type,document_ref
M1,2026-09-15,B2611A,CO-250,Production partner P,Warehouse 1,2376,bottle,receipt,GRN-5521
M2,2026-09-22,B2611A,CO-250,Warehouse 1,Warehouse 2,600,bottle,transfer,TO-318
M3,2026-09-23,B2611A,CO-250,Warehouse 1,Warehouse 3,400,bottle,transfer,TO-321
M4,2026-10-05,B2611A,CO-250,Warehouse 2,Warehouse 3,150,bottle,transfer,TO-344
M5,2026-10-06,B2611A,CO-250,Warehouse 3,Warehouse 4,380,bottle,transfer,TO-349
Repacking records
repack_id,repack_date,source_batch_code,source_quantity,location,new_batch_code,new_sku,new_quantity,unit
R1,2026-10-01,B2611A,360,Warehouse 1,X2611-R1,CO-250-EX,354,bottle
Dispatch lines (all lines for SKU CO-250 and CO-250-EX from 15 September to 12 October)
dispatch_id,dispatch_date,batch_code,sku,quantity,unit,ship_from,destination,retailer_reference,carrier_reference
D1,2026-09-18,B2611A,CO-250,288,bottle,Warehouse 1,Retailer A DC North,RA-PO-7741,CAR-1101
D2,2026-09-19,B2611A,CO-250,336,bottle,Warehouse 1,Retailer B stores,RB-4402,CAR-1105
D3,2026-09-30,B2611A,CO-250,240,bottle,Warehouse 2,Retailer A DC North,RA-PO-7790,CAR-1120
D4,2026-10-03,B2611A,CO-250,192,bottle,Warehouse 3,Retailer C,RC-1187,CAR-1131
D5,2026-10-08,B2611A/B2611B,CO-250,120,bottle,Warehouse 2,Retailer D,RD-0095,CAR-1140
D6,2026-10-09,,CO-250,96,bottle,Warehouse 3,Retailer B stores,RB-4460,CAR-1144
D7,2026-10-10,B2611-A,CO-250,48,bottle,Warehouse 2,Own-site orders (consolidated),,CAR-1150
D8,2026-10-12,X2611-R1,CO-250-EX,240,bottle,Warehouse 1,Export distributor E,ED-3310,CAR-1160
Settings: batch to trace B2611A; unit bottle; quality lead named "the quality lead"; operations named "the operations lead"; trace prepared 10 November 2026.
What comes out
BATCH DISTRIBUTION TRACE: B2611A, Chilli oil 250 ml (CO-250)
For: the quality lead, to confirm scope with the operations lead. Records used: batch record pasted; movements to 6 October 2026; repacking records pasted; dispatch lines 18 September to 12 October 2026. Prepared 10 November 2026.
1. The batch
Produced: 2,400 bottles on 2026-09-14. Recorded as received: 2,376, which is 24 fewer than produced (G1).
2. Where it moved
- 2026-09-15 M1: received from Production partner P into Warehouse 1, 2,376 (GRN-5521). Warehouse 1 now 2,376.
- 2026-09-18 D1: dispatched from Warehouse 1, 288. Warehouse 1 now 2,088.
- 2026-09-19 D2: dispatched from Warehouse 1, 336. Warehouse 1 now 1,752.
- 2026-09-22 M2: Warehouse 1 to Warehouse 2, 600 (TO-318). Warehouse 1 now 1,152; Warehouse 2 now 600.
- 2026-09-23 M3: Warehouse 1 to Warehouse 3, 400 (TO-321). Warehouse 1 now 752; Warehouse 3 now 400.
- 2026-09-30 D3: dispatched from Warehouse 2, 240. Warehouse 2 now 360.
- 2026-10-01 R1: repacked out at Warehouse 1, 360. Warehouse 1 now 392.
- 2026-10-03 D4: dispatched from Warehouse 3, 192. Warehouse 3 now 208.
- 2026-10-05 M4: Warehouse 2 to Warehouse 3, 150 (TO-344). Warehouse 2 now 210; Warehouse 3 now 358.
- 2026-10-06 M5: Warehouse 3 to Warehouse 4, 380 (TO-349). Warehouse 3 now -22 (G2); Warehouse 4 now 380.
Recorded balance by location: Warehouse 1 392; Warehouse 2 210; Warehouse 3 -22; Warehouse 4 380. Total 960.
3. Batch-to-shipment map
- D1, 2026-09-18: 288 from Warehouse 1 to Retailer A DC North; retailer reference RA-PO-7741; carrier CAR-1101. Route: Production partner P, Warehouse 1. Status: Traced.
- D2, 2026-09-19: 336 from Warehouse 1 to Retailer B stores; retailer reference RB-4402; carrier CAR-1105. Route: Production partner P, Warehouse 1. Status: Traced.
- D3, 2026-09-30: 240 from Warehouse 2 to Retailer A DC North; retailer reference RA-PO-7790; carrier CAR-1120. Route: Production partner P, Warehouse 1, Warehouse 2. Status: Traced.
- D4, 2026-10-03: 192 from Warehouse 3 to Retailer C; retailer reference RC-1187; carrier CAR-1131. Route: Production partner P, Warehouse 1, Warehouse 3. Status: Traced.
Recorded to each destination (traced, direct): Retailer A DC North 528; Retailer B stores 336; Retailer C 192. Total 1,056.
Unplaced lines (not counted):
- D5, 2026-10-08: 120 from Warehouse 2 to Retailer D; the code reads "B2611A/B2611B", so the quantity is not split (G4).
- D6, 2026-10-09: 96 from Warehouse 3 to Retailer B stores; no batch code, SKU matches, and Warehouse 3 recorded the batch on 2026-09-23 (G5).
- D7, 2026-10-10: 48 from Warehouse 2 to Own-site orders (consolidated); the code reads "B2611-A" (G6).
Blank-code lines for this SKU from locations with no record of the batch, not listed: 0.
4. Repacking links
R1, 2026-10-01: 360 of B2611A into X2611-R1 (CO-250-EX) at Warehouse 1; 354 recorded as made, 6 fewer (G3). Shipments of X2611-R1: D8, 2026-10-12: 240 from Warehouse 1 to Export distributor E; retailer reference ED-3310; carrier CAR-1160. Route: Production partner P, Warehouse 1, repacked under R1. Status: Traced. Balance of X2611-R1: Warehouse 1 114.
5. Gaps in the trace
- G1. Receipt differs from production: batch record, M1. Quantity at stake: 24 bottles. Question for the operations lead: what does the goods-in record for GRN-5521 show, and what quantity does Production partner P's record show as sent?
- G2. Unmatched transfer: M5. Quantity at stake: 22 bottles (Warehouse 3 recorded 358 on 2026-10-06 and TO-349 moved 380). Question for the operations lead: what do the Warehouse 3 receipt and transfer records show for the 22 bottles on TO-349 beyond the 358 recorded there?
- G3. Repack quantity differs: R1. Quantity at stake: 6 bottles. Question for the operations lead: what does the repacking record show for the 6 bottles between the 360 used and the 354 made?
- G4. Mixed lot: D5. Quantity at stake: up to 120 bottles. Question for the operations lead: how many of the 120 bottles came from B2611A and how many from B2611B, according to the pick record?
- G5. No batch code: D6. Quantity at stake: up to 96 bottles. Question for the operations lead: which batch did the pick record assign to these 96 bottles at Warehouse 3?
- G6. Near-match code: D7. Quantity at stake: up to 48 bottles. Question for the operations lead: is "B2611-A" on D7 a mistyped B2611A or a different batch?
6. For the quality lead and operations
Tie-out: 2,376 received - 1,056 direct dispatches posted to the ledger - 360 repacked out = 960; location balances add to 960 (392 + 210 - 22 + 380).
What the records show: 1,056 bottles to 3 destinations through traced dispatch lines; 240 bottles to Export distributor E through X2611-R1; still recorded on hand: Warehouse 1 392, Warehouse 2 210, Warehouse 4 380, with Warehouse 3 recorded at -22 (G2), and X2611-R1 114 at Warehouse 1.
Quantity not placed: 264 bottles in 3 lines (G4, G5, G6).
Operations to verify: D1 to D4 and D8 against the carrier and retailer documents; the answers to the six questions in section 5.
Open gaps: 6. This trace is incomplete, so it cannot show that no other stock is affected. The quality lead confirms the affected scope, and operations verifies each match, before any hold or contact. This trace decides no recall or regulatory question, contacts nobody and changes no record.
Where it fits
- Quality management, where a batch concern needs a fast, careful reading of where the stock is.
- Supply chain and inventory, which owns the movement and dispatch records the trace reads.
- Consumer brands, where one batch can leave through several warehouses, a production partner and many retail accounts.
- Manufacturing, for makers who ship their own batches onward through distributors.
- Ecommerce and retail, where a batch is split between marketplace, wholesale and own-site orders.
- Established businesses, where the records have grown over years and codes are written several ways.
- Growth & scaling, when a second warehouse or a production partner has been added faster than the record keeping.
What has to change for your company
- Your exports. The column names your systems produce, so the template reads them as they come, and the words they use for movement types.
- Your batch codes. How a code is written, what a near-match looks like in your records, and how you mark a mixed lot.
- Your locations. The warehouses, production partners and third-party sites, and which of them keep their own records.
- Your units. The unit each file counts in, and any conversion that repacking involves, agreed in advance.
- Your people. Who confirms scope, who verifies matches and who owns each kind of gap.
- Your platform. It runs in ChatGPT, Claude, Copilot or Gemini. Decide which files the assistant may read and where the trace is kept.
What has been checked
Fully Powered AI wrote this capability template. It was editorially reviewed on 10 November 2026. It was tried on its invented example in Claude on 10 November 2026; the record is published with it. Small wording edits made to the instructions and example after that trial have not been run again. It has not yet been tested in a client environment. It has not yet been tested as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your environment means running it on a past batch the quality lead already knows, with hard cases written in advance: a header that does not match, a receipt that differs from production, a transfer larger than the stock recorded, a line with two batch codes, a near-match code and a repack that changes the unit. Operations checks every route against carrier and retailer documents before anyone relies on the map. Pilot acceptance-test preparation sets those cases up, and what we test before we call an AI workflow ready describes the record we keep.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Put this capability to work for your team: on your plan, or built with you in a sprint.
Build this in a sprint
In a sprint, Fully Powered adapts this capability template to your rules, proves it on your own work and puts it in the hands of the roles that own it.
Two ways to begin: