Check ERP customer prices by quantity and validity in the shop
A worked example links customer account, unit price, volume tier and expiry. Checking before order completion helps catch outdated prices.
A customer-specific price needs more context than an item number. Odoo describes price rules with product scope, minimum quantity and validity periods. Shopify’s B2B company location shows how authorised company assignments also determine the offered price. An ERP-shop integration needs clear links between these elements.
A price example with quantity changes and expiry
A fictional filter retailer is planning the integration. The example considers customer account K-58 and item FILTER-A, ordered in individual units. The standard price is 17 EUR excluding tax per unit; a time-limited customer rule offers 16 EUR excluding tax per unit from 6 units.
Rule state | Line quantity | Expected unit price excluding tax |
|---|---|---|
Customer rule valid | 5 units | 17 EUR |
Customer rule valid | 6 units | 16 EUR |
Customer rule expired | 6 units | 17 EUR |
These are fictional prices and expected results for a planned trial. After expiry, an old copy of the customer rule should not keep providing the lower price.
Connect the fields needed for pricing
Keep authorised customer assignment, item identifier, order unit, quantity, currency and validity together. Check whether the ERP and shop mean the same thing by the same quantity unit. A carton price must not appear as a unit price without checking. The ERP reference and the time of the calculated price snapshot should remain traceable for internal review.
Recheck when things change
The planned flow recalculates after a quantity change and checks the current customer context and rule validity again before order completion. A fast cache can support display; its entry needs the relevant context attributes and a defined approach to changes. A general retention period alone does not establish whether a rule has expired in the meantime.
If the price changes, the interface should show the new amount clearly before completion. For this example shop, the agreed rule is to pause completion without a reliably confirmed price and offer another check.
Make the comparison visible in the trial
Walk through the table’s cases with a suitable test integration. Compare the ERP result, the display and the intended order price. Add a change of authorised customer context and an unavailable price source. The saved price snapshot must belong to the relevant transaction; an earlier price that has not been rechecked must not be saved as the currently confirmed order price.
Sources
Read more
All articles
E-Commerce with ASES
Online shops, marketplaces and B2B portals