CIAMA
CIAMA
English
Multichannel marketplace management
Bring offers and orders together, synchronise stock and adjust prices. Use your shared PIM and sales costs to decide where to grow your business.
Modular licensed product · Managed dedicated hosting or your own servers
Marketplace operators and technology platforms: supported accounts, countries and operations are confirmed for each connection. Connections depend on scope or require an integration assessment. No official partnership is claimed.
View connections and availabilitySeller accounts feed CIAMA. The PIM matches product references; the modules connect offers, inventory and results.
Offers and orders collected through APIs.
SKUs and aliases matched to your products.
Inventory, prices and margins in a shared context.
Your costs. Your decisions.
Review tax-inclusive sales, VAT and tax-exclusive amounts, then examine associated purchase costs, commissions and logistics fees. CIAMA distinguishes actual, estimated and missing amounts so the margin’s scope remains clear.
Compare sales by order, product and marketplace on a tax-exclusive basis.
Match product costs, commissions and available shipping costs, including those collected through supported FBA flows.
Read the calculated margin alongside the share of sales with sufficient cost data for meaningful analysis.
Analyse activity by year, month, week or day, then drill into PIM products, brands, categories and tags. Review commissions, costs and margins within the selected scope to identify ranges and channels worth examining.
Sales excluding tax − purchases − commissions − logistics costs
Margin depends on the costs actually provided. General business overheads are not implicitly included, and a missing amount is not zero.
01 / Expand coverage
Find products offered on some marketplaces but missing from others. The coverage matrix compares the PIM with collected offers and helps you prioritise products using stock availability and catalog segments.
Consistent SKUs and configured aliases link offers to the correct PIM product. An alias maps an external reference; it does not create a new product variant.
02 / Centralise orders
Collected orders join a shared model with B2B and e-commerce. Review lines, statuses and products while preserving the seller account and fulfillment context.
Accessible data depends on the permissions and information provided by each marketplace.
03 / Connect inventory and offers
Bring together availability from your own warehouses and third-party logistics providers (3PLs). Your ERP or WMS pushes warehouse stock through the API whenever it changes; native logistics connectors collect inventory from supported providers, such as Amazon FBA.
Stock held by a 3PL cannot necessarily serve every sales channel. Selected sources must be eligible to fulfill the relevant orders; publishing availability and requesting fulfillment are separate operations.
Multichannel fulfillment · In development
Planned workflow example: a Fnac offer draws on your own warehouse and FBA stock eligible for Amazon Multi-Channel Fulfillment. When an order arrives, you choose the shipping source: your warehouse or a fulfillment request to Amazon to deliver to the Fnac customer.
Selecting the shipping source and sending fulfillment requests to 3PLs are in development in CIAMA. Activation will depend on connectors, subscribed services, and product and destination eligibility. Aggregating inventory does not, by itself, reserve units for an order.
04 / Improve your position
Track competitor observations and the Buy Box over time. Compare these signals with sales and costs, then use supported repricing actions to request a price change and follow its outcome.
Available signals and write operations vary by connector. Repricing rules are defined within the agreed scope.
A shared order flow
Shopify, marketplace and B2B orders centralised in CIAMA are available through a token-authenticated REST API. Your development team or service provider can use the API documentation to integrate them with your ERP or another application independently, without requiring development by Dawap. If you prefer us to handle the connection, Dawap can build a custom middleware.
CIAMA brings orders together from connected sources.
Your application searches orders, their updates and their lines through the API.
Your integration maps the data and writes it into the receiving system.
API reading is available. ERP integration still needs to be implemented: this access does not imply automatic delivery to every software system.
Extensions in development
These capabilities are part of the planned module evolution. Availability and supported actions will be specified for each connector.
Bring return and refund tracking together around orders to preserve their commercial context.
Use shipping information and extend tracking updates to compatible sales channels.
Adapt product content to each marketplace’s requirements while keeping a shared product reference.
Prepare and manage promotional activity according to each channel’s capabilities.
Extend price adjustment rules and safeguards around your commercial strategy.
Supported flows exist for Amazon Europe, Cdiscount/Octopia, Fnac/Darty and Mirakl/Cultura. Reading data, sending stock, changing prices and retrieving logistics data are checked separately for each connection.
Check my connections ↗We assess new connectors where an API allows integration. Accessible data, permitted actions and integration complexity determine the scope and project terms. CIAMA is a modular licensed product, available on dedicated hosting managed by Dawap or on your own servers.
Plan your marketplace expansion ↗Choose the accounts, flows and operations you need.
Check SKUs, aliases and PIM product references.
Validate collected data and integration outcomes.
Gradually enable the agreed automation.
Yes. CIAMA organises activity around configured connections and sales channels. Account numbers, volumes and API permissions are assessed to size your deployment and define each connector’s scope.
They link offers and order lines to one product reference. Configured aliases map selected external identifiers to the relevant product, maintaining a consistent view of inventory and results.
These are separate operations. The matrix identifies missing offers and can check for an existing product page on supported channels. Offer creation workflows on existing pages still require completion by channel; automated creation of new product pages is in development.
Dedicated flows collect inventory, logistics operations and available costs. CIAMA matches these to the relevant products and sales. FBA has a distinct scope from sending merchant warehouse stock to marketplaces.
Yes. Your integration can read centralised marketplace, B2B and e-commerce orders and their lines through the REST API. Channel and date filters support retrieval. Mapping and writing into your ERP require configuration.
The calculation uses available purchase costs, commissions and logistics fees. Views distinguish actual, estimated and unknown values. General business expenses are not automatically added: results must be read with their cost scope in mind.
No. Observations and price requests help you decide and track changes. The Buy Box depends on marketplace rules and factors beyond price alone.
We can assess its API and your expected use cases together. Feasibility, access, technical constraints and complexity determine the integration terms.
Let’s start with your seller accounts, catalog and costs to show how CIAMA can support your marketplace growth.
See CIAMA for my marketplaces ↗