A batch code is the least glamorous field on a beauty pack, & it is the field that everything else depends on. Sellers normally discover this at the worst possible moment: a customer complaint, a marketplace case, or a distributor asking which consignment received a particular lot. At that point the code on the unit is the only thing connecting the pack in somebody's hand to the tank it came from, the material lots that went into it & the release test that let it leave the factory.
This article covers how batch & date information is usually structured for a brand selling through marketplaces. It sets out what the pack has to carry, how a code is built so that it survives small print sizes, how shelf life, a period-after-opening figure & a printed date relate to one another, how fulfilment centres handle dated stock, which coding methods hold up on a production line, & how a code is read back when a question arrives six months later. It ends with a brief you can send to a factory as it stands.
Why the date code is a key rather than a decoration
Every other record in the chain hangs off one identifier. An email that quotes a batch code gives the factory a manufacturing order, a dispensing record, a filling record, the raw material lots behind each ingredient, the release results & the retained sample still sitting on a shelf. The same email without a code produces a conversation about which shipment it might have been, & that conversation is where most complaints become expensive.
Marketplace hygiene rules regard a date as an inventory attribute rather than as artwork. Where a category holds dated goods, the platform normally expects the seller to declare a date on the listing & to keep a minimum remaining shelf life at the point of receipt, & a fulfilment centre may refuse, quarantine or dispose of stock that falls below the threshold. A date chosen by the design team for legibility, rather than by the brand for a reason, is exactly the kind of field that produces a disposal charge nobody forecast.
The practical consequence is that coding is a brief-stage decision, not a printer's decision. Who generates the code, what it encodes, which surface carries it, whether it appears on the primary unit or only on the carton, & how it is captured in the dispatch record are five answers that have to exist before sampling closes. Answered late, they cost a print plate, a new dieline & a reprint of a whole order.
What the pack carries, & what it should not
Three different things get called a date, & confusing them is the most common source of rework. The first is the date of manufacture, which is a fact about the batch. The second is a date before which the product is at its best, which is a claim about stability & is derived from the testing behind the shelf life. The third is the period after opening, which starts when the consumer breaks the seal & is a separate figure entirely, usually expressed as a number of months inside an open-jar symbol.
A generous printed date is not a marketing freebie. If the pack states a long life, the brand has made a statement it may be asked to support, & the support is a stability file rather than an intention. Sellers are usually better served by a shorter, defensible figure than by a round number chosen to look confident on a listing.
What the pack should not carry is a code that only the factory understands when the market expects a readable date for the consumer, or a date in a format that locals read differently from the way the brand reads it. A numeric date such as 03/04 is read as March in some markets & April in others, & a dispute between two readings of the same six characters is a slow way to lose a customer.
How a batch code is usually built
Most contract manufacturers settle on a structure that is short, sortable & readable at a glance on a pack: a line or site identifier, a date element, a sequence or shift element, & occasionally a formula version marker. A common shape is a two-digit year plus a three-digit day of year, so 26259 means the 259th day of 2026, with a letter appended for the line or shift. It sorts correctly in a spreadsheet, which matters more than most brands expect, because the first useful thing anyone does with a code list is put it in date order.
The design constraint is the print, not the database. On a tube, a crimp, a blister foil or a 3ml ampoule the code may be printed at a character height of a millimetre & a half, in a dot-matrix font, on a curved or reflective surface. That rules out characters that look alike: I & 1, O & 0, S & 5, Z & 2, B & 8. A code convention that excludes the ambiguous letters costs nothing at the design stage & removes a whole class of transcription errors at the packing bench.
Uniqueness is the other constraint, & it is a two-party problem. A code has to be unique within the factory across every client it runs for, not only within one brand's orders, because warehouses, freight forwarders & returns centres hold stock from many sellers at once. Where two brands share a base formula, the codes must still be separable, & that is worth confirming in writing rather than assuming.
Shelf life, the open-jar figure & how the two pair up
The two figures answer different questions & they are frequently set without reference to each other. Shelf life covers the sealed unit & runs from production, which is why the code matters to it: the code records the start of the clock. The open-jar figure covers the unit after first use, under the conditions the pack assumes, & it runs from the consumer's first opening rather than from the factory gate.
Where the pairing goes wrong is a long open-jar figure attached to a short shelf life, or the reverse. A formula supported to eighteen months sealed & twelve months after opening is internally consistent. A formula supported to eighteen months sealed & twenty-four months after opening is a statement with nothing behind it, & it tends to surface when a retailer's own chemist reviews the file.
Not every market requires a printed date, & where one is required it is often triggered by the shelf life falling below a threshold rather than applying to every product. Because those triggers differ, the date element on the pack should be settled per destination rather than once for the whole range, & the seller is the party who knows the destination mix. A factory can hold the record that proves the figure; only the brand can decide which markets it is asserting the figure in.
Where fulfilment centres change the requirements
A fulfilment centre is an operational environment, & its rules are written for scanning rather than for reading. Dated inventory is normally declared in the seller account, with a removal or disposal instruction for stock that ages past a threshold, & the receiving process may count & check a sample of units against the declared date. A date the seller never entered, or entered inconsistently across shipments, shows up later as an unplanned removal fee or a blocked inbound.
The second effect is label placement. Prep services apply a fulfilment label to a unit that already carries an ingredient panel, a batch code, a date, & often a barcode & a net content statement. Unless the instruction states which panel must stay clear, the label lands wherever the operative finds space, & a covered code is functionally a missing code. The cheap fix is a line in the packing instruction naming the panel to leave free, with a photograph of an approved finished unit.
The third effect is pooling. Where a platform combines identical SKUs from different sellers in one bin, the only separator between your stock & another seller's stock is what is printed on the unit. A brand that prints its code on the carton only has, in that environment, no separator at all, which is how a complaint about somebody else's storage can arrive in your account.
Alcohol & fragrance add a fourth layer that has nothing to do with dates. A high alcohol content fixes a flash point, which drives the hazard classification, the safety data sheet, the packing instruction & the choice of air or sea freight. A brand moving a mist or a perfume from sea to air to hit a launch can find that the transport documentation, rather than the freight cost, sets the schedule.
Coding methods & how each one fails
The table below compares the coding routes normally available on a beauty line, where each one suits, what drives its cost & the failure that turns up most often in practice. It is a comparison of fit & risk rather than a price list, because the cost of any method depends on the run length & the packaging supplier.
| Method | Where it suits | What drives cost | Usual failure |
|---|---|---|---|
| Continuous inkjet on line | Tubes, bottles, cartons | Print head, ink, maintenance time | Faint or smudged print on a curved or shiny surface |
| Thermal transfer overprint | Labels & flexible film | Ribbon consumption per unit | Ribbon wear mid-run producing half-legible codes |
| Hot stamp foil | Cartons, folding boxes | Die & foil per design change | Damage to carton graphics if the stamp is mis-registered |
| Laser marking | Blister foil, caps, rigid packs | Capital cost amortised over volume | Contrast too low to read on a light substrate |
| Pre-printed on the pack | Long runs of one specification | Plate cost & minimum print quantity | Dead stock when the formula or market list changes |
| Applied label at packing | Short runs & multi-market stock | Labour per unit & label stock | Label lost, skewed or applied over another field |
| Hand stamp or pen | Sample & small trial quantities | Negligible | Illegible entries that cannot be searched later |
Read the table as a comparison of fit rather than of quality. A short launch run in three markets often suits an applied label better than a pre-printed pack, because the flexibility is worth more than the unit cost saved. A high-volume single-market line is the opposite case, & both answers can be right for two brands ordering the same formula.
Reading a code back: the register that makes it work
A code is only useful if something in the building can resolve it. The joining document is a batch register that ties each code to its production date, its formula version, the material lots dispensed, the filling line, the quantity produced, the release outcome & the markets the batch was cleared for. Without the register the code is a string of characters; with it, the code is a query.
The second join is dispatch. A dispatch record that carries the batch code against each consignment is what allows a brand to answer the forward question, which is the one that arrives during an incident: which customers received this batch, in what quantity, & when. Adding a batch column to the order system & the packing list costs nothing at the design stage & saves days later.
The third join is physical. Retained samples should be labelled with the same code & stored against the same register, so that a request for a specific batch resolves to a position on a shelf rather than to a search. A shelf of bottles with no register is a collection, not a retention programme, & a retention programme is what a serious buyer asks about during qualification.
Codes in bundles, sets & repacked units
A bundle is a new unit in the eyes of most systems, & it needs its own identity even though its parts already have codes. The components keep their own markings, & the bundle carries its own code &, where dates are declared, its own date. That date is normally derived from the earliest component date rather than from the day the bundle was assembled, because the consumer's clock runs on the oldest item inside.
Where a fulfilment partner assembles the bundle on your behalf, the link between the bundle code & the component codes has to be written into the kitting instruction. Otherwise the assembled unit arrives with a code that nobody can decompose, & the record stops at the outer box. This matters most for gift sets, where two products with different shelf lives are combined for a seasonal window.
Repacking after a return is the harder case. A unit that has left the fulfilment centre, been opened & come back is not the same product, whatever the pack looks like, & putting it back into sellable stock without a decision on its condition & its date is a habit that eventually produces a complaint that cannot be answered. The tidy approach is a documented rule: which returned units may be re-sold, which are quarantined, & who signs that decision.
What goes wrong in practice
The failures are boring & repetitive. A printer date left on yesterday's setting after a midnight shift change, so the code & the record disagree. The same code issued twice because two lines generated it independently. A date printed in a format the factory reads one way & the marketplace interprets another. A code applied to the carton when the specification called for the primary pack, discovered at the warehouse rather than on the line.
The control that catches most of them is a first-off check: the first unit off a line is inspected against the work order, the code, the date & the artwork before the run proceeds, & the check is recorded with a time & a name. Periodic checks during the run catch a printer that drifts, which is common on long runs & on foil.
The second control is a reconciliation at the end of the batch, comparing the quantity produced & the codes issued against the codes recorded in the register. A batch that produced more units than codes issued, or fewer, is a signal worth reading immediately rather than at the next audit.
Fragrance, allergens & the fields that move with the code
Where a fragrance is present, the pack normally has to declare the fragrance allergens present above the applicable threshold, & the underlying declaration comes from the fragrance house. The declaration belongs to a compound version rather than to a scent name, so when the level or the compound changes, the declaration & the pack both move. Codes are what let a brand show which version was in which batch, which is why a code change is often the first visible sign that a formula changed.
The same logic applies to the allergen list itself. That list is reviewed periodically, & a formulation that is compliant now can need labelling work later when a substance is added or reassessed. A brand holding a batch register can identify which stock carries which declaration without opening a single carton.
Alcohol-based formats sit alongside this rather than inside it. The flash point determines the transport classification, the safety data sheet & the packing instruction, & those documents sit next to the batch record rather than in the artwork file. When a marketplace asks for documentation on a flammable liquid, the batch code is what ties the request to the consignment that was actually shipped.
What to put in the brief
Give the factory the destinations & the channels, because the date field, the required documentation & the fulfilment rules all follow from those two lines. Then say who inside your brand owns the code convention & the date figure, so that the answer is a decision rather than a debate between the designer & the formulator.
- The markets the product is sold in, & whether any require a printed date or a period-after-opening figure.
- The shelf life the brand intends to claim, & the stability data behind it.
- The open-jar figure, if the pack carries one, & how it was set.
- The code convention, including which characters are excluded & who generates the number.
- Whether the code goes on the primary unit, the carton, or both, & the panel to be left clear for any label.
- The recommended storage conditions, since they affect both the code & the marketplaces that ask about temperature.
- Any bundle, set or gift pack, & which component date governs the assembled unit.
- The batch-level dispatch field on the order system, or the plan to add one before the first shipment.
Then agree how a code question will be answered after the launch. A named contact, a stated response time for a batch record request & a quarterly check that the batch register still matches the retention register turn the whole system into routine work. A coding scheme that is only tested when a customer complains is not a system, it is a reconstruction.
Where our capability fits
We generate & record a batch code for every order, link it to the manufacturing order, the material lots, the filling record & the retained sample, & we can walk a code back to those records on request rather than rebuilding the history from memory. Codes are assigned uniquely across the factory rather than within one client's orders, so two brands running a similar base never share an identifier. Where a fragrance or an alcohol level changes, the allergen declaration & the transport documentation are updated through the same change control as the formula.
We work with brands on private label (your brand on a proven base), OEM/ODM contract manufacturing & full custom formula development, & the coding & date fields are settled at sampling rather than at the printer. Our lines include a blister-packed argan hair oil capsule set, custom softgel face serum capsules & Moroccan hair oil softgel capsules, all of which carry a code on the primary unit as well as on the carton.
Tell us the destinations, the shelf life you intend to claim & the channels you sell through, & we will come back with the code convention, the date fields, the panels to leave clear & the documentation that ships with each batch. Start at our inquiry page, email capsulebiotech@163.com, or message the right team on WhatsApp: Capsule Series (capsules only) +86 158-7655-5319, Cosmetics Series (serum, hair care, body care, fragrance) +86 158-7655-5319. The barcode side of retail pack data is covered in our guide to barcodes & GTINs, & the testing behind a date figure in our article on stability testing & shelf life.
General manufacturing information, not regulatory or legal advice. Date formats, shelf life rules, labelling duties, allergen thresholds & marketplace inventory policies vary by market & change over time, so the position for a specific product should be confirmed with a qualified advisor before it is placed on sale.