A manufacturing label version control system should answer one operational question before a printer receives a job: which approved label is valid for this SKU, customer, destination market and production event? A revised drawing is not enough if old artwork remains on a workstation or a roll of preprinted labels remains in storage. This guide explains how to design approval, effective dates, ERP/MES integration, verification, obsolete stock control and acceptance testing as one process for factories in Thailand and elsewhere. Product-specific legal requirements should be confirmed by your quality and regulatory teams.
What a manufacturing label version control system controls
A label printing system primarily handles issuance, numbering, reprints and printer connections. Version control determines which content may be used, under which conditions, after whose approval and from which event. A label may carry a correct serial number and still show an obsolete customer warning. Conversely, a current template can print the wrong lot if ERP or MES supplies the wrong item data. The template, variable data and physical product must be linked.
A version is more than a file modification date. It includes display text, warnings, languages, symbology and encoding rules, artwork, customer specifications, approvals, validity windows and the version it replaces. Product labels, work in process tags, cartons and pallets need separate rules. Inventory every print path: PCs, print servers, machine software, subcontractors and preprinted stock. Deleting a central file does not prevent printing from an unmanaged local copy. Our label printing and numbering guide covers issuance; this article concentrates on selecting and retiring the permitted version.
“Latest” is not a sufficient selection rule
A new version for a Thai customer need not replace a still valid version for another buyer. A new domestic label may be approved while an export translation remains under review. Even the event that determines the effective date can differ: order acceptance, production order release, lot start, print request or dispatch. Selecting the file with the largest version number can therefore select the wrong artwork.
Consider a hypothetical part P supplied to customers A and B. A needs an English and Thai warning, while B has another handling notice. A’s version 2.1 may be active while B’s version 1.8 is still valid. Those numbers are examples, not regulatory limits. The system should resolve exactly one candidate for the tuple of label type, SKU, customer, destination market, packaging level, plant and agreed effective event. Zero or multiple matching versions must stop the job. An operator should not be forced to guess which near match is acceptable.
Emergency artwork must not become an untracked permanent file. Give a temporary version an identifier, authorized approver, affected lots, expiry and return condition. Record why it was needed. If an exception cannot be approved in time, hold the job rather than silently allowing a manual edit.
Fix applicability by SKU, customer, market and effective date
An applicability table needs fields for label type, product, customer, destination, language, packaging level, plant, start and end time and the event whose time is evaluated. Include the timezone. Define overlap detection and the response to ambiguous rules. Priority should come from approved quality and contractual rules, not from which template happens to be first in a folder.
| Design field | Decision required | Failure if left open |
|---|---|---|
| Applicability key | SKU, customer, market, pack level, label type | Another customer’s artwork is selected |
| Effective event | Lot release, production, print or dispatch | Correct date but wrong lot |
| Validity window | Start/end and timezone | Mixed versions on a night shift |
| Conflict | Stop when zero or multiple matches | Operator chooses arbitrarily |
| Exception | Approval, scope and expiry | Temporary art becomes permanent |
Sector and market requirements vary. For example, EU food information rules address the language of mandatory information for consumers in a destination Member State. The US FDA’s medical device Quality Management System Regulation became effective in February 2026 and incorporates ISO 13485 by reference. These are examples of why conditions must be separated by product and market; they do not impose the same label text on every factory. Confirm the current requirements relevant to your product before approving art.
What happens when a lot crosses the effective date?
A lot started on Sunday night may continue after a new version becomes active on Monday. Selecting by print time could put two versions on one lot. Selecting by lot release helps maintain consistency but requires a separate rule if the destination changes during production. There is no universal answer. Put the chosen event, timezone, open lots and already printed stock into the change record. Never overwrite the historical decision when a master record changes later. Store the version ID, rule ID and data snapshot for each print job.
Approval starts before a file reaches production
Useful states include draft, review, approved, scheduled, active, blocked and obsolete. Define who can move a version between them. Artwork staff can prepare a change; quality can verify mandatory content; customer-facing staff can confirm a buyer specification; IT can validate mapping and print behavior. Keep the production release traceable to the people and evidence that approved it.
Approve variable fields as well as the PDF appearance. Specify the source of GTIN, SKU, lot, serial, date, quantity and destination; blank-field behavior; length; date format; and barcode encoding. GS1 Application Identifiers describe data meaning. Parentheses shown around AIs in human-readable interpretation are not characters to encode in the barcode itself. Use the relevant GS1 specification and trading-partner requirements for the chosen symbol.
A change record should contain the reason and originating notice, differences from the prior version, affected combinations, first lot, disposition of existing stock, tests, approvers and timestamps. A side-by-side image helps reviewers, but cannot prove encoded data or printed quality. Link artwork review to decoded barcode values and a physical sample. An immutable version location or file hash can help show that the approved file was the one printed.
Must every SKU be reapproved for a small edit?
Define approval scope by dependency. A shared template component might affect many products; a warning for customer A may affect only A. Trace dependencies from shared component to template, applicability rule and SKU/customer combinations. The change record should list all affected combinations automatically where possible. This makes the review scope defensible without claiming every version is identical.
Control artwork handed to outside parties
Version control extends to artwork studios, printers, packaging suppliers and contract packers. Do not use an email attachment name as the only release instruction. Send the version ID, applicable SKU/customer/market/language/pack level, approved file identity, effective window and old-version disposition together. Ask the recipient to acknowledge the version and quantity, and verify the first delivery after the change. GS1 describes a standardized collaborative packaging artwork process between brands and artwork studios; a company’s approval and physical quarantine still need their own controls.
If an outside printer edits artwork, tie the request, difference, reason, proof and final approval to one change ID. Agree which color or margin adjustments are permitted without a new content approval. Put an approved version ID and validity conditions on the purchase order instead of “latest.” Reconcile old material remaining on the supplier’s shelf and prevent its reuse on the next order. Approve translation meaning separately from the printed form: Thai combining marks and Vietnamese accents must survive the actual printer, material and resolution. Check code quiet zones and text clipping even when only one warning sentence changed. At receipt, link the delivered batch and version ID and compare the first sample with the approved master.
Divide responsibilities across ERP, MES and the print server
ERP often owns orders, customers and product masters; MES often owns production orders, lots and execution events. Actual ownership varies by plant. A version control service can own approved art and applicability rules, while a print server routes authorized jobs to printers. Restrict local template edits on the print server or the central approval can be bypassed.
A print request should identify order, production instruction, SKU, customer, market, lot, pack level, quantity, printer and requester. Resolve the approved version, reject missing or invalid data and return the version ID, rule ID, input snapshot and job ID. Use an idempotency key so a timed-out API request does not silently create two jobs. Distinguish a known failure from an uncertain print outcome; require a physical check before resending the latter.
| Component | Typical ownership | Boundary to test |
|---|---|---|
| ERP | Order, customer, destination and item master | Timing of changed customer data |
| MES | Lot, route and production event | Lot start and version change |
| Version service | Approved art and selection rules | Zero or multiple matches rejected |
| Print server | Queue, printer and reprint log | Local edits and unrestricted reprints blocked |
| Inspection | Data, physical quality and product match | Rejected items actually segregated |
Reliable product and route identifiers underpin label selection. See our manufacturing routing master design guide for that upstream data problem.
Verify encoded data, visible content and print quality separately
A scanner reading a code does not establish that the code contains the right SKU or that the human-readable warning is current. GS1 explains the use of conforming barcode verifiers and application-specific minimum grades. Its DataMatrix guidance covers data and print-quality verification, including ISO/IEC 15415 methodology for 2D symbols. Agree the applicable symbol and specification table before setting pass criteria.
Use three layers. First, decode the code and compare values with the ERP/MES expectation. Second, compare human-readable text, language, warnings, artwork and placement with the approved master. Third, check physical quality: contrast, damage, position, orientation and adhesion. A camera, scanner and verifier perform different jobs; choose the equipment and sampling plan according to the product, line and customer requirement.
Recheck after a roll, ribbon or printer change, a restart, a version cutover and a reprint as specified in the quality plan. Define whether inspection is complete or sampled and how far back to segregate product after a failure. Retain the inspected item, time, lot, version, device, criterion and result. An NG signal must trigger a real stop or segregation action, not merely a screen alert.
Does a 2D barcode eliminate wrong labels?
No. GS1 materials show that GS1 DataMatrix can carry GTIN, lot, expiry and serial data in relevant applications. If the source SKU is wrong, the code may encode the wrong value perfectly. Symbol selection, source-data validation and matching the label to the actual product are separate controls. Check which symbols are allowed by the destination market and trading partner.
Quarantine obsolete labels in both systems and stores
Marking a version obsolete in software leaves preprinted rolls, loose labels, subcontractor stock and device caches. A changeover plan must state when old versions become unprintable, what happens to printed stock, how work in process is treated and who verifies disposition. WHO GMP guidance for pharmaceutical products discusses secure printed-material storage, destruction of obsolete printed packaging material and recorded disposal. That is a sector-specific source and a useful physical-control example, not a blanket legal rule for all manufacturing.
Identify rolls or bundles by version, scan them when issued and compare them with current applicability. Move obsolete stock to controlled storage and remove the digital version from the selection screen. Reconcile receipts, issues, uses, damage, returns and destruction; investigate differences. A matched count alone does not prove the correct label was applied, so connect stock records with lot and carton scans. Include outside warehouses and contract manufacturers in the cutover.
Write an RFP that can be demonstrated
“Supports version control” is too vague. Specify input, expected behavior, refusal behavior and retained evidence. A testable requirement reads: for SKU P, customer A, market TH and lot event t, resolve exactly one approved version; reject zero or two matches; save the rule ID with the print job.
Ask for immutable version and rule history, separated roles, rejection before approval, scheduled activation, obsolete-version blocking, customer/market branching, variable-data validation, decoded-data comparison, quality records, controlled reprints, offline rules and searchable audit evidence. Include machine models, DPI, label stock, ribbon and interfaces in scope. An emergency manual path still needs approver, permitted version, quantity, after-the-fact reconciliation and restoration to normal controls.
Evaluate each requirement as demonstrated, configurable, requiring development or unsupported. Treat old-version blocking and physical segregation as gates, not points that can be offset by a pleasant UI. Compare total scope: master-data cleanup, migration, printer integration, verification equipment, training, support and future customer additions. General prices and durations would be misleading without plant-specific data.
FAT and SAT must include failures
FAT verifies the agreed behavior in the supplier test environment. SAT verifies the solution with the actual plant equipment, network, operators and product. Define representative SKUs, customers, markets, languages, lot boundaries and expected proof before testing. A successful normal print is only one case.
| Test | Required outcome | Evidence |
|---|---|---|
| Unapproved version requested | Reject with reason | Request and refusal log |
| Two versions match | Stop rather than guess | Conflicting rules |
| Effective date crosses a shift | Apply agreed event consistently | Lot, timestamp, version |
| Order changes customer | Resolve a new job | Changed order and job |
| Readable code has wrong value | Reject and segregate | Decoded/expected values |
| Timeout and duplicate request | One job or controlled reprint | Idempotency and reason |
| Network outage and recovery | No uncontrolled replay | Queue and physical count |
| Old stock returned to line | Reject before use | Scan and quarantine record |
During SAT, test that an inspection NG actuates the reject device or operator segregation procedure. Record verifier calibration, materials and lighting. Distinguish machine acceptance from process acceptance. After launch, track wrong-version attempts, overlapping rules, reprints, inspection rejects and obsolete-stock discrepancies by cause.
A practical rollout sequence
First inventory labels by SKU, customer, market and packaging level, and find local copies without an owner. Next define applicability and approvers; use a small set of SKUs to test no match, overlapping match, obsolete art and reprints. Then connect ERP/MES data, printing and inspection and run FAT. Run SAT with physical product and staff before disabling every old print path and reconciling old stock.
A pilot with customer variants and both production and dispatch checks tends to expose design gaps. If the first products are regulated or high risk, the quality team must set a stricter scope and release conditions. Make the source of truth explicit before and after migration. Lock old folders to read-only, inventory caches and local templates, and check Thai and Vietnamese marks on paper, not only on screen. Standardize identifiers and audit fields across sites while allowing local approval for language, customer and equipment differences.
Monitor changes after launch
Register each customer change notice with receipt date, effective date, affected products and plants, destination and approval method. Link it to the version being replaced and work already produced. A disputed interpretation should stay on hold until the responsible function decides. Monitor rejected unapproved print attempts, rule conflicts, missed activations, reprint reasons, inspection rejects and obsolete-stock differences. Initial increases in detected events can reflect better detection; investigate cause and time to resolve rather than treating the count alone as failure.
Close a change only after approval, deployment, first-product verification, shutdown of old print paths, old-stock reconciliation and the first affected shipment are evidenced. Include outsourced printers and warehouses. Across timezones, record both local time and UTC. Periodically start from an actual product and retrieve its version, approver, job, inspection result and dispatch record. That exercise tests whether the trace is usable when an incident occurs.
Frequently asked questions
What drives the cost of a label version control system?
The number of templates is only one factor. SKU/customer/market combinations, approval routes, ERP/MES connections, printer types, inspection devices, old-stock work and sites all matter. Give bidders the same scope and current master-data condition. Align responsibility for version selection and obsolete-stock control before comparing prices.
Is a spreadsheet version register enough?
It can be a starting point for a small, tightly controlled operation. If updating the register does not remove printable old files or prevent direct printer access, the register cannot itself stop a wrong version. You still need demonstrable approval, change history, print-time checking and physical quarantine.
Must the existing printing system be replaced?
Not necessarily. If it can receive the approved version through an API, log version and rule IDs and reject obsolete art, integration may work. If operators can only choose local templates freely, add a central resolution or print-server layer. Test whether reprints can revive an old version.
Are barcode verification and version approval the same test?
No. Approval permits a design under defined conditions. Verification checks the actual printed symbol and content. Product, carton and order matching is another step. Link all three to show that approved information reached the right physical item.
Conclusion
A manufacturing label version control system resolves one approved version for each SKU, customer, market and effective event; links it to ERP/MES values; checks the physical output; and removes obsolete labels from software and stores. Write refusal cases into the RFP and prove them with real data and equipment in FAT and SAT. If your template inventory or applicability rules are still unclear, contact TOMAS TECH to discuss an initial inventory and pilot scope.
