GS1 Barcode & Label Printing

The problem

Labels are where a clean F&O warehouse implementation meets the physical world, and it is usually where it breaks. Standard print management handles documents — packing slips, invoices, picking lists — but it was never a label designer. So the labels that actually matter get produced somewhere else: a desktop label application on one PC in the despatch office, a spreadsheet somebody merges into a Word template, or a legacy print server nobody wants to touch.

The result is predictable. A licence plate label prints without the check digit a customer's receiving scanner expects. An SSCC on a pallet does not match what went out on the despatch advice. Warehouse mobile app users complete a put-away step and then walk to a shared printer hoping the right label came out. Someone edits the label layout, nobody versions it, and a month later a retail customer charges back for a non-conformant carton.

GS1 compliance is not optional for anyone shipping into grocery, pharma, automotive or large retail. Application identifiers have to be encoded correctly, the SSCC has to be unique and correctly structured, and the barcode has to be the right symbology at the right density for the scanner reading it.

What ECOSIRE builds

ECOSIRE builds a GS1-compliant label design and printing layer for Dynamics 365 Finance and Supply Chain Management, delivered as an X++ extension model — chain-of-command and event handlers only, no overlayering.

Label templates and design

Label layouts are held as versioned template records in F&O, each bound to a label type — item, licence plate, pallet, location, production output, shipping carton. Templates can be authored as native printer command language (ZPL or equivalent) for direct-to-printer speed and pixel fidelity, or as SSRS report designs where your team prefers to maintain layouts in the standard reporting stack. ECOSIRE builds against whichever approach your label stock, printers and internal skills point to, decided at scoping. Templates are versioned, effective-dated and transportable between environments as a DMF data package, which ends the era of the undocumented layout on one PC.

GS1 encoding done properly

A dedicated encoding service builds GS1 element strings from F&O data with the application identifiers your trading partners require — GTIN (01), batch or lot (10), serial (21), production date (11), best-before (15), expiry (17), SSCC (00), content GTIN (02) and quantity (37), among others. Check digits are calculated, not typed. SSCCs are allocated from a dedicated F&O number sequence scoped to your GS1 company prefix, with an allocation log so a serial reference number is never reused across legal entities. Symbologies covered include GS1-128, GS1 DataMatrix and ITF-14, selected per template.

Printing from the processes that need it

Printing is triggered from the points where labels are actually needed: licence plate creation and consolidation in warehouse work, item receipt and put-away, production order report-as-finished and co-product output, packing station container close, and load or shipment confirmation. For warehouse mobile app users, ECOSIRE adds label print steps and menu items so an operator prints from the device at the moment of the transaction rather than walking to a queue. Reprint is a first-class function with a reason code and a full audit trail, because a smudged label is an operational reality, not an exception.

Printer routing

A printer routing table resolves the destination printer from warehouse, location, work user, workstation or device, so the same mobile flow prints to the right printer in the right aisle. Routing falls back through a configurable hierarchy rather than failing silently. Print jobs are dispatched through the Document Routing Agent for network printers, or to a print service endpoint where your estate uses one. Failures are logged, retried and visible on a print log form instead of vanishing.

Operations and integration

A batch job handles bulk and deferred label runs — reprint a whole pallet, relabel a receipt, produce a run of item labels ahead of a production campaign — using the standard batch framework so it is scheduled and monitored like everything else. Label templates, printer routing, GS1 AI configuration and the print log are all exposed as data entities through the Data Management Framework with OData enabled, so configuration can be promoted between environments and print activity reported in Power BI. Financial dimension defaults on any label-consumable postings follow your existing ledger dimension setup.

Who this is for

Warehouses and plants running Dynamics 365 F&O advanced warehousing that ship to customers with GS1 labelling mandates — grocery and retail suppliers, pharmaceutical and medical device distributors, automotive tier suppliers, food and beverage manufacturers. It suits organisations who have outgrown a standalone desktop label tool and want label design under the same change control as the rest of the ERP.

How delivery works

This app is built to order. There is no pre-built package waiting for download.

1. Scoping call. ECOSIRE reviews your label types, printer models and languages, GS1 company prefix, trading-partner specifications, warehouse processes and F&O version. 2. Fixed quote. A written scope and fixed price are issued before any code is written, including the specific label templates in scope. 3. Build. Development runs against a matching F&O version, typically two to four weeks depending on template count and printer variety. 4. Install in test. The deployable package goes into your LCS project or ADO pipeline and is applied to your sandbox. Your team prints real labels on real stock and scans them with your real scanners before anyone signs anything. 5. Production. After sign-off, the same package moves to production through your release process, with ECOSIRE supporting the cutover. 6. Support. A defect-fix window after go-live covers issues in the delivered code against the agreed scope.

Full X++ source is handed over to your repository.