Configuring Internal and Outbound Shipment Labels

[ 1 Key Configuration Fields ] [ 1.1 Label Assignment Behavior Explained ] [ 1.2 Using Simplate & SQL Logic ] [ 1.3 Reprinting Behavior ] [ 1.4 Administrator Tips ]

WMS+ prints internal and outbound shipment labels based on event triggers configured in the Admin Panel. Administrators assign label fragments and layouts to specific warehouse workflows, define output formats, and map printers to ensure labels are automatically or manually generated at the correct point in the process.

Key Configuration Fields

Label Fragment. Defines label structure and logic using ZPL, Simplate or SQL.
Label Layout. Links a label fragment to a print event, printer and output format.
Print Event. The system event that triggers label printing.
Printer Assignment. Routes output to the correct printer by event or user.
Custom Label Context. An optional logic layer using Simplate or SQL for dynamic label data.
Layout Status. Only active layouts are used in live workflows.

Workflow Type	Print Event	Typical Use Case
Internal	Receiving Complete	After item intake, once batch or quantity is entered
Internal	License Plate Created	On creation of a new LP during intake or transfer
Internal	Production Receipt	When finished goods are received from production
Outbound	Goods Issue Created	When the shipping document is posted
Outbound	Manual Print (Pallets Screen)	User-initiated print of a staged pallet
Outbound	Order Dispatch	When dispatch occurs, often batch-based

All of these must be mapped to a layout in the Admin Panel → Common Configuration → Labels Configuration → Label Layouts Configuration to enable printing.

Label Assignment Behavior Explained

When assigning layouts to print events in the Admin Panel, the system’s label behavior depends on how these events are configured. Misconfiguration can result in silent failures, misrouted prints, or missing labels.

Common scenarios:

Layout correctly assigned to a valid print event
Label is generated automatically at the expected workflow stage. This supports traceability and reduces manual effort.
Event left unmapped
No label is printed. This may cause missing documentation or slow down packing and loading processes.
Inactive layout assigned
The system silently skips label generation. Admins may believe labels are printing when they are not.
Invalid or deprecated event used (e.g. ‘Transfer Issued’)
Layout is ignored entirely. No label is produced, and there is no system alert.
Incorrect printer routing (e.g. sending to a warehouse office printer)
Label is generated but sent to the wrong location, often causing delays or reprints.

Tip: Always validate that layouts are mapped to active print events listed in the Admin Panel, with correct printers and label types assigned.

Using Simplate & SQL Logic

Custom Label Contexts allow labels to include live data from the transaction being processed. Admins can use:

Simplate tokens insert values from the process context. For example:

{{$:@item.ItemCode}} inserts the item code.
{{$:@item.BatchNo ?? 'N/A'}} displays the batch number if available; otherwise, it shows “N/A”.
{{$:@item.ExpiryDate ? format(@item.ExpiryDate, 'MM/dd/yyyy') : 'N/A'}} formats an Expiration Date or shows “N/A” if missing.

SQL queries to fetch SAP B1 values not in the default context:

Example query:

sql
CopyEdit
SELECT ItemCode, ItemName, ItmsGrpCod  
FROM OITM  
WHERE ItemCode = @ItemCode

The variable @ItemCode is mapped to {{$:ItemCode}} inside the label context.

Query results can be used in fragments:

{{#each itemGroupInfo}}
^FDItem: {{$:ItemCode}} - Group: {{$:ItmsGrpCod}}^FS
{{/each}}

The above example assumes the SQL query result is named itemGroupInfo. Update the key name as needed based on your configuration.

Reprinting Behavior

Label reprints are permitted only while the source document remains open:

Allowed: While transfer, staging or if a shipment is still in progress.
Blocked: Once the source document is posted or closed, WMS+ blocks label reprinting to prevent duplication and maintain traceability.
Logged: All print and reprint actions are tracked via Label Watcher.
Controlled: User permissions determine reprint access.

Administrator Tips

Name layouts clearly and version them (e.g., OUT_Pallet_v2025-07).
Test label triggers and output in a non-production environment to confirm correct event mapping and printer routing.
Confirm the fragment and layout status is Active before assigning to events.
Use Label Watcher to debug unexpected output or failed prints.
Keep internal and outbound fragments/layouts separate.
Document Simplate or SQL logic in the description field for future maintenance.