Article published on · Updated on · By DAWAP, the publisher of CIAMA
Give every B2B price its context
A B2B price needs context: the product, the customer’s commercial category, currency and applicable quantity. Sending an isolated amount does not preserve that context between systems.
Building on customer records, we structure exchanges around B2B customer pricing. Your source system’s references remain the connecting thread.
What changes in daily work
- Associate customers with their source price category.
- Send product prices with currency and minimum quantity.
- Track the dependencies required to apply a price.
Features in detail
B2B
Preserve the dimensions of a price
The exchange model separates price categories from product prices. A price carries the source product, category, minimum quantity, amount, currency and active state. A customer can reference its price category.
Find offers within B2B activity
B2B offer search supports channel, brand, category, tag and active-state filters. It complements pricing references with a view of the offers used in business sales.
API: establish references before prices
PUT /api/b2b/price-categories/by-external-id/{externalId} sends a category. PUT /api/b2b/product-prices/by-external-id/{externalId} sends a price linked to a product and that category.
Writes are asynchronous. If the product or category cannot be resolved, processing can remain in pending_dependency. Use GET /api/b2b/product-prices/receipts/{receiptId} to check the outcome. This import model does not imply a universal discount-rule editor: the source system defines the submitted values. Prepare exchanges with the CIAMA API documentation.
Send reseller prices from your ERP
Your ERP prepares a “Resellers” category and prices for a product range. The integration sends the category, PIM products and then the associated prices with their minimum quantities and currencies. Relevant customers can reference the category in their B2B representation.
If a product is not recognised yet, processing identifies the missing dependency. The technical team can restore the reference before treating the price as applied.
This edition looks back at CIAMA’s evolution. The month is an editorial milestone in the product story, not a production deployment date.