Amazon Now Lets Sellers Block Amazon Logistics on Multi-Channel Fulfilment Orders — With a 5% Surcharge
Amazon now lets sellers block Amazon Logistics on Multi-Channel Fulfilment orders at the account, order, or API level, though opting out incurs a 5% surcharge on affected orders.
Overview
Amazon has introduced a new option allowing sellers to block Amazon Logistics as the shipping carrier on Multi-Channel Fulfilment (MCF) orders. The feature addresses a long-standing request from sellers who use MCF to fulfil orders from non-Amazon sales channels but prefer to avoid Amazon-branded delivery experiences. However, opting out of Amazon Logistics comes with a 5% surcharge on affected MCF orders.
What's New
- Block Amazon Logistics on MCF orders — Sellers can now prevent Amazon Logistics from being assigned as the carrier for their Multi-Channel Fulfilment shipments
- 5% surcharge applies — Using this blocking feature triggers a 5% fee increase on the affected MCF order, reflecting the higher cost of routing through alternative carriers
- Three levels of control — The block can be applied at the account level, the individual order level through Seller Central, or programmatically via the MCF API
- Designed for external channels — The option was specifically added for sales channels that don't yet support Amazon Logistics as a recognised carrier
How to Block Amazon Logistics
Sellers have three distinct methods for blocking Amazon Logistics on their MCF orders, each suited to different operational needs. The most sweeping option is at the account level, where sellers can navigate to their MCF settings within Seller Central and enable the blocking option. This applies to all future MCF orders across every connected sales channel, making it ideal for sellers who consistently want to avoid Amazon-branded deliveries on their off-Amazon orders.
For more granular control, sellers can block Amazon Logistics on a per-order basis directly within Seller Central. When creating an MCF order through the platform, there is now a dedicated option on the order creation page to exclude Amazon Logistics for that specific shipment. This approach works well for sellers who only occasionally need to route orders through alternative carriers, perhaps for specific customers or sales channels that have particular delivery requirements.
API-Level Integration
The third method is available through the MCF API, which allows sellers and developers to programmatically block Amazon Logistics when submitting CreateFulfillmentOrder requests. This is particularly valuable for sellers with high-volume operations or those using automated order management systems that connect their various sales channels to Amazon's fulfilment network. By including the appropriate setting in their API calls, sellers can dynamically decide on a per-order basis whether to block Amazon Logistics without manual intervention in Seller Central.
Analysis & Recommendations
Why This Matters
Sellers using MCF to fulfil orders from non-Amazon channels can now avoid Amazon-branded deliveries that confuse customers and undermine independent branding. However, the 5% surcharge means sellers must weigh brand consistency against increased fulfilment costs.
Key Takeaways
- Amazon Logistics can now be blocked on MCF orders at account, order, or API level
- Blocking Amazon Logistics triggers a 5% surcharge on affected MCF orders
- The feature targets sellers fulfilling off-Amazon channel orders who want neutral carrier branding
- API-based blocking requires the newer MCF API version
Recommended Actions
- →Calculate the financial impact of the 5% surcharge against your MCF order volume before enabling the account-level block
- →Consider using per-order blocking for selective control rather than a blanket account-level setting to minimise surcharge costs
- →If using the MCF API, check that you are on the latest API version and review Amazon's developer documentation for the carrier blocking parameter
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!