Label Engine: EPP
Print Envoy supports enterprise labeling environments and connects D365 to leading enterprise labeling platforms, including Enterprise Printing Platform (EPP).
What is EPP?
EPP (Enterprise Printing Platform) is a label engine that processes print requests, generates printer-ready output, and tracks print jobs for monitoring and reprint workflows through features like Printer and Job Monitor and Reprint.
What you get with EPP
Multiple print request methods (XML, JSON, ULD) depending on your integration style
Job visibility and reprint workflows with print history stored in PostgreSQL
Flexible printer connectivity (SOCKET or LOCAL printer profiles)
Advanced label designer capabilities like multi-up printing and dynamic graphics
How Print Envoy connects D365 to EPP
1
D365 Creates The Label Request
Receiving • Picking • Production • Shipping
2
Print Envoy Routes The Request
Rules • Printer selection • Site/warehouse routing
3
EPP Processes The Label Output
Templates • Enhancements • Print-ready data
4
Prints to the right printer & location
Distributed operations • Cloud printing
EPP is designed to integrate with different file types and delivery methods, support multiple ERP systems, and print to hundreds of printers (industrial, mobile, desktop).
EPP Print Request Formats
XML print requests
- Common for Web Service requests; only format for Socket Listener
- Supports multiple templates per request body but one printer destination.
JSON print requests
- Supported starting EPP 10.1.0.0 for Web Service + File Drop
- Multiple templates per request body but one printer destination.
ULD print requests
- Parameter-based batch format; first line defines label/printer/copies/layout
- Each line prints another instance of the same label to the same printer.
Printer Connectivity Options
SOCKET
EPP can check printer conditions/states; monitoring can send more frequent status commands (paused, out of stock, open, jammed, etc.).
LOCAL
Jobs route through Windows Spooler or Linux CUPS on the machine running the EPP service.
LOCAL is recommended when printers are using language emulation that may not support native status checks expected by SOCKET.
Supported Printer Languages
ZPL
IPL
PCL5e
SBPL
PGL
DPL
Monitoring, Reprint, and Print History
EPP stores print request history in PostgreSQL (eppPrintJobContainer) used for job management, dashboard status counts, monitoring, and reprint searches/resubmissions.
The community guidance recommends keeping the table under ~200,000 records to reduce performance risk and trimming periodically.
EPP 10.0.1.0+ includes an option for automatic purging by “days to retain” and selected job statuses (not enabled by default).
