Article published on · Updated on · By DAWAP, the publisher of CIAMA
Avoid completing an incomplete catalogue
Your ERP needs to send an entire product range to CIAMA. If the transfer stops, some products have not arrived yet: should they be treated as removed from the source? Without an end-of-import check, teams risk treating an incomplete list as the expected catalogue.
Building on the catalogue writes introduced in R002, snapshots let an integration declare a complete set, send its products and request completion. CIAMA PIM checks that set before applying the effects of reconciliation.
What changes in daily work
- Distinguish an individual update from a complete source state.
- Check the count and integrity of received items.
- Prevent completion while a set remains incomplete or contains failures.
Features in detail
PIM · Catalogue
Declare the expected set
PUT /api/pim/products/snapshots/{snapshotId} opens a snapshot with a synchronisation watermark, expected count and control hash. Relevant product writes are associated with that set.
Verify before completing
PATCH /api/pim/products/snapshots/{snapshotId}, with status completed, requests completion. CIAMA checks that processing is no longer pending, no events have failed and the count and hash match the expected contract.
Understand the effect of missing references
Successful completion deactivates active resources missing from the snapshot within the account, source and resource-type scope. A snapshot is therefore neither a partial batch nor a backup: it represents a declared complete state.
Track writes during reconciliation
GET /api/pim/products/receipts/{receiptId} lets you check individual writes before completing the snapshot. The protocol builds on the external identities and receipts introduced earlier. Developers can prepare its use with the CIAMA API documentation.
Resume an interrupted catalogue transfer
A catalogue team prepares a full transfer from its ERP. The developer opens a snapshot for the agreed scope and sends the products. An interruption leaves processing pending: completion cannot succeed until processing and integrity checks are satisfied.
After resuming writes and checking their receipts, the integration requests completion again. Active resources absent from this complete state are then deactivated within the account, source and resource-type scope. The team therefore checks the declared scope before this step: an import limited to a few products must remain a partial update.
This edition looks back at CIAMA’s evolution. The month is an editorial milestone in the product story, not a production deployment date.