Catalogue ForgeThe layer between your product data and O1's PIM + infrastructure
Catalogue Forge is the layer between your product data and O1's PIM plus the rest of our infrastructure. It maps whatever you already have — ERP, PIM, Shopify, custom DB, CSV or XLSX — into the O1 data model, so every downstream Forge (PIM syndication, Advertising, Visual, Support, Logistics) operates against one canonical source. Live and running today as part of every brand onboarding.
The onboarding pipeline our team uses for every brand we bring live as Merchant of Record. ERP / PIM / Shopify / CSV / spreadsheet — mapped into the O1 data model before anything downstream runs.
Concrete capabilities
- Maps catalogue, attributes, variants and assets from ERP, PIM, Shopify, custom DB, CSV or XLSX into the O1 data model
- Bulk imports, scheduled syncs, REST API — your choice of cadence per source
- The onboarding workflow O1's team runs to get a new brand live across marketplaces
- Layers above O1 PIM — Catalogue Forge brings data IN, PIM pushes per-channel feeds OUT
- Same workspace and single login (app.o1.eu) as the rest of O1 Suite
Where Catalogue Forge sits in the Merchant-of-Record stack.
Catalogue Forge is the first layer a new brand touches inside the Merchant-of-Record operation. We take whatever you already have — a SAP or Microsoft Dynamics export, an Akeneo or Pimcore feed, a Shopify catalogue, a master spreadsheet — and map fields, variants, family attributes and asset references into the O1 data model. From that moment on, the same canonical SKU drives everything downstream: O1 PIM syndicates per-marketplace content, Visual Forge attaches imagery to the same record, Advertising Forge uses identical product identifiers in campaigns, Logistics Forge routes inventory against the same SKU keys, and Support Forge attaches buyer cases to it. When your master data changes upstream — a new SKU launch, a packaging update, a discontinuation — Catalogue Forge re-syncs the diff, and every other Forge inherits it in the next run.
How Catalogue Forge connects with the rest of the Suite.
Catalogue Forge sits directly upstream of O1 PIM: it normalises your inbound product data into the model PIM then syndicates per marketplace. Once a brand is live, every other Forge — Advertising, Visual, Support, Logistics — operates against the catalogue Catalogue Forge wired in.
How Catalogue Forge shows up for a brand we run.
A European consumer-electronics seller — 4 brand catalogues, two ERPs after an acquisition
Two ERPs spoke two different attribute schemas, and the merged catalogue carried a long tail of incomplete records on Amazon EU. Catalogue Forge mapped both source systems into one O1 data model during onboarding, reconciled duplicate SKU keys, and held the inbound feed open on a nightly cadence. Inside three weeks every downstream Forge ran against one canonical catalogue — the listing rebuild, the ad restructure and the fulfilment routing all started from the same source of truth.
See the full O1 Suite operation.
Catalogue 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.