A carton can carry a clean date code and still leave the buyer with unanswered questions. Does the code show the actual production date, a packing date, a supplier’s internal batch code, or an expiry date? Which lot does it apply to? Was the product stored under the condition that supports the buyer’s intended use? Has the factory used older stock first? How much usable life remains when the goods reach the buyer’s warehouse? If the supplier cannot connect the answer to the right product, lot, carton, storage record, and shipment, a printed date has limited value.
China supplier shelf-life control is a buyer process for setting and verifying date, storage, age, rotation, and shipment evidence before goods leave the factory or warehouse. It begins with a product-specific requirement. The buyer defines what date field matters, which storage condition applies, whether a date code must appear on the product or carton, what record establishes the date, and what minimum remaining-life or age-on-delivery condition applies if qualified owners have set one. The supplier then provides evidence for the actual shipment scope.
This article provides general sourcing and quality-management guidance. The eCFR materials cited apply to pharmaceuticals or government-owned inventory, not ordinary commercial China supplier sales. They do not establish an expiry date, shelf-life period, stability method, retest date, date-code format, age-on-delivery period, storage temperature or humidity range, first-expired-first-out rule, shipment-release requirement, or compliance duty for a reader’s product. Buyers must establish product-specific requirements using supplier evidence, product specifications, customer needs, applicable law, and qualified technical, regulatory, and legal review. A manufacture date or date code alone does not prove remaining performance, safety, stability, or compliance. Food, drugs, cosmetics, medical devices, children’s goods, chemicals, batteries, electrical items, safety products, aerospace parts, and other regulated or safety-sensitive products require qualified review.
Make the date requirement specific before production
The buyer should define why a date matters for the particular product. A product may have a true limited useful life. A material may degrade or become unsuitable after a defined period. A customer may require a production-date code for inventory rotation. A service-part program may need a date code to distinguish revisions. Another item may have no limited-life requirement at all, even if the supplier uses a date code for internal traceability.
Do not ask a factory to “use a fresh date” without defining the basis. The supplier needs a written product requirement that identifies the date type, unit of display, product or carton location, source record, storage condition, and the buyer decision it supports. If the buyer requests an age-on-delivery or minimum remaining-life rule, qualified owners should establish the rule before the order is released.
In the pharmaceutical context, 21 CFR 211.137 links expiration dating to appropriate stability testing and storage conditions stated on labeling.1 That does not create a commercial date-code rule for China imports. The transferable point is that a date claim and storage condition must be considered together. A date printed without an applicable product basis or storage record cannot answer a buyer’s suitability question.
| Date or identifier | What it can mean | Buyer control question |
|---|---|---|
| Manufacture date | Date the product or defined production stage was made. | Which production event sets this date and what record supports it? |
| Production date code | Supplier or buyer code that may represent a date, line, shift, lot, or internal reference. | Is the code format documented and linked to a product lot or run? |
| Packing date | Date finished goods entered final packaging. | Does the buyer need this date separately from the production date? |
| Expiry date | Date after which a product should not be used under its established basis. | Who established the date and under what qualified product and storage basis? |
| Best-by or quality date | Buyer, supplier, or market date used for quality or inventory purposes. | Is it a contractual or regulatory requirement, and how is it supported? |
| Retest date | Date when a material requires reevaluation under an applicable process. | Does the product have a valid reevaluation procedure and decision owner? |
| Date of receipt | Date the factory or warehouse received materials or goods. | Is it being confused with the actual manufacture or packing date? |
| Date of shipment | Date goods move to a forwarder or carrier. | Does it support the buyer’s calculation of age at delivery? |
| Lot, batch, or serial code | Product identity reference that may include or link to date information. | Can the supplier trace the code to production, inspection, packing, and shipment scope? |
A buyer should not use supplier terminology without confirming its meaning. One factory may call a carton “production date” when it prints the final packing date. Another may use a month-year batch code. A third may apply a date after a rework or repack. Ask for the code logic and a sample of the label or carton mark before mass production, then include it in the approved artwork, packing instruction, or product specification.
The date requirement should apply to a clear population. Define whether the code belongs on the unit, inner pack, carton, pallet, warehouse label, shipping document, or all of these. If one carton can contain several lots or date codes, the buyer needs a packing and traceability rule that shows the range. A generic statement that the goods are “new” does not provide this information.
Define product, storage, and age-on-delivery rules together
Shelf-life control is more than a date calculation. A buyer needs a product basis, storage conditions, date logic, and a release rule that work together. If the supplier’s product specification requires dry storage, a date code cannot prove that the product stayed dry. If a buyer wants an age-on-delivery limit, it must decide which date starts the clock and what shipping or warehouse stage ends it. If the product can be stored at more than one condition, qualified owners need to define which condition governed the actual shipment.
The federal inventory regulation defines shelf-life items, in its government inventory context, as items with deteriorative or unstable characteristics that require an assigned storage period to assure satisfactory use.2 It also connects shelf-life management to identification, storage, inspection, and inventory analysis. A commercial buyer can use that structure without copying government codes, periods, or rules.
| Requirement field | What the buyer should state | Supplier evidence before release |
|---|---|---|
| Product and revision | Exact SKU, part number, market version, and approved revision. | Product record, label or carton sample, and current order reference. |
| Date field | Manufacture, packing, expiry, best-by, retest, or buyer-defined code. | Code explanation and link to the controlling record. |
| Date format | Calendar date, month-year, Julian code, lot code, or other approved display. | Approved artwork, marking instruction, and label or carton evidence. |
| Date location | Unit, inner pack, carton, pallet, warehouse label, or shipping document. | Photos, packing record, label verification, or pallet record. |
| Storage condition | Buyer-approved condition or manufacturer instruction applicable to the product. | Storage record, warehouse location, monitoring or handling evidence where required. |
| Age-on-delivery rule | Buyer-approved maximum age or minimum remaining life, if applicable. | Calculation basis, date-code range, shipment date, and scope record. |
| Rotation rule | Oldest stock first, first-expired-first-out, or another buyer-approved process when applicable. | Inventory listing, pick or issue record, and aged-stock review. |
| Mixed-lot rule | Whether cartons or pallets may include multiple date codes or lots. | Carton mapping, packing list, pallet record, and approval evidence. |
| Hold and disposition | How unclear, aged, damaged, relabeled, or unsuitable stock is controlled. | Hold tag, investigation, buyer decision, and disposition record. |
The buyer should avoid setting a date threshold without an approved product basis. A factory may agree to ship goods “within six months of manufacture,” but that promise is not meaningful unless the buyer has specified why six months applies, what date counts, which storage condition is assumed, and how mixed lots are handled. An arbitrary threshold can create false assurance or disrupt supply without improving product control.
When a product has a limited-life requirement, the buyer can use a simple factual calculation after qualified owners have defined the inputs. For example, if the product specification establishes a manufacture date, an expiry date, and storage condition, the buyer can compare the verified shipment date with the available date range. If those inputs are not defined, do not create a remaining-life percentage from a carton label alone.
A supplier should separate date evidence from fitness decisions. It can provide the lot, date code, storage record, and shipment scope. The buyer’s qualified technical or regulatory process should decide whether the facts meet a product-specific use, compliance, or customer requirement.
Link date codes to product lots, cartons, and warehouse stock
A buyer cannot control shelf life if it cannot trace a date code to the actual goods. The supplier should connect the product’s date or lot code to the production run, inspection status, pack-out, warehouse location, and shipment. For a simple item, a carton range and packing record may be enough. For a component or sensitive product, the buyer may need unit, lot, serial, pallet, or warehouse-level links.
The supplier should not present a single photo of one carton as evidence for an entire shipment without explaining the scope. If the shipment contains multiple production dates, list each date range, quantity, carton range, pallet, and location. If the factory repacked goods or moved them between warehouses, retain the original and current identity link under the agreed process.
| Evidence link | What it connects | Buyer check |
|---|---|---|
| Production run or lot record | Product, date, line, shift, process, or material population. | Does the date code map to the correct manufacturing scope? |
| Inspection or test record | Lot or date-coded population to quality status. | Were the goods under this code accepted, held, or reworked? |
| Packing record | Accepted goods to inner packs, cartons, and pallet configuration. | Does the stated date code appear on the actual packed scope? |
| Carton or label verification | Approved artwork or mark to carton identity. | Is the date format, location, and content correct? |
| Warehouse record | Date-coded goods to physical location and hold or release status. | Are the goods identified and segregated as required? |
| Inventory listing | Available date ranges, quantities, and aged stock. | Does the shipment select the right stock under the agreed rule? |
| Picking or issue record | Warehouse selection to packing or loading. | Did the supplier issue the intended date-coded lot? |
| Packing list and shipment release | Product, cartons, quantity, lot or date-code scope to cargo. | Does the shipment document match the verified date-code population? |
| Container loading or handoff record | Approved cartons or pallets to cargo movement. | Did held or unapproved date-coded goods remain out of the shipment? |
Article 071 covered lot traceability records, Article 069 covered finished-goods storage control, Article 084 covered production reconciliation, and Article 085 covered post-shipment record retention. A shelf-life release package should use the same identifiers. It should not introduce a date-code list that cannot be connected to production, packing, warehouse, and shipment evidence.
Mixed date codes require special attention. A buyer may permit them if cartons, pallets, and shipment documents show the composition clearly and the product requirement allows it. A buyer may prohibit mixed lots for products that need uniform date coding or simple warehouse rotation. State the rule before the factory packs goods. Discovering a mixed pallet after container loading creates a more difficult logistics and release decision.
Request storage and age evidence before shipment
The buyer should request evidence that matches the product risk and agreed storage condition. A general warehouse photo may show that cartons exist but not whether a specific lot was stored under the required condition. A temperature log may be relevant for a product with a defined temperature requirement, but it is not useful if the buyer has not identified the applicable range, storage scope, and review need. Request the smallest set of records that answers the actual requirement.
Where the supplier holds goods for a long period, request an aged-inventory review before release. The review should list the product, lot or date code, quantity, storage location, release status, and any reason the goods remain in stock. The factory should identify any stock that falls outside the buyer’s written age, date, packaging, or storage requirement and place it under the appropriate hold or review process.
| Pre-shipment question | Evidence the supplier can provide | Buyer decision use |
|---|---|---|
| What date code will ship? | Lot or carton list with date-code range, quantity, and product revision. | Confirms the factual date-coded shipment population. |
| How was the code set? | Approved marking instruction, artwork, production or packing record. | Confirms the code means what the buyer expects. |
| Which storage condition applied? | Product storage instruction, warehouse area or location record, and relevant monitoring or handling record. | Supports review against the buyer’s defined condition. |
| How old is the stock at shipment? | Verified date basis, shipment or release date, and quantity by date-code range. | Supports any buyer-approved age-on-delivery review. |
| Is older stock still held? | Inventory listing, date-code range, location, and disposition status. | Identifies aged inventory that could be selected incorrectly. |
| Did the warehouse rotate stock correctly? | Picking, issue, or first-in-first-out record where the buyer requires it. | Verifies the actual stock-selection process against the stated policy. |
| Are cartons mixed by date code? | Carton, pallet, and packing map. | Determines whether the shipment fits the buyer’s mixed-lot rule. |
| Was any stock relabeled or repacked? | Rework or repack record, reason, old and new identity, inspection or approval. | Prevents a new outer label from obscuring the goods’ history. |
| Is any stock held or unclear? | Hold tag, status report, event or investigation record. | Keeps uncertain goods out of shipment until the buyer decides. |
The federal inventory rule calls for controls to identify shelf-life items and generally uses oldest-stock-first issue in its government setting.2 A commercial buyer should not assume that the rule applies to its goods. It can decide whether first-in-first-out, first-expired-first-out, customer-specific allocation, or another method is appropriate for its product and agreement. The supplier needs to follow the written requirement, not a vague expectation that it will choose “fresh” stock.
If a supplier says it has no older inventory, ask for the relevant inventory status rather than accepting a verbal assurance. If it says the goods have been stored correctly, ask for the relevant record or warehouse evidence tied to the date-coded scope. The buyer does not need to audit every warehouse movement for a simple product, but it should be able to review the evidence when the product requirement or risk justifies it.
Review aged inventory and rotation before approving release
Aged inventory is not automatically unsuitable. It becomes a buyer issue when it conflicts with the written product, date, storage, packaging, customer, or shipment requirement. The supplier should identify the stock and date evidence, preserve the relevant records, and request a buyer decision rather than quietly relabeling, mixing, repacking, or shipping it as a later production lot.
The buyer should use a defined review path. Compare the verified date code, product revision, storage condition, inspection status, packaging integrity, remaining-life basis if one exists, warehouse location, and shipment plan. If the product requires qualified technical, safety, regulatory, or customer approval, route the question to the appropriate owner. Do not decide that product is “still good” merely because the carton appears clean or a date has not yet passed.
| Aged-stock situation | Supplier action | Buyer review question |
|---|---|---|
| Stock meets all written date and storage requirements | List it in the release package with date-code and shipment scope. | Does the evidence match the buyer’s requirement for this order? |
| Stock is within a buyer-defined age limit but has mixed lots | Provide carton or pallet map and quantity by date range. | Does the buyer allow mixed date codes and is the shipment document clear? |
| Stock has unclear date-code meaning | Hold the scope and provide code logic, records, and label samples. | Can the buyer establish a valid date basis before release? |
| Storage condition is not supported by records | Preserve available facts and notify the buyer under the agreed path. | Does the product need qualified technical or regulatory assessment? |
| Outer label was changed after packing | Hold as appropriate and provide old and new identity, reason, and approval records. | Does relabeling preserve traceability and meet the buyer’s requirements? |
| Date-coded stock was found in the wrong warehouse status | Segregate it, count it, and identify movement history. | Can the buyer confirm the affected scope and prevent shipment error? |
| Product may be near a buyer-defined cutoff | Notify before packing or cargo release with factual date and location evidence. | Should the buyer approve, reallocate, inspect, or hold the product? |
| Product may be expired or unsuitable under an applicable requirement | Stop release and escalate through qualified product, regulatory, legal, and safety owners. | What disposition is authorized under the relevant product and legal process? |
The supplier should never “refresh” a date by changing a label, box, or outer carton unless the buyer-approved and product-appropriate procedure allows it. Repackaging may be a legitimate operation in some supply chains, but it does not automatically change the underlying production history, date basis, shelf life, or storage evidence. Preserve the old identity and the reason for the action.
Article 058 covered rework and repair control. If the supplier repacks, relabels, reworks, or repairs a date-coded product, it should link the action to the lot, date code, inspection, and packing record. Without that link, the buyer may not be able to distinguish an approved correction from a change that obscures aged or held stock.
Verify date codes during packing and shipment release
Date control can fail during packing even when production records are correct. A warehouse may pick the wrong pallet. A line may use an old label or carton. A packer may mix two date-coded lots. A draft packing list may contain only total quantity and not identify the required date range. The buyer should include date-code checks in the packing and shipment-release process when the product requirement calls for them.
The supplier can use a packing checklist that identifies the product, revision, required date format, actual date-code range, carton range, mixed-lot status, label or artwork version, quantity, pallet, warehouse location, and shipment reference. The buyer can review a summary with supporting photos or records when appropriate. The check should occur before container loading or cargo handoff, not after the bill of lading is issued.
| Release check | Factory record | Buyer confirmation |
|---|---|---|
| Product identity and revision | Order, packing instruction, and label or carton reference. | The packed product is the buyer-approved version. |
| Required date field and format | Artwork or marking instruction and current code example. | The code format and location match the written requirement. |
| Actual date-code range | Carton or pallet map, packing record, and quantity by code. | The shipment contains the approved date-coded scope. |
| Mixed-lot status | Carton, pallet, or shipment map. | Any mixture follows the buyer’s documented rule. |
| Storage and warehouse status | Warehouse location, hold or release record, and relevant condition evidence. | Goods were selected from the correct status and location. |
| Aged-inventory exception | Hold, approval, or qualified review record. | No unsupported aged stock is included in cargo. |
| Packing list alignment | Draft packing list and carton or pallet count. | Documents match actual quantity and date-code scope where required. |
| Loading and handoff | Loading record, container or vehicle reference, and cargo release. | Only approved goods entered the shipment. |
A buyer should state whether date-code details need to appear on the commercial invoice, packing list, certificate, carton label, or a separate attachment. Different products and customers need different document treatments. The critical point is that the factory and buyer know where the date-code scope is recorded and how it relates to the physical goods.
If a date-code discrepancy appears after packing but before release, stop the affected scope, identify the cartons or pallets, preserve photos and records, and decide whether the correction process is authorized. If goods have already moved beyond the factory’s control, follow the buyer’s quality-escape and logistics escalation path. Do not solve the issue by updating only the paperwork.
Use this supplier request wording
The following language can be adapted for a purchase-order quality attachment. It is a commercial date, storage, and release-control request, not a shelf-life determination, stability program, legal labeling rule, or regulatory approval.
For [product and revision], Supplier shall apply and control the date, lot, batch, or other identification required in Appendix A. Before Buyer authorizes shipment release, Supplier shall provide the actual date-code or lot scope, quantity, carton or pallet mapping where applicable, product and revision reference, storage location and status, packing and label verification, and shipment reference. Supplier shall maintain records that link the date-coded goods to the applicable production, inspection, packing, warehouse, and shipment scope. If Buyer specifies an age-on-delivery or remaining-life condition, Supplier shall calculate or report the condition using the date basis, storage condition, and method defined by Buyer and shall identify any mixed date-code, aged, unclear, repacked, relabeled, held, or otherwise exceptional stock before release. Supplier shall not alter, obscure, substitute, rework, repack, relabel, or ship such stock outside the parties’ approved process. Product suitability, stability, regulatory, legal, customer, and safety decisions remain subject to Buyer’s qualified review and separate procedures.
Add the actual product, date definition, code format, storage requirement, lot scope, age-on-delivery rule, evidence list, buyer contacts, language, photo need, document field, confidentiality controls, and release authority before using this wording. A buyer should avoid a generic maximum-age condition if it has not established a product-specific basis.
Common mistakes in shelf-life and date-code control
The first mistake is treating a manufacturing date, packing date, expiry date, and internal lot code as interchangeable. The second is setting a “freshness” rule without a defined product basis. The third is reviewing a single carton photo as evidence for a mixed-date shipment. The fourth is using a date code without linking it to the production, inspection, packing, warehouse, and shipment records. The fifth is correcting a date or label after packing without preserving the underlying identity and approval history.
Another mistake is assuming that old stock is always unusable or that new stock is always suitable. The relevant question is whether the specific product meets its defined storage, date, quality, customer, and release requirements. The buyer should use qualified technical, regulatory, and commercial decision paths when the requirement is safety-sensitive, regulated, contractual, or uncertain.
FAQ
What is China supplier shelf-life control?
It is a buyer process for setting and verifying date, storage, age, rotation, and shipment evidence before goods leave a China factory or warehouse. It links the buyer’s product-specific requirement to actual date-coded lots, cartons, warehouse stock, packing, and shipping records.
Is a manufacture date the same as an expiry date?
No. A manufacture date identifies when a defined production event occurred. An expiry date is a product-specific date that depends on an established basis and applicable storage conditions. A buyer should define which date it needs and how the supplier proves it.
How should I set an age-on-delivery requirement?
Set it in writing only after qualified owners identify the product, date basis, storage condition, shipment or receipt point, calculation method, mixed-lot rule, and evidence needed. Do not use an arbitrary number without a valid product and commercial basis.
What should a supplier provide before shipment?
Ask for product and revision identity, date-code or lot range, quantity, carton or pallet scope where relevant, storage status, packing and label evidence, warehouse status, shipment reference, and any exception involving aged, unclear, mixed, repacked, relabeled, or held stock.
What if the supplier cannot prove storage conditions or date-code scope?
Hold the affected release scope as appropriate, request the available facts and record links, and route the question through the buyer’s product, quality, regulatory, legal, and commercial process. Do not assume suitability from the carton date alone.
Make the date code useful at the release point
China supplier shelf-life control turns a date mark into a verifiable release record. Define the date field and product basis, link date codes to lots and cartons, verify storage and aged-inventory status, confirm packing and shipment scope, and hold exceptions for the right buyer decision before cargo moves.
Supplier Ally can help buyers build date-code requirements, supplier evidence checklists, warehouse-age reviews, carton and lot mapping, and pre-shipment release procedures. The objective is a practical control that connects product identity, date, storage, packing, and cargo evidence before the buyer authorizes shipment.
References
[1] Electronic Code of Federal Regulations, “21 CFR 211.137 Expiration Dating”
[2] Electronic Code of Federal Regulations, “41 CFR Part 101-27 Inventory Management”
EN 
ES 