Connecting a carrier — the connection and its configuration

Connect a carrier the same way as a sales channel: choose a connector from the Available integrations tab and create a connection (Integrations list — my connections and the available catalog).

Step by step

1. Go to Integrations → Integrations and open the Available integrations tab.
2. In Type, choose Delivery to see only carriers.
3. Click + Add on the carrier tile.
4. In the New integration form, enter a Name. If you have two accounts with one carrier, give them distinct names — for example, include the branch.
5. Click Create. You will go to the configuration screen.
6. At the Connection stage, enter access credentials, sender details, and default parcel settings (see below).
7. Save with Save changes in the bottom bar. The system will ask for a code in the 2FA verification required dialog (2FA confirmation when changing permissions).
8. Click Test in the header. Do not continue until you see Connection OK — the next steps are pointless if the keys are wrong.
9. Turn on the toggle beside Test to activate the connection.
10. Complete the three steps in the “After connecting” section at the end of this article.

What you need to enter

• Access credentials — keys, login, and customer number for the carrier. The fields depend on the connector.
• Sender details — the address the shipments leave from. It appears on the label.
• Default parcel settings — dimensions and weight used when a shipment does not have them.

Find fields using Search settings… above the stages instead of scrolling through the whole list.

After entering the details, use Test. Its result is stored as the integration health, shown in the header under Connection, and is the quickest way to determine whether the problem is with the credentials or somewhere else.

One company, several accounts

You can have several connections with the same carrier — for example, two DHL accounts for two branches. Each has its own sender details and configuration.

What each carrier supports

Connectors differ in their capabilities — not every one supports tracking, returns, or cancellation. For a full overview, see courier support in shipment tracking.

Check this before deployment, not afterward. If you expect to cancel shipments through the system but the carrier does not support it, your service process will have to change.

What you cannot configure

Two things are unavailable in every connector:

• booking a courier pickup — arrange it in the carrier’s panel,
• a consolidated shipping note / manifest — the system does not generate one.

Do not look for these settings; they are not available (see courier support in shipment tracking).

Global24: two connectors

The catalogue has two Global24 tiles. Global24 is the older API (login and password). Global24 Partner API is the newer API (token). To move to the new API:

1. Create a Global24 Partner API connection and paste the token from Global24 into API token.
2. Click Test. The message says how many shipping services your account can see.
3. Enter a service for each country in Delivery service per country (and Return service per country for returns), for example {"DE": {"code": "DE-DHL", "service": "DST", "size": "NP"}}. The "*" key covers all remaining countries. You can leave a country blank if Global24 offers your account only one service there — the system will select it. If there are several services, shipment creation stops and the message lists the codes you can choose from.
4. Remap delivery methods to the new Global24 Partner courier (Delivery-method mapping and shipment validation).

Do not disable the old connection right away. Parcels sent through the old API continue to be tracked by the old connection until they arrive.

Shipments to the United Kingdom and Ukraine require customs details. Fill in Customs HS code and Customs country of origin. These shipments can contain only one parcel. The Partner API does not yet support returns from these countries — the system will refuse with a message.

The API requires the customer’s email address. If the order does not have one, the system sends Fallback email; if the address is too long, it is replaced with Replacement for too long email. The return goes to the address in the Global24 account profile, not the warehouse address in Noxti.

Saving requires 2FA

Integration keys and variables are sensitive data — saving requires a code (2FA confirmation when changing permissions).

After connecting

1. Check that the carrier is in the courier directory (Courier list — carrier directory).
2. Map marketplace delivery methods to this courier (Delivery-method mapping and shipment validation).
3. Generate a test label (Carrier labels — generation, reprinting, expiration).