Skip to content
TierCommerce

Calculator

Will your B2B store hit your ERP’s API limits?

Enter a few numbers about your store and pick your ERP. You’ll see how many API calls a day the integration makes, how your busiest minute compares with the limit, and what to change first if it doesn’t fit.

Interactive

Sync budget calculator

How many API calls a day your store would make, against your ERP’s published limits.

Your store and ERP

MYOB, Pronto Xi, Options, SAP Business One and Unleashed don’t publish limits to calculate against.

orders
calls

Contact, invoice or order, payment, read back

orders

Say, just after a promotion email goes out

minutes

0 if your ERP sends webhooks

calls

Prices or balances fetched while a buyer waits

SKUs
accounts
runs

Every product and customer, 100 per call

API calls a day

2,934

Daily limit (5,000) 59%
Busiest minute: 124 of 60 calls 207%

Queued at the limit, the busiest minute takes about 3 min to send.

Over the limit

The ERP will refuse calls unless the integration queues them and asks for less.

Where the calls go each day

Sending orders
600
Checking stock
288
Live lookups
2,000
Full refreshes
46

Live lookups use the most calls. Cache prices and balances in the store, and only ask the ERP live at checkout.

Xero: 60 calls a minute and 5,000 a day for each connected organisation, with up to 5 at once. Source, checked October 2026.

How we work it out

No hidden multipliers. These are the sums behind every number in the calculator.

For what to do with the result, read our guide to ERP integration for B2B ecommerce.

  1. Sending orders = orders a day × API calls per order.
  2. Checking stock = 1,440 minutes in a day ÷ minutes between checks, around the clock. Zero when your ERP sends webhooks.
  3. Live lookups = the calls made while a buyer waits, such as a live price or account balance.
  4. Full refreshes = (products + customers) ÷ 100 records per call, rounded up, × refreshes a day.
  5. Busiest minute = orders in that minute × calls per order, plus live lookups spread over an 8-hour trading day.
  6. The verdict uses whichever limit is closest: under 60% fits comfortably, up to 100% is tight, and over 100% is over the limit. Retries aren’t counted, so leave room for them.

About this calculator

Where do the API limits come from?

From each vendor’s own developer documentation, checked in October 2026. The calculator links to the source for whichever system you pick. Vendors change their limits, so check the source before you rely on a number.

Why aren’t MYOB, Pronto Xi or Options in the list?

They don’t publish numeric limits to calculate against. MYOB applies per-second and daily limits per API key without listing the numbers, and on-premises systems such as Pronto Xi, Options and SAP Business One are limited by your own server. Ask your ERP partner what load the integration can safely add.

What counts as an API call?

Every request the integration sends to the ERP: reading a page of products, creating an invoice, applying a payment, or checking a price while a buyer waits. One online order usually takes several calls.

What should we do if we’re over the limit?

Queue writes so bursts go out at a steady rate, cache prices and balances in the store instead of asking the ERP live, use webhooks instead of polling, and fetch only what changed. The calculator shows which of these saves the most for your numbers.

Does TierCommerce stay within these limits?

Yes. Our integrations queue writes, cache what changes rarely and fetch only what changed, so they stay inside each ERP’s limits as order volume grows. Book a demo and we’ll show you the sync log on your own ERP.

See TierCommerce running on your own products.

Bring a price list and a recent purchase order. We’ll show you both working in 30 minutes.