CIAMA
English
Multi-store e-commerce management
Connect stores to your PIM and track sales and margins. With or without an ERP, prepare to expand onto marketplaces from your e-commerce business.
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 availabilityCompare stores without combining separate exports for every review. Trace offers and orders back to their source, then move from the overall view to each channel’s detail.
Store APIs feed CIAMA with the data they make available.
SKUs and aliases link references to the shared PIM.
Review sales, quantities and margins by store and alongside other channels.
Products connect the picture
Products and variants collected through e-commerce offers are matched to your reference catalog using their identifiers. Analyse the same product across stores, marketplaces and B2B, using the brands, categories and tags in your PIM.
Centralise orders, lines, statuses and customer information supplied by your connections. Preserve the store context to monitor activity and prepare data for use in your business applications.
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.
Explore the CIAMA API ↗You have an ERP
Your ERP feeds the PIM through the API. The planned offering creates and updates products in your online stores from this reference: content, images and attributes according to each platform’s capabilities.
Catalog publishing to stores: in development, scoped per connection.
Your store is your source
Without an ERP, data collected from your store can initialise PIM references. Prepare the catalog for marketplaces and review results in the same platform.
Full product data imports need scoping; initial references can be created according to configuration.
The authoritative source is defined for each flow. Reading from a store and publishing to a store are configured workflows, not implicit two-way synchronisation of every field.
From an online store to multichannel commerce
Use the PIM to prepare products for new channels. Connect each launch to your stock, fulfillment setup and expected margin.
Connect offers and orders; initialise PIM references according to your account configuration.
Check SKUs, EANs, images, descriptions and categories; complete the data required by your chosen marketplaces.
Choose marketplaces, connect seller accounts and prepare offers through supported workflows.
Bring sales, stock and costs together to understand what each new channel contributes.
Each launch needs a seller account, an eligible catalog, prices, stock and a fulfillment setup. Offer creation workflows still require completion by channel; automated creation of new product pages is in development.
Plan my marketplace expansion ↗From sales to contribution
Compare sales excluding tax with purchase costs and available fees. Analyse results by store, period and product, then see how e-commerce contributes to your multichannel business.
Revenue, orders and quantities to track each store’s progress.
PIM brands, categories and tags to understand which assortments sell.
Included costs and calculated margins to support commercial decisions.
Sales excluding tax − purchase cost − included fees
Margin reflects the costs provided. Shipping, payment fees and other charges require suitable data and mapping. The result does not automatically represent the company’s accounting net margin.
Synchronization and automation · Rules per store
An ERP request, an inventory change or a business rule can trigger an action on a store. We define the flows to connect to e-commerce APIs according to your needs and the operations each platform permits.
Feed availability from your warehouses and connected logistics providers. Distribute availability to your ecommerce stores according to their APIs and the sources and rules defined for each connection.
Send price requests from your ERP or internal rules. Price updates and automated repricing are part of the planned offering, with conditions and checks to configure.
Prepare promotional actions and relay them to compatible stores. Scope depends on each platform’s mechanisms and API endpoints.
Data changes in your ERP or CIAMA.
The flow identifies the relevant stores and operations.
The integration sends the authorised request.
Platform responses allow the outcome to be verified.
Order retrieval and inventory distribution are supported. We configure API permissions, product references and exchange frequency. Pricing, promotions and product publication are scoped separately.
Multiple stores can join the same platform. We check incoming data and outgoing actions separately for each store.
CIAMA retrieves orders from your stores and automatically sends inventory updates. Each store retains its channel identity. API access, product references and transmission rules are configured for your project.
Order retrieval and inventory distribution are part of our ecommerce offering, including PrestaShop, Magento and custom stores. The connection takes account of versions, extensions and available APIs.
Your deployment scope
CIAMA connects stores to the PIM, logistics and multichannel reporting. Your platforms retain the storefront, cart and checkout. We define connections, data and automation with your teams.
Modular licensed product: dedicated hosting managed by Dawap or installation on your own servers, including on-premise.
Yes. CIAMA retrieves orders and sends inventory updates for Shopify, as it does for WooCommerce and Wix. We configure API access, product mappings and availability rules for each store.
No. A connected store can be your starting point. Depending on the enabled catalog policy, collected offers can create initial PIM references. Importing content, images and categories must be scoped for your connection; missing data needs completing before preparing marketplace expansion.
Yes. The model distinguishes connections and channels by store. Shopify, WooCommerce and Wix flows use a store identity to preserve the origin of offers and orders.
SKUs and configured aliases match offers and order lines to the shared product. Unmatched references need correcting to achieve consistent analysis across channels.
Customer information available in collected orders, according to the connection and permissions. This does not imply synchronisation of the store’s entire CRM.
We set up automatic inventory distribution to your stores according to their APIs. Pricing, repricing and promotions have a separate scope: triggers, rules and operations are defined for each store.
We can assess the project where a suitable API is available. Accessible data, permissions, volumes and complexity determine the integration scope.
Yes, this workflow is part of the planned offering in development: your ERP feeds the PIM, then CIAMA creates or updates store products through their APIs. Supported fields, media, variants and operations are defined for each connection. Existing collection flows do not mean publishing is already available.
Your platforms, ERP, stock sources and priorities: let’s prepare a demonstration focused on the operations that matter to your team.
See CIAMA for my stores ↗