Fixed schema. Locked pricing engine.
Every commerce platform hands you two problems, not one:
- A fixed catalog schema you can only extend by forking it or bolting on a separate PIM to hold the fields it won't.
- A pricing engine with a rule grammar you can't extend past percentage-off and BOGO, or a bespoke service bolted in front of checkout, drifting out of sync with your catalog and yours to maintain forever.
Vendure handles both in one core, where the catalog model and the pricing rules live in code your team controls.
Catalogue model, pricing pipeline, and rules
The catalogue model, the pricing pipeline, and the promotions engine ship as the foundation. Contract pricing and packaging units extend the same pipeline for B2B complexity.
Catalogue model and promotions
The product, variant, and collection model, the multi-stage price pipeline, and the promotions engine — conditions and actions you configure in the dashboard or extend in code.
B2B pricing
Quantity breaks, customer-group pricing, and contract pricing, scoped by channel and currency. Priority and exclusivity flags decide which rule wins when several match a line.
Packaging units
Sell by piece, box, or pallet with per-variant conversion factors. The catalog stays one source of truth and the price recalculates against the unit a buyer actually orders.
Your catalog model, without a separate PIM
Vendure's catalog is one canonical model: products, variants, facets, and filter-based collections. You extend it by adding typed custom fields in config that become first-class columns on the real entities, surfaced automatically in the API and dashboard.
One catalog, every market
The same model projects across every market. One master catalog is assigned per channel, each with its own currency, language, and tax zone, with prices stored per channel and currency and product content stored per language and resolved to the request's language.
This is the catalog the pricing chain reads from: every price rule resolves against this model.
Pricing logic your team controls end to end
Pricing resolves as a chain of swappable strategies. Your team plugs its own rules in at the same point as the built-in ones.
- Resolve the catalog price.
- Apply any matching price rule (quantity break, customer group, contract row, or channel override).
- Convert against the requested packaging unit.
- Apply matching promotions in the order calculator.
Every step runs in your codebase. One chain, one core — no separate pricing vendor to integrate or maintain.
Three commercial models handled without custom code
Trusted by complex B2B commerce and enterprise retail.
What buyers and engineers ask before they commit
Common questions from commercial and engineering teams evaluating Vendure for a real pricing workload.
Part of one platform, not a point solution
Catalogue and pricing is one of several capability areas in the wider Vendure capability set, alongside B2B workflows, search and discovery, operations and automation, and governance and compliance. Every area runs on the same core, so you extend one platform instead of stitching together a separate vendor for each. See the full capability overview.
