Article published on · Updated on · By DAWAP, the publisher of CIAMA
Follow a B2B sale through CIAMA
A business order moves through several steps: its customer and items must be recognised, the sale recorded and its shipment linked to the right order. Your ERP knows these events; your teams need to find them in CIAMA under the same references.
This edition brings together B2B customer identities and logistics exchanges to connect operations to your source system. Each write keeps its own processing result.
What changes in daily work
- Keep your ERP references throughout B2B exchanges.
- Link each shipment to its order and products.
- Check applied orders, shipments and stock separately.
Features in detail
B2B
Send orders with the right context
PUT /api/b2b/orders/by-external-id/{externalId} creates or replaces a source-owned order. The required customer and products must be resolvable; a missing dependency can leave processing pending.
Connect fulfillments to the order
PUT /api/b2b/fulfillments/by-external-id/{externalId} sends a B2B fulfillment with its business references. Processing resolves the associated order and products before applying data.
Resource-specific receipts distinguish acceptance, pending work and results. The integration uses B2B permissions and synchronisation metadata; receiving a request does not by itself complete the operation.
Features in detail
Logistics
Supply diffusable stock for Default
PUT /api/inventory/default-warehouse/stocks/by-product-external-id/{externalId} receives fields including quantity and calculatedAt. The submitted quantity represents immediately diffusable stock; optional rtlQuantity remains diagnostic information.
This contract covers the Default warehouse. It should not be treated as a generic write API for every external or 3PL warehouse. Source product identity, stock permissions and processing receipts define the exchange. Explore the integration workflow in the CIAMA API documentation.
Track an order from ERP to shipment
A distributor records a business sale in its ERP. Its integration checks customer and product references, sends the order to CIAMA and reads the receipt to establish the outcome.
When the warehouse confirms shipment in the source system, the integration sends it with the order reference and relevant products. It also updates distributable Default stock through the dedicated flow.
The developer checks these three processes separately. Sales can review the order and shipment while logistics follows the stock supplied. Distribution to marketplaces is a separate subsequent step handled by the configured connectors.
This edition looks back at CIAMA’s evolution. The month is an editorial milestone in the product story, not a production deployment date.