Otto Carrier Mapping
Otto accepts a shipment confirmation only with a carrier from its own list. On this page, you map a Business Central shipping agent to the Otto carrier – needed only where the code of the shipping agent does not reveal the carrier.
Opening the Page
- Via search: Otto Carrier Mapping
- Via the Otto settings on the marketplace card → action Lists → Carrier Mapping
- Via the Otto Dashboard → Advanced → Carrier Mapping
How the Carrier of a Shipment Confirmation Is Determined
The carrier comes from the shipping agent merchantCENTRAL registered the tracking number with – from the shipping label, the posted shipment or the supplier's report.
- Your own extension: A subscriber to the event
OnBeforeMapShippingAgentToCarrier(codeunit ALN MCO Shipment Confirmation) decides before anything else. - Mapping on this page, if there is one for the shipping agent.
- Code of the shipping agent: If the code reads like an Otto carrier without spaces and separators, it is recognized –
DHL,HERMES,DPD,GLS,UPS,DHLEXPRESS(DHL Express),DHLFREIGHT(DHL Freight),DBSCHENKER(DB Schenker),DACHSERand the other Otto carriers need no mapping. The column Without Mapping shows what the result would be without a mapping.
merchantCENTRAL does not guess a carrier – a wrong one would report the parcel to Otto under another service. If no carrier results, the shipment confirmation is not sent. It stays in the list of shipment confirmations with the message "No Otto Carrier for the Shipping Agent", which names the shipping agent and leads here. After the mapping, the confirmation goes out on the next run of the job.
Fields
| Field | Description |
|---|---|
| Shipping Agent Code | Business Central shipping agent. |
| Shipping Agent Name | Name of the shipping agent. Read-only. |
| Otto Carrier | Carrier under which Otto knows the shipping agent. |
| Without Mapping | Carrier the shipping agent would get from its code; empty if the code is not an Otto carrier. Read-only. |