Article published on · Updated on · By DAWAP, the publisher of CIAMA
Find a product as your range grows
A commercial reference is not always enough to find the right product. As your ranges grow, your teams need an organised catalogue to identify items, understand their classification and access their information.
Following the shared foundation introduced in R001, this edition focuses on the product repository. We bring search, product records and classification together in CIAMA PIM, giving your teams a common starting point for understanding your catalogue.
What changes in daily work
- Find your account’s products through a shared search.
- Organise your ranges with brands, categories and tags.
- Give your teams common product references.
Features in detail
PIM · Catalogue
Find your account’s product references
Product search gives you access to your company catalogue. Combine search with brand, category or tag filters to focus on a range and open the product record you need.
Structure your ranges with brands and categories
We keep brands and categories distinct: brands identify commercial ranges, while categories and their parents organise the catalogue hierarchy. Your teams can browse products from several starting points.
Use tags for an additional view
A product can have several tags. These groups complement its brand and category, helping you find a set of products according to your company’s organisation.
A product record as a shared reference
From search, you can open the product details. PIM establishes a common identity that other modules can build on. This edition introduces the repository and its API ingestion; data quality workflows will be covered in a dedicated edition.
Feed the catalogue from your ERP through the API
Your source system can send products, brands, categories and tags to CIAMA through the REST API. External identifiers locate resources within the account and technical client that supplies them. A product can reference its brand, category and tags without manually recreating its classification in every tool.
PUT /api/pim/products/by-external-id/{externalId}: create or fully replace a product representation from your source system.GET /api/pim/products/by-external-id/{externalId}: retrieve that source’s binding and the last applied representation.GET /api/pim/products/receipts/{receiptId}: check the processing status of an accepted write.
Writing requires the catalog.write permission and the expected synchronisation metadata. A 202 Accepted response confirms acceptance for asynchronous processing; the receipt lets your integration track the result. Stock uses separate resources and is not written through the product record.
For example, your ERP first sends a brand and a category, then a product that references them. Your integration checks the receipt before treating the update as applied. Explore resource families and exchange behaviour in the CIAMA REST API documentation.
Prepare a catalogue review
You distribute several accessory brands and are preparing a range review. Your team selects a brand, narrows the search by category and finds the relevant products. Tags provide another way to group products without changing their main classification.
A colleague then opens the same product record to read its information. You discuss the same reference and classification, without rebuilding a different list for each team.
This edition looks back at CIAMA’s evolution. The month is an editorial milestone in the product story, not a production deployment date.