A batch code is only useful if it can be resolved into records. Printing a code is easy; producing the paperwork behind it, for the specific cartons you received, is the part worth verifying. This guide covers how to ask for traceability records, what a request should contain, and how to check that the records you get back describe your goods rather than a different run.
It is written for buyers. Search for batch traceability and most results are aimed at manufacturers — ERP modules and electronic batch record systems — which does not help you obtain anything from a supplier.
1. Traceability is three separate things
The word gets used as if it were one feature. Split it and the request becomes concrete.
| Element | What it means | How you check it |
|---|---|---|
| Batch identity | A code on the goods that distinguishes this run from every other run | Read it off the units and cartons you actually received |
| Record linkage | Records that connect that code to production, materials and release | Match the code on the document to the code on the goods |
| Availability | The documents can still be produced after delivery, on request | Ask for one after delivery, not only before the order |
The third element is the one that separates a filing cabinet from a traceability system, and it is the cheapest to test. Ask for a record for a batch delivered some months ago and see what comes back.
2. What makes a batch code usable
Before requesting anything, look at the code itself. A code you cannot interpret is hard to reference in a complaint, and a code that repeats across years cannot separate two runs.
- Unique per run — not a product code, and not a code reused every few months.
- Readable — legible on the tube or bottle and on the retail carton, and identical in both places where both carry it.
- Traceable to a date basis — you should be able to say whether the printed date is production or expiry, and how it was derived. Our shelf-life documentation guide covers that derivation.
- Not the only mark — the carton should also carry what your market requires, so the batch code is not doing two jobs.
3. A request that gets an answer
A vague request produces a vague reply. State the goods, the scope, the format and the deadline, and say what you will do with the records.
| Field in your request | What to write |
|---|---|
| Product identification | Product name and your reference for it |
| Batch codes | The exact codes read from the received units and cartons, listed |
| Quantity and shipping reference | Units per code, and the invoice or shipment reference |
| Records requested | Name each one rather than asking for "the batch file" |
| Purpose | Import clearance, a retailer requirement, or an internal complaint — it changes which records matter |
| Format and language | PDF or scan, and the language your market or retailer accepts |
| Deadline and contact | A date, and the person who will receive them |
4. Records worth naming
- Batch record or manufacturing record for the code in question, covering production and filling.
- Certificate of analysis for that batch, showing what was tested against the specification.
- Specification the batch was released against, with its version or date.
- Incoming-material references for the components used, so a question about a material can be followed.
- Packaging and print records, which matter when the issue is a wrong artwork revision or an unreadable code.
- Retention sample note — who holds a sample of that batch, and for how long.
If your market requires a document from the manufacturer rather than the seller, say so at the start. It is a common reason a file arrives late or arrives from the wrong party.
5. Verify that the records describe your goods
Receiving a document is not the same as receiving the right document. Check these before filing it.
- The batch code on the document matches the code on your units, character for character.
- The product and the packaging format match what shipped, including the artwork revision where it is stated.
- The production date on the record is consistent with the date printed on the carton.
- The quantity covered is plausible for the quantity you received, or the shortfall is explained.
- The document names the batch, not a product family or a generic template.
A file that fails any of these is not evidence yet. It is a document to query.
6. When the records do not arrive
Decide the consequence in advance, in the same way you would for a failed inspection: agree a response time in the purchase order, and state what happens if it is missed. In practice the options are a formal query, a hold on the next order, or a documented note that the record was requested and not provided. What you should not do is assume a document exists because the site or the catalogue says the supplier is certified. Whether a specific record can be produced for a specific batch is the only thing that answers the question.
7. The rule that probably does not apply to you
Search for traceability requirements and you will be buried in food regulation, including the United States Food Traceability Rule under the Food Safety Modernization Act. That rule is about certain foods. Toothpaste is not a food: the FDA lists toothpastes among cosmetics, and notes that toothpastes containing fluoride are regulated as both cosmetics and drugs. So a food traceability rule is the wrong framework for a toothpaste order, even though it dominates the search results.
That does not mean nothing applies. It means the requirement you actually have to meet is the one for your product category in your destination market, which may include record-keeping duties, a batch-marking expectation, or a document a retailer asks for contractually. Confirm it for your market instead of borrowing a food rule.
8. Next step
Send us the product reference, the batch codes you have received and the records your market or retailer requires, and we will confirm which documents can be produced and in what format. Send your request. If you have not placed the order yet, start with the quality control documentation guide so the record requirements are agreed before production rather than after delivery.