Choose stock sources
Connect data from your ERP, internal warehouses or third-party logistics providers according to the integrated flows. Keep their quantities distinct.
CIAMA
CIAMA
English
Multistore ecommerce management
Centralise orders, distribute stock and compare margins by store. CIAMA connects ecommerce to your catalogue and logistics, alongside your ERP or starting directly from your stores.
Shopify, WooCommerce and Wix: order retrieval and inventory distribution. API access and transmission rules are configured per store. Connections depend on scope or require an integration assessment. No official partnership is claimed.
View connections and availabilitySales are spread across several sites or brands. Bring them together around the same products to coordinate sales and logistics while keeping the origin of every order.
Find collected orders, their lines and statuses without searching every store back office. The original store remains identifiable.
Send availability to connected stores according to the stock sources and rules defined for each one.
Move from overall activity to individual stores and products to understand sales and their contribution based on available costs.
Inventory and availability
CIAMA supports stock distribution to Shopify, WooCommerce and Wix. Other stores connect according to their APIs. Define the source stock, availability rules and frequency for each connection.
Connect data from your ERP, internal warehouses or third-party logistics providers according to the integrated flows. Keep their quantities distinct.
Specify which products and availability to send to each site. Product mappings connect stock updates to the correct reference.
Configured connections send availability to your stores. Your platforms keep their product pages, cart and checkout.
An example workflow
Your product is listed on a Shopify store and a WooCommerce store. Here is how CIAMA connects their operations, using the sources and rules defined for your project.
Identifiers from both stores are mapped to the same catalogue product.
Availability from the selected sources is sent according to each store’s rules.
Collected orders join CIAMA with their product and original store.
Review sales, known stock and available costs before planning replenishment or revisiting the assortment.
Illustrative example. Availability and update frequency depend on the sources and rules configured for each store.
We will prepare a demonstration of orders, stock and margins around that workflow.
Your products, connected to your operations
SKUs and aliases connect store offers and orders to the shared catalogue. Your teams can find a product’s sales, stock and available margins, even when it sells on several sites.
Review the lines, statuses and customer information provided by each connection. Store context stays with the order so you can follow activity and feed your business systems.
The REST API gives access to orders centralised in CIAMA. The API is available; exchanges with your ERP need to be configured by your team, your integration partner or DAWAP. Technical documentation is available on request.
Explore API use cases ↗You have an ERP or PIM
Your existing tool feeds the CIAMA catalogue. Products are matched to store offers and orders so you can follow operations using consistent references.
Data, mappings and responsibilities are defined with your team or integration partner.
Your stores are the source
Collected offers can initialise catalogue references according to configuration. You then match products across stores to compare their activity.
Content, images and categories to bring across must be scoped; collecting data does not guarantee a complete product record.
The master source is chosen for each flow. Matching records does not automatically publish every product page to all your stores.
Beyond revenue
A product can sell on several sites with different fees. Bring untaxed sales together with purchase costs, shipping and other integrated costs to understand each store’s contribution and the products behind it.
Review revenue, orders and quantities by store over a consistent period.
Return to the product, its brand or category to identify the sales and costs behind its contribution.
Base assortment choices and pricing analysis on covered costs, distinguishing actual data, estimates and unknowns.
Untaxed sales − purchases − covered selling costs
Shipping, payment fees and other costs depend on integrated data. An unknown cost is not zero. Calculated contribution is not the company’s accounting net profit.
One store or several, on the same platform or different technologies: the project starts with your operations and the exchanges to configure.
Collect orders and distribute stock while keeping each store’s identity. Access, product mappings, rules and frequency are configured for your project.
We assess order and stock flows according to the version, extensions and available access. Scope is confirmed for each connection.
When your business expands
Your stores remain the starting point. If you open a marketplace channel, reuse the catalogue to prepare the assortment, connect stock and track the new channel’s contribution.
Identify the products to offer and their availability.
Complete identifiers and data required by the chosen marketplace.
On supported channels, create offers linked to existing product pages and track the result.
Bring sales and available costs together with your other channels.
Creating offers on existing product pages depends on the channel, product and configuration. Creating new marketplace product pages is a separate scope to confirm.
Explore the marketplace workflow ↗Your deployment scope
Your ecommerce platform keeps the storefront, cart and checkout. Your ERP or PIM can remain the master source for its data. CIAMA brings catalogue, orders, stock and analysis together within the scope agreed with your teams.
CIAMA is modular licensed software, with dedicated hosting managed by DAWAP or installation on your own servers. Licence, integration and operations are scoped and quoted for your project.
CIAMA supports order collection and stock distribution for Shopify, WooCommerce and Wix. For PrestaShop, Magento and custom sites, flows are assessed according to available APIs. Access, product mappings and frequency are configured for each store.
Yes. Each store has its own connection and channel identity. Bring sales together in a shared view while keeping the original store for every order and offer.
Distribution can be automated at the frequency defined for each connection. Stock freshness depends on sources, APIs and configuration. Physical quantities and published availability remain distinct; CIAMA does not guarantee instant synchronisation across every channel or the absence of overselling.
No. A connected store can be the starting point: collected data can initialise catalogue references according to configuration. If you already have an ERP or PIM, it can remain the master source. Identifiers, data scope and each tool’s responsibilities are defined during integration.
Yes. Centralised orders are available through CIAMA’s REST API. Your team, integration partner or DAWAP needs to configure the ERP connection. Technical documentation is available on request; this is not a universal outbound connection already installed for every ERP.
Compare sales over the same period, then examine purchases and integrated fees by store and product. Results depend on covered costs, including shipping and payment fees. Actual data, estimates and unknowns remain distinct. This contribution is not accounting net profit.
These operations have a separate scope from order collection and stock distribution. Required features, rules and capabilities are checked for each platform. Publishing ecommerce product pages from the CIAMA catalogue remains in development; it is not implicitly included in the connection.
No. Start with your online stores alone. If you later add marketplaces or B2B sales, the shared catalogue helps connect products and their operations. New channels and the features to enable are scoped separately.
An order to find, stock to publish or a margin to understand: start with your platforms and a product so we can prepare a demonstration for your team.
See CIAMA for my stores ↗