📬

You can now set a separate default weight specifically for returns. This default weight is used when a return is created without a weight and there’s no outbound shipment to reference.

💡

Return parcels don’t always weigh the same as outbound shipments. Using a dedicated default return weight helps prevent incorrect label weights and unexpected shipping costs when a return is created without weight details.

By default it's empty, so nothing changes for existing users. It falls back to outbound defaults the same way it always has. Users who need it can set it when they're ready

📬

You can now select a carrier service once in your return rules, and the correct weight bracket is applied automatically.

💡

You no longer need to create separate return rules for every weight bracket, which makes setting up returns faster and easier.

ℹ️

Your existing return rules stay unchanged unless you choose to migrate. The previous action has been renamed to “[Deprecated] Ship with return method” to avoid breaking existing setups.

📬

The new table editor lets you to fit your workflow. Choose which information to show or hide, and add a This helps you and your team focus on the most relevant details to process orders faster.

💡

Saved columns and sorting settings help you keep a consistent and efficient workspace every time you log in.

With the Create label button, you can start creating labels more quickly after importing orders, with fewer steps and less confusion—especially if you’re new to shipping.

🚀

📬

You can now ship seamlessly to the Canary Islands (Spain), as well as the Isle of Man, Jersey, and Guernsey (UK). Shipments to these locations are handled consistently across all carriers - so whether you select “Spain” or “Canary Islands”, or choose between “United Kingdom”, “Isle of Man”, “Jersey”, or “Guernsey”, your shipment will be routed correctly.

💡

You no longer need to guess which country option a specific carrier expects for these destinations. This helps you avoid address-related errors when creating labels.

🚀

📬

Customers with their own contract can now start ship from Switzerland with the Swiss Post being the first carrier available in this market.

💡

You can start creating domestic and international Home Delivery labels and shipping orders from Switzerland to >230 destinations.

📬

You can now use the new API v3 migration guidelines to move from API v2 to API v3. The guide includes examples for common actions (like creating parcels or orders) and shows how API v2 fields map to API v3.

💡

You can migrate to API v3 with clearer instructions and fewer guesswork steps. This helps you update your integration faster and with more confidence.

🚀

ℹ️

Read the guidelines here: https://sendcloud.dev/docs/getting-started/migration-guidelines-for-api-v3

📬

If you're using Sendcloud rates, you can now see estimated PostNL surcharges in the price breakdown before you create a label. This works in the Sendcloud panel when you create a shipment, and for API v3 users using , as long as you enter parcel dimensions at announcement.

The estimates can include volumetric surcharges (>50 dm³, >100 dm³, >200 dm³), exceeding maximum dimensions (currently only for Klein Pakket), and packaging size surcharges (too small <10×10×1 cm or too large >95×70×58 cm within the EU).

💡

You get an early warning about possible extra carrier charges, so the final PostNL invoice is less likely to surprise you weeks later. This helps you choose the right shipment option and avoid unexpected costs.

🚀

ℹ️

These are estimates and are marked as approximate, because the carrier can re-measure the parcel at scan. The surcharge is not charged at label creation; it’s shown to inform you upfront.

📬

You can now use the new “Generate invoice now” action to instantly create an invoice that includes all open invoice items.

💡

You get more control over when you settle your outstanding balance. This helps you stay ahead of your credit limit and avoid shipping disruptions.

🚀

📬

If you’re on a Premium plan (or higher), you can now send tracking email notifications from your own email address. Tracking emails no longer have to come from a Sendcloud address.

💡

Your customers see tracking updates coming from your brand, which keeps the post‑purchase experience consistent from order confirmation to delivery.

🚀

ℹ️

This is available on Premium plans and higher. If you want to use your own logo, you may need to validate it with Google yourself.

📬

You can now create and announce shipments/ orders in API v3 using native carrier service point IDs (for example PostNL or DPD ). This means you no longer need to map carrier IDs to Sendcloud service point IDs before creating the shipment.

💡

If your system already stores carrier-specific service point IDs, you can send them directly to Sendcloud. This reduces extra API calls and removes the need for hardcoded mappings.

🚀

ℹ️