Core delivery work·AVOS sits on top →

CASE · B2B ORDERING · ERP + ACCOUNTING EXPORT

15,000 SKUs, 5 price tiers.
ERP orders without re-typing.

A B2B dental-supplies distributor moved trade ordering onto one storefront that prices per customer and hands every order to its ERP and accounting software, checked before it lands. About 500 orders a month now go into the ERP, and nobody types them again.

Client
B2B dental-supplies distributor (anonymized)
Stack
Magento 2 + ERP + accounting software + CRM
Scope
Ground-up build, then ongoing operations layer
Status
● Live
01 · The context

Every price depends on who's buying.

Clinics and labs order hundreds of SKUs, each at a price that depends on who is buying.

Before the build, a trade order meant someone reading it, finding the right price, and typing it again into the ERP. Then again into accounting for the VAT invoice. At a few dozen orders a day, that's where errors and month-end surprises come from.

02 · Before

Typed twice, found wrong at month-end.

  • Prices lived in spreadsheets and people's heads. One catalog couldn't show each customer its own price.
  • Orders were re-keyed into the ERP and the accounting system by hand.
  • Mismatches (SKU not in the ERP, customer without a code, wrong unit of measure) showed up at month-end reconciliation, not when the order came in.
03 · What we built

One storefront, one check, two exports.

  • One catalog, per-customer prices. ~15,000 SKUs on 5 customer price tiers, so a logged-in buyer only ever sees their own price.
  • Web → ERP order export with a health check. Every order is checked before it's pushed: unmapped SKU, missing customer code, unit-of-measure mismatch, two-step Incoterms, shipping as its own line, VAT by company. Bad orders stop at preview instead of leaking into the ERP. This layer alone took ~35 real tickets. Each order type had its own trap.
  • SKU registry and customer master. Aliases, temporary SKUs and duplicates resolved in one registry. New customers get a code auto-filled from a template, so their first order doesn't stall.
  • Web → accounting export for VAT invoices. Same order, no second typing.
  • CRM ↔ storefront sync. Customer and account data stays the same in sales and on the store.
  • Built with clean, structured product and business data from day one.
04 · After

Orders reach the ERP already checked.

  • ~500 orders a month exported to the ERP, rising month over month (Apr–Aug 2026).
  • ~500 orders a month exported to accounting for VAT invoices.
  • ~1,000 CRM ↔ storefront records synced a day.
  • The health check catches mapping errors before they cost a reconciliation.
05 · Why it holds up

One system, not three plugins.

Ordering, pricing and ERP sync are designed as one system. Each rule (price tier, unit conversion, VAT) lives in one place, so a change doesn't break the next order.

~500/mo

Orders into the ERP

Checked before export. Rising Apr–Aug 2026.

~500/mo

Orders to accounting

For VAT invoices. Same order, no second typing.

~1,000/day

CRM ↔ storefront records

Customer and account data kept in sync.

Not claimed: revenue, order growth, headcount saved. We didn't measure them.

STILL RE-KEYING TRADE ORDERS?

Start with the
$850 B2B Ordering Blueprint.

2 weeks, fixed. We map how your orders, prices and stock really move, then price the build line by line. Credited to the build if you go ahead.