Terminals & QR Pairing
A terminal is a registered workstation in the warehouse – either a fixed packing station PC or a mobile handheld scanner. Every device works under a terminal, which defines its printers, allowed shipping agents and module settings.
Open: Search (Alt+Q) → MC Warehouse Terminals (terminal list). The list is also
directly accessible from the Dashboard.
Create a terminal
- Open the terminal list → New.
- Fill in the mandatory and basic fields (see below).
- Set printers and – if desired – allowed shipping agents and module overrides.
- Save. The terminal can now register from the app or be paired via QR.
Self-registration
If a user enters a still-unknown terminal code in the app and connects, the app automatically creates the terminal as a Workstation. For full control (printers, agents, overrides), still create terminals in BC beforehand.
Fields
General
| Field | Meaning |
|---|---|
| Terminal Code | Unique code (e.g. PACK-01, MOBILE-03) – mandatory |
| Description | Plain text (e.g. "Packing station 1") – appears in the app header |
| Location Code | Assigned location (controls location-specific counters/documents) |
| Terminal Type | Workstation (fixed) or Mobile (handheld) |
| Enabled | Terminal active – only active terminals receive assignments and count toward the limit |
Status (display only)
| Field | Meaning |
|---|---|
| Active User ID | Currently signed-in user |
| Last Activity | Time of the last activity (controls "online/idle" on the dashboard) |
Printing
| Field | Default | Meaning |
|---|---|---|
| ZPL Printer IP | – | IP address of the ZPL thermal printer (Zebra) for labels |
| ZPL Printer Port | 9100 | TCP port of the ZPL printer (1–65535) |
| PDF Printer Name | – | Windows network printer for A4 documents (packing lists, PDF labels) |
| Auto Print Label | – | Automatically print the shipping label after posting |
| Auto Print Packing List | – | Automatically print the packing list after posting |
Printer IP flows into the QR code
ZPL Printer IP and ZPL Printer Port are included in the QR code –
so the device is ready to print immediately after the scan.
Module overrides
Each of the 11 modules can be overridden per terminal. The override fields have three states:
| Value | Effect |
|---|---|
| Use Global Setting | Adopts the global default from the Setup Card |
| Enabled | Module always on for this terminal |
| Disabled | Module always off for this terminal |
Override fields: Goods Receipt, Goods Issue, Pick List, Item Lookup, Warehouse Activity, Complaint, Return, Putaway, Label Print, Item Weighing.
Behavior overrides:
| Field | Meaning |
|---|---|
| Override Startup Module | Startup module for this terminal only (empty = global) |
| Override Require Weight Entry | Weight entry requirement per terminal |
| Override Require Serial No. Scan | Serial scan requirement per terminal |
| Override Multi-Package | Multi-package per terminal |
| Override Auto-Create Label | Automatic label creation per terminal |
Example: Mobile scanner without packing station functions
A handheld for goods receipt does not need goods issue, for instance. Set Override Goods Issue = Disabled and Override Goods Receipt = Enabled.
Shipping defaults per terminal
| Field | Meaning |
|---|---|
| Default Shipment Provider | Default shipment provider of this terminal (empty = global) |
| Default Shipment Service | Default shipping product of this terminal (empty = global) |
Allowed shipping agents
In the Allowed Shipping Agents subtab of the terminal card, you restrict which shipments appear on this terminal – based on the shipping agent (BC standard "Shipping Agent").
- Empty: All shipping agents are allowed – the terminal sees all open shipments.
- Filled: Only shipments with these shipping agents are displayed and counted ("Goods Issue" badge).
Division of labor by provider
With allowed shipping agents you split the packing stations cleanly – e.g. terminal A for DHL shipments, terminal B for DPD. This reduces search time and misshipments.
QR Pairing
Instead of entering all connection data by hand, you pair a device via QR code.
Generate QR: Terminal card/list → action Show QR Code (page Terminal QR Code).
The QR code contains configuration only, no passwords:
| Field in QR | Content |
|---|---|
v |
Format version (2) |
t |
Tenant ID (Azure AD) |
c |
Entra Client ID (from the setup) |
e |
BC environment name (e.g. Production) |
o |
Company ID (GUID of the company) |
r |
Terminal code |
l |
Location code |
p |
ZPL printer IP |
n |
ZPL printer port |
Pair in the app: Settings → Scan QR. The app adopts all fields automatically and is ready to use after signing in.
Prerequisite: Entra Client ID
For the QR code to contain a valid client ID, the Entra Client ID must be stored in the Setup. Without it, the later sign-in will fail.
Sign-in remains interactive
The QR code only establishes the connection. User sign-in still happens interactively via Microsoft Entra ID (no password in the QR).
Monitor & release terminals
- Online/Idle: The Dashboard shows which terminals are active (based on Last Activity and Terminal Idle Minutes).
- Disable: Set Enabled = No to take a device offline and free up a license slot.
- Stuck lock: If a terminal crashes, resolve remaining locks via Cleanup Expired Locks on the Setup Card.
Next steps
- The App at a Glance – pairing and sign-in on the device
- Dashboard & KPIs – monitor terminals
- Client Installation & Updates – install the app on the devices