Handling EU Customs Reform Carrier Validation for FBM Shipments 🇪🇺📦🚢

[chrisskhoury]

Handling EU Customs Reform Carrier Validation for FBM Shipments 🇪🇺📦🚢

The EU Customs Reform (EUCR) introduces carrier eligibility validation for FBM shipments entering the EU from outside the EU. Starting July 1, 2026, Amazon will reject shipment confirmations that use a carrier not on the approved list.

This guide is our opinionated take on how integrators should handle this change. Every integration is different, your architecture, UX, and seller workflows will determine the exact implementation. But the principles here apply universally: surface errors clearly, restrict carrier selection where possible, and make sure customs data flows to the right place.

Authored by: Chris K - Solutions Architect, Selling Partner Developer Services

Effective July 1, 2026 Amazon enforces carrier eligibility validation on confirmShipment for cross-border FBM shipments entering the EU.

Use this as a starting point. Adapt it to your solution.

🚧 This only applies to sellers who confirm their own shipments (self-ship). If a seller uses Amazon's Buy Shipping service to purchase labels, Amazon handles carrier compliance internally : no action needed.

Two Ways Shipments Are Confirmed (Both Affected)

There are two methods integrators use to confirm FBM shipments with Amazon. Both are subject to EUCR carrier validation:

Method	Use Case	API
confirmShipment operation	Single order confirmation, real-time	Orders API v0
POST_ORDER_FULFILLMENT_DATA feed	Bulk confirmation of multiple orders	Feeds API v2021-06-30

If you use the Feeds API, the CarrierCode field in the OrderFulfillment XML is validated the same way. An invalid carrier will cause a feed processing error for that message.

Order Fulfillment Feed XML Example (affected field):

      <FulfillmentData>
        <CarrierCode>Yun Express</CarrierCode>  <!-- Must be from approved list -->
        <ShippingMethod>Express</ShippingMethod>
        <ShipperTrackingNumber>YT2312345678901</ShipperTrackingNumber>
      </FulfillmentData>
      <Item>
        <AmazonOrderItemCode>60696125413094</AmazonOrderItemCode>
        <Quantity>1</Quantity>
      </Item>

Who Is Affected?

Scenario	Action Required?
FBM seller ships from China/UK/US → EU, confirms shipment via API	✅ Yes
FBM seller uses Buy Shipping (Amazon labels)	❌ No
FBA shipments	❌ No
Domestic EU → EU FBM shipments	❌ No
Shipment total > €150	❌ No
Non-EU destination	❌ No

The Error You Will See

When confirmShipment (or the Order Fulfillment feed) is called with an unsupported carrier for an OOR → EU shipment:

{
  "errors": [
    {
      "code": "InvalidInput",
      "message": "The selected carrier is not supported for shipping your order. Please use only supported carriers."
    }
  ]
}

⚠️ Do not silently retry with free-text carrier names, internally mapped aliases, or fallback carriers. Surface this error clearly to the seller.

Step-by-Step: What Integrators Must Do

Step 1: Surface the Error Clearly to Sellers

When Amazon rejects a shipment confirmation, your UI must show the seller exactly what went wrong and what to do next. Do not display a generic "shipment failed" message.

What to show:

⚠️ Shipment Confirmation Rejected

Your carrier "XXX Express" is not authorized for shipments entering the EU 
from outside the EU under the new EU Customs Reform rules (effective July 1, 2026).

What to do:
→ Select an approved carrier from the dropdown below
→ Use the exact carrier code accepted by Amazon
→ Re-submit your shipment confirmation

What NOT to do:

• ❌ Show a generic "Error 400 : Bad Request"
• ❌ Silently retry with a different carrier name
• ❌ Map the rejected carrier to a fallback alias
• ❌ Swallow the error and leave the order unconfirmed

Step 2: Add an Approved Carrier Dropdown to Your Shipping UI

If your UX allows sellers to select a carrier when confirming shipments, replace free-text carrier input with a restricted dropdown for orders that match EUCR criteria. This will vary depending on your solution, but the logic is the same regardless of implementation.

When to show the restricted dropdown:

IF ship-from country is NOT in EU
AND ship-to country IS in EU
AND total item price ≤ €150 (excl. VAT, shipping, discounts)
THEN → show EUCR-approved carrier dropdown only

Dropdown implementation guidance:

