Cosco’s Red Sea Return: the Transit-Time and Cost Benchmarks Amazon.fr Sellers Must Now Use for China Inbound
12.08.2026
Your Carton Passed the Dock Check Last Month. It Might Not Pass This Week.
14.08.2026
FLEX. Logistics
We provide logistics services to online retailers in Europe: Amazon FBA prep, processing FBA removal orders, forwarding to Fulfillment Centers - both FBA and Vendor shipments.
A seller ships a pallet toward Amazon.fr and gets an FC code back from Carrier Central: XOR2. The next shipment, same product, same season — XFRN. Nothing about the seller’s setup changed, yet the destination did. If you sell into France and keep seeing these two codes rotate through your inbound plans, the honest answer is that XOR2 (Satolas-et-Bonce) and XFRN (Saint-Quentin-Fallavier) are two Geodis-operated fulfilment centres sitting in the same greater Lyon logistics cluster, and Amazon — not the seller — decides which one gets your stock. This article compares what genuinely differs between them, what is essentially shared, and what that means for your forwarding and prep planning, since routing preference between the two is not something an Amazon fulfillment center delivery service in France can influence.
Why XOR2 and XFRN Keep Showing Up Together in Carrier Central
XOR2 and XFRN sit roughly a short drive apart in the Lyon logistics belt, both close to Lyon-Saint-Exupéry Airport, and both run day-to-day by Geodis under Amazon’s operating contract. That proximity is not a coincidence — it reflects how Amazon clusters fulfilment capacity around strong transport nodes rather than spreading facilities evenly across a region. For a seller booking inbound shipments through Carrier Central, this means the appointment slot, the receiving process, and the general handling expectations at either code will feel broadly similar, because the same operator is running both buildings with the same regional playbook.
Both facilities accept deep-sea import containers, which matters if your product moves through a French or Benelux port before reaching FBA stock, and both run active pallet exchange programs, so the mechanics of dropping and swapping pallets at the dock are consistent regardless of which code you land on. This is the part sellers underestimate: the operational experience of delivering to XOR2 versus XFRN is closer to identical than most FC comparisons across France, which changes what you should actually be planning for.
What Actually Differs
The real distinction between these two sites is road access, not warehouse process. XOR2, at Satolas-et-Bonce, is reached via the A432 motorway. XFRN, in Saint-Quentin-Fallavier, sits on the A43 corridor — the same route that runs through the Fréjus tunnel into Italy. That single detail matters for carriers running cross-border legs, since a truck already routed toward northern Italy has a more natural path to XFRN than to XOR2, purely on road geometry rather than any Amazon-side preference.
For a seller, this distinction is informational, not actionable. You are not selecting a motorway corridor when you book a shipment — Amazon assigns the FC, and Carrier Central returns the destination code after the fact. Knowing the A432/A43 split helps you anticipate transit time variance and brief your carrier correctly, not steer your inventory.
What Stays the Same
Everything that actually affects your prep and forwarding decisions is shared between the two. Both facilities serve the same broad demand zone — southeastern France, Switzerland, and northern Italy — so your regional stock strategy doesn’t need a separate plan for each code. Both accept deep-sea import containers, both are Geodis-run, and both have live pallet exchange programs, meaning your carton compliance, pallet structure, and labelling standards don’t change depending on which one you draw.
The practical takeaway: build your forwarding process to satisfy either destination equally well. A prep and pallet setup that only works cleanly for one of the two codes is a setup with a gap, since you cannot predict — or request — which one you’ll get on any given inbound plan.
Here’s the checkpoint that actually matters before a truck leaves your prep facility: confirm your carton labels and pallet configuration meet Amazon’s general inbound standard, not a facility-specific variant. Because XOR2 and XFRN share an operator and a regional profile, there is no separate rulebook to satisfy for one versus the other. What changes shipment to shipment is the FC code returned by Carrier Central after booking, and your appointment window, ASN accuracy, and pallet exchange documentation should already be built to travel to either address without rework. Sellers using FBA prep services with a standardized carton and pallet template avoid the scramble of re-labelling once the destination code lands.
What This Means for Forwarding Planning in the Lyon Corridor
Since you cannot choose XOR2 over XFRN or the reverse, the planning question shifts from “which FC do I want” to “is my inbound process resilient to either.” That reframing has real consequences for how you set up Amazon FC forwarding from a port of entry, a bonded warehouse, or a pre-Amazon storage buffer. If your forwarding partner builds routing plans around a single assumed destination, a code switch between shipments can expose gaps — a carrier not familiar with the A43/Fréjus corridor, or an appointment booking process tuned to one facility’s typical slot pattern rather than a general-purpose approach.
The stronger approach treats both codes as equally likely outcomes from the same regional lane. That means your carrier relationships, your pallet exchange paperwork, and your buffer stock positioning should be built for the greater Lyon cluster as a whole, not for one specific FC address. A forwarding setup that already accounts for deep-sea container intake, pallet exchange compliance, and flexible appointment booking through Carrier Central will handle either destination without a separate contingency plan. This is the operational value of working the corridor rather than trying to game an assignment you don’t control.
Consider a seller shipping FBA-bound stock from a bonded facility near Marseille. The plan assumes XOR2 based on last quarter’s pattern, books a carrier tuned to the A432 approach, and prepares pallets accordingly. Carrier Central returns XFRN instead. If the carrier isn’t equally comfortable on the A43, or the appointment slot was pre-negotiated around the wrong facility’s typical booking rhythm, the shipment slips a day — not because anything about the product or the paperwork was wrong, but because the plan was built for one code instead of the corridor. A forwarding setup designed around Amazon FC forwarding in France as a regional capability, not a single-address bet, avoids this exact failure.
Control Point
You control carton and pallet build, ASN accuracy, and carrier readiness across both A432 and A43 access routes. You do not control which FC code Carrier Central assigns.
Visibility Checkpoint
Confirm the returned FC code against your carrier’s route familiarity before dispatch, not after — the address on the label should match a route your carrier has actually run.
Escalation Rule
If pallet exchange documentation or appointment booking fails at either facility, treat it as a corridor-wide process issue, not an FC-specific one, and fix the template.
Plan for the Corridor, Not the Code
XOR2 and XFRN are more alike than different: same operator, same airport proximity, same container capability, same pallet exchange programs, same regional customer base across southeastern France, Switzerland, and northern Italy. The one confirmed difference — A432 access for XOR2 versus A43/Fréjus-tunnel access for XFRN — is useful context for your carrier, not a lever you can pull to influence assignment. Every inbound shipment to either facility still gets booked through Amazon’s Carrier Central, and that system, not seller preference, decides the destination.
The decision that actually sits in your hands is whether your forwarding and prep setup is built for the Lyon corridor as a whole. That means carton labels, pallet structure, and carrier route familiarity that hold up whether the code comes back as XOR2 or XFRN. If your current process only performs well against one assumed destination, that’s the gap worth closing before your next shipment, ideally by reviewing your prep center France workflow against both access routes rather than one.
Since the FC assignment isn't something a seller controls, the more useful question is whether your inbound setup would hold up regardless of which code lands on your shipment plan. A carton spec, pallet build, or carrier booking that only works cleanly for one approach route can quietly become the reason a slot gets missed when Amazon assigns the other facility instead. Contact the FLEX. Logistique team to review your current carton, pallet, and carrier plan against both the A432 and A43 approach — a practical way to close the gap before it costs you a missed appointment window.
