ORY1 Returns Workflow: Inspection, Photos, Relabel, Relist
26.05.2026
Amazon ORY1 vs. Other France FCs: Where Should You Actually Send Stock?
26.05.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.
Every unit you send directly to Amazon ORY1 in Saran carries a cost stack that most sellers only discover after the invoice arrives. The fulfillment fee is visible. The inbound placement fee is partially visible. The low-inventory coverage charge, the volumetric weight surcharge, and the compounding effect of a poorly split shipment are almost never visible until margin has already been lost.
This breakdown is for mid-to-large FBA sellers distributing on Amazon.fr who need to understand exactly what drives the per-unit cost at ORY1 — and which handoff, if fixed first, produces the fastest margin recovery. The answer is almost always the inbound model, not the fulfillment rate itself.
How Amazon Builds the Per-Unit Cost at ORY1
The ORY1 fulfillment centre in Saran, near Orléans, is one of Amazon's primary French sortation and storage nodes. When sellers ship directly to ORY1, Amazon applies a layered cost structure that combines at least four distinct charge types before a single unit reaches a French customer.
The base fulfillment fee is calculated on dimensional weight, not always actual weight. For standard-size products, the bracket thresholds are narrow enough that a minor change in packaging can push a unit into the next tier. Above that sits the inbound placement fee, which applies when a seller uses the minimal shipment split option and Amazon must redistribute inventory internally across its French and Pan-EU network. A third-party logistics buffer, used as a pre-Amazon storage and cross-docking node, can absorb the split cost before the shipment ever reaches the FC appointment queue.
Volumetric Weight and Bracket Sensitivity
Amazon calculates fulfillment fees using the greater of actual weight or dimensional weight. At ORY1, this means a product that ships at 400g actual weight but occupies a 25 x 20 x 15 cm box may be billed at a higher weight bracket than the seller expects.
The practical control point is carton compliance and packaging audit before the inbound plan is created. Sellers who measure and declare dimensions accurately at the FNSKU level avoid bracket creep. Those who rely on supplier-declared dimensions often find their cost-to-serve is higher than the product margin can support. Reviewing dimensional data at the SKU level, before each inbound shipment, is the first check that prevents avoidable fee escalation at ORY1.
What Happens When the Bracket Is Wrong
When a unit is placed in the wrong dimensional weight bracket, the fee difference compounds across every unit in the shipment. For a seller moving several thousand units per month through ORY1, a single bracket error on a core SKU can represent a meaningful monthly margin leak that does not appear as a line item — it simply reduces net revenue per unit.
The consequence is not just financial. If the declared dimensions trigger an oversize classification, Amazon may route the unit to a different FC than planned, disrupting the inbound placement logic entirely. Oversize misclassification is one of the most common causes of unexpected storage cost at French FCs, because the unit ends up in a higher-cost storage zone with a longer dwell time before it can be re-routed or sold through.
The Inbound Placement Fee at ORY1: Minimal Split vs. Optimised Split
Amazon's inbound placement fee applies when a seller chooses the minimal shipment split option — sending inventory to a single FC rather than distributing it across multiple locations as Amazon's algorithm recommends. At ORY1, this fee is applied per unit and varies by product size tier and the degree of redistribution Amazon must perform internally. The operational decision is straightforward: sellers who accept the optimised split send inventory to multiple FCs upfront, paying lower or zero placement fees but managing more complex inbound logistics. Sellers who use a third-party logistics buffer in France can consolidate stock at the 3PL, then drip-feed inventory to multiple FC destinations in controlled batches — capturing the placement fee saving without managing multi-FC inbound complexity directly. This is the core economic argument for FBA prep services positioned between the supplier and ORY1.
Low-Inventory Fee: The Charge Most Sellers Discover Too Late
Amazon's low-inventory fee applies when a seller's stock level at a given FC falls below a threshold calculated from historical days of supply. The metric is tracked at the FNSKU level, using both a 30-day and a 90-day historical average. Sellers must monitor both windows independently — a product that looks healthy on a 90-day view can trigger the fee if the 30-day supply drops sharply due to a delayed replenishment or a customs hold.
At ORY1, this fee is particularly relevant for sellers who ship in large, infrequent batches rather than maintaining a steady inbound cadence. A single delayed container can push multiple FNSKUs below the threshold simultaneously, triggering per-unit charges across the entire affected range. The fee is not a penalty for stockout — it applies before stockout, when Amazon determines that the current inventory level is insufficient to meet projected demand without internal redistribution cost.
The structural fix is a pre-Amazon storage buffer in France that allows sellers to hold inventory close to the FC network and replenish in smaller, more frequent batches. This keeps the days-of-supply metric stable at the FNSKU level and prevents the low-inventory fee from activating during normal demand fluctuations or minor inbound delays.
Monitoring Days of Supply: The 30-Day Window
The 30-day historical days-of-supply figure is the more volatile of the two metrics Amazon tracks. It reflects recent sell-through rate and current inventory position. A promotional period, a seasonal spike, or a delayed replenishment can all compress this figure rapidly.
Sellers should pull this data from Seller Central's inventory health reports at least weekly for high-velocity FNSKUs. The practical threshold to watch is not the fee trigger itself but the buffer above it — if the 30-day figure is within two weeks of the threshold, a replenishment order should already be in transit. Waiting until the metric crosses the line means the fee is already accruing. Amazon FBA inbound planning that accounts for this lead time is the operational control that prevents the charge from appearing at all.
The 90-Day Window and Structural Risk
The 90-day historical days-of-supply figure is slower to move but harder to recover quickly. If a seller has had consistently low stock over a three-month period — due to supply chain disruption, customs delays, or a deliberate inventory reduction — the 90-day metric will reflect that pattern and may keep the low-inventory fee active even after stock is replenished.
This is the structural risk that sellers underestimate. Recovering a damaged 90-day metric requires sustained, consistent inbound volume over multiple weeks — not a single large shipment. Sellers who use a third-party logistics buffer to maintain a steady drip-feed of inventory into ORY1 protect both metrics simultaneously, because the FC always sees a consistent replenishment pattern rather than feast-and-famine inbound cycles that distort the historical baseline.
The ORY1 Native Model vs. a 3PL-Fed Model: Cost Card
Consider a seller shipping 2,000 standard-size units per month to Amazon.fr. Under the native model — single shipment, minimal split, direct to ORY1 — the cost stack includes the base fulfillment fee, the full inbound placement fee for single-location delivery, and a low-inventory surcharge if the replenishment cadence is monthly rather than weekly.
Under a 3PL-fed model, the same seller holds stock at a French pre-Amazon storage facility, ships to ORY1 in weekly batches of 400-500 units, and qualifies for the optimised placement rate by distributing across two or three FC destinations as Amazon recommends. The placement fee drops materially.
Pan-EU Oversize Surcharges and the Saran Routing Trap
ORY1 in Saran is a primary node in Amazon's Pan-EU network. For sellers enrolled in Pan-EU FBA, inventory placed at ORY1 may be redistributed to FCs in Germany, Spain, Italy, or Poland to serve local demand. This redistribution is handled by Amazon, but the cost of that movement can appear as a surcharge on the seller's account when the product is classified as oversize or when the redistribution volume exceeds Amazon's internal efficiency threshold.
The trap is that sellers often enrol in Pan-EU FBA to reduce per-unit fulfillment costs in non-French markets, without accounting for the redistribution surcharge that applies when ORY1 is used as the primary inbound point. The fee is not always labelled clearly, and it compounds with the placement fee if the seller is already on the minimal split option.
The practical fix is to audit Pan-EU redistribution costs separately from French fulfillment costs. Sellers using Amazon FC forwarding through a 3PL buffer can control which FC receives the initial inbound shipment, reducing the distance and cost of Amazon's internal redistribution. This is particularly relevant for sellers with high-volume SKUs that Amazon consistently moves from ORY1 to German or Spanish FCs — routing the initial inbound to a more central FC may reduce the total redistribution cost even if the inbound transport cost is slightly higher.
Pre-Shipment Checks: Unit Economics
- Verify dimensional weight at FNSKU level before creating the inbound plan
- Confirm size tier classification matches the product's current packaging
- Check 30-day days-of-supply for all active FNSKUs before each shipment
- Confirm the inbound placement option selected matches the fee budget for the shipment
- Audit Pan-EU redistribution history for high-velocity SKUs to identify routing patterns
- Validate that carton compliance meets ORY1 receiving requirements before dispatch
3PL Buffer Handoff Checks
- Confirm storage window is booked at the French pre-Amazon storage facility before goods arrive
- Verify FNSKU labels are applied correctly at the 3PL before FC forwarding
- Check that the drip-feed schedule aligns with the 30-day days-of-supply threshold for each FNSKU
- Confirm FC appointment is booked for each outbound batch before dispatch from the 3PL
- Validate that the inbound plan reflects the optimised split option, not minimal split
- Review removal handling procedures for any units rejected at FC receiving
Implementing the Buffer Model: Sequence and Ownership
The shift from direct-to-ORY1 shipping to a 3PL-buffered inbound model follows a specific sequence. Getting the order wrong — for example, booking FC appointments before the 3PL storage window is confirmed — creates the same inventory-stuck-between-systems problem that the buffer is designed to prevent.
Step one is establishing the pre-Amazon storage facility in France with a confirmed inbound schedule from the supplier or freight forwarder. Step two is setting the drip-feed cadence based on the 30-day days-of-supply metric for each FNSKU — not on a fixed weekly schedule, but on a demand-responsive one. Step three is creating the inbound plan in Seller Central using the optimised split option, with FC destinations confirmed before the 3PL dispatches each batch.
Ownership of the days-of-supply monitoring must sit with one person or one system. When it is split between the seller's operations team and the 3PL, the 30-day metric can deteriorate before either party acts. A single coordinated inbound plan, reviewed weekly, with clear escalation if any FNSKU drops within two weeks of the low-inventory threshold, is the operational control that keeps the fee structure predictable. Amazon FBA prep and forwarding support at the 3PL level should include this monitoring as a standard handoff, not an optional add-on.
Shipment Split Decisions: The Structural Cost of Getting It Wrong
The minimal shipment split option is not inherently wrong — for sellers with very low inbound volume or highly concentrated French demand, it may be the correct economic choice. The error is applying it by default, without calculating the placement fee cost against the operational saving of a single inbound destination. For sellers moving more than a few hundred units per month through ORY1, the optimised split almost always produces a lower total cost when the placement fee is included in the calculation. The operational complexity of managing two or three FC destinations is real, but it is manageable when a 3PL handles the split at the dispatch stage. The seller sees one inbound plan; the 3PL executes the multi-destination dispatch.
Check Your Placement Fee First
Before adjusting any other part of the ORY1 cost stack, calculate the placement fee you are currently paying under the minimal split option. For most sellers above a few hundred units per month, this single line item is the largest controllable cost in the inbound model.
Track Both Supply Metrics Weekly
Pull both the 30-day and 90-day historical days-of-supply figures from Seller Central every week for your top FNSKUs. If either metric is within two weeks of the low-inventory threshold, a replenishment batch should already be staged at your French storage buffer and ready to dispatch.
Audit Pan-EU Redistribution Costs
If you are enrolled in Pan-EU FBA and using ORY1 as your primary inbound point, pull your redistribution cost history by SKU. High-volume products that Amazon consistently moves from Saran to other EU FCs may be cheaper to route directly from your 3PL to a more central FC at the inbound stage.
What to Fix First at ORY1
The ORY1 fee structure is not opaque by accident — it is layered in a way that makes each individual charge look small until they are calculated together at the FNSKU level. The sellers who control their unit economics at Saran are the ones who treat the inbound model as a financial decision, not a logistics default.
The sequence is clear: audit your placement fee option first, then stabilise your days-of-supply metrics with a consistent inbound cadence, then review Pan-EU redistribution costs for your highest-volume SKUs. Each of these steps requires data that is already available in Seller Central — the gap is usually not information, it is the operational structure to act on it before the invoice arrives.
A French pre-Amazon storage buffer, used as a cross-docking and drip-feed node, addresses all three problems simultaneously. It converts an unpredictable, batch-driven inbound model into a controlled, metric-aware one. For sellers distributing on Amazon.fr at meaningful volume, this is not an optional upgrade — it is the structural fix that makes the ORY1 cost stack manageable. Reviewing your current inbound plan against the fee layers described here is the practical next step before the next shipment is booked.
If your ORY1 per-unit cost is higher than your product margin can absorb, the inbound model is almost certainly where the leak is. FLEX. provides pre-Amazon storage, FBA prep, and FC forwarding support in France, with inbound planning that accounts for placement fees, days-of-supply thresholds, and multi-FC split logistics. Speak with the FLEX. France operations team about mapping your current ORY1 cost stack and identifying which handoff to fix first.
