B2B commercial terms
Pricing data import; editing and price application require project-specific scoping.
Reseller lists, quantity breaks, negotiated terms: a price alone is not enough. CIAMA can receive B2B pricing records and their links to products and customers, preserving the structure defined in your ERP.
For the same product, the amount can depend on the customer category and order quantity. An import needs to preserve those relationships, not just a column of amounts.
Before sending revised prices to CIAMA, check the three relationships that give those amounts their meaning.
Importing terms preserves their structure. Calculating a quote price or displaying it in a portal requires a separate workflow.
When prices are set in your ERP, integration should preserve that authority. CIAMA receives data within the agreed scope; importing those records does not imply a complete negotiation or discount calculation engine.
Your deployment scope
Agree where prices are set, how they are transferred and where teams use them. Stacked discounts, promotions and ERP write-back require a specific scope.
CIAMA is licensed software deployed on-premise. Connections, enabled features and adaptations are defined for your deployment.
The import model associates a product price with a category and minimum quantity. Applying those tiers in a sales workflow requires scoping.
No. A customer price-category assignment can be absent. The business treatment of that absence must be defined rather than assuming a default list.
An import foundation does not guarantee a complete editor. Editing and redistribution of prices must be verified for your deployment.
One product, its quantity breaks and the customer groups concerned: use that example to define the data CIAMA should receive and the workflows your teams need.
Discuss your B2B pricing ↗