🌐 NL · Last reviewed: 27 May 2026
Labels: codes, setup, shipping labels, printers
The full label mechanism is four connected layers: Label Codes (type + report ID), Label Setup (which label code applies per customer/subcontractor/item combination), Shipping Labels (concrete label per bundle/shipment), and Printer Selections Per Area (which printer the label routes to).
The four layers
-
Label Codes — defines available labels (Internal, Customer, Subcontractor, Production). Each code links to a Report ID.
-
Label Setup — rules saying "For customer X + subcontractor Y + item Z → use label code A".
-
Shipping Labels — physical label generated from a bundle. Contains sender, recipient, lot data, barcode/RFID.
-
Printer Selection Per Area — routes label to physical or PDF printer based on warehouse area.
Workflow — printing a label
-
Create a bundle (see previous page).
-
Open Print Labels Dialog from the Shipping Label header.
-
DXSteel uses PrinterSelectionMgtDMX to find the right printer for the warehouse area.
-
The report (Report ID from Label Code) runs, the label goes to the printer.
-
With PrintNode integration, it routes via Aggregated Printers to an external print server.
Key screens
-
Label Codes — label-type master.
-
Label Setup — rule matrix: type × customer × subcontractor × item.
-
Shipping Label and Shipping Label List.
-
Printer Selections Per Area — area → printer mapping.
-
Aggregated Printers — PrintNode integration.
-
RFID Label Print via the LNIPrintRFIDLabel method.
Best practices
Add a catch-all row in Label Setup (no customer, no subcontractor, no item) as the default. DXSteel evaluates rules specific-to-general.
Configure printer selection per location area (e.g. "Warehouse North" → ZebraGK420). In multi-site organisations this prevents wrong-printer mistakes.
[Screenshot: Label Setup with multiple matching rules]