B2B pricing engine
Stop rebuilding contract prices and discounts in spreadsheets and application code. Define products, customers and pricing rules once — PriceRules resolves the right price for every customer through one REST API.
Free plan, no credit card. Sample data included.
Contract prices, volume breaks and exceptions end up spread across spreadsheets, ERP exports and application code.
Every key account has its own price list, and every update means finding, editing and re-sending the right file.
The storefront, the quoting tool and the ERP each re-implement contract prices and volume breaks — and drift apart.
Sales, ecommerce and finance can't be sure they're quoting the same price for the same customer and quantity.
PriceRules becomes the single place prices are defined, and the API is how every other system reads them.
Upload products, customers and pricing rules as CSV. Map columns, then every row is validated and rejected rows come with a reason.
CSV import referenceFixed prices and percentage discounts per customer, per SKU or both, with minimum quantities and priorities.
How rule matching worksYour application sends a customer code, SKUs and quantities to the pricing API with a workspace API key.
API referenceThe response returns the final unit price, the rule that was applied and why it matched.
Resolve your first priceThis runs the same resolution function as the API, on a small sample workspace. The most specific rule scope that qualifies wins; within a scope, the highest qualifying minimum quantity, then the highest priority.
Rules in this sample workspace
Products: VLV-304 ($48.00), FAS-1001 ($24.00).
Resolved unit price
$39.50$48.00
Rule: Acme volume price 100+
{
"customer_id": "ACME-BUILD",
"products": [
{
"sku": "VLV-304",
"quantity": 100
}
]
}{
"final_price": 39.5,
"applied_rule": {
"name": "Acme volume price 100+",
"type": "fixed",
"value": 39.5
},
"match_reason": "MOST_SPECIFIC_RULE",
"pricing_summary": {
"savings": 8.5,
"message": "Customer saved 8.50 due to active pricing rules"
}
}One rule set for every channel instead of price logic copied into each application.
Learn moreScope a rule to one customer and one SKU, one SKU, one customer, or everyone.
Learn moreColumn mapping, row-level validation, rejection reasons and safe retries for large files.
Learn moreUp to 500 SKUs per request, or up to 10 customers per bulk call.
Learn moreMinimum quantities create volume breaks; priorities settle ties deterministically.
Learn moreSee monthly resolutions in the app, with email alerts at 90% and 100% of your plan.
Learn moreA central pricing layer means one update instead of several, one rule instead of the same logic in every application, and one answer when someone asks what a customer pays. Estimate what that's worth with your own numbers.
An estimate from your inputs only: weekly hours × people × 48 working weeks gives today's workload; the share you expect to remove, times your hourly cost, gives the estimate. It isn't a benchmark or a guarantee, and it doesn't include your subscription or the development time to integrate the API.
Keep your ERP as the system of record. PriceRules holds the pricing rules and answers price requests from the systems that need them.
Your data
Brought in as CSV files, or created in the app.
PriceRules
REST API
POST /api/v1/pricing/resolvePOST /api/v1/pricing/resolve/bulkYour applications
Your team calls the API from these systems.
Every plan includes the same engine, imports and API. Plans differ in capacity and API volume.
For trying PriceRules with your own data.
$0/ month
For small pricing teams putting a real pricing layer in place.
$29.99/ month
For established B2B teams pricing across more than one channel.
$79.99/ month
The import formats, rule matching and every API response are documented — including the error codes.
A B2B pricing engine stores your base prices and the rules that change them for specific customers, products and quantities, and calculates the final price on request. Instead of each system keeping its own copy of contract prices and volume breaks, they all ask the engine.
Distributors, manufacturers, wholesalers and B2B ecommerce teams that sell the same catalog at different prices to different customers — and the developers who need to serve those prices to a storefront, portal or quoting tool.
Two rule types: a fixed unit price, or a percentage discount off the product's base price. Each rule can target one customer, one SKU, both, or everyone, and can have a minimum quantity and a priority.
Not through a native connector today. You bring data in with CSV imports (for example, exports from your ERP) and your applications request prices from the REST API, which requires some development work on your side.
No. PriceRules sits alongside your existing systems as a pricing layer. Your ERP can stay the system of record; PriceRules answers the question "what does this customer pay for this SKU at this quantity?".
Sign in with Google or your work email to create a workspace on the Free plan. Onboarding can load sample data so you can resolve a price in the app before importing your own.
Create a free workspace, load the sample data or import your own CSV files, and resolve your first price through the API.