Launch Announcement: CarrierId Standardization for Cross-Border Shipments (FRITES)

Amazon Shipping is standardizing the carrierId field for all cross-border (international) shipments across France, Italy, and Spain (FRITES) marketplaces. This change applies to both On-Amazon and Off-Amazon shipment types and affects the getRates, oneClickShipment, and Tracking APIs.

What is changing?

Previously, the carrierId returned in API responses for cross-border shipments reflected the source country (e.g., AMZN_FR, AMZN_IT, AMZN_ES). Going forward, all cross-border shipments will return a standardized carrierId: AMZN_INTL — regardless of source or destination country.

Domestic shipments are not affected — they continue to use country-specific carrier IDs as before.

Which marketplaces are affected?

Who is affected?

All shippers and integrators using the getRates, oneClickShipment, or Tracking API endpoints for cross-border shipments. This applies to any integration that:

• Reads or stores the carrierId value from API responses
• Passes carrierId as a query parameter in tracking requests

What action is required?

After rollout, tracking requests using country-specific carrier IDs (e.g., AMZN_FR) for cross-border shipments will return errors. You must use carrierId=AMZN_INTL for all cross-border tracking requests.

1. Update API response handling: If your integration reads or stores the carrierId from getRates or oneClickShipment responses, update your logic to recognize AMZN_INTL as a valid carrierId for cross-border shipments.

2. Update Tracking API calls: When calling the Tracking API for cross-border shipments, pass carrierId=AMZN_INTL instead of the source country-specific carrier ID.

3. Update internal systems: Ensure your order management, warehouse management, and reporting systems can handle the new carrierId value.

This change does NOT affect:

• Pricing or rate calculations
• Tracking ID formats
• Label generation
• purchaseShipment API (does not return carrierId)
• API credentials or authentication
• Error codes or API schemas
• Billing or invoicing structure

Technical Details

1. getRates API Response for cross border shipments

Endpoint: /shipping/v2/getRates

Before:

{
  "rates": [
    {
      "rateId": "b647c4b5d84c215e...",
      "carrierId": "AMZN_FR",
      "carrierName": "Amazon Shipping",
      "serviceId": "SWA-FR-PRIME-PREM",
      "serviceName": "Amazon Shipping One Day"
    }
  ]
}

After:

{
  "rates": [
    {
      "rateId": "b647c4b5d84c215e...",
      "carrierId": "AMZN_INTL",
      "carrierName": "Amazon Shipping",
      "serviceId": "SWA-FR-PRIME-PREM",
      "serviceName": "Amazon Shipping One Day"
    }
  ]
}

2. oneClickShipment API Response for cross border shipments

Endpoint: /shipping/v2/oneClickShipment

Before:

{
  "rates": [
    {
      "carrierId": "AMZN_IT",
      ...
    }
  ]
}

After:

{
  "rates": [
    {
      "carrierId": "AMZN_INTL",
      ...
    }
  ]
}

3. Tracking API Request for cross border shipments

Endpoint: /shipping/v2/tracking

Note: The Tracking API response body does not include a carrierId field — only the request query parameter is affected.

Scope

Timeline

FAQs

1. Why is Amazon making this change?
This standardization simplifies cross-border shipment management and provides a consistent experience across all international shipping lanes. It eliminates the need to track source country-specific carrier IDs for cross-border shipments.

2. How do I identify if a shipment is cross-border?
A shipment is cross-border when the origin country code differs from the destination country code in your shipment request.

3. Do I need to update my API credentials or authentication?
No. This change only affects the carrierId field value. Your existing API credentials, authentication tokens, and endpoints remain unchanged.

4. Will the tracking ID format change?
No. Tracking ID formats remain unchanged. Only the carrierId parameter in the tracking API request needs to be updated to AMZN_INTL for cross-border shipments.

5. How can I test this change?
The sandbox environment has been updated. You can test your integration changes there before production rollout.

6. What if my system has hardcoded carrier ID values?
Update any hardcoded carrier ID logic to dynamically handle the carrierId returned in API responses. Hardcoding carrier IDs is not recommended as it reduces flexibility for future changes.

7. Will this affect my invoicing or reporting?
The carrierId field may appear in your invoices and reports. Ensure your financial systems and reporting tools can recognize AMZN_INTL as a valid carrier identifier. The underlying service charges and billing structure remain unchanged.

8. What if I'm using a third-party integration platform?
Contact your integration platform provider to ensure they are aware of this change and will update their Amazon Shipping connector accordingly.

9. Are there any changes to error codes or API schemas?
No. Only the value of the carrierId field is changing for cross-border shipments. All other request and response structures remain identical.

10. Does the x-amzn-shipping-business-id change for cross-border FRITES shipments?
No. Continue using the business ID corresponding to the origin country (where the parcel is shipped from), as you do today.

Example: If you are shipping from France to Italy, continue using x-amzn-shipping-business-id: AmazonShipping_FR. Only the carrierId value in API responses is standardized to AMZN_INTL for cross-border shipments.

Support

For questions or assistance with this change, please reach out to your Account Manager or support.