Article published on · Updated on · By DAWAP, the publisher of CIAMA
Recognise one item across different references
An ERP reference and a seller reference can describe the same item under two different identifiers. Your teams need to establish that relationship to find the product behind an offer and understand its associated operations.
Following the catalogue structure introduced in R002, aliases in CIAMA PIM make these relationships explicit. You choose the reference record and identifier to associate after checking the item, variant and pack size.
What changes in daily work
- Associate several references with one product record.
- Link unmatched offers through an exact identifier match.
- Keep business aliases distinct from integration identities.
Features in detail
PIM · Catalogue
One record, several recognised references
You view and add aliases from the product record. Each alias belongs to your account and points to a specific product. CIAMA rejects empty aliases, the product’s own primary identifier and aliases already assigned to another product.
Match offers without waiting for another import
Adding an alias links previously unlinked offers whose identifier matches it exactly within your account. The product relationship becomes available without waiting for the next synchronisation. This action does not publish a new offer to a sales channel.
Check the relationship before combining records
If the reference already identifies another product in the account, the operation can move its order, offer and stock relationships to the selected product. Check the item, variant and pack size first: assigning an alias is a catalogue decision.
API: find a product from its source system
For an integration, GET /api/pim/products/by-external-id/{externalId} returns the source-owned binding and its last applied representation. This external integration identity is distinct from an alias entered in the back office: creating an alias does not automatically create an API binding.
This lookup complements the catalogue ingestion introduced in R002. Your developers can explore access principles and object families in the CIAMA API documentation.
Match a seller reference to the ERP product
For example, your ERP uses “ITEM-100” while an imported offer uses “SELLER-100”. After checking that both references describe the same item and pack size, you add “SELLER-100” as an alias of the reference product. Unlinked offers in your account with that exact identifier are then attached to the product.
A different variant or pack keeps its own identity. Similar descriptions alone are not enough to justify combining references.
This edition looks back at CIAMA’s evolution. The month is an editorial milestone in the product story, not a production deployment date.