ERP and WMS Integration
Render the labels produced by your warehouse and enterprise systems as a service — with no installation, or on-premise.
The problem
ERP and WMS systems produce labels as ZPL and send them straight to the printer. When you need on-screen preview, a PDF archive or sharing by email, there is no rendering layer in between. Writing that layer in-house means taking on a ZPL parser, barcode encoders and font metrics from scratch — a maintenance burden that isn't your core business.
What does Labelixa do?
A single HTTP call
Your system sends the ZPL in the body and gets a PNG or PDF. No SDK, library or server installation required.
Multi-label PDF and page layout
Get a multi-label ZPL as a single PDF laid out in a grid on A4 or Letter; send it to the warehouse printer in one go.
On-premise deployment
If data cannot leave the organisation, the same service runs on your own server. It is stateless, so migration cost is low.
Quota and usage tracking
A daily request and label counter per API key; see which system produces how much.
Example label
ZPL
^XA
^FO25,20^A0N,26,24^FDWAREHOUSE TRANSFER^FS
^FO25,52^A0N,20,18^FDLocation: A-12-03^FS
^FO25,78^A0N,20,18^FDSKU: SKU-99381^FS
^BY2,3,80^FO25,108^BCN,80,Y,N,N^FDSKU99381^FS
^FO330,108^BXN,6,200^FDSKU-99381|A-12-03^FS
^FO25,215^A0N,20,18^FDQuantity: 240 units^FS
^XZ
Commonly used symbologies
How to integrate
- Send the ZPL your ERP/WMS produces with a test request, unchanged.
- If there is an unsupported command, see it in the warning header of the response — the request does not fail, the unknown command is skipped.
- For multi-label output, set the PDF page size and grid layout.
- If you have an on-premise requirement, bring up the same image on your own server.
ZPL in WMS integrations, in practice
Who generates the ZPL?
There are two models: the WMS emits ready-made ZPL (the template lives inside the system), or the WMS sends data and the template lives with you. In both, the cheapest acceptance-test step is the same: send the generated ZPL to a screen before any printer — a field-mapping mistake shows without spending a single label.
Rack labels: Code 128 or Data Matrix?
A rack label scanned from a distance down a long aisle wants wide-module Code 128; a narrow bin or location label fits the same data into far less space as Data Matrix. The decision is the intersection of scan distance and surface area — render both candidates at real size and scan them before choosing.
Printer fleets and dialect drift
Printers in one fleet can behave differently even within one brand, firmware by firmware. Version the template in one source; roll a change out to the screen first, then one pilot printer, then the fleet. The screen render is the fleet's common reference point.
Before a template change goes live
Rendering the old and new template versions with the same data over the API and comparing the two images makes the claim 'this change only touched the intended field' measurable. That step belongs before rollout — not on the shipping line.
Request an integration assessment
Tell us which system produces your labels and roughly how many you print. We reply by email with what Labelixa can and cannot do for that setup. Labelixa is the preview and conversion layer; your print system stays yours.
Go to the API reference →
Frequently asked questions
Will an unsupported ZPL command stop our multi-label request?
No. The unknown command is skipped and reported in the warning header of the response; the request does not stop over a single command.
Our data cannot leave the organisation — what can we do?
The service can be installed on-premise. Because the rendering layer is stateless, migration cost is low; the installation guide is in the documentation.
Which resolutions do you support?
6, 8, 12 and 24 dpmm — 152, 203, 300 and 600 dpi printers respectively.
