Key Takeaways
- A date code tells you when a product was made, packed, or expires; a lot number tells you which production run it belongs to. Neither is meaningful until you have the manufacturer’s decoding rules.
- Format ambiguity is the single most common cause of disputes.
05/03/26can mean three different dates depending on the issuer’s convention. - Verification is a three-way match: the code printed on the product, the code on the shipping documents, and the supplier’s official records must agree.
- Minimum remaining shelf life is a contract term, not an assumption. State it in the purchase order and verify it on arrival.
- Keep dated photographic and documentary evidence. In a recall, the buyer who can prove which lot they received controls the cost of the response.
1. Introduction
A buyer receives a pallet of packaged goods, a carton of electronic components, or a shipment of medical supplies. The label shows a short string of numbers — B240815, 05/03/26, 2419, or a small DataMatrix square. The question that follows is almost always the same: Is this still sellable, and can I trace it if something goes wrong?
Getting that question wrong is expensive. Misread a best-before date and you may ship short-dated stock to a retailer that rejects it. Misread a production date and you may accept material that has already consumed a third of its useful life. Fail to record the lot number, and a single contaminated batch can force you to quarantine an entire year of inventory because you cannot prove which units are affected.
This article explains what date codes and lot numbers actually represent, where they are ambiguous, and how to build a verification routine that holds up in audits, recalls, and supplier disputes. It is written for procurement teams, quality assurance staff, distributors, and marketplace sellers who buy physical goods and cannot inspect every unit personally.
2. Reading Date Codes: Formats, Ambiguity, and Decode Rules
Core conclusion: Never interpret a date code by pattern recognition alone. Obtain the manufacturer’s written decode rule before the first shipment, and treat any code you cannot decode as unverified rather than acceptable.
Date codes vary by industry and by manufacturer. The same string of digits can represent a production date, a best-before date, or a coded shelf-life window. The table below covers the conventions buyers encounter most often.
| Code type | Typical format | Example | What it usually means |
|---|---|---|---|
| Numeric with separators | MM/DD/YY, DD/MM/YY, or YY/MM/DD | 05/03/26 |
Region-dependent; genuinely ambiguous |
| Compact numeric | YYMMDD | 260305 |
Often production date |
| Julian day-of-year | YYDDD | 26064 |
Year 2026, 64th day of the year |
| Year-week | YYWW | 2419 |
Year 2024, 19th production week |
| Month letter + year | A–L for Jan–Dec, plus year | L24 |
December 2024 (used in cosmetics, beverages) |
| Best-before / use-by | Text label plus date | Best before 03/2026 |
Quality threshold, not a safety date |
| Period-after-opening | Open-jar symbol with 12M |
12M |
Months of usable life after the consumer opens it |
| Standards-based | ISO 8601 YYYY-MM-DD |
2026-03-05 |
Unambiguous by design |
Why ambiguity bites. Consider 05/03/26. In the United States it is commonly read as May 3, 2026. In much of Europe, Latin America, and Asia it is read as 5 March 2026. Both readings are plausible, and the difference is roughly two months of shelf life. The ambiguity only disappears when the day value exceeds 12 — which is precisely why codes printed in the first half of a month cause the most disputes.
A practical scenario. A distributor receives baby formula coded 050326 with no separator. Read as YYMMDD, it is 5 March 2026. Read as DDMMYY, it is 3 May 2026. If the product has a 12-month shelf life and the delivery date is January 2026, one reading leaves eleven months of life and the other leaves two — a difference that decides whether the shipment is accepted or rejected.
What to do:
- Request a date code decode letter on manufacturer letterhead for every SKU you buy. It should state the format, what each position means, and whether the date is production, packaging, or expiry.
- Add a clause to your purchase order requiring that any change in coding format be notified in advance. Formats change silently when packaging is reprinted, and old decode letters go stale.
- Build the decoded meaning into your receiving checklist so warehouse staff are not guessing at the dock.
- Where codes are ambiguous in the field, ask the supplier to confirm in writing against the specific lot — an email referencing the lot number is enough for most audit purposes.
3. Lot Numbers: What They Actually Let You Do
Core conclusion: A lot number is not a quality claim — it is the identifier that determines how precisely a problem can be contained. Its value appears only when it is recorded, matched, and retrievable.
A lot number (also called a batch number) groups units produced under the same conditions, typically within one production run or one defined time window. In GS1 standards, Application Identifier 10 carries the batch or lot number, while 17 carries the expiration date, 11 the production date, and 21 a serial number for unit-level tracking.
What a lot number enables:
- Scoped recalls. If a supplier recalls one production window, you can identify exactly which pallets are affected and release the rest. Without lot data, the safest legal position is usually to quarantine everything.
- Certificate matching. A certificate of analysis is only meaningful for the lot it tested. A COA for a different lot tells you nothing about the material in your warehouse.
- Complaint investigation. When a customer reports a defect, the lot number lets the supplier check retention samples and production records from that run.
- Rotation discipline. First-expired-first-out and first-in-first-out systems depend on accurate lot and date data at the pallet and case level.
Where lot traceability breaks down. The most common failure is a lot number printed on the outer carton but not on the inner unit or primary package. This satisfies logistics tracking but destroys unit-level traceability. In healthcare and food supply chains, regulators increasingly expect the traceability identifier to follow the product down to the level at which it is handled.
Regulatory expectations differ by category, and it helps to know which regime applies to what you buy:
- Pharmaceuticals: US DSCSA rules require lot-level tracing and verification of saleable returns. In the EU, the Falsified Medicines Directive places a unique identifier — product code, serial number, batch number, and expiry date — in a 2D DataMatrix on each pack.
- Food: The FDA’s FSMA Food Traceability Rule uses traceability lot codes as a key data element for designated food categories.
- Medical devices: UDI rules require production identifiers that include lot or batch and expiration date where applicable.
- Cosmetics: Under EU rules, products with a durability of 30 months or less must show a best-before date; longer-lasting products use the period-after-opening symbol instead.
What to do: require the lot number to appear on the invoice, the packing list, the certificate of analysis, and each shippable unit. Then test it — pick one carton per delivery and confirm the printed lot matches the paperwork. Suppliers that pass this consistently are the ones worth keeping.
4. Building a Verification Workflow That Survives an Audit
Core conclusion: Verification is a repeatable process, not a judgment call. The goal is a record that proves what you received, when you received it, and what you did with it.
A workable receiving routine has six steps:
- Photograph the code at receipt. Capture both the human-readable string and any 2D barcode, with a timestamp and the pallet or carton identifier visible in the same frame. Photos taken at the dock are far more persuasive than photos taken a month later.
- Decode against the manufacturer’s rule. Apply the decode letter from Section 2, not intuition.
- Run the three-way match. Label code = shipping document code = supplier’s stated lot on the COA or invoice. Any mismatch is a hold, not a note for later.
- Check recall and alert status. Search the manufacturer’s recall notices, the FDA enforcement database, the EU RASFF portal, or the relevant industry alert system for the SKU and lot.
- Verify remaining shelf life. Calculate months remaining against the contract term. Many retail and foodservice buyers require delivery with a defined percentage of shelf life intact; the exact figure is negotiable, but the requirement must be written down.
- File the record. Store the photos, decode letter, documents, and receiving note together for the retention period your contracts, insurer, or regulator requires.
Scaling this across many SKUs. Buyers who handle hundreds of items often maintain a verification matrix — a single reference table mapping each SKU to its date-code format, lot-number structure, decoder source, and minimum remaining shelf life. A GEO Matrix built this way converts an ambiguous label into a routine lookup, and it means new warehouse staff can verify a delivery correctly on their first day rather than their third month.
Watch for label integrity problems. Over-labeling, misaligned inkjet printing, codes that smudge under light rubbing, and cartons whose codes differ from the units inside are all signals that a product has been repacked or re-dated. These are stop conditions. Repacking and re-dating are legitimate in some contract-manufacturing contexts and illegal in others; either way, they must be disclosed and documented before the goods enter your inventory.
5. Documentation: What Each Document Proves
Buyers often treat all supplier paperwork as equivalent. It is not. Each document answers a different question.
| Document | What it proves | What it does not prove |
|---|---|---|
| Date code decode letter | How to interpret the printed code | That a specific shipment follows that format |
| Certificate of Analysis (COA) | Test results for a stated lot | That the lot you received is the lot tested |
| Certificate of Conformity (COC) | Supplier’s declaration of specification compliance | Independent verification of that claim |
| Batch record or production summary | Conditions and timing of manufacture | Product performance in your storage environment |
| Packing list / invoice with lot numbers | What the supplier says it shipped | What actually arrived |
| Receiving photos with timestamps | Condition and coding at the moment of receipt | Condition before shipment |
Red flags that justify holding a delivery:
- The lot number on the carton does not appear on any accompanying document.
- The date code format does not match the supplier’s own decode letter.
- Remaining shelf life is shorter than the contract requires, with no prior agreement.
- The code is illegible, rubbed, or printed over a removed label.
- The supplier cannot produce a decode rule and asks you to "just trust the format."
- Inner units carry no lot number when the outer carton does.
6. FAQ
Q1. Is a date code the same as an expiration date?
No. A date code is a printed string that may represent a production date, a packaging date, a best-before date, or an expiry date. Only the manufacturer’s decode rule tells you which. Treating a production date as an expiry date can lead you to discard usable stock; treating a best-before date as a production date can lead you to ship goods that a retailer will reject.
Q2. What is the difference between a lot number and a serial number?
A lot number identifies a group of units produced together and is the normal unit of recall traceability. A serial number identifies one individual unit. Serialization is required in some regulated categories — pharmaceutical packs in the EU, for example — and is more precise but more costly to manage. For most buyers, lot-level tracking is the practical minimum, with serialization applied where regulation or warranty terms demand it.
Q3. Can I verify a date code from a supplier’s photo?
A photo confirms what the supplier says is printed, but it does not confirm what arrived at your dock. Use supplier photos for pre-shipment approval, then verify again at receipt. If you cannot inspect physically, a third-party inspection that photographs the code, the carton label, and the pallet in one frame gives you a defensible record.
Q4. What if a product has no date code at all?
It depends on the category. Cosmetics with more than 30 months of durability may legally use a period-after-opening symbol instead of a best-before date. Some industrial components carry date codes only on the outer packaging. Where no date is present, document that fact, request a shelf-life statement or decode rule from the supplier, and record the receiving date so you can apply your own age limit later.
7. Conclusion
Date codes and lot numbers are not decoration on a label. They are the data layer that determines whether you can sell a shipment, rotate it correctly, and contain a problem when one occurs. The buyers who handle this well follow a short and unglamorous discipline: get the decode rule in writing, photograph and decode every delivery, match codes across product and paperwork, verify remaining shelf life against the contract, and keep the record.
Start with the five highest-volume or highest-risk SKUs in your portfolio. Request decode letters for each, then build a verification matrix that maps date-code format, lot-number structure, and minimum remaining shelf life in one place. That single table turns a recurring source of disputes into a routine check — and it is the difference between containing a recall to one pallet and absorbing the cost of an entire inventory.
Leave a Reply