┌─────────────────────────────────────────────────────────┐
│  Confirm Shipment - Order #403-7654321-1234567          │
├─────────────────────────────────────────────────────────┤
│                                                         │
│  Ship From: Shenzhen, CN                                │
│  Ship To:   Munich, DE                                  │
│  Item Total: €42.00                                     │
│                                                         │
│  ⚠️ EU Customs Reform : Only approved carriers accepted │
│                                                         │
│  Carrier: [▼ Select approved carrier          ]         │
│           ┌──────────────────────────────────┐          │
│           │  YUN - Yun Express               │          │
│           │  4PX - 4PX                       │          │
│           │  SF_EXPRESS - SF Express         │          │
│           │  WANB - WanbExpress              │          │
│           │  SUNYOU - SunYou                 │          │
│           │  CNE - CNE Express               │          │
│           │  YDH - YDH Express               │          │
│           │  SFC - SFC Service               │          │
│           │  TOPYOU - TopYou                 │          │
│           │  UBI - UBI Smart Parcel          │          │
│           │  CAINIAO - Cainiao               │          │
│           │  JS EXPRESS - JS Express         │          │
│           │  HUAHAN - HUAHAN Logistics       │          │
│           │  JIEHANG - Jiehang               │          │
│           │  SHANGHAI - SHOUWU  Shanghai..   │          │
│           │  JIUFANG - Jiufang               │          │
│           │  ECMS - ECMS                     │          │
│           │  Etc.... - Etc...                │          │
│           └──────────────────────────────────┘          │
│                                                         │
│  Tracking Number: [________________________]            │
│  Ship Date:       [2026-07-02              ]            │
│                                                         │
│                  [ Confirm Shipment ]                   │
└─────────────────────────────────────────────────────────┘

Key UX recommendations:

1. Detect EUCR applicability automatically: check ship-from, ship-to, and item price before the seller reaches the carrier selection step
2. Lock the dropdown to approved carriers only when EUCR applies (allow normal free-text or full carrier list for non-EUCR shipments)
3. Show a clear banner explaining WHY the carrier selection is restricted
4. Use the exact carrierCode** value** (left column in the table below) as the value submitted to the API; the display label can be the friendly carrier name
5. Link to the official carrier list so sellers can verify independently

Step 3: Use Exact Carrier Codes (No Free-Text)

Use the exact carrierCode value from the approved list in your confirmShipment request or feed XML. Do not use free-text carrier names or internal aliases.

# ❌ WRONG — will be rejected
package_detail = {
    "carrierCode": "UPS Express",       # Free-text, not a valid code
    "trackingNumber": "1Z999AA10123456784"
}

# ✅ CORRECT — use the exact approved carrier code
package_detail = {
    "carrierCode": "Yun Express",       # Exact code from approved list
    "trackingNumber": "YT2312345678901"
}

Step 4: Retrieve IOSS Number and ASIN Data for Customs

Carriers need the Amazon IOSS number (Import One-Stop Shop) and ASIN-level data to clear customs. Both are available from the Orders API:

Data	Orders API v0	Orders API v2026-01-01
IOSS Number	getOrderItems → IossNumber field	orderItems[].fulfillment.shipping.internationalShipping.iossNumber (requires includedData=FULFILLMENT)
ASIN	getOrderItems → ASIN field	orderItems[].product.asin
Item Price	getOrderItems → ItemPrice	orderItems[].proceeds.breakdowns[].subtotal (type=ITEM, requires includedData=PROCEEDS)

[!NOTE] The IOSS number is Amazon's Import One-Stop Shop VAT registration number (format: IM...). Your integration should provide a way for sellers to access this data and transmit it to their carrier for customs declarations.

What integrators should do with IOSS/ASIN data:

• If you manage label generation or carrier booking for the seller: pull this data from the Orders API and include it in the carrier's customs workflow automatically
• If you don't manage label generation: make sure sellers can view and export this data from their order details, so they can provide it to their carrier through another workflow
• Provide a settings field where sellers can store/configure the IOSS number for transmission to carriers

Approved Carrier List (as of July 1, 2026)

🚨 Additional carriers are under contractual discussion and may be added after July 15, 2026. Monitor the official carrier list on Seller Central for updates.

EU Customs Reform — Approved Carriers (as of 22 July 2026) ✅

Status: 34 carriers enabled.

