In the ready‑to‑eat, confectionery and bulk‑food sectors, serialisation is no longer optional – it underpins traceability, recall efficiency and compliance with regulations such as the EU Food Information Regulation and the US FSMA. Getting the right supplier for printed codes, data‑matrix labels or integrated smart‑packaging can be the difference between a smooth product launch and a costly compliance breach. This guide walks you through the full sourcing journey, from defining the technical specification to managing overseas risk, and ends with three actionable tips you can apply immediately.
Defining the Technical Specification – What to Include in Your RFQ
Before you send a request for quotation (RFQ), create a serialisation specification sheet that removes ambiguity. The sheet should capture four layers of detail:
- Code format and data model: State whether you need a GS1‑128 linear barcode, a 2‑D DataMatrix or a QR code, and list the exact data elements – e.g. GTIN, serial number (12‑digit alphanumeric), batch/lot, expiry date (YYMMDD) and, where required, a country of origin indicator.
- Print quality and durability: Define minimum module size (e.g. 0.5 mm for DataMatrix), contrast ratio (minimum 3:1), ink type (UV‑curable, food‑grade), and environmental resistance (temperature range –20 °C to +70 °C, humidity up to 90 %).
- Regulatory compliance: Cite the standards you must meet – GS1 General Specification for barcodes, ISO 22000 for food safety management, and, for EU markets, the requirement that the serial number be stored in a centralised traceability database as mandated by the Food Information to Consumers (FIC) regulation.
- Integration and data flow: Explain how the serial numbers will be generated (in‑house ERP, third‑party serialization software) and the file format you will provide to the supplier (CSV, XML). Include a test‑run schedule – for example, “first 5 000 labels must be printed and scanned on our line before full‑scale production”.
Concrete example: A manufacturer of 250 g ready‑to‑eat salads wants a 2‑D DataMatrix on the inner film. The specification states a 2 × 2 mm matrix, 0.5 mm module size, printed with UV‑curable ink, readable after a 30‑second soak at 4 °C, and containing GTIN (14 digits) + serial (10 digits) + expiry (YYMMDD). By locking these details into the RFQ, you avoid later re‑work and costly “code unreadable” rejections on the shop floor.
Vetting Suppliers – Certificates, Audits and Sample Orders
Once you have a shortlist, the verification phase must be evidence‑driven. Rely on three pillars: documented certifications, third‑party audits, and functional samples.
- Certificates: Request current ISO 22000 and ISO 9001 certificates, a valid GS1 Member Organisation registration, and, where applicable, BRC Global Standard for Food Safety accreditation. Verify the certificate numbers on the issuing body’s website.
- Audit reports: Ask for the most recent audit report from an accredited body (e.g. DNV GL, SGS). Pay attention to sections on “Traceability and Serialisation” – a “non‑conformity” here signals a red flag. If the supplier is overseas, request a copy of the local customs clearance audit that confirms their export documentation meets your target market’s legal requirements.
- Sample order protocol: Place a pilot order of 5 000–10 000 units. Test the samples on three fronts: (a) visual inspection for print defects, (b) scanner verification using the same hardware you use on the production line (e.g. Honeywell 1910g handheld), and (c) data integrity by decoding the serial numbers and cross‑checking against the supplied CSV file. Record the reject rate; a rate above 1 % for a pilot run typically indicates a process that will need remediation before full‑scale release.
During the pilot, document any edge cases – for instance, a supplier’s printer struggled with the 0.5 mm module size on a glossy film, leading to a 2 % scan failure that only appeared after the label passed through a cold‑storage tunnel. Capture these findings in a “Supplier Acceptance Report” and use them as negotiation leverage for corrective actions or price adjustments.
Managing Overseas Risks – Common Pitfalls and How to Avoid Them
Outsourcing serialisation to low‑cost regions can be attractive, but it brings specific challenges that, if unaddressed, can derail compliance.
- Language and data‑format mismatches: Suppliers in East Asia may default to Unicode characters for serial numbers, which can introduce invisible characters (e.g., zero‑width spaces) that break downstream scanning. Mitigate this by insisting on ASCII‑only serials and including a checksum validation step in the RFQ.
- Printing technology gaps: Not all label printers can achieve the high resolution needed for sub‑millimetre DataMatrix codes. Request a print‑capability test report that includes DPI (dots per inch) and a sample of a printed code on the exact substrate you will use.
- Customs documentation delays: Missing or incorrect HS codes for “printed label” versus “printed packaging material” can cause clearance holds. Work with a freight forwarder who knows the local export classification and ask the supplier to provide a pro‑forma invoice that matches the final invoice in detail.
- Counterfeit serial numbers: Some overseas printers may reuse serial ranges to reduce setup time, violating the “one‑time‑use” principle of GS1. Include a contractual clause that obliges the supplier to maintain a secure, tamper‑evident serial‑number generation system and to provide an audit trail for each production batch.
- Regulatory divergence: The EU’s FIC regulation demands that the serial number be linked to a traceability database accessible to authorities. If your overseas supplier cannot guarantee data‑security standards comparable to GDPR, you risk non‑compliance. Conduct a data‑privacy impact assessment before finalising the contract.
Edge case example: A UK confectionery brand contracted a Chinese printer for QR codes on seasonal packaging. The printer used a different colour profile, resulting in a low contrast ratio that passed the supplier’s visual inspection but failed the brand’s in‑line scanner when the package was stored at 30 °C for 48 hours – the ink bled slightly, reducing contrast. The brand resolved the issue by adding a clear protective over‑laminate in the next production run, a cost that could have been avoided with a more rigorous pre‑production sample test.
Logistics, Incoterms and Lead Times – Planning for Predictable Delivery
Serialisation projects involve both hardware (printers, applicators) and consumables (labels, inks). Aligning logistics with the technical timeline reduces hidden delays.
- Incoterm selection: For consumable labels, DAP (Delivered at Place) is often safest – the supplier handles export clearance, you control import formalities and can inspect the cargo before it enters your warehouse. For high‑value printing equipment, DDP (Delivered Duty Paid) may be preferable if you want the supplier to manage all customs duties and taxes, reducing surprise costs.
- Typical lead‑time chain: – Specification finalisation: 2–3 weeks – Supplier design review and tooling (if a custom label die is required): 4–6 weeks – Pilot production: 1–2 weeks – Full‑scale run ramp‑up: 1 week per 100 000 units (scale‑dependent) – Sea freight from Asia: 4–6 weeks; air freight: 5–7 days. Add a buffer of 5–7 days for customs clearance and post‑arrival quality check.
- Buffer planning: If your product has a short shelf‑life (e.g., fresh‑cut fruit), aim for a total “order‑to‑shelf” time of under 8 weeks. In such cases, air freight for the first two production runs may be justified, despite higher cost, to avoid stock‑out risk.
- Visibility tools: Use a supply‑chain visibility platform that integrates the supplier’s shipping milestones with your ERP. Real‑time alerts for “container arrived at port” or “label batch cleared customs” help you schedule line change‑overs without idle time.
Practical illustration: A bakery chain ordered 1 million printed serial stickers for its new gluten‑free loaf. By specifying DAP, they received a pre‑cleared pallet in the UK warehouse 2 days before the production start date, allowing a 48‑hour in‑house validation that reduced the risk of a line stoppage. Had they used FOB (Free on Board) and left customs to the buyer, the same shipment was delayed 10 days by an unexpected import duty re‑assessment.
Three Actionable Tips for Procurement Teams
- Lock the data model early and share a “Serialisation Spec Sheet”. Include field length, character set, checksum algorithm and a visual mock‑up. Circulate this document to all potential suppliers before the RFQ deadline to eliminate divergent interpretations.
- Run a pilot batch on your own production line. Even if the supplier’s sample passes a third‑party scanner, only a test on your specific equipment (including any conveyor‑speed variations and temperature zones) will reveal hidden failures.
- Insert a “Right‑to‑Audit” clause with measurable penalties. Define audit frequency (e.g., annual on‑site audit, plus surprise audits for high‑volume runs) and stipulate a financial penalty (e.g., 5 % of the invoice value) for each non‑conformity that exceeds the agreed reject rate.
FAQ
What is the minimum module size for a DataMatrix on a food label? For most retail scanners, a 0.5 mm module size is the practical minimum, provided the contrast ratio meets the 3:1 requirement and the printed area is at least 2 × 2 mm.
Do I need GS1 certification to use serial numbers? While GS1 registration is not legally mandatory in every market, most large retailers and traceability regulations (e.g., EU FIC) expect a GS1‑compliant format. Using GS1 simplifies data exchange with downstream partners.
How can I verify that an overseas supplier’s printed codes are readable after storage? Request a “post‑storage durability test” where the supplier stores a sample batch under your target conditions (temperature, humidity) for the intended shelf‑life period, then performs scanner verification.
Which Incoterm gives me the most control over customs documentation? DAP (Delivered at Place) places import‑clearance responsibility on the buyer, allowing you to ensure that all required certificates and HS codes match your internal records.
What is a realistic reject rate for a pilot serialisation run? For a well‑configured process, a reject rate of 0.5 % to 1 % is typical. Anything consistently above 2 % signals a need for process adjustment before scaling up.
This article is provided for general information and education. It does not replace professional advice.
