CargoLine

Carrier-specific setup for CargoLine in Shipping Labels.

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.
  1. Create or verify the CargoLine shipping agent service combination in the shared setup.
  2. Maintain the CargoLine product list and package-type list.
  3. Assign the CargoLine test or productive URL and the authorization token.
  4. Maintain pickup window, label size, and fallback package properties.
  5. 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.

For the public documentation, the critical rule is simple: do not improvise product or package codes. Use the carrier-provided values and keep code, name, and description aligned with the information from CargoLine.

If item attributes are already maintained, this area still needs the package-type code, pickup window, and label size to be set cleanly in practice. For label size, A4 typically means printing on standard paper, while A6 points to a classic label-printer scenario.

Complete credentials and endpoint assignment

CargoLine requires the authorization token as well as the correct test or productive endpoint. These technical values should be maintained before business users start selecting the service in documents.

Separate the environments clearly:

  • test URL for validation and onboarding
  • productive URL for live requests
  • authorization token for the corresponding environment

Maintain pickup and output properties carefully

The setup includes operational properties that directly influence the request:

  • pickup-from time
  • pickup-until time
  • label size, typically A4 or A6
  • package type code
  • fallback length, width, height, and weight

These values are not only cosmetic. CargoLine expects package-size information even when it is not printed in the final label output.

Prefer item attributes over fallback package values

If item attributes for dimensions and weight exist, they override the fallback package properties on the CargoLine setup. The fallback values should therefore be treated as a safety net for scenarios where item-level logistics data is not available.

If neither item attributes nor setup properties provide valid package data, the API request can fail.

Process Important CargoLine notes These points prevent avoidable setup and request errors.
  • Maintain product and package-type lists before the final setup line is used in documents.
  • Keep test and productive URL assignments separate and verify the token against the correct environment.
  • Provide package dimensions and weight either through item attributes or through the CargoLine fallback properties.
  • Use the carrier-provided units and product codes unchanged.
  • Re-test the setup whenever label size or pickup windows are changed.

Links

Further Information

Related content