The complete e-Mark readiness checklist

Most companies discover the same thing in the same order: registering in e-Mark is not the hard part — the form itself takes an afternoon. The hard part is everything the form assumes you already have. Almost every delay we see in a marking project traces back to preparation that was skipped, and because marking sits on top of a physical process, each gap stops production, shipment or sale rather than just a spreadsheet. This is the full sequence, condensed into one checklist. Step 1 — Confirm you are actually in scope Check the current product group schedule on the official e-Mark resources: which categories are mandatory now, and which have announced start dates. Do not rely on an article from last year — the schedule is revised, and both a false alarm and false comfort cost money. If your category has a date, work backwards from it. Registration, data preparation and equipment all have to be finished before the first mandatory day, not on it. Step 2 — Prepare the company file You need the legal essentials in one place: registered company name exactly as filed, tax number, legal address, authorised signatory and an active electronic signature. A mismatch between your tax records and what you type into e-Mark produces the kind of support ticket that takes weeks to clear. Decide who the responsible person is once — if the signatory changes later, you plan for re-authorisation. Step 3 — Build the product catalogue before you open the form This is where most registrations stall. Every product that falls under marking needs a card, and you have to be honest about variants: each size, volume, flavour or pack type is normally a separate item with its own barcode. Companies routinely register the flagship product, forget the 0.5 L version, and then halt a line while the missing card clears. Count the real assortment, not the price list. Step 4 — Fix barcodes and classifier codes Each item needs its GTIN — the EAN barcode you already print — and its code in the commodity classifier. If some products never had a proper GTIN, resolve that now; improvised internal codes will not pass. For classifier codes, check the current version rather than an old spreadsheet, because codes shift between revisions. Our free ATGAA code search covers all 962 codes if you need to look one up. Step 5 — Decide your packaging levels Write down how a unit becomes a case and a case becomes a pallet, because that hierarchy is what aggregation encodes. If you cannot describe it on paper, no system can automate it. This is also the point to decide which level gets scanned at dispatch — getting that wrong is what turns a two-second shipment scan into a two-minute one. Step 6 — Register, then order a test batch Only now open the form. Complete registration, then request a small batch of codes and run it end to end before you commit a production run: generate, print, apply, scan back, aggregate, record the movement. A test batch surfaces the problems that no amount of planning finds. Step 7 — Check the software layer The system of record is where product data lives, where codes are requested and tracked, and where circulation status is reconciled against your ERP and warehouse records. Get this wrong and everything downstream inherits the error — a code issued against bad product data is still a code you have to account for later. Step 8 — Check printing and scanning, together A DataMatrix that looks perfect on screen can fail on packaging: too small, too low-contrast, printed on a curved or reflective surface, or applied at a line speed the printer cannot sustain. Test print settings against your actual packaging, not a sample sheet. Then test reading it back where it will really be read — on the warehouse floor, in a cold store, at a checkout, on a worn label. Software, printer and scanner have to work as one; missing any of the three means the other two do not matter. Step 9 — Plan API integration around a process you already understand API integration is worth doing when volumes make manual entry expensive, but it only helps if the workflow is already clear. A system cannot automate confusion — it can only automate a defined process. Before a developer opens the documentation, the business should be able to say what each step means: which data is sent, which codes come back, how warehouse movements are reflected, and what a report has to match. Assign the internal owner for each of those before the technical work starts. What good preparation looks like When these nine steps are done, the team sees one process instead of a pile of codes: the product was received, the code was printed, the package was aggregated, the movement was recorded, and the report is ready. Start with one product group or one line, prove it, then extend. A small measurable release is safer than replacing the whole chain at once.