Shipping Labels on Product Documentation

Overview

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

Shipping Labels connects Microsoft Dynamics 365 Business Central directly with supported shipping providers so that users can create shipping labels, retrieve tracking information, and review shipping requests without switching to a separate carrier portal. The solution combines the shared setup in Business Central with carrier-specific onboarding so that operational users and key users can work with one consistent shipping model.

Business Value

Create shipping labels directly from operational documents such as sales orders, warehouse shipments, and shipment orders.
Control productive carrier, product, and service combinations through one shipping agent service setup matrix.
Reduce manual coordination by keeping carrier onboarding, request URLs, and request history in the same Business Central solution area.
Download generated labels, review tracking IDs, and generate same-day shipping reports from the app.
Troubleshoot failed requests with request and response data instead of relying only on generic carrier error messages.

Areas and Topics

Supported carrier landscape

Shipping Labels covers 12 main carriers. Their exact product and service combinations depend on the configured carrier account, but the supported landscape includes CargoLine, DACHSER, DHL Express, DHL Freight, DHL Shipping, DPD, DSV, FedEx, GLS, Hermes, PCH, and UPS.

Setup

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page explains the shared setup logic of Shipping Labels in Microsoft Dynamics 365 Business Central. Before you configure a specific carrier, prepare the common master data, create the required shipping agents and services, and complete the global Shipping Labels setup so that later label requests are based on consistent data.

Prerequisites

Shipping Labels is installed and available in the Business Central environment.
The required carrier accounts, API credentials, customer numbers, or onboarding data are available from the shipping provider.
Sender and recipient master data such as addresses, contact data, phone numbers, and email addresses are maintained with the quality required by the target carrier.
Users can access the pages for shipping agents, shipping agent services, shipping agent service setups, and the central Shipping Labels setup.

Recommended sequence

Clarify which carriers, products, and service options are required in the business process.
Prepare the master data for addresses, package handling, weights, dimensions, and Incoterms.
Create the shipping agents and shipping agent services in Business Central.
Maintain the shared Shipping Labels setup, including assigned source types and Incoterms.
Build the shipping agent service setup matrix for the valid carrier and service combinations.
Complete the carrier-specific properties, credentials, and tests on the corresponding carrier setup pages.

Setup components

Prepare master data before the first label request

Successful label requests depend on consistent business data. In practice, the most important preparation is not the carrier page itself, but the quality of the sender and recipient data that later flows into the request.

CargoLine

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the CargoLine-specific setup in Shipping Labels. Use it after the shared setup is complete to maintain the CargoLine product catalog, package types, credentials, URL assignments, and the properties that control pickup windows, label output, and fallback package data.

Prerequisites

The shared Shipping Labels setup is complete.
CargoLine test or productive endpoints and the required authorization token are available.
The relevant shipping agent and shipping agent service are already maintained in Business Central.
Item attributes for dimensions and weight are maintained where possible, or a fallback package definition is available on the setup.

Recommended sequence

Create or verify the CargoLine shipping agent service combination in the shared setup.
Maintain the CargoLine product list and package-type list.
Assign the CargoLine test or productive URL and the authorization token.
Maintain pickup window, label size, and fallback package properties.
Test one realistic label request with complete package data.

Setup components

Maintain products and package types first

CargoLine depends on two reference catalogs before the final setup line is usable: the available CargoLine products and the allowed package types. These lists define which business combinations can be selected later in the actual setup.

DACHSER

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the DACHSER-specific setup in Shipping Labels. It covers the reference lists for products, branches, and package types as well as the API keys, endpoints, divisions, depot selection, and fallback package properties required for productive label requests.

Prerequisites

The shared Shipping Labels setup is complete.
DACHSER test and productive endpoints are available.
The required API keys for the relevant environment are available.
Products, branches, and package types are known from the DACHSER onboarding material.

Recommended sequence

Maintain the DACHSER product list.
Maintain the DACHSER branch list and package types.
Assign test or productive endpoint and API key.
Select division, depot, product, label count, and fallback package properties.
Validate the setup first in test mode and switch to productive mode only for go-live.

Setup components

Build the DACHSER reference lists first

DACHSER is not only a credential setup. Before the main line becomes usable, you should maintain the supporting lists for products, branches, and package types.

DHL Express

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the DHL Express-specific setup in Shipping Labels. It focuses on product selection, allowed service options, customer credentials, pickup-window properties, and return-service behavior for national and international express scenarios.

Prerequisites

The shared Shipping Labels setup is complete.
DHL Express test or productive credentials and URLs are available.
The required DHL Express products and account information are known.
The relevant shipping agent service is already maintained in Business Central.

Recommended sequence

Maintain the DHL Express product list.
Define the allowed service options per product.
Assign credentials and the correct environment URL.
Maintain pickup times, closing time, sender email fallback, and return-service behavior.
Test one realistic shipment with the selected service option combination.

Setup components

Start with products and allowed service options

DHL Express combines products with selectable service options. The public-facing setup should therefore explain two layers:

DHL Freight

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the DHL Freight-specific setup in Shipping Labels. It focuses on product constraints, package types, API access, stackability, and the package dimensions and weights that must stay within the limits of the selected DHL Freight product.

Prerequisites

The shared Shipping Labels setup is complete.
DHL Freight account number, API key, and the correct test or productive endpoint are available.
DHL Freight product settings and package types are known from the carrier onboarding.
Item attributes or fallback package data are available for the relevant shipment scenario.

Recommended sequence

Maintain or import the DHL Freight product settings.
Maintain the DHL Freight package types.
Assign account number, API key, and URL.
Choose the product, package type, stackability, and fallback dimensions and weight.
Validate the request against the selected product constraints before productive use.

Setup components

Start with the product settings, not with the final setup line

DHL Freight is strongly driven by carrier product constraints. The product settings define the allowed ranges for package dimensions, package weight, total shipment weight, volume, pieces, and loading meters.

DHL Shipping

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the DHL Shipping setup in Shipping Labels. It covers domestic parcel scenarios, return labels, SOAP and REST credentials, participation numbers, print format, detailed request properties, and optional international return handling.

Prerequisites

The shared Shipping Labels setup is complete.
The required DHL Shipping credentials and URLs are available for the target environment.
Country data contains the required ISO Alpha-3 values for REST-based scenarios.
Default sender contact data and package data are available.

Recommended sequence

Decide whether the rollout should start directly with REST credentials.
Maintain the required URL entries for test or productive use.
Maintain credentials, participation number, default sender email, and print format.
Configure request properties such as return labels, validation, insurance, and notification behavior.
Add international return settings only for locations and products that actually support them.

Setup components

Prefer REST credentials and keep SOAP only for compatibility

DHL Shipping currently spans older SOAP-based values and newer REST-based access. For public guidance, the safest rule is to prefer REST credentials from the beginning whenever the carrier account supports them.

DHL API Assistant – MCP Integration

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes how to integrate the DHL API Assistant MCP Server into an AI-enabled development environment. The integration allows supported AI tools and IDEs to access DHL API-specific capabilities through the Model Context Protocol (MCP).

The DHL API Assistant helps developers create request examples, analyze API errors, understand required fields, and test DHL API workflows in the sandbox environment. The integration is limited to the sandbox environment. For production use, the official DHL API documentation is authoritative.

DPD

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the DPD-specific setup in Shipping Labels. The DPD setup is comparatively compact and focuses on service type, credentials, URL assignment, and the package limits that the request must respect.

Prerequisites

The shared Shipping Labels setup is complete.
DPD credentials and the correct test or productive URL are available.
The intended DPD service is known.
Item or fallback package weight is available for the request scenario.

Recommended sequence

Assign the DPD shipping agent service in the shared setup.
Maintain username, password, and URL.
Select the DPD service and maintain package limits.
Validate one realistic request with complete package data.

Setup components

Maintain credentials and environment URL

DPD requires a straightforward credential setup with the correct environment URL. Keep test and productive values separate and validate each environment independently.

DSV

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the DSV-specific setup in Shipping Labels. It covers residential delivery handling, pickup windows, fallback package data, notification options, and the multiple credential sets needed for shipping and tracking-related services.

Prerequisites

The shared Shipping Labels setup is complete.
DSV shipping credentials, tracking-related credentials, and the correct environment URLs are available.
Sender and recipient contact data are maintained in the required format.
The required notification scenario is known.

Recommended sequence

Maintain shipping credentials and URL assignment.
Maintain pickup window and residential-delivery behavior.
Maintain notification settings and the related tracking credentials.
Verify phone and email data in a realistic test request.

Setup components

Start with the DSV credential model

DSV setup can include several technical values, for example account number, x-pat, Subscription-Key, Service-Auth, and additional tracking-oriented values for notification scenarios. Keep these values grouped by service purpose so that shipping requests and notification flows are not mixed accidentally.

FedEx

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the FedEx-specific setup in Shipping Labels. It focuses on product selection, label format, customs-relevant fields, direct API credentials, and the fallback package data needed for national and international scenarios.

Prerequisites

The shared Shipping Labels setup is complete.
FedEx account number, API key, secret key, and the correct environment URL are available.
The FedEx product list is known.
Customs-relevant values such as currency and country of manufacture are available where needed.

Recommended sequence

Maintain the FedEx product list.
Assign account number, API key, secret key, and URL.
Choose product and label format.
Maintain customs-relevant properties and fallback weight.
Validate one national and, if relevant, one international scenario.

Setup components

Start with the product list

FedEx setup uses a product catalog that distinguishes between national and international shipping scenarios. Maintain the product code and name exactly as agreed with the carrier.

GLS

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the GLS-specific setup in Shipping Labels. The main topics are service type selection, delivery-time promise, credentials, URL assignment, and the parcel-size limits that belong to the chosen GLS scenario.

Prerequisites

The shared Shipping Labels setup is complete.
GLS credentials and the correct test or productive endpoint are available.
The business scenario is clear about whether a standard parcel or an express scenario is required.
Item or fallback package weight is available.

Recommended sequence

Assign GLS credentials and URL.
Choose the service type.
Maintain express delivery time if the express service is used.
Maintain parcel limits and fallback package weight.
Validate one realistic request with the chosen service type.

Setup components

Start with the GLS service decision

The key business decision in GLS is whether the setup represents a regular parcel flow or an express flow. If Express is chosen, the delivery-time commitment becomes part of the setup. If Parcel is chosen, that additional time promise is not required in the same way.

Hermes

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the Hermes-specific setup in Shipping Labels. It focuses on parcel class, output format, ZPL handling, and the separate authentication and shipping URLs that Hermes requires for test and productive operation.

Prerequisites

The shared Shipping Labels setup is complete.
The Hermes authentication and shipping URLs are created in the shared URL setup.
The required Hermes credentials are available for the productive environment.
The business scenario is clear about parcel class and output format.

Recommended sequence

Maintain the shared URL entries for Hermes authentication and shipping access.
Maintain the Hermes credentials for the relevant environment.
Choose parcel class and output format.
If ZPL is used, maintain the required resolution.
Validate the setup with the target output format and printer scenario.

Setup components

Treat authentication URL and shipping URL separately

Hermes uses separate URL concepts for authentication and the actual shipping service. These entries should be maintained explicitly in the shared URL setup before the Hermes line itself is completed.

PCH

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the PCH-specific setup in Shipping Labels. It focuses on the product catalog, response language, label size, customer and client credentials, and the strict geographic scope for Switzerland and Liechtenstein.

Prerequisites

The shared Shipping Labels setup is complete.
PCH test or productive client credentials and URLs are available.
The relevant PCH products are known.
Company Information contains the sender address used for PCH requests.

Recommended sequence

Maintain or import the PCH product list.
Validate the products with the available product-check functionality.
Maintain customer number, client credentials, response language, and label size.
Test one valid scenario inside the supported country scope.

Setup components

Start with the product list and product check

PCH uses a product list that should be maintained from the carrier-provided data. Use the product-check step when it is available to validate whether the maintained products are still usable.

UPS

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the UPS-specific setup in Shipping Labels. It focuses on service type, return-service behavior, international shipment handling, units of measure, and the transition from older authentication fields to preferred OAuth-based access.

Prerequisites

The shared Shipping Labels setup is complete.
UPS shipping account data and the required environment URL are available.
The chosen UPS service type is known for the origin and destination corridor.
Fallback package weight is available where item weight is not maintained.

Recommended sequence

Maintain the UPS URL and the preferred authentication method.
Maintain shipper number and the required credential fields.
Select the UPS service type and return-service behavior.
If international shipping is required, maintain the international-shipment settings and description.
Validate one domestic and, if relevant, one international scenario.

Setup components

Prefer OAuth-based access when available

UPS can still contain older access-license-style fields, but the preferred direction is OAuth-based access with client ID and client secret. Keep older values only where a supported compatibility scenario still requires them.

Shipping Label Print Connect Connector

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the setup of the Shipping Label Print Connect Connector. The connector links Shipping Labels with BE-terna Printconnect and enables direct ZPL label printing without routing through the browser’s local printer.

Prerequisites

BE-terna Printconnect is installed and configured. For details, see Printconnect – Setup.
A user account is available and registered in PrintNode.
The Shipping Label Print Connect Connector app is installed in the target environment.

Recommended Sequence

Make sure BE-terna Printconnect is fully configured.
Open the Shipping Label Setup page.
Configure the printer assignment per user and label type.

Setup Components

Open the Shipping Label Setup Page

In Business Central, open the Shipping Label Setup page.

Process catalog

Mon, 01 Jan 0001 00:00:00 +0000

Goal

This process catalog shows the main day-to-day workflows in Shipping Labels. It explains how label creation starts from different Business Central documents and how users can continue with downloaded labels, tracking information, and shipping reports.

Context

Shipping Labels supports several operational entry points because companies do not always ship in the same way. Some teams create labels directly from sales orders, others rely on warehouse shipments, and some use shipment orders for scenarios outside the classic warehouse flow.

Administration

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the operational administration of Shipping Labels after the shared and carrier-specific setup is in place. It focuses on URLs, reusable setup packages, request analysis, retention settings, and the support information that helps key users and administrators keep the solution stable.

Access in Business Central

Open Shipping Label Setup for global settings, request logs, deletion settings, and access to related setup pages.
Open Shipping Label URL when productive or test endpoints must be created or updated.
Open Configuration Packages when setup data should be exported, imported, or rolled out across companies or environments.
Open BE-terna Support Info and the BE-terna license update page when support or license maintenance is required.

Prerequisites

Shared setup and at least one carrier setup are already maintained.
The user has permission to change setup data, URLs, and configuration packages.
Productive and test credentials or URLs are available from the relevant carrier.
Customer number, ident, and other support metadata are available where license or support actions are required.

Activities

Maintain shipping label URLs for productive and test use

Shipping label URLs define which carrier endpoint is called by the respective setup. In practice, this usually means that you maintain separate entries for test and productive access and assign them to the relevant carrier setups.

FAQ

Mon, 01 Jan 0001 00:00:00 +0000

FAQ Why does Shipping Labels say that an assigned source type is missing? The table ID required for the current source document is not maintained in Assigned Source Types. +

Open Shipping Label Setup > Assigned Source Types and verify that the table ID required for the affected process is maintained together with the correct source type. Shipping Labels can only generate labels for the source types that are assigned there. If a new document context needs additional information, extend the Assigned Source Types setup accordingly. See Setup.

FAQ Why can the request not be sent successfully? Usually a mandatory setup value, credential, URL, or master-data field is missing, or there is a connectivity issue. +

Start in the request log and compare Error Text, Response, and HTTP Status. If the request never reached the carrier, first verify internet connectivity, the maintained URL, and the credentials. If the carrier rejected the request, review the source data that was sent: shipping agent service setup, assigned Incoterms, country data, addresses, package data, and required contact information. The Administration page explains which technical details are available in the request log.

FAQ How do I know whether a carrier setup is complete enough for the first test? Before the first request, verify the shared setup, the carrier-specific setup, and the source-document data together instead of testing one field at a time. +

Use a short readiness check before the first end-to-end test: