LabelCross Print

How to print labels from SAP, an ERP or a WMS

Every order, lot and pallet needs a label, and the data already lives in your ERP or WMS. The question is how to get it onto the right industrial printer, quickly and reliably. Here are the six common integration methods, with their pros and cons.

Updated November 19, 2026 · LabelCross

Why printing from an ERP is harder than it looks

Business systems are good at managing data, not at driving thermal printers. Label layouts change, printers come from different brands and speak different languages (ZPL, DPL, Fingerprint…), and each line, dock or packing station needs its own printer. Building all of this inside the ERP quickly becomes expensive to maintain. Hence the choice of integration method matters.

The six integration methods

MethodHow it worksMain limit
1. Printer driversThe ERP prints like a document to a Windows or CUPS queueSlow, bitmap output, layouts maintained in the ERP
2. Raw printer codeThe ERP generates ZPL or DPL itself and sends it to port 9100Each layout coded by developers, one language per printer brand
3. File dropThe ERP writes a file (CSV, XML, JSON) to a folder watched by a print serverNeeds a shared folder and an export
4. REST APIThe ERP or an application calls a web service with the label dataNeeds a small development
5. Database watchThe print server polls a table and prints new rowsNeeds read access to the database
6. Print captureThe print server emulates a printer and reprints what the ERP sendsThe existing output must contain the needed data

Methods 1 and 2: printing from inside the ERP

Printing through drivers is the simplest start, but labels are sent as images: slower, larger, and barcodes are not generated natively by the printer. Generating raw printer code (for example ZPL — see our ZPL guide) is fast and sharp, but every layout must be developed in the ERP, and a mixed fleet of Zebra and Honeywell printers means several languages to maintain.

Methods 3 to 6: a print server between the ERP and the printers

A label print server separates responsibilities: the ERP or WMS only provides data; the server holds the label templates, chooses the printer and generates the printer language. Changing a label no longer requires an ERP change, and replacing a Datamax printer by a Zebra one does not change anything upstream.

  • File drop is ideal when the ERP can already export files: the server watches the folder, prints, then archives or deletes the file.
  • REST API suits WMS, MES and custom applications: one HTTP call per label or batch, with an immediate answer.
  • Database watch works when the system writes print requests into a table.
  • Print capture requires no change at all: the ERP keeps printing to “its” printer, which is in fact the print server.

Checklist before choosing

  1. Which systems produce label data (ERP, WMS, MES, PLC)? Can they export files or call an API?
  2. How many printers, of which brands and languages, on how many sites?
  3. Who will change label layouts — IT or the business?
  4. What traceability is required: print history, reprint control, audit?
  5. Must data stay on-premise for security or compliance reasons?

How LabelCross Print handles it

LabelCross Print is an on-premise print server that supports methods 3 to 6 — file capture, REST web service with OpenAPI description, database watch, print capture — plus TCP sockets, SFTP and Modbus for PLCs. Labels are designed once in a web designer and printed natively in ZPL, DPL, Fingerprint or cab JScript, with a full print history. See the flow inputs documentation and the compatible printers.

Frequently asked questions

Can SAP print directly to a Zebra printer?

Yes. SAP can send output to label printers, either through printer drivers or by sending native printer code such as ZPL, but each label layout must then be developed and maintained inside SAP.

What is label printing middleware?

A print server placed between your business systems and your printers. It receives the data, merges it with a label template and sends the result to the right printer in its native language.

What is print capture?

The print server emulates a printer: your ERP keeps printing to a queue as it does today, and the server captures that stream, extracts the data and reprints it with your new label design.

Is a Windows driver needed on each workstation?

Not with a print server: it talks to the printers directly over the network, usually on TCP port 9100.

Which method is fastest to set up?

File drop and print capture usually need no change in the ERP. A REST API gives the most control when developers can call it.

Try it with your own printers

Free demo with a download link for Windows, Linux or macOS. No credit card.