Article published on · Updated on · By DAWAP, the publisher of CIAMA
Follow each store through a shared catalogue
Several stores can share a catalogue without sharing the same commercial activity. Your teams need a common view while still knowing which store owns each offer and order.
We extend the multichannel story to e-commerce operations. Configured stores join the cockpit with their own channel identities.
What changes in daily work
- Review offers and orders from each connected store.
- Keep a distinct channel for every store.
- Reuse a channel’s orders through the OMS API.
Features in detail
E-commerce
Each store has an identifiable channel
Configured e-commerce connections collect offers and orders, including supported Shopify and Wix workflows. Each store retains its channel, with its connection and collection capabilities enabled for the relevant scope.
Dedicated searches, a shared catalogue
Search a store’s offers and review its orders by status and period. Product relationships follow the PIM’s matching and alias rules, without inventing a link when a reference is unrecognised.
API: retrieve a store’s sales
GET /api/oms/orders with channelId reads orders for the selected channel within the authenticated account. GET /api/oms/order-lines adds item-level detail, with channel or channel-type filtering.
These routes reuse the shared order model presented in R006. They provide access to collected data without implying automatic stock or price updates to every store. Prepare your connection with the CIAMA API documentation.
Connect two stores to your ERP
A team operates two stores with different market positions. It reviews each channel’s monthly orders and finds the same product references in the shared PIM while retaining the origin of every sale.
To send those sales to the ERP, its middleware calls GET /api/oms/orders with the channelId filter, then reads the required lines. This workflow builds on the multichannel orders API introduced in R006.
Your developers, a service provider or DAWAP can implement the integration and define the mappings expected by the ERP. Collection remains configured per store; the middleware then checks transmission to the receiving system. Explore the approach to connecting your ERP and sales channels.
This edition looks back at CIAMA’s evolution. The month is an editorial milestone in the product story, not a production deployment date.