CIAMA
English
ERP, e-commerce and marketplace integration
Copying product records, reconciling stock and rekeying orders? CIAMA connects your systems to your sales operations, so your teams can spend less time moving data and more time using it.
A DAWAP product · Licensed software · Dedicated hosting or your own servers
Your source and destination systems: API exchanges are scoped by software, version and business data. Connections depend on scope or require an integration assessment. No official partnership is claimed.
View connections and availabilityKeep your ERP in place
Your ERP holds key reference data. Your stores and marketplaces generate sales. CIAMA brings these together in a shared cockpit for your catalogue, stock, orders and business analysis.
You choose which system owns each type of data.
Match product references, centralise operations and run the exchanges configured for your business.
Each destination receives the scope defined for it.
Four use cases for your teams
Start with an operation that takes up your team’s time every day. CIAMA provides the business foundation; the integration translates your data and operating rules.
Catalogue
Shared product references
Feed the CIAMA catalogue from your ERP or PIM. Products, brands and categories become part of a shared reference linked to offers, stock and sales. Your teams work with matched product identities.
Explore the catalogue & PIMSource identifiers and data mappings are defined during integration.
Inventory
Consistent availability
Connect your reference stock to CIAMA, then publish availability using the rules of each connected channel. Compatible marketplaces, Shopify, WooCommerce and Wix fit this workflow; other stores depend on their APIs.
Explore stock distributionConnections and frequency need configuration. Stock writes through the CIAMA API cover default stock; other warehouses require separate scoping.
Orders
API available · integration required
Orders centralised in CIAMA are available through its API. Your ERP or another system can retrieve them through an integration, helping reduce rekeying and extend your management process.
Explore the API & integrationsYour team, your service provider or DAWAP can build the connection. Fields, statuses and exchange frequency are agreed with you.
Purchasing and B2B
Connected business operations
Bring supplier purchases and receipts into CIAMA to connect them with your catalogue and analysis. Supported B2B data can also be integrated: customers, offers and orders add context to your business activity.
Explore supplier purchasingIntegration preserves source data. A supplier receipt is not an automatic stock update.
An example workflow to configure
Your team should not have to piece the journey together from separate exports. Here is how an order can move between systems, with clear responsibilities at each step.
01 / Collect
The order is collected from the connected channel according to its access rights and collection frequency. Your teams can view its lines and statuses in the cockpit.
02 / Connect
Matched references connect order lines to the catalogue and available business data. Mapping gaps are handled within the integration scope.
03 / Transfer
The integration reads available orders through the API and adapts them to your ERP’s expected format. Creation, update and recovery rules are tested for your process.
Order API access is available. Importing orders into your ERP requires an integration; an order being present in CIAMA does not confirm that the ERP has processed it.
One useful exchange, then your next priorities
Your developers, your service provider or DAWAP can build the integration. You choose who delivers it, with technical documentation available on request for your instance’s API contract.
Which task should no longer need rekeying? Which data needs connecting? Choose a first exchange that helps a team.
A clear business use case and scope.
Agree the source of truth, data scope, frequency and who handles exceptions.
Shared rules across your systems and teams.
Check representative cases, mappings, errors and recovery through to the destination system.
Business acceptance before enabling the exchange.
Add a channel, a business object or a useful adaptation according to your organisation’s priorities.
An agreed roadmap for your integration.
The product and integration, in your environment
CIAMA is a licensed DAWAP product, available on a dedicated OVHcloud instance managed by DAWAP. You can also deploy it on your own servers, including on-premise. Your ERP and logistics tools retain the responsibilities agreed with you.
Modules, integration, operations, maintenance and adaptations are scoped in your quote. Start with what your business needs.
Understand the offer and pricingThe project starts with your ERP’s interfaces, version and required data exchanges. The CIAMA API can receive supported business resources and provide access to centralised orders. A specific connection or middleware may be needed; API availability does not guarantee an immediate connection.
CIAMA connects the catalogue, sales, stock, purchasing and analysis. Your ERP retains the management and accounting functions defined in your organisation, while your WMS handles warehouse execution. Each system’s responsibilities are agreed at the start.
Centralised orders are available through a token-authenticated REST API. Your team, your service provider or DAWAP can build their retrieval and integration into your ERP. Mapping, statuses, duplicate checks and frequency need to be defined; a universal ERP push connection is not installed by default.
Order collection and stock distribution are part of the CIAMA e-commerce scope for Shopify, WooCommerce and Wix. Marketplace exchanges depend on each channel and connector’s capabilities. Access, rules and frequency need configuration; other stores are assessed based on their APIs. Pricing, promotions and product publication have separate scopes.
Your team, your service provider or DAWAP can build the connection. Technical documentation is available on request for your instance’s contract. Operational and recovery responsibilities are defined in the project. Available logs vary by exchange; processing needs to be checked through to its destination.
Yes. Choose one useful exchange, then test the data, errors and recovery before activation. Add other exchanges according to your priorities. Frequency depends on the APIs and process; not every exchange runs in real time. Licensing and integration are scoped in a quote.
Your first useful exchange
Show us your ERP, your channels and the operation you want to simplify. We will walk you through the relevant CIAMA use cases and the integration to plan.
Request a CIAMA demoTell us about your project. No account required.