Printing without the
print dialog
Shipping labels print the moment they are created, delivery notes and invoices right after posting: merchantCENTRAL Print Service sends them from Business Central to the printers in your warehouse and office – as PDF or ZPL, with nobody pressing Print. Your print data never passes through our infrastructure.
How does Business Central online print straight to your printers?
Business Central online runs in the cloud and cannot address the printers in your network directly. Print Service closes that gap with a small Windows service, MC.PrintService, on a machine in your network. It accepts the print jobs from Business Central and passes them on: PDF to any Windows printer, ZPL over TCP/IP straight to Zebra label printers. Printing happens on its own – labels when they are created, reports after posting.
From label to invoice – on the right printer
Two triggers print on their own, rules pick the printer, and a queue makes sure no job disappears unnoticed.
Labels the moment they exist
Shipping labels from the merchantCENTRAL carrier connectors print right after they are created. To reprint or print by hand, use the Shipment Labels list and pick printer and copies in the dialog.
Printed after posting
Print Subscriptions print a Business Central report of your choice once a sales shipment, sales invoice, credit memo, warehouse shipment, transfer shipment or purchase receipt is posted – any report that needs no mandatory input on its request page, with a number of copies and, if you like, for one location only.
Routing rules
Rules checked by priority, built from carrier, format and location: DHL labels from warehouse 1 to the Zebra in warehouse 1, everything else to the office printer. A PDF label never goes to a ZPL printer.
Fallback printer
When a printer reports Offline or Error, its fallback printer takes over – only one with the same print method, and only if Fallback Enabled is on in the Print Service Settings. If no rule applies, the default printer prints.
Print queue
Every job ends printed, failed with its reason, or cancelled. Connection errors are retried automatically, and a failed job goes out again with one click.
A dashboard that explains silence
Open, hanging and failed jobs, what printed today, and which printers are reachable. When nothing prints, the notice What limits automatic printing names the reason and what to do about it.
Printing happens after posting, not inside it
The posting only writes the print job. A background task of its own renders the report seconds after the commit and sends it – an error while rendering or printing can never affect the posting.
- Immediate printingEvery new job – from a posting, a label, a manual print or a retry – goes out seconds later. With Poll only when the wake-up ping is set up, otherwise on the Azure Function's 5-minute cycle.
- A safety net every 5 minutesA job queue entry sends retries and picks up anything a task did not reach.
- Location from header or linesIf a document carries its location only on the lines, the one location all lines share counts. Warehouse and transfer shipments always use the header.
- Several subscriptions per eventThe delivery note on the office printer and a second report in the warehouse – all of them fire.
- Reports always as PDFRendered for exactly the posted document, without a request page. Only PDF printers qualify as targets.
Three ways from the data centre to your printer
The transport mode is chosen per printer, and modes can be mixed. In none of them does print data pass through ALTENBRAND infrastructure: with Direct Push it goes straight to your service, with Relay and Poll through your own Azure subscription.
| Direct Push (default) | Relay (Azure Queue) | Poll (Azure Queue) | |
|---|---|---|---|
| How the job arrives | Business Central calls the service at your public HTTPS address | Business Central puts the job into a queue in your Azure | An Azure Function in your Azure fetches the jobs |
| Inbound port opening | required | not required | not required |
| Fixed public IP address | required | not required | not required |
| HTTPS certificate | managed by you | not needed | not needed |
| Outbound calls from Business Central | yes | yes, job including label | only a short wake-up ping |
| Your own Azure subscription | not needed | yes, a few euros a month | yes, a few euros a month |
Relay and Poll take more setup than Direct Push: the action Set up Relay/Poll in Azure opens the Azure portal with a ready-made template for the resources. After that, the script grant-bc-access.ps1 gives the function access to Business Central, it is registered under Microsoft Entra Applications with a permission set, and the keys go into Business Central and, by hand, into the service's appsettings.json. This needs administrator rights in Azure and Microsoft Entra. In operation the service holds a single outbound connection over port 443; if several machines print to different printers, each gets a queue of its own.
A Windows service next to your printers
MC.PrintService is installed once on a machine that runs permanently and can reach the printers. The download is linked from Business Central; the setup wizard takes you through the download, the first printer and automatic printing.
Installation
The recommended route is the signed MSIX package through the Windows App Installer: a Windows service that starts automatically and keeps itself up to date. The .NET runtime is included. For Windows Server 2016/2019, where MSIX does not run, ALTENBRAND provides a ZIP package with Install.bat – without automatic updates.
Operating system
Windows 10 version 1903 or later, Windows 11, or Windows Server 2022 or later (64-bit); Windows Server 2016/2019 only with the ZIP package. There is no container – PDF printing needs the machine's Windows print spooler.
Printers
PDF: any printer with a Windows driver on that machine – laser, inkjet, thermal. ZPL: Zebra thermal printers such as the GK420, ZD421 or ZT411 over TCP/IP on the local network, no driver needed.
Delivery notes carry customer addresses
That is why the service accepts no job without its API key, Business Central prints to remote addresses over HTTPS only, and your firewall can, if you want, let Business Central through and nothing else.
An API key from the service
The service creates its own key on first start and accepts no print job without it – not even from its own machine. The key is never displayed; in Business Central it is stored encrypted in the merchantCENTRAL credential store.
HTTPS required
For remote addresses the app accepts https:// only, and Business Central validates the certificate – self-signed certificates do not work. A reverse proxy with a Let's Encrypt certificate is the proven setup.
A firewall for Business Central alone
With Direct Push, the opened port can be restricted to the Azure service tag Dynamics365BusinessCentral. The service only talks to ZPL printers in private networks on printer ports – adjustable if your network differs.
What you need
Business Central & hub
Microsoft Dynamics 365 Business Central online version 28 or later, Essentials or Premium, and the free hub app AD merchantCENTRAL. Available in Germany, Austria and Switzerland.
One machine on your network
A Windows machine that runs permanently and can reach the printers. Direct Push also needs a fixed public IP address, access to your router or firewall and a valid HTTPS certificate.
For Relay and Poll
Your own Azure subscription with the Owner role (or Contributor plus User Access Administrator), and for granting access to Business Central the Entra role Privileged Role Administrator or Global Administrator. The setup wizard does not cover these steps; the guide describes them.
€39 per 4 weeks
Net, per tenant, billed every four weeks from activation – not by calendar month. The first 30 days are free. The licensed module is PRINTSERVICE.
Direct printing from Business Central – FAQ
Do I need additional software?
Yes, MC.PrintService: a Windows service on a machine in your network that can reach the printers. Business Central online cannot address local printers by itself. The download is linked from the app; the signed MSIX package installs through the Windows App Installer and keeps itself up to date. For Windows Server 2016/2019 there is a ZIP package without automatic updates.
Which printers are supported?
For PDF, any printer installed with a Windows driver on the service's machine – laser, inkjet or thermal. For ZPL, Zebra thermal printers such as the GK420, ZD421 or ZT411, which the service addresses over TCP/IP on the local network.
Does my print data pass through your servers?
No. With Direct Push it goes straight from Business Central to your print service, with Relay and Poll through your own Azure subscription. ALTENBRAND infrastructure is not involved in any mode.
We have no fixed IP address – does it still work?
Yes, with Relay or Poll – at the price of more setup: create the resources in your own Azure from a ready-made template, give the function access to Business Central with a script, register it as a Microsoft Entra application with a permission set, and copy the keys into the service. This needs administrator rights in Azure and Entra. After that the service holds only an outbound connection over port 443: no port opening, no certificate of your own, Azure costs of a few euros a month in your subscription.
Can a print error hold up a posting?
No. The posting only writes the print job. A background task of its own renders the report seconds after the commit; if the posting fails, the task never runs. Errors while rendering or printing end up in the print queue, not in the posting.
What happens when a printer goes down?
If a fallback printer is set and Fallback Enabled is on in the Print Service Settings, it takes over – only one with the same print method. The queue retries connection errors automatically; anything that fails for good is marked Failed with its reason and can be sent again with Retry or Retry All Failed.
Can other apps print through Print Service?
Yes. A public codeunit prints Business Central reports as well as ready-made PDF and ZPL documents to a Print Service printer, and integration events let you adjust jobs before they are sent or react to success and failure – useful for partners with extensions of their own.
Is Print Service available on Microsoft AppSource?
Yes – Print Service is published on Microsoft AppSource and comes with a 30-day free trial. After that it costs €39 per 4 weeks, net, per tenant. Prefer to see it first? Get in touch and request a demo.
Manual, data sheet & online help
The installation and user manual as a PDF – from the local print service through all three transport modes to troubleshooting. The online help is always current and reachable straight from Business Central.
Installation & user guide (PDF)
Installing the service, setting up Direct Push, Relay and Poll, printers, routing rules and print subscriptions, the dashboard, daily use and troubleshooting.
Data sheet (PDF, German)
The short version: features, transport modes, security and system requirements – made to hand on to IT, the warehouse manager or management.
Online help
Help pages for every page of the module – reachable in Business Central through the question mark menu, always up to date.
No more print dialogs at the packing station
Install the hub and Print Service from AppSource, set up the print service on a machine next to your printers and create your first printer – the setup wizard takes you through the download, the first printer and automatic printing. Free for 30 days.