01
Structure
Organize products, brands, categories and tags. Use these dimensions to navigate data and select a working scope.
Find products missing from channels ↗
CIAMA
CIAMA
English
Product catalog & PIM
The PIM is CIAMA’s required foundation, connecting products to offers, orders, inventory and results. Your ERP or existing PIM remains the source of truth and feeds the shared reference data used by every module through APIs.
Product data at the centre
CIAMA stores your catalog data to connect operations around the same products. SKUs, EANs and external identifiers help match references between your source system and collected commercial data. Keep your ERP or PIM and add an operational view across channels.
Your ERP or existing PIM owns the product data. It sends products and their classification to CIAMA and keeps them updated through APIs.
Inbound catalog API
Segment · Check · Analyse
Organize products, brands, categories and tags. Use these dimensions to navigate data and select a working scope.
Find products missing from channels ↗
Quality scores highlight missing identifiers, images and attributes to prioritise corrections in the source system. Completeness supports preparation, but does not replace each channel’s requirements.
Identify data that needs correcting ↗
Relate products to offers and observed performance. Reference data becomes a shared business foundation instead of an isolated file.
Understand sales by product ↗Connecting a channel sets up data exchanges. It does not automatically publish your entire catalog: collected offers are matched to products using their identifiers.
Select the connector and supply API credentials. Depending on the connection, CIAMA automatically collects offers and orders. Recognised references link back to the shared product.
Connect supported stores to match their offers and orders to your catalog. Follow the same product across stores and other sales channels.
Create your B2B channel in CIAMA and feed its data through APIs from your ERP. B2B orders contribute to the cross-channel view of your products.
An example following one product reference from your source system to business decisions.
Your ERP sends the product, its identifiers and its classification through the API.
CIAMA stores the reference and links recognised offers from connected channels.
Find sales, units sold, inventory and available margins around the same product.
Review its performance or prepare replenishment in the relevant modules.
Your systems, clear responsibilities
Inbound APIs support creating, updating and deactivating products, as well as supplying brands, categories and tags. External identifiers preserve the link to your source system. Read resources let authorised applications retrieve exposed data within their permissions and the API contract.
Examples of ERP and e-commerce platforms in your ecosystem. Their presence does not guarantee an available catalog connector or bidirectional synchronization. Integration depends on the agreed scope; no official partnership is claimed.
Product content improvements and recommendations based on existing data, with content tailored to channel needs. These services are not yet available and will carry additional charges.
An extension to receive images through APIs and expose them through HTTPS URLs for applications and marketplace or e-commerce feeds. Public or protected access will be scoped for each integration.
Your deployment scope
Every CIAMA module relies on the PIM foundation. API scope, available margin data and channel flows are agreed during integration. AI services under development will carry additional charges according to the services selected.
CIAMA is licensed software deployed on-premise. Connections, enabled features and adaptations are defined for your deployment.
Yes. It holds the shared product references used by every module. Your ERP or existing PIM can remain the source of truth; CIAMA needs a copy of the data to power its features.
They are in development. Their scope and additional charges will be specified before activation.
Yes. A project can retain an existing product source. Exchanged data and system responsibilities must be defined within the integration scope.
No. A completeness check is not certification against every channel and category requirement.
Your catalog in practice
Your product source, your channels and the information your teams need: let’s prepare a demonstration around those uses.
Request a catalog demo ↗