3.3.0 - Labels, Priority Balancing, and Compatibility Improvements

June 29, 2026

Labels / Printing

- Added the new Labels app for Zebra printing in ItemPath 3, including Zebra connection support, integration setup, manual runs, workflow-triggered printing, and run logs.
- Added built-in Shipping Label and Packing Slip document types, along with saved ZPL template support and dry-run preview rendering.
- Improved compatibility for older label-printing integrations by supporting the legacy ItemPath 1 response format when requested.
- Updated the app experience so Labels replaces the older Zebra naming in navigation while preserving existing Zebra-related workflows.

Orders / API Compatibility

- Added opt-in ItemPath 1 request and response compatibility for ItemPath 3 order list, detail, and update endpoints.
- Improved legacy lookup behaviour for order detail and update flows, including handling-unit support for compatible requests and safer UUID miss handling.
- Tightened active-order detail loading so compatibility responses no longer mix active orders with processed or history order lines.

Priority Balancing / Warehouse

- Reintroduced the licensed Priority Balancing app for customers who use metered batch-release workflows.
- Added zone mapping and queue-size controls so operators can manage backlog and queue targets by PowerPick zone from the UI.
- Added scheduled balancing logic in ItemPath 3 to recompute backlog counts and release priorities automatically using configurable app settings.
- Kept Priority Balancing app license-gated so it only appears for customers whose environments are entitled to use it.

Data Pull / Integrations

- Added a warning when Data Pull Update Lines is enabled without an Order Line Number mapping, helping prevent line updates that cannot be matched correctly.
- Kept the warning informational so teams can still save other settings while clearly surfacing the missing mapping requirement.

Reliability / Monitoring

- Improved internal error handling around request and connection failures to avoid reporting known non-actionable issues as application errors.