Logistics ForgeYour warehouse · FBA / Bol logistics · 2 O1 EU FCs
Logistics Forge is the unified fulfilment routing layer inside O1 Suite, managed by O1's logistics team. Three fulfilment models, one routing surface — per SKU per country, you pick any of them: your own warehouse, marketplace-native programmes, or O1's own EU fulfilment centres.
Two own EU fulfilment centres (DE + NL) plus native Amazon FBA, Bol logistics and other marketplace-fulfilment integrations — all running live today for the brands we operate. Plus brand-warehouse routing for brands that prefer to keep stock in their own DC.
Concrete capabilities
- Model 1 — your own warehouse: you pick / pack / ship, O1 connects the marketplaces to it
- Model 2 — marketplace-native: Amazon FBA, Bol.com logistics, and other channel-specific programmes
- Model 3 — two own O1 EU fulfilment centres (DE + NL) when you want O1 to handle the physical side
- Per SKU per country, mix any of the three models — change the routing without re-onboarding
- Returns processed back to whichever node shipped them, with basic refurbishment and automatic re-listing where re-saleable
Where Logistics Forge sits in the Merchant-of-Record stack.
Logistics Forge is the physical layer of the Merchant-of-Record operation. It carries the same SKU identifiers Catalogue Forge wired in and O1 PIM syndicates, so the routing engine, the marketplace listings and the inbound replenishment view all agree on what's in stock and where. Per SKU per country, the brand and O1's logistics team pick the model: hold inventory in your own warehouse and let O1 connect every marketplace into it; ship into Amazon FBA or Bol logistics where channel-native fulfilment wins the Buy-Box; or hand the physical side to one of O1's two EU FCs in Germany and the Netherlands. Returns flow back to whichever node shipped them, basic refurbishment runs at the FC, and resaleable units re-list automatically. The result is a single fulfilment surface inside the Suite instead of three logistics dashboards stitched together by hand.
How Logistics Forge connects with the rest of the Suite.
Logistics Forge wires into the Suite's Replenishment module: purchase orders, inbound shipments and items-to-be-shipped show up in the same workspace as orders and returns. The catalogue Catalogue Forge wired in is the same catalogue Logistics Forge routes against.
How Logistics Forge shows up for a brand we run.
A mid-market apparel brand — UK production, EU demand concentrated in Germany with a second tier in France and the Benelux
Fast-moving SKUs needed Prime-eligible FBA stock close to German buyers, slower SKUs were tying up cash in over-shipped FBA inventory, and B2B pallet orders ran best out of the brand's own UK DC. Logistics Forge routed bestsellers into FBA DE, mid-velocity SKUs into O1's NL FC for Bol and EU-wide MFN coverage, and kept B2B + long-tail in the brand's warehouse. Routing decisions changed quarterly as the data moved, without re-onboarding the brand or rebuilding the marketplace connections.
See the full O1 Suite operation.
Logistics Forgeis one of seven Forges inside O1 Suite. They share one data model, one workspace and one accountable team per brand. Talk to us and we'll walk you through how the stack runs against the brands we already operate.