Navigating French TVA: Autoliquidation and OSS Setup for Benelux-Based Brands
15.06.2026
Colissimo vs. Chronopost vs. Mondial Relay: Choosing the Right Carrier by SKU Profile
15.06.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.
Amazon's XOR2 fulfillment center in Satolas-et-Bonce is not a generic French FC. It carries a dual designation — robotics-integrated receiving and deep-sea import container reception — that makes it both faster at processing compliant inbounds and less forgiving of non-compliant ones than a standard manual-receiving facility. Sellers who treat XOR2 as a routine destination, booking the last available Carrier Central slot and presenting pallets built to general French FBA tolerances, often discover the gap the hard way: a gate refusal, a missed appointment rebooking cycle, or inventory sitting in a receiving queue for ten days before appearing as available in Seller Central. This guide covers the three operational control points that determine whether your XOR2 inbound moves cleanly — appointment scheduling, pallet and label compliance for automated receiving, and capacity constraint windows — so you can fix the right handoff before your next delivery.
Why XOR2 Operates Differently from Other French FCs
XOR2's position in the French FC network is shaped by two factors that do not apply to Amazon's other French facilities. First, its location near Lyon-Saint-Exupéry Airport and the A432 motorway makes it the natural gateway for southern France, Switzerland, and the Francophone cross-border corridor — a catchment that generates disproportionate inbound volume from Iberian sellers, Swiss cross-border flows, and Asia-origin seasonal inventory routed overland from Marseille and Fos-sur-Mer. Second, XOR2's automated receiving infrastructure — including conveyor-fed tote-handling systems and autonomous mobile robots being rolled out across Amazon's European FC network — means that the receiving decision at the dock is increasingly made by a scanner, not a human. A human receiver can make a pragmatic call on a borderline pallet. An automated scanner cannot. The consequence is that XOR2's inbound compliance requirements are effectively stricter in practice than Amazon's published French FBA spec, and the penalty for non-compliance is faster and less negotiable than at a manual-receiving facility.
Carrier Central Booking: The 24-Hour Rule Is the Floor
What the Booking Requirement Actually Means
All inbound shipments to XOR2 must be booked through Carrier Central with a minimum 24-hour advance notice, and receiving hours run Monday to Friday from 06:00 to 16:00. Those are the published parameters. The operational reality is that the 24-hour minimum is the floor, not the planning target. During standard periods, booking three business days ahead is the working standard for sellers using Amazon FC forwarding in France. During Q3 and Q4 peak windows, available appointment slots at XOR2 fill faster than the published lead time implies, and sellers who wait until 24 hours before their planned delivery date will frequently find no slot available — triggering a rebooking cycle that can push the pallet's receiving date back by five to seven days. Sellers shipping from a pre-Amazon buffer warehouse near Lyon should treat three to five business days as the minimum booking horizon during any peak period.
What a Missed Appointment Costs in Practice
The Rebooking Cycle and Its Downstream Effect
A missed or refused appointment at XOR2 does not simply delay one delivery. It triggers a rebooking cycle that compounds across the replenishment timeline. A pallet turned away at the dock without a confirmed appointment cannot be rescheduled on the same day — the next available slot may be five to seven days out during high-capacity periods, and the inventory remains unavailable to sell throughout that window. For sellers whose XOR2 stock covers southern France and cross-border demand, a seven-day receiving delay during a peak sales period translates directly into lost buy box coverage and suppressed ranking. Sellers who maintain a confirmed backup appointment for every primary booking during Q3 and Q4 avoid this exposure entirely. The backup slot costs nothing to hold and eliminates the rebooking cycle as a planning risk. Partial shipment arrivals without a confirmed appointment are turned away regardless of how much of the load is compliant.
Pallet Compliance for XOR2's Automated Receiving Systems
XOR2's automated conveyor and tote-handling infrastructure imposes tolerance requirements that go beyond Amazon's general French FBA pallet specification. The practical control point is label placement. Every carton label must be positioned on the correct face in a location that automated scanners at the conveyor entry point can read without manual repositioning. A label placed two centimetres outside the scanner's read zone will pass a human visual check at the dock but will be flagged for manual processing — removing the pallet from the automated receiving queue and adding unpredictable dwell time before units appear as available inventory. Pallet height must be consistent within the tolerance that automated stacking systems can handle, and stretch wrap must be applied at a tension that holds the load without obscuring barcodes. None of these requirements are unique to XOR2 in principle, but the consequence of non-compliance is faster and less negotiable here than at a manual-receiving facility. FBA prep services calibrated to XOR2's specific tolerances prevent this failure at source.
XOR2 Capacity Constraints: The Three Peak Windows
XOR2's receiving capacity is not uniformly constrained across the year. Three seasonal windows consistently produce the longest appointment lead times and the highest gate refusal rates for sellers without confirmed slots and compliant pallets. The first is the Q3 July–August inbound surge, driven by back-to-school replenishment and early Q4 inventory flowing through XOR2's southern France and cross-border catchment. Sellers targeting this window should book appointments in late May to early June — well before the surge compresses available slots. The second is the October–November pre-Black Friday inbound peak. XOR2's deep-sea container reception designation makes it the primary French entry point for Asia-origin seasonal inventory arriving at Marseille and routed overland to the Lyon zone, and the volume concentration during this window is significant. Appointments for this period should be confirmed no later than September. The third window is the post-January Rebajas restock period, when Iberian sellers who used XOR2 as their French FC during the summer sale period return simultaneously with replacement inventory. Booking before the Christmas period closes the window is the practical rule for this cycle.
What to Confirm Before Your XOR2 Appointment
Pre-Delivery Compliance Checklist
Before releasing inventory to XOR2, confirm each of the following control points. Carrier Central appointment reference confirmed and within the receiving window (Monday to Friday, 06:00–16:00). Backup appointment slot held for the same delivery week. FBA shipment ID and PRO label attached to every pallet. Carton labels positioned on the correct face within automated scanner read zone. Pallet height consistent and within dimensional tolerance for automated stacking. Stretch wrap applied at correct tension — load secured without barcode obstruction. ASN submitted and matched to the physical shipment. Carrier briefed on XOR2 dock procedures and appointment reference. For sellers using Amazon FC forwarding in France from a cross-border origin, confirm that the inbound plan in Seller Central reflects the correct destination FC code before the shipment departs the origin warehouse. A mismatch between the Seller Central shipment plan and the physical destination is a common cause of dock refusal that has nothing to do with pallet compliance.
What Breaks When These Controls Are Skipped
Common XOR2 Inbound Failure Modes
The failure modes at XOR2 follow a consistent pattern. Appointment timing failures are the most frequent: a seller books at 24 hours, finds no slot, ships anyway assuming the dock will accept a walk-in, and is turned away. The pallet returns to the carrier's depot, a new appointment is booked five days out, and the inventory misses a peak sales window. Label placement failures are the second most common: pallets that pass visual inspection at the prep center but carry labels positioned for human reading rather than automated scanner reading. These pallets enter the dock, clear the initial check, and then stall in manual processing — the seller sees the shipment as received but units do not appear as available inventory for days. Partial shipment failures occur when a multi-pallet delivery arrives with one pallet missing its appointment reference — the entire delivery may be refused, not just the non-compliant unit. Each of these failures is preventable with the right pre-Amazon storage and preparation workflow upstream of the FC.
How the XOR2 Inbound Owner Map Works
Understanding who owns each handoff in the XOR2 inbound flow prevents the most common accountability gaps. The seller owns the Seller Central shipment plan, the FBA shipment ID, and the Carrier Central appointment booking. The prep operator owns carton labelling, pallet build, stretch wrap tension, and dimensional compliance. The carrier owns the appointment reference at the dock and the delivery window. Amazon owns the receiving decision at the dock — and at XOR2, that decision is increasingly automated. The gap that causes most XOR2 inbound failures sits between the prep operator and the carrier: the prep operator builds a compliant pallet, but the carrier arrives outside the booked window or without the appointment reference, and the dock refuses the delivery. Sellers using a coordinated Amazon FC forwarding service in France — where the prep operator and the carrier operate under the same instruction set — close this gap by design. The appointment reference, the pallet spec, and the delivery window are confirmed at a single point before the shipment moves.
The Hidden Cost of Managing XOR2 Inbound as a Carrier Task
The most common weak operating assumption among sellers shipping to XOR2 for the first time is that inbound management is a carrier booking task — something delegated to whoever arranges the final-mile delivery. This assumption works at manual-receiving FCs where a human receiver can exercise discretion. At XOR2, it produces a specific and predictable failure pattern. The carrier books the appointment at the minimum lead time, arrives at the dock with a pallet built to general FBA tolerances, and encounters either a full appointment schedule or an automated receiving rejection. The seller then faces a seven-to-fourteen-day delay before the inventory appears as available, during which the replenishment gap is live and the cost-to-serve has increased by the carrier's return trip, the rebooking fee, and the storage cost at the carrier's depot. The operational fix is to remove the dependency on origin-to-FC transit timing entirely. Sellers for whom XOR2 is a primary or high-volume French FC destination should hold pre-compliant, appointment-ready inventory at a buffer warehouse near Lyon, releasing to XOR2 on a controlled schedule aligned with confirmed appointment slots. This model eliminates transit timing uncertainty as a variable in appointment compliance — which is the core planning risk that makes long-haul and cross-border inbound flows to XOR2 unreliable when managed as a single-leg carrier task.
XOR2 Appointment Readiness Checks
- Carrier Central appointment confirmed at least three business days ahead during standard periods
- Backup appointment slot held for the same delivery week during Q3 and Q4
- Receiving window verified: Monday to Friday, 06:00–16:00
- FBA shipment ID confirmed in Seller Central before shipment departs
- PRO label attached to every pallet and legible
- Carrier briefed on appointment reference and XOR2 dock address
- ASN submitted and matched to physical shipment contents
XOR2 Pallet and Label Compliance Checks
- Carton labels on correct face, within automated scanner read zone
- No label obscured by stretch wrap or pallet edge overlap
- Pallet height consistent and within dimensional tolerance
- Stretch wrap applied at correct tension — load secured, barcodes clear
- No mixed SKUs on a single pallet unless shipment plan permits
- FNSKU labels applied at unit level before palletisation
- Pallet count matches Seller Central shipment plan exactly
Implementing a Buffer-Led XOR2 Inbound Model
The practical implementation sequence for sellers who want to remove XOR2 inbound risk from their replenishment cycle starts before the inventory leaves the origin. Step one is to establish a pre-Amazon storage buffer near Lyon — a facility that holds inventory in a pre-compliant state, built to XOR2's specific pallet and labelling tolerances, and ready to release on a confirmed appointment slot without further rework. Step two is to decouple the origin-to-buffer transit from the buffer-to-FC release. Long-haul and cross-border inbound flows — Asia-origin containers arriving at Marseille, Iberian sellers routing through the Francophone corridor, Benelux sellers consolidating for southern France — carry transit timing uncertainty that makes appointment compliance impossible to guarantee on a single-leg basis. Holding inventory at the buffer absorbs that uncertainty. Step three is to book XOR2 appointments from the buffer, not from the origin. The buffer operator confirms the appointment, releases the pallet on the confirmed slot, and the carrier moves a pre-compliant load on a known schedule. This model is how forwarding to Amazon in France works when the inbound flow involves cross-border origins or seasonal volume concentration — and it is the operational structure that prevents the seven-to-fourteen-day receiving delays that sellers experience when they manage XOR2 inbound as a direct-from-origin carrier task.
XOR2 and the Francophone Cross-Border Inbound Corridor
XOR2's geographic position makes it the logical French FC destination for sellers whose consumer base is concentrated in southern France, French-speaking Switzerland, and the northern Italy corridor. That geographic advantage is real — but it only materialises for sellers whose inbound flow arrives at the dock in a state that XOR2's automated receiving systems can process without manual intervention. Sellers routing inventory from Iberian origins through the Francophone corridor, or consolidating Benelux stock for southern France distribution, face a specific planning challenge: the transit leg is long enough that appointment timing cannot be managed reactively. A shipment that departs Spain or Belgium without a confirmed XOR2 appointment slot will arrive at the dock during a period when available slots may be five or more days out. The solution is not faster transit — it is a pre-Amazon storage buffer in the Lyon area that decouples transit arrival from FC release. Sellers using Amazon fulfillment center delivery service in France through a buffer model hold appointment control at the buffer, not at the origin, and release to XOR2 only when a confirmed slot is in hand.
Q3 Window
Book July–August XOR2 appointments in late May to early June. Back-to-school and early Q4 replenishment compress available slots faster than the published lead time implies. Buffer inventory in Lyon before the surge.
Q4 Window
Book October–November pre-Black Friday appointments no later than September. XOR2's deep-sea container reception role concentrates Asia-origin seasonal inventory at this FC during this window. Slot availability tightens early.
January Restock Window
Book post-Rebajas January restock appointments before the Christmas period closes the booking window. Iberian sellers returning with replacement inventory create a simultaneous demand spike at XOR2 in early January.
The decision every seller shipping to XOR2 needs to make is whether they are managing inbound as a carrier booking task or as a controlled preparation and appointment workflow. The first approach works at manual-receiving FCs where human discretion absorbs borderline compliance. At XOR2, it produces gate refusals, rebooking cycles, and inventory unavailable to sell for seven to fourteen days during the periods when replenishment matters most. The second approach — pre-compliant inventory held at a buffer warehouse near Lyon, released on confirmed appointment slots, with label placement and pallet dimensions built to automated scanner tolerances — removes the variables that cause XOR2 inbound failures. For sellers whose XOR2 volume is high enough that a single receiving delay affects buy box coverage or seasonal sell-through, the buffer model is not an optional upgrade. It is the operating standard. The three peak windows — Q3 July–August, October–November pre-Black Friday, and post-January Rebajas — are the periods where the gap between these two approaches is most visible in Seller Central data. Knowing how to send inventory to Amazon fulfillment centers in France with XOR2-specific preparation in place is what separates sellers who hit their replenishment targets from those who spend peak periods chasing receiving confirmations.
FLEX. operates a pre-Amazon storage and forwarding service in the Lyon area designed specifically for sellers shipping FBA inventory into XOR2. Inventory arrives at the FLEX. buffer facility, is built or verified to XOR2's pallet and labelling tolerances, and is released to the FC on confirmed Carrier Central appointment slots — removing transit timing uncertainty from the appointment compliance equation. If you are planning your first XOR2 inbound, troubleshooting a previous gate refusal, or managing a cross-border inbound flow that makes direct-from-origin appointment booking unreliable, contact the FLEX. France team to discuss the preparation and forwarding workflow that fits your replenishment cycle.
