Sorting from lowest to highest price sounds simple. In B2B, the order has to reflect the rates your signed-in customer actually pays.
A buyer clicks “Price: low to high.” They expect products to appear in the order of what their account will actually pay. In B2B commerce, that sequence can differ from one customer to the next.
Take two comparable items. The first carries the lowest public list price, while the second has a negotiated rate for this specific account. Once contract pricing applies, the second item becomes the less expensive option.
When sorting relies on public prices while product cards show customer-specific rates, the list becomes confusing right away. Visible prices jump out of order, forcing buyers to compare items manually.
It is just as important to be explicit about quantities and units of measure: sorting a per-piece rate next to a per-case rate does not give buyers a meaningful comparison.
From a design perspective, the practical question is how to determine the right rates across all matching products while keeping browsing responsive.
Depending on catalogue size, ERP interfaces and rule complexity, different patterns can be evaluated, whether calculating rates on demand, preparing selected pricing data or combining approaches suited to the project.
A price or document comes from the ERP. That does not mean every click needs to ask it for a fresh response. Here is how we organize these exchanges.
A good-looking catalogue is only the start. The journey must account for customer terms, approvals and the work that follows an order.