Carrier Code	Notes
17FEIA	New
4PX
APC Postal Logistics	New
Asendia	New
Cainiao
China Post	New
Chukou1	New
CNE
DHL Express	New
DPD	New. DPD Local is not supported for EUCR.
ECMS Express, Inc	New. Previously listed as "ECMS"
Evri	New. Previously listed as "EVRI"
GlobalPost	New
HUAHAN Logistics	Previously listed as "Huhan Logistics"
JD Logistics	New
Jiehang
Jiufang
JS Express
LANDMARK	New
Royal Mail	New
SF Express	Also: Shunfeng Express
SFC	Also: SFC Service
Shanghai Shouwu
ShipGlobal	New
Spring	New
Sunyou
The Delivery Group	New
Topyou
UBI	Also: UBI Smart Parcel
WanbExpress
Whistl	New
YDH	Also: YDH Express
Yanwen	New
Yun Express

Quick Decision Flowchart

Need Help? 🆘

For Sellers:

• Contact Seller Support for questions about which carriers are approved, IOSS requirements, or if your shipments are being rejected
• Review the official carrier list on Seller Central for the latest approved carriers

For Developers and Integrators:

• 📖 SP-API Documentation
• 💬 GitHub Discussions
• 🎫 Developer Support

Related Resources 📚

• Confirm the Shipment Status (Use Case Guide)
• Amazon-Approved Carrier List for OOR Shipments (Seller Central)
• Orders API v2026-01-01 Reference
• Feeds API v2021-06-30 (for bulk order fulfillment)

Additional Resources

• SP-API Documentation
• Usage Plans and Rate Limits
• Selling Partner API Changelog

---

Let us know what you think!👇 React or reply down below to share your feedback.

❤️ Like what you see?
👍 Excited to try it out?
🎉 Want to see more of this?

---

Content Governance 🕵️‍♂️

Last Reviewed: [June 30, 2026]
Next Review Date: [July 15, 2026]

---

Keywords: EU CR, FBM, EU Shipments, Confirm Shipments

---

Please note the publication date above. While we strive to keep our content current, the rapid evolution of this topic means some details may have changed since publication. For the most up-to-date information, we encourage readers to follow the announcements in SP-API developer documentation.

[AitorUria]

Hello @chrisskhoury

I am confused by this comment so I'll provide an example.

Additional carriers are under contractual discussion and may be added after July 15, 2026. Monitor the official carrier list on Seller Central for updates.>

Whistl is a carrier featured on Amazon.ie does that mean this is part of the "appoved list"?

We are assuming it is but prefer not to take chances. Thanks

[chrisskhoury]

Hello @AitorUria :)

So this change only applies if you shipFrom is outside the EU and the shipTo is to the EU.

This effect will take place on July 1st Central Europe Summer Time. The carriers in the table above (Approved Carrier List) is the list that will be valid, otherwise an error will be returned and you will need to update accordingly.

Does this clarify?

Thanks!

[AitorUria]

Hello @chrisskhoury,

Yes correct. We ship from outside the EU into the EU.

A few issues:

• The link https://sellercentral.amazon.com/gc/sell-across-europe/out-of-region-carrier-list does not work.
• The approved list is incomplete; for example, our current carrier, Whistl, appears in the Seller Central list. Is there any reasonable explanation for this? Naturally, switching carriers or fully restructuring cannot be done in hours.
• The guidance has been published very late, considering how close we are to the July 1st deadline.

Please let us know your thoughts to avoid major disruption.

Thanks

[AitorUria]

@chrisskhoury Any further feedback about this?

Thanks,

Aitor

[chrisskhoury]

Hey @AitorUria is this still the case? The SC list should be up to date now. It will only allow carriers from the options mentioned here in my Blog

[AitorUria]

Hello Chris,

Thank you for the update.

One significant concern is that the current list appears to omit several major carriers, including UPS, FedEx, Whistl, and ePostGlobal. These carriers are regularly used by sellers and, in many cases, are central to their existing logistics operations.

Users of the API are not only shipping platforms such as ShipStation, Veeqo, or Parcelgo, but also individual sellers with established carrier relationships. For those sellers, changing carriers is not something that can realistically be completed within a couple of weeks.

In recent days, I have found myself having to inform some of the major affected carriers that they appear to no longer be available as supported services on Amazon. That has been concerning, as these carriers are relied upon by many US- and UK-based sellers.

I hope the list can be reviewed and revised soon so that it more closely reflects the previously comprehensive carrier coverage.

Thanks,

Aitor

[chrisskhoury]

Hello @AitorUria ,

Sorry for the late reply here - we added some new carriers above and we will keep updating this list as we go.

I'd also encourage you to surface this through Seller Support

Thanks!

[chrisskhoury]

New Carriers added to the list above ^