Print Service Settings
The central configuration of the merchantCENTRAL Print Service: auto-print, default and fallback printers, retries, the print queue, print subscriptions and the Poll connection. As with the other merchantCENTRAL modules, it is embedded as the Print Service Settings part in the hub card Extension. There is no separate setup page that search would find.
Opening the Page
- In BC, search for merchantCENTRAL Setup.
- In the Extensions section, choose the Print Service row → action Set Up.
The hub card Extension of the Print Service opens:
| Section | Content |
|---|---|
| General | Among others the Enabled switch, which switches the module on (see Module and License) |
| Extension Settings | The Print Service Settings part with all fields and actions described on this page |
| License | License status of the PRINTSERVICE module |
Name or Set Up?
Clicking the name Print Service in the list opens the Dashboard, not the settings. The Set Up action leads to the settings.
On first opening, the setup record is created with default values.
The Print Service Setup wrapper
When the hub opens the module's setup directly (e.g. from a FactBox), the Print Service Setup page appears. It contains the same Print Service Settings part, plus the License part and the Activate in Hub action, which opens the hub card Extension. If the Hub is not set up yet, it first takes you to the Hub setup.
Fields
Local Print Service App
Instructional text: printing requires the local MC.PrintService on a Windows machine that can reach your printers. The Download Print Service action opens the signed installer (see Installation).
Printing
| Field | Default | Description |
|---|---|---|
| Auto-Print Enabled | off | Shipping labels are printed automatically after creation – on the printer from the routing rules or the default printer. Off: labels are printed manually from the Shipment Labels list |
| Default Printer Code | – | Printer used when no routing rule matches, and for reports without their own printer |
| Routing Rules Enabled | off | Activates the routing rules for shipping labels |
| Fallback Enabled | on | If the resolved printer is offline or in error, a fallback printer is used (see Printers) |
Auto-print
With auto-print enabled, every newly created shipping label is queued immediately. If no suitable printer can be found, a failed print job with the reason is created – the label is not silently lost.
Retry Settings
| Field | Default | Range | Description |
|---|---|---|---|
| Max Retry Attempts | 3 | 0–10 | Number of retries before a print job counts as failed |
| Retry Delay (Seconds) | 5 | 1–300 | Wait time between two attempts |
Maintenance
| Field | Default | Range | Description |
|---|---|---|---|
| Log Retention (Days) | 30 | 1–365 | Printed and cancelled print jobs older than this are removed by the Cleanup Old Jobs action |
| Print Queue | – | – | Shows whether the job queue entry that runs the print queue every five minutes is scheduled: Scheduled or Not scheduled - no retries. New print jobs go out at once without it, but it is the safety net: it retries failed sends and takes the jobs an immediate print task did not reach |
Print queue and immediate printing
Every new print job – from a posting, a new shipping label, printing by hand or a retry – starts a background task that renders and sends it seconds after the commit (with Poll: sends the wake-ping). This never happens inside the posting itself; if the posting fails, the task is dropped as well.
In addition, the app creates a job queue entry (parameter PRINTQUEUE) during installation
that runs every 5 minutes. It is the safety net: it renders reports from posting that no task
reached, returns hanging jobs, sends retries once their delay has passed and, in Poll mode,
the wake-ping. For a company created later, the entry is created the first time the Print
Service Settings are opened (hub card Extension, row Print Service).
Report Printing
| Field | Default | Description |
|---|---|---|
| Print Subscriptions Enabled | off | Activates the print subscriptions (automatic report printing after posting) |
Poll Connection (Azure)
Only for printers with transport mode Poll (Azure Queue) (see Installation, Part B).
| Field | Description |
|---|---|
| Poll Function URL | Base URL of the Azure Function App. BC only sends a short wake-ping there; the Function fetches the jobs itself. Empty: BC stays fully passive and the Function relies on its timer |
| Poll Function Key | Shows Configured or Not configured. Click to enter or change the Function key; it is stored encrypted |
Wake-ping required in production
With a Poll Function URL and Poll Function Key stored, BC tells the Function as soon as a job is ready – it prints within a few seconds. Without the wake-ping, the Function only fetches jobs on its timer, every 5 minutes by default. Check URL and key with the Test Poll Connection action.
Module and License
These two sections belong to the hub card Extension, not to the Print Service Settings part:
| Section | Field / Action | Description |
|---|---|---|
| General | Enabled | Switches the Print Service on in merchantCENTRAL. When it is switched on, the Hub checks the license and offers the demo registration. As long as the module is off, auto-print and print subscriptions stay quiet |
| License | License Status | License status of the PRINTSERVICE module |
| Demo Status, Demo Expiry | Demo only: how long it still runs (or that it has ended) and its expiry date | |
| Register Demo, Refresh License | Unlock a demo license or query the license server again |
Actions
The actions are in the action menu of the part Print Service Settings (not in the action bar of the hub card) and are arranged in three groups.
Installation
| Action | Description |
|---|---|
| Setup Wizard | Assisted setup: local print service, first printer and automatic printing (see below) |
| Download Print Service | Opens the download page for MC.PrintService, pre-filtered to the versions compatible with your installation |
| Open Local Configuration | Opens the configuration page of the local print service (http://localhost:5049/config): API key, printers, agent mode. Works only on the computer where the service is installed |
| 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. Works only on the computer where the service is installed |
| Set up Relay/Poll in Azure | Opens the Azure portal with the template for the Relay/Poll infrastructure in your own Azure subscription and shows the parameters bcCompanyId and bcEnvironmentUrl already filled in. The Function code comes with the template |
| Test Poll Connection | Sends a wake-ping with the stored Poll Function URL and key and shows the Function's answer. Without a working wake-ping, Poll printers only print when the Function's timer runs |
| Clear Poll Function Key | Removes the stored Poll Function key |
Process
| Action | Description |
|---|---|
| Test All Printers | Tests the connection to all enabled direct push printers and updates their status |
| Process Queue | Runs the print queue now: renders the reports from posting, returns direct push jobs that hang in sending to the queue, and sends all due jobs. The same run as on the Dashboard and in the print queue |
| Restart Print Queue | Schedules the print queue's job queue entry, also when it is on hold or in error, and creates it if it is missing |
| Cleanup Old Jobs | Deletes printed and cancelled print jobs older than Log Retention (Days). Failed jobs are kept |
Navigate
| Action | Description |
|---|---|
| Printers | Opens the printer list |
| Print Jobs | Opens the print queue |
| Routing Rules | Opens the Print Routing Rules |
| Print Subscriptions | Opens the print subscriptions |
Setup Wizard
The Print Service Setup Wizard can be reached in two ways:
- Assisted Setup → group AD merchantCENTRAL Setup → Set up the merchantCENTRAL Print Service
- The Setup Wizard action in the action menu of the Print Service Settings (group Installation)
It guides you through five steps:
- Welcome – overview of the transport modes and prerequisites.
- Install the Print Service – actions Download Print Service and Set up Relay/Poll in
Azure; pointer to copy the API key to the clipboard with Copy at
http://localhost:5049/config(it is never shown). - First Printer – code, description, transport mode, print method, printer name or address, ZPL port if needed, and depending on the mode the service URL and API key, the relay function URL and key, or the poll function URL.
- Automatic Printing – Use as Default Printer, Auto-Print Enabled, Print Subscriptions Enabled, Routing Rules Enabled.
- Ready – for Direct Push Test Connection, then Finish.
Running the wizard again
When run again, the First Printer step shows the default printer with its stored values; the code of another existing printer shows that printer. Finish only changes the fields the wizard shows – all other settings of the printer are kept.
Notes
MC.PrintService required
The Print Service requires a running MC.PrintService instance on the customer's network. Without a reachable service, no jobs are printed. See Installation.
What gets printed
The Print Service prints shipping labels, BC reports and raw documents (PDF/ZPL). The Document Type of each print job shows which one it is (Shipping Label, Report, Raw Document).