Where DOXAP fits in your commerce stack: a coverage matrix
Every commerce system covers a slice of the picture: the CMS runs the storefront, the PIM holds the catalog, the ERP owns stock and finance. The gaps appear between them. This matrix maps who covers what, capability by capability, and where DOXAP fits.
The building blocks of a commerce stack
Most sellers run a handful of specialised systems, each excellent at its own job:
- CMS (storefront): your own e-commerce site, checkout and customer experience.
- PIM (catalog): the product reference, attributes, media and translations.
- ERP / WMS (stock and finance): inventory, purchasing, accounting and warehouse operations.
- OMS (orders): order capture, fulfilment and after-sales.
- Pricing tools: price rules and marketplace repricers.
- Feed integrator (marketplaces): pushes product feeds to Amazon, Cdiscount and other channels.
- iPaaS / ETL: generic integration and data pipelines between systems.
None of these owns the whole flow. The catalog lives in one place, stock in another, orders in a third, and every marketplace wants its own format. DOXAP is the orchestration hub that sits in the middle: it becomes the single source of truth for product data and keeps every system and channel consistent.
The coverage matrix
Reading guide: ● handled natively, ◐ partial or dependent on setup, ○ not covered. The DOXAP column is highlighted. Scroll the table sideways on mobile.
| Capability | CMS | PIM | ERP / WMS | OMS | Pricing | DOXAP | Feed integrator | iPaaS / ETL |
|---|---|---|---|---|---|---|---|---|
| Catalog & product | ||||||||
| Product reference (PIM) | ◐ | ● | ◐ | ○ | ○ | ● | ○ | ○ |
| Media, description, translation enrichment | ◐ | ● | ○ | ○ | ○ | ● | ○ | ○ |
| Codification, families, attributes | ○ | ● | ◐ | ○ | ○ | ● | ○ | ○ |
| Bundles & variants | ◐ | ◐ | ◐ | ○ | ○ | ● | ○ | ○ |
| Price & margin | ||||||||
| Pricing by SKU / channel / country | ◐ | ○ | ◐ | ○ | ● | ● | ◐ | ○ |
| COGS & acquisition costs | ○ | ○ | ● | ○ | ◐ | ● | ○ | ○ |
| Promotions | ◐ | ○ | ○ | ○ | ● | ● | ◐ | ○ |
| RSP & margin analysis | ○ | ○ | ◐ | ○ | ● | ● | ○ | ○ |
| Channels & distribution | ||||||||
| Customer storefront & checkout | ● | ○ | ○ | ○ | ○ | ○ | ○ | ○ |
| Marketplace distribution (COT) | ○ | ○ | ○ | ○ | ○ | ● | ● | ◐ |
| Per-channel category mapping | ○ | ◐ | ○ | ○ | ○ | ● | ● | ○ |
| Push products to marketplaces | ○ | ○ | ○ | ○ | ○ | ◐ | ● | ○ |
| Push offers (price / stock) to marketplaces | ○ | ○ | ○ | ○ | ○ | ◐ | ● | ○ |
| Orders & customer service (OMS) | ||||||||
| Multichannel orders | ◐ | ○ | ◐ | ● | ○ | ● | ◐ | ◐ |
| Refunds & incidents | ◐ | ○ | ◐ | ◐ | ○ | ● | ○ | ○ |
| Marketplace ticketing / after-sales | ○ | ○ | ○ | ◐ | ○ | ● | ◐ | ○ |
| Stock & logistics | ||||||||
| Multi-warehouse stock | ◐ | ○ | ● | ● | ○ | ● | ○ | ◐ |
| Movements, logs, purchasing (PO) | ○ | ○ | ● | ◐ | ○ | ● | ○ | ○ |
| Shipping, carriers, tracking | ○ | ○ | ◐ | ● | ○ | ● | ○ | ◐ |
| Fulfilment (Amazon / Cdiscount MCF) | ○ | ○ | ○ | ● | ○ | ● | ○ | ○ |
| Data & orchestration | ||||||||
| CMS / ERP / marketplace connectors | ○ | ◐ | ○ | ◐ | ○ | ● | ● | ● |
| Scheduled data streams / syncs | ○ | ○ | ○ | ○ | ○ | ● | ◐ | ● |
| ETL & data mapping | ○ | ◐ | ◐ | ○ | ○ | ● | ◐ | ● |
| Reconciliation & mirror data | ○ | ○ | ○ | ○ | ○ | ● | ○ | ◐ |
| Steering & finance | ||||||||
| GMV / revenue | ◐ | ○ | ◐ | ○ | ○ | ● | ◐ | ○ |
| P&L / consolidated margin | ○ | ○ | ● | ○ | ○ | ● | ○ | ○ |
| Dashboards by domain | ◐ | ○ | ◐ | ◐ | ◐ | ● | ◐ | ○ |
| Multi-partner / multi-currency | ○ | ○ | ◐ | ○ | ○ | ● | ○ | ○ |
| Governance & custom | ||||||||
| Business rules on orders | ◐ | ○ | ◐ | ◐ | ○ | ● | ○ | ◐ |
| Price governance multi-channel × country | ○ | ○ | ◐ | ○ | ◐ | ● | ◐ | ○ |
| Workflows & product states | ○ | ◐ | ◐ | ○ | ○ | ● | ○ | ○ |
| Fine-grained permissions & audit (RBAC) | ◐ | ◐ | ◐ | ◐ | ○ | ● | ◐ | ○ |
| Multi-entity financial consolidation | ○ | ○ | ◐ | ○ | ○ | ● | ○ | ○ |
| Custom code & features | ○ | ○ | ◐ | ○ | ○ | ● | ○ | ◐ |
| Marketing & growth | ||||||||
| Ads management (Google / Amazon) | ○ | ○ | ○ | ○ | ○ | ● | ◐ | ○ |
Where the gaps are, and how DOXAP fills them
Catalog and channels. A PIM structures the catalog well, but it does not push enriched products to each marketplace with the right category mapping. A feed integrator pushes feeds but does not own the source data. DOXAP centralises the catalog and drives the distribution, so the same enriched product reaches every channel. Catalog →
Stock and orders. The ERP knows stock, the OMS knows orders, but neither reconciles a single real-time position across every marketplace. DOXAP unifies stock and pulls every order back into one normalised place. Orders →
Data and orchestration. An iPaaS can move data, but it has no commerce model: no products, no offers, no channel logic. DOXAP runs scheduled data streams that enrich, map and reconcile commerce data specifically. Connectors →
Steering and margin. Each tool shows its own slice of numbers. Only an orchestration layer that sees catalog, orders, refunds and costs together can produce a consolidated P&L and a single business pulse. P&L →
The takeaway
DOXAP is not a replacement for your CMS, ERP or marketplaces. It is the layer that sits between them, covering the orchestration work that falls through the cracks: keeping the catalog, stock, pricing and orders consistent across every channel, and giving you one place to operate it all. For the full picture of how that works, read our guide on marketplace data orchestration.
Want to see where DOXAP fits on your own stack? Book a demo →