Build or buy

Build your own pricing engine, or use Quantaprice.

Your prices live in the ERP, the commerce platform or code your team wrote. This page lists what a pricing service has to handle, what Quantaprice provides for each item, and the cases where building it yourself is the better choice.

In short

The decision in short

What you would build

An endpoint that returns a price, and behind it inheritance between pricelists, rules, currencies, VAT, rounding, scheduling, history and change events. Each is work your team would own and maintain.

What Quantaprice is

A dedicated pricing service that your ERP, commerce platform and storefront call over a REST API. It holds articles, pricelists, prices and rules, and returns the price for a SKU, a customer, a currency and a tax area. Platform overview

How to test the choice

The Evaluation plan is free for 90 days, with 100,000 articles and 1M prices. Load your own catalogue and compare the result with the service you would build. Plans and prices

Scope

What a pricing service has to handle

Use the list as a scope check for your own build.

The service has to handleWhat Quantaprice providesDocumentation
Pricelist hierarchy and inheritance Pricelists form a tree: base, segment, customer. A pricelist without its own price for a SKU inherits its parent's price and applies its own rules to it. A price set on the pricelist itself takes precedence. Inheritance
Price rules CEL expressions on a pricelist, such as prices.cost * 1.35, with an optional filter on article metadata. The first matching rule sets the sales price. Price rules
Quantity breaks Each price can carry breaks: a fixed unit price or a percentage of the sales price from a minimum quantity. A query returns every break, converted and with VAT. Quantity breaks
Customer and segment prices A query selects pricelists by code or by metadata such as a customer ID. When several of them price the same SKU, the lowest price excluding VAT in the requested currency is returned. Best-price selection
Bundles A bundle is priced per pricelist as the sum of its components' prices, with an optional discount, or at a fixed price. VAT is calculated per component. Bundles
Currencies and exchange rates Each pricelist holds one currency, and a query can request any currency. Rates come from the European Central Bank's daily feed, and you can set your own. Exchange rates
VAT Tax areas, VAT classes per article and tax area, and dated VAT rates. VAT is added on a NET pricelist and extracted on a GROSS one. VAT
Rounding Rounding profiles round the final price by price range, with an optional offset for prices ending in .99. The VAT amount is derived from the rounded price, so the three figures add up. Rounding
Scheduled changes Prices, pricelist rules, bundle rules, rounding profiles, VAT rates and exchange rates can be written in advance with a start date, and take effect at that moment on every pricelist they affect. Scheduled updates
History and as-of queries A change never overwrites what it replaces. A query with as_of returns the price in force at that moment, within the history your plan keeps. Historical pricing
Change events A changelog of every change, polled with a cursor. Webhooks signed with HMAC-SHA256 push the same events where your plan includes them. Change events
Rate limits A read limit and a write limit per tenant, each with a sustained rate and a burst. A request above the limit gets 429 with a Retry-After header. Rate limits
Backups A consistent snapshot of all your data every 10 minutes. You list, take and restore backups in the console. Backups
Audit log Sign-ins, access changes, API keys, settings and webhooks in an append-only, hash-chained log that your SIEM can fetch from the API. Price changes are in the changelog. Audit log
Approval Where your plan includes price approval, price changes go into a release and take effect together when someone who made none of them publishes it. Price approval

Every price is calculated in the same order: price rules, currency conversion, VAT, rounding. How a price is calculated For pricelists per customer and negotiated discounts, see customer-specific pricing.

Architecture

Where it sits between your ERP and your storefront

Your source systems write to Quantaprice, and every channel reads prices from the same endpoint.

  • ERP or PIM writes. An integration loads articles, pricelists and prices with batch endpoints that validate each item separately, and keeps them in sync as the source systems change. Loading data
  • Storefront reads at render time. The shop calls POST /price/query with the SKUs on the page, the customer's pricelist filter, the currency and the tax area. Quantaprice answers in under 10 milliseconds at the 99th percentile, however deep your pricelist hierarchy and however many rules and bundles you have. Platform overview Storefront pattern
  • Browser reads without an API key. A shop page can fetch prices from the shopper's browser with a short-lived storefront token that your server issues. Storefront prices
  • ERP, CPQ and warehouse stay in step. Webhooks keep prices current during the day, and the changelog catches up after downtime. ERP sync

Paid plans have a monthly availability target for the production Price API, from 99.5% on Starter to 99.9% on Scale. The Service Level Agreement describes how availability is measured and when service credits apply, and the pricing page lists each plan's limits.

The other answer

When building it yourself is the right call

A separate pricing service adds a system to run and integrate. In these cases your own code or the system you already have is the better fit.

One pricelist and no customer prices

Every customer pays the same price in one currency and one market, and prices change rarely. The price field in your commerce platform or ERP covers that.

Logic that does not fit pricelists and rules

A Quantaprice rule works on one price at a time. It cannot read other SKUs' prices, external data or the time of day, and it does not depend on the query. A price calculated from a product configuration or a live external feed needs code of your own. Rule limitations

Your main problem is promotions

Quantaprice does not manage promotions. Your checkout applies discount codes and campaign offers on top of the price it returns, so that logic stays with you either way. Order management and checkout

FAQ

Questions about building or buying a pricing engine

Does Quantaprice replace the prices in our ERP?

Your ERP can stay the source of base prices and costs. An integration loads articles, pricelists and prices through batch endpoints, and Quantaprice applies inheritance, price rules, currency conversion, VAT and rounding when your storefront, CPQ or order system asks for a price.

How fast is a price query?

Quantaprice answers a price query in under 10 milliseconds at the 99th percentile, however deep your pricelist hierarchy and however many rules and bundles you have. One query prices the SKUs of a whole page.

Can we start with flat prices and add rules later?

Yes. You can write prices through the API and query them without rules, hierarchies or inheritance. Price history, scheduling and several currencies work from the start. Customer prices, quantity breaks and inheritance can be added one step at a time, and the query API stays the same.

Can we reproduce a price we quoted or invoiced earlier?

Yes, within the price history your plan keeps. Store the as_of you used with the quote or order, and repeat the query with it: the price is calculated with the rules, exchange rates and VAT in force at that moment.

How do our other systems learn that a price changed?

Every change is recorded in a changelog that you poll with a cursor, on every plan. Webhooks push the same events to your endpoint on the plans that include them.

Can I try it with my own catalogue before deciding?

Yes. The Evaluation plan is free for 90 days with 100,000 articles and 1M prices, and includes every API.

Get started

Test it against your own catalogue.

The Evaluation plan is free for 90 days: load your pricelists, query them through the API, and check the result against the list above before you decide what to build.