Dynamic Pricing

One catalog. Different strategies. Different prices.

B2B and multi-market commerce often runs the same products at different prices for different audiences. Building separate catalogs per market, per brand, or per client creates duplication and breaks every time pricing rules change. The pricing has to be the variable, not the catalog.

A parallel pricing engine runs multiple strategies against a single catalog at the same time. Business users define strategies through formulas and rules with no code, each strategy applies its own margin guardrails, and the engine outputs validated prices to separate pricebooks (US, EU, wholesale, client-specific) that distribute to storefronts and external retailer systems.

Real-time per-store pricing and inventory across 40+ retail locations.

Multi-store retail commerce with physical locations is structurally different from single-instance commerce. Every product has independent pricing across multiple price types (regular, sale, member, best, plus case-pack variants) at every store, with independent inventory quantity, stock status, aisle location, and express delivery flags.

A pre-aggregation pipeline indexes all store data for each item into a single Algolia document, with each variant carrying every store's pricing and inventory packed alongside aisle and fulfillment metadata. The customer's selected store filters search results client-side with no additional API calls at render time.

Two-track pricing with parallel promotion evaluation

B2B commerce often maintains parallel price structures (unit/wholesale and retail) managed by different teams, and promotions need to apply to each track independently without interfering with the other or confusing the buyer.

Promotions run against both the unit price and the retail price on parallel tracks, each scoped to a specific price list. After both tracks evaluate, the system selects whichever discounted price is lower as the final customer price, while preserving the original unit price as the reference point for savings calculations in B2B quotes.

Every price calculated live. Cached intelligently.

Standard e-commerce pricing relies on a static price list. In B2B, the price a customer sees depends on their account, ship-to location, tax jurisdiction, currency, and in some categories the physical dimensions of the product they are configuring. A static list cannot represent any of that.

Every price displayed on the storefront is calculated live by the ERP based on customer context, quantity, and product configuration. The caching layer builds a composite key from 12+ parameters, product, quantity, unit of measure, warehouse, bill-to, ship-to, VAT code, tax code, currency, and an MD5 hash of the full product configuration including dimensions, keeping cached prices accurate without redundant ERP calls.

Ten pricing tiers. One signed-in customer.

Wholesale and specialty retailers often serve multiple customer types at the same time: retail shoppers, loyalty members, verified military and first responders, and dealers across multiple volume tiers. Each one expects a different price on the same product, and the system has to resolve the right one the moment they sign in.

Identity verification through ID.me unlocks government and first responder pricing in seconds. EDGE loyalty membership applies tier-based rewards on top of the customer's base price. Dealer accounts route to one of five wholesale tiers based on volume and agreements. The pricing engine resolves the price group and selects the final price following a defined priority, with ten distinct pricing tiers across two storefronts, the customer seeing only their price.

Sales-rep override pricing applied at the quote level.

B2B pricing rarely lands on the list price. Negotiated discounts, customer-specific terms, volume incentives, and deal-specific pricing all need to be applied at the quote level, often by a sales rep with the authority to override standard pricing within defined rules.

Sales reps apply custom pricing to line items within the quote, with the override captured alongside the standard catalog price. Approval rules can route overrides above a threshold to a manager before the quote can be sent. When the quote converts to an order, the negotiated pricing carries through to the ERP with the custom price preserved at the line item level.