Printers
Management of all printers controlled by the merchantCENTRAL Print Service. Each printer has its own transport mode and its own connection to an MC.PrintService.
Opening the Page
- Via search: Printers (Print Service list)
- Via the Dashboard → Printers
- Via the Print Service Settings (action menu of the part → Navigate) → Printers
Printer List
Fields (List View)
| Field | Description |
|---|---|
| Code | Unique short code of the printer (e.g. LABEL-01, ZPL-WH). Referenced in routing rules, print subscriptions and print jobs |
| Description | Descriptive name (e.g. "Zebra ZD421 Warehouse 1") |
| Print Method | PDF (Windows printer driver) or ZPL (direct printing to Zebra thermal printers) |
| Status | Last known status: Not checked yet, Online, Offline or Error |
| Enabled | Whether the printer may be used for print jobs |
| Service URL | Address of MC.PrintService (Direct Push only) |
| Pending Jobs | Number of jobs Queued or Sending for this printer |
Actions (List)
| Action | Description |
|---|---|
| Test Connection | Tests the connection to the selected printer (see below) |
| Test All | Tests all enabled direct push printers and updates their status |
Create new printers with New; the printer card opens.
Printer Card
General
| Field | Description |
|---|---|
| Code | Unique short code (required) |
| Description | Description of the printer |
| Enabled | Enables or disables the printer. New printers are enabled |
| Is Default | Shows whether this printer is the default printer in the Print Service Settings (read-only; change it with Set as Default Printer) |
Connection
| Field | Description |
|---|---|
| Transport Mode | How print jobs reach this printer: Direct Push (straight to the service URL, fixed public IP needed), Relay (Azure Queue) (BC puts the job into a queue in the customer's Azure) or Poll (Azure Queue) (the Function fetches the jobs from BC). Controls which fields are visible. A change resets Status, Last Status Check and Last Error Message (Not checked yet) |
| Service URL | (Direct Push only) Address of the MC.PrintService instance, e.g. https://print.customer.com. http:// only for localhost/127.0.0.1 |
| API Key | (Direct Push only) Shows Configured or Not configured. Click to paste the API key you put on the clipboard with Copy in the service's configuration UI – it is never shown there. BC sends it as header X-Api-Key |
| Printer Name | For PDF the exact Windows printer name on the service machine, for ZPL the IP address of the Zebra printer |
| Print Method | PDF: the document is printed through the Windows printer driver. ZPL: the label is sent as ZPL code via TCP/IP directly to the Zebra printer |
| ZPL Port | (ZPL only) TCP port of the Zebra printer (default 9100) |
Relay (Azure Queue)
Visible only with transport mode Relay (Azure Queue).
| Field | Description |
|---|---|
| Relay Function URL | Base URL of the Azure Function App in the customer's Azure (e.g. https://mcpsrelay-func-….azurewebsites.net). Must use https:// |
| Agent | Only when several computers print via Relay/Poll: name of the computer that prints for this printer, e.g. LAGER. Its service listens to the queue print-jobs-<agent> (in lower case), which the Azure deployment creates for every name in the parameter agentNames. Letters, digits and - _ . are allowed. Empty = one computer prints everything |
| Relay Function Key | Shows Configured or Not configured. Click to enter the Function key; BC sends it as X-Functions-Key when enqueuing a job |
Poll (Azure Queue)
Visible only with transport mode Poll (Azure Queue). Note: the Azure connection for Poll printers is configured centrally in the Print Service Settings. The printer only needs a Printer Name and Print Method – and, with several printing computers, the Agent field:
| Field | Description |
|---|---|
| Agent | As with Relay: name of the computer that prints for this printer (queue print-jobs-<agent>). Empty = one computer prints everything |
PDF or ZPL?
PDF: for all printers with a Windows driver (laser, inkjet, thermal). The service renders each page at 300 DPI, keeps the aspect ratio, and picks a matching paper size and orientation where the printer offers them. ZPL: for Zebra thermal printers on the local network. No driver needed, highest speed. The service only connects to printers in private networks on the printer ports 9100–9103 and 6101 (adjustable, see MC.PrintService – Reference).
Multiple locations
Each printer can have its own connection. With Direct Push, printers at different
locations (e.g. warehouse 1 and warehouse 2) can therefore be controlled through separate
MC.PrintService installations. With Relay/Poll, one computer is often enough: the service
addresses ZPL printers by their IP address on the network, only PDF printers have to be
installed on the computer. If several computers still print on different printers, the
Agent field names the computer, and the Azure deployment gets its name in the parameter
agentNames (see Installation – Several computers).
Fallback
| Field | Description |
|---|---|
| Fallback Printer Code | Printer used when this printer reports Offline or Error. Only printers with the same print method are offered; a printer cannot be its own fallback. Empty = no fixed fallback printer |
If Fallback Enabled is set in the Print Service Settings and the resolved printer cannot be reached, the fallback printer entered here is used first – provided it is enabled and Online. Otherwise, the Print Service takes another enabled printer with status Online and the same print method. A fallback printer is not chained any further.
Status
| Field | Description |
|---|---|
| Status | Connection status (read-only). Updated by Test Connection and by the results of print jobs. A new printer, or one whose transport mode was changed, shows Not checked yet |
| Last Status Check | Time of the last status check |
| Last Error Message | Last error message of this printer |
Statistics
| Field | Description |
|---|---|
| Total Jobs Printed | Number of successfully printed jobs |
| Pending Jobs | Jobs Queued or Sending |
| Failed Jobs | Failed jobs of this printer |
Actions (Card)
| Action | Description |
|---|---|
| Download Print Service | Opens the download page for MC.PrintService |
| Open Local Configuration | Opens the configuration page of the local print service (http://localhost:5049/config): API key, printers, agent mode |
| Check Local Print Service | Opens the status page of the local print service (http://localhost:5050/health); it shows that the service is installed and running on this computer |
| Test Connection | For Direct Push: calls the service at the Service URL with the API key and sets the status to Online, Offline or Error. Relay and Poll printers cannot be reached directly from BC; their status follows the results the agent reports |
| Set as Default Printer | Makes this printer the default printer in the Print Service Settings. It receives labels no routing rule matches, and reports without their own printer |
| Clear API Key | Removes the stored API key |
| Clear Relay Function Key | Removes the stored Relay Function key |
| Print Jobs | Shows the print jobs of this printer |
Download Print Service, Open Local Configuration and Check Local Print Service are in
the Installation group. The two local actions open localhost and therefore only work on the
computer where the print service is installed.
Setting Up a New Printer
- Install MC.PrintService: on a machine that can reach the printer (see Installation).
- Create the printer: in the printer list → New → enter Code and Description.
- Configure the connection: choose the Transport Mode and, depending on the mode, enter the Service URL and API key (Direct Push) or the Relay Function URL and key (Relay). With Poll there is nothing to enter – the connection is stored centrally in the Print Service Settings. Then Printer Name and Print Method. When several computers print via Relay/Poll, also the Agent field.
- Test Connection (Direct Push): Status must show Online.
- Optional: Set as Default Printer.
Setup Wizard
The Setup Wizard also creates the first printer (see Print Service Settings).