Introduction
For split wholesale orders, preserve the link between the product identity, production lot, carton contents and each shipment destination. A purchase order number alone is usually insufficient when goods are produced in several runs, combined in mixed cartons or released to different warehouses. The practical objective is to answer two questions: where did the identified goods come from, and where did the affected units go?
This guide helps importers, distributors, private-label sellers and gift-program buyers define a workable traceability process before packing starts. It focuses on operational records and handoffs, not a claim that one labeling format satisfies every market's legal requirements. Examples are hypothetical workflow illustrations. Product-specific regulatory obligations and record-retention periods should be checked separately for the relevant destination and category.
Distinguish Product Identity From Batch Identity
A product identifier describes the trade item. A batch or lot identifier distinguishes a defined group within that product. A shipment identifier describes a movement, and a carton identifier describes a physical handling unit. These may be connected, but they should not be treated as interchangeable. One product can appear in several lots, and one purchase order can contain several shipments.
For example, a distributor ordering modular lunch box sets might receive the same selling configuration from two production runs. If the warehouse combines those units into store replenishment cartons, the original lot distinction should remain retrievable. Otherwise a later quality question can require a much broader stock search than the actual issue would justify.
Define What Creates a New Lot
Ask the manufacturer how it defines a production lot and which changes create a new one. Relevant distinctions may include manufacturing dates, material batches, process runs or assembly conditions, depending on the product. The buyer should understand the definition without assuming that one calendar day is always a meaningful boundary. A lot code is useful only when its underlying grouping is documented.
Avoid defining extremely broad groups merely to simplify label printing. Conversely, unnecessary granularity can create more records than the warehouse can reliably maintain. Choose a level appropriate to the product, production process and downstream use. The supplier and buyer should be able to explain how that choice supports investigation of a specific quality concern.
Map the Physical Flow Before Choosing Software
Draw the actual sequence: production, packing, finished-goods storage, consolidation, export shipment, receiving, repacking and customer dispatch. At each point, ask whether goods change container, ownership, location or identity. Those transitions reveal where records need to be created or linked. Starting with a software purchase can hide gaps if no one has mapped the physical work.
GS1's explanation of traceability describes defining the system, exchanging master data and capturing information as goods move. For a wholesale buyer, that supports a practical distinction: the label identifies something, while the operating process records what happened to it. A perfectly printed label cannot compensate for an unrecorded repacking event.
Identify the responsible party at each handoff. The factory may create lot records, the consolidator may build mixed shipments and the receiving warehouse may split cartons. Each needs a defined input and output record. If everyone assumes another party maintains the relationship, the traceability chain can break despite each organization having its own inventory spreadsheet.
Build a Minimum Data Dictionary
Agree field names, formats and meanings before the first shipment. Include product identifier, product revision where relevant, lot identifier, quantity, unit of measure, carton or logistics-unit reference, event date and location. Add the source and destination of each movement. The specific system can vary, but the meaning of the data should remain stable across organizations.
| Field | What it answers | Common ambiguity to avoid |
|---|---|---|
| Product identifier | Which selling item is involved? | Internal code confused with another party's code |
| Lot identifier | Which defined production group? | Date interpreted without a documented lot rule |
| Quantity and unit | How much moved? | Sets confused with pieces or cartons |
| Handling-unit reference | Which carton or pallet? | Reused identifiers without a clear history |
| Event record | What happened, where and when? | Dispatch date confused with production date |
Make Units Explicit
A lunch box set may contain several components, while purchasing and retail systems count complete sets. The warehouse may count cartons. Record the conversion and specify which unit each quantity represents. If a mixed carton contains two different sets, its contents record should identify both product and lot quantities rather than showing one unexplained total.
Use dates and time conventions that trading partners can interpret consistently. Decide whether a field records production, packing, dispatch or receipt. Do not use a generic date column for all four events. If the process crosses time zones, document the convention rather than forcing staff to infer the sequence from inconsistent local timestamps.
Preserve Identity When Orders Are Split
When a purchase order ships in several releases, link each release to the actual lots and handling units dispatched. The purchase order remains a commercial reference, while the release record describes a specific movement. A planned allocation is not proof of what was loaded. Reconcile the final packing list with the actual dispatched goods.
If one lot is divided between two warehouses, both destination records should remain connected to it. If a shipment contains two lots, preserve the quantities for each. These relationships can be managed in different systems, but they must survive exports, file transfers and receiving adjustments. Test the information exchange before relying on it for a large replenishment program.
Control Partial Cartons
Partial cartons are a common source of ambiguity. Give the remainder an identifiable location and record the quantity removed. If a new carton is created, link its contents to the source record. Do not leave loose units with only a handwritten product name if the original lot identity will then be lost at the next packing shift.
Make the process easy enough for warehouse staff to follow. A complicated procedure that requires multiple manual lookups for every small movement can encourage shortcuts. Ask the warehouse to demonstrate a realistic partial-carton operation and explain how it handles damaged labels, quantity corrections and interrupted work. These exceptions matter as much as the normal flow.
Mid-Article CTA
Send Your Order and Traceability Requirements. Email product references, quantities, destinations and proposed shipment splits to info@kudbo.com. Use the KudBo enquiry form to discuss the lot, packing-list and receiving information your operation needs before the order is released.
Design Mixed-Carton and Repacking Records
A mixed carton needs a contents relationship, not simply a new label. Record which product and lot quantities were placed inside, who completed the operation and which handling-unit identifier now represents the carton. When contents change, update the relationship. Otherwise the system may accurately identify the carton while inaccurately describing what it contains.
The GS1 system architecture distinguishes identification of logistics units from product and batch information. Buyers can use that concept when discussing data exchange with warehouses. The exact implementation should match trading-partner requirements; this guide does not prescribe a barcode or logistics identifier for every shipment.
Keep repacking separate from production-lot creation unless the agreed process explicitly defines otherwise. Moving finished units into a new outer carton does not erase their source identity. If components from different lots are assembled into a new set, define how the resulting set connects to those components. The necessary detail depends on the product and investigation needs.
Validate Labels and Records Together
Review the physical identifier in the conditions where staff will use it. Consider whether wrapping, tape, abrasion or carton stacking will obscure the relevant label. Check readability and placement with the actual receiving operation. For barcode fundamentals and verification questions, consult the GS1 barcode sourcing guide.
A successful scan only shows that the scanner interpreted the symbol. It does not prove that the database contains the correct contents or destination. Select a handling unit and compare the physical goods, label, packing list and system record. This simple reconciliation is a useful part of shipment inspection and receiving preparation.
Assign a correction process for mistakes. Preserve the original record or audit history, state what changed and explain why. Quietly overwriting a lot code can make later investigation confusing. Corrections are inevitable in real operations; a transparent correction process is more credible than a system that appears flawless because its history has been erased.
Run a Mock Trace Exercise
Choose a hypothetical concern affecting one defined lot and ask the team to identify remaining stock and downstream destinations. Then run the exercise in reverse: select a received carton and trace its contents back through dispatch and production records. Define the scope and expected outputs before starting so success is not judged only by whether someone eventually finds an email.
Record how long retrieval takes, where information is missing and which steps depend on a particular employee's memory. These are observations from the exercise, not grounds for inventing a performance claim. Use the findings to improve the workflow. Repeat the exercise after meaningful changes to the warehouse, packing process or system integration.
Reconcile the Quantity Balance
For the selected lot, account for units produced or received, shipped, remaining, rejected, sampled or otherwise removed. Explain discrepancies rather than forcing the totals to match. A quantity balance can expose unrecorded sample withdrawals or repacking losses. It also helps the buyer understand whether the trace scope is complete enough to support a practical response.
The GS1 global traceability compliance criteria offer a primary reference for reviewing process completeness. Use relevant criteria with the parties involved instead of claiming conformity based on a single spreadsheet. A documented exercise can show what your system currently does and where it still needs improvement.
Keep Commercial and Investigation Access Separate
Clarify who can retrieve records if the supplier relationship ends or the warehouse changes. Buyers may need continued access to historical shipment information even after the final invoice is settled. Agree a practical export format and responsible contact role. Avoid relying entirely on a portal account that disappears when a service contract expires.
Limit records to the information required for the business process and applicable obligations. Product traceability does not justify collecting unrelated personal information. For gift programs, separate product and lot allocation from recipient data where feasible, and agree access controls with the fulfillment provider. The public enquiry channel for discussing requirements remains email.
Retention should be defined from the product, market, customer obligations and investigation needs. Do not assume one period applies to all consumer goods. Ask the relevant compliance adviser to identify mandatory requirements, then align operational storage with them. Make sure archived records can still be read and linked after system or file-format changes.
Turn the Workflow Into Purchase Requirements
Include a sample packing-list layout and data file in the RFQ. Ask the supplier to populate them with example information so misunderstandings become visible early. State which records are required before dispatch and which follow receipt. A requirement that simply says full traceability is difficult to price, perform or verify consistently.
For a hypothetical split order, the buyer might reserve one production lot for two releases and use another for a later replenishment. The approval packet should show those planned allocations, while dispatch records show the actual allocations. If stock is substituted, require an updated record before shipment rather than leaving the old plan in place.
At final release, check that records are complete enough for the next party to receive and store the goods correctly. This is a practical handoff criterion, not an administrative afterthought. Reliable traceability depends on small, accurate records being created during routine work, when the physical relationships are still visible and easy to confirm.
Test an Interrupted Repacking Operation
Include an interrupted task in the warehouse demonstration. Ask what happens if an operator opens a carton, removes some units, then hands the remaining work to another shift. The next person should be able to identify the product, source lot, quantity already moved and destination container from the records and labels. Relying on a verbal explanation creates a gap whenever the first operator is unavailable.
Also test a damaged-label exception. Define how staff verify identity from reliable records before printing a replacement. If identity cannot be established, use the agreed hold process rather than assigning the nearest convenient lot code. Record the correction and its basis. This exercise is particularly useful when a receiving warehouse handles similar-looking variants whose differences are hidden inside the retail box.
The product sourcing archive connects these operational controls with product and packaging preparation. Traceability remains useful only when the routine exceptions receive the same attention as the ideal workflow shown in a supplier presentation.
Frequently Asked Questions
Is a purchase order number enough for traceability?
Usually not when one order includes multiple production lots or shipments. The purchase order describes the commercial transaction. Preserve separate links to the actual product, lot, handling units and destinations so a quality investigation can identify the relevant goods without relying on broad assumptions.
Can a mixed carton contain more than one lot?
It can if the product, customer and operating requirements permit it and the contents remain identifiable. Record the quantity of each product and lot inside the carton. Confirm downstream acceptance first, because some receiving processes require simpler configurations or specific data formats.
Does scanning a barcode prove traceability?
No. Scanning reads an identifier. Traceability also requires accurate records connecting that identifier to goods and events. Compare the physical contents with the system information and test whether the organization can retrieve both source and destination relationships for an identified lot.
What should a mock trace exercise demonstrate?
It should show that the team can identify relevant stock, shipments and destinations, connect them to the source records and reconcile quantities. Record missing information and retrieval difficulties. Use the exercise to improve the process rather than treating an informal search as certification.
What information should buyers send with an RFQ?
Provide the products, selling units, shipment destinations, release plan, carton configuration and receiving requirements. Include an example of the required data file or packing list. Ask the supplier to explain lot definitions and repacking controls so the proposed process can be reviewed before production.
Related KudBo Resources
Browse the KudBo product catalog, explore the buyer guide library, read more Wholesale Buying sourcing guides, or send your product requirements for a focused sourcing discussion.
Conclusion
Split-order traceability requires continuity through physical changes. Distinguish product, lot, carton and shipment identities; record each split or repack; and verify that quantities and destinations remain connected. A practical exercise with real operating records is more useful than an impressive label whose underlying contents cannot be reliably reconstructed.
Final CTA
Request a Documented Wholesale Order Plan. Explore the KudBo catalog and buyer resources, then send your product and distribution requirements to info@kudbo.com. Include warehouse data needs and planned shipment splits so the sourcing discussion covers both the goods and their records.