Shipment Provider Card
The Shipment Provider Card shows the details and configuration of an individual shipping provider.
Opening the Page
- Click an entry in the Shipment Provider List.
Fields
General
Most of this group is maintained by the connector itself and is read-only. Only Enabled and Open Label After Creation are yours to set.
| Field | Description |
|---|---|
| Code | Unique provider code (assigned by the connector). |
| Name | Display name of the shipping provider. |
| Description | Short description of the connector. |
| Enabled | Releases the provider for label creation. |
| Open Label After Creation | Hands the generated label documents straight to the download after successful creation — see below. |
| Status | Current state of the connector (colour-coded). |
| Shipping Agent Code | The Business Central shipping agent this provider is linked to. |
| Connector App Name, Connector Version | Origin and installed version of the connector. |
| Last Label Created | When the last label was created. |
| Last Error Message, Last Error DateTime | The last error reported by the provider. |
Capabilities
Supports Manifesting, Supports Retoure Labels, Supports Bulk Labels, Supports Cancellation, Supports Multi-Colli, Supports Customs and Supports Tracking are reported by the connector. They cannot be set, but they do shape the UI — without Supports Customs the customs fields are hidden, without Supports Manifesting there is no pickup schedule.
Further sections
| Section | Content |
|---|---|
| Provider Settings | The connector shows its own setup here (e.g. DHL). |
| Automation | Auto Create Label — None, On Release or On Post. The provider then creates labels without the dialog through the job queue, see Automatic Labels. |
| Package List | Manifest Report Note — additional text at the top of the internal package list. Plain text or HTML (<b>, <i>, <br/>). Typical use: carrier account number, depot number, billing reference. |
| Pickup Schedule (this provider) | Pickup windows, only for providers with manifesting. |
| General Shipment Settings | Platform-wide defaults across all providers. |
| License | License status of the corresponding module. |
| Data Protection | When this carrier receives the phone number and e-mail address of the recipient — see below. |
Open Label After Creation
This setting decides whether you receive the generated documents right away:
| State | Behaviour |
|---|---|
| On (default) | After single creation the label is offered for download immediately. After a batch run all documents of the run are handed out as one ZIP file. |
| Off | Nothing is downloaded. The documents remain available in the shipment label list. |
When to switch it off
Only when the labels are not needed on screen anyway — for instance when printing directly through the print service. For every other workflow the switch should stay on; otherwise a batch run ends without output and the labels have to be fetched one by one.
Actions
| Action | Description |
|---|---|
| Setup Wizard | Opens the connector's guided setup wizard. Shown only when the connector provides one. |
Data Protection: Recipient Data to the Carrier
Passing the phone number and e-mail address of a recipient to a parcel service is a transfer of personal data to a third party. German data protection authorities have held since their 2018 decision that this needs the recipient's consent — unless the delivery itself depends on it.
Two fields, one per channel:
| Mode | What happens |
|---|---|
| Never | The field stays empty on the label. Even a service that needs the value does not get it — the shipment is then refused with a message. |
| Only when the service requires it | The field stays empty on the label. Where the booked service needs the value — parcel shop delivery, timed delivery, forwarder notification — the connector asks for it for that one shipment. |
| Only with recorded consent | The value travels when Recipient Agreed to Carrier Notifications is set on the sales order or on the ship-to address. |
| Always | The value travels on every shipment. This is what the earlier Send Recipient Email to Carrier switch did, and the upgrade carried it over unchanged so that nothing changed silently. Your company carries the consent behind it — it is obtained outside Business Central. |
Marketplace orders are exempt
When the order came from a marketplace, the e-mail address is never passed on, whatever this setting says. The phone number is capped at only when the service requires it. Marketplace policies allow buyer data to reach only those who need it to fulfil the order — the carrier needs the address, not the mailbox.
Where to see how many carriers stand at Always
In the data protection cockpit, as a tile of its own. It is not an error but a question: do you have the consent this mode relies on?
Separately, recipient data on a label is removed again after delivery — the period and what it covers are in the data protection cockpit.