Overview

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.

The carrier depth differs by provider. The documentation highlights these examples in particular:

The documented scope also includes EU countries and the United States as well as English, German, and Serbian language contexts. In productive use, the decisive factor is always the carrier-specific setup and account scope.

Shared setup model in Business Central

Shipping Labels builds on a shared setup model instead of separate per-carrier processes only. The common business structure consists of:

• shipping agents and shipping agent services as the functional carrier model in Business Central
• Shipping Labels setup for shared source-document, Incoterm, and default behavior
• shipping agent service setups as the matrix of allowed carrier and service combinations
• shipping label URLs, request logs, and support information for operational administration

This shared layer is what keeps later carrier pages manageable. Carrier-specific credentials and properties are still required, but the document model, source types, and service combinations are controlled centrally.

Daily label processes

The operational entry points stay close to standard Business Central work:

• create labels from sales orders
• create labels from warehouse shipments
• create labels from shipment orders when a separate warehouse process is not used
• download and review generated labels and tracking IDs
• generate shipping reports for the current day per carrier

Because these processes rely on the same shared setup, the solution can support different operational paths without redefining the carrier logic each time.

Diagnostics and operational control

Shipping Labels also provides the transparency needed for troubleshooting and day-to-day support. Request logs record successful and unsuccessful calls, request parameters show the header data of a chosen request, and the Request Shipping Labels page provides the generated file, tracking ID, return tracking ID, and file type when a request succeeds.

This makes the solution more than a label trigger. It also gives key users a controlled way to understand what was sent to a carrier and how the carrier responded.

Result

• You understand which carriers and business scenarios the Shipping Labels solution covers.
• You know that shared setup, carrier-specific onboarding, operational usage, and troubleshooting are separated into dedicated pages.
• You can use the documentation both for the initial rollout and for the daily handling of shipping requests in Business Central.