Sendcloud API V2 vs. V3: Key Differences

Commerce 365 for Sendcloud supports both the Sendcloud API V2 and the newer API V3. You choose which version to use in the Sendcloud API Version field on the Sendcloud Setup page. This section explains how the two versions differ, so you can decide which one fits your business best.

At a glance

API V2    API V3

Import all shipping options upfront    ✅ Yes    ❌ Not yet available from Sendcloud

Map shipping options to carriers and services    ✅ Yes    ❌ No

Map BC Shipping Agents to Sendcloud carriers    —    ✅ Yes

Set commercial prices per shipping option upfront    ✅ Yes    ❌ No

Multi-collo support    Limited    ✅ Applied by default when the carrier service supports it

Shipping options and mapping

V2: You can import the full list of Sendcloud shipping options into Business Central upfront. You then map these options to carriers and services and work with them directly on your documents. Most existing users are used to working this way.

V3: Sendcloud does not yet offer an API to fetch shipping options upfront. This means you cannot import all shipping options in advance, and you cannot map options to carriers and services the way you did in V2.

V3 uses a different mapping method instead: you link your Business Central Shipping Agents to Sendcloud carriers with the Sendcloud Carrier Code field on the Shipping Agent. This mapping works differently from V2, so plan time to review your setup before you switch.

Commercial prices

V2: Because all shipping options are available in Business Central upfront, you can set a commercial (sales) price for each shipping option.

V3: Shipping options cannot be imported upfront, so there is currently no way to set commercial prices per shipping option in advance. If you charge shipping costs to your customers based on the shipping option, take this into account.

Multi-collo

V3 has much better support for multi-collo shipments, where one shipment is sent as several parcels. If the selected carrier service supports multi-collo, V3 applies it by default, with no extra setup needed.

Which version should I use?

Stay on V2 if your processes depend on importing shipping options upfront, on mapping options to carriers and services, or on commercial prices per shipping option.

Consider V3 if you ship multi-collo often, or if mapping Shipping Agents to Sendcloud carriers is enough for your setup.

Note: Sendcloud is still developing the V3 API. When Sendcloud releases an API for fetching shipping options upfront, we expect to close the gap with V2. Check the release notes for updates.