B2B ordering system integrated with ERP, for distributors
If your distribution business runs B2B orders on Excel, Zalo, and a website that's really just a showroom, the website isn't the problem. The problem is that the website can't talk to your ERP, your accounting, or your field sales team. LUMA-E builds a B2B ordering system wired straight into SAP/MISA and a CRM, so every order a dealer places on the web flows in one line: contract price applied correctly, the order pushed into the ERP, accounting issuing the invoice, sales able to track it. Nobody re-types anything twice.
This isn't “build a B2B website”. It's an 8-layer operating system we've already built and that's running in production.
The real problem for a distributor
A real B2B distributor doesn't ask whether the site looks nice. They ask:
- Dealer A and dealer B buy the same SKU at different contract prices. Does the web apply the right price per company on its own?
- After a customer orders on the web, who re-keys that order into SAP? Do they fumble the product code or the unit (case / pack / each)?
- A warehouse runs short mid-order. Does the system split the order, ship what's on hand, hold the rest — or leave the whole thing stuck?
- Accounting needs to issue an invoice from MISA. Does the web data group into the right lines, with the right VAT?
- A field rep wants to place an order for a customer. Where do they do it, and whose price applies?
How LUMA-E solved it — told through Oroca
Each of those questions is a layer. Together they're why 90% of the “B2B websites” out there are just an online catalog, while the real work still runs on Excel.
Oroca is a system we built over the 5 months after go-live — about 1,150 real tickets closed (pulled straight from Plane), shaped into 8 operating layers:
- Storefront + Magento B2B — a ~15,000-SKU catalog, fast ordering by code list.
- B2B pricing & catalog — 3 price tiers (Retail, Clinic Mid, Clinic Chain), per-company custom pricing, prices hidden from unapproved buyers.
- Orders & operations — hold/unhold, order splitting when stock runs short, partial fulfillment, reps editing orders in place.
- Finance & accounting — orders exported to MISA, per-item VAT, order-to-invoice reconciliation.
- SAP/MISA bridge — Magento 2 to SAP S/4HANA (starting with manual CSV at minimum cost, API later), mapping SKU / customer / unit.
- In-house CRM — 13 epics, reps placing orders for customers, quote to approval to Won, owning the customer and attributing revenue.
- DMS field sales — offline route check-in app, 2,184 clinic prospects, 6 clusters of 6 reps.
- SEO/AEO/GEO — a Visibility Dashboard, and the AI result: 45% share-of-voice on industry questions (ChatGPT, Gemini, Perplexity, Claude).
The numbers
- ~1,150 tickets closed in 5 months, packaged into 8 layers. Not a web project, an operating system.
- 15,000 SKUs, 3 price tiers, custom pricing per company.
- Web → SAP orders: ~500 SOs/month (Apr–Aug, growing each month). Auto-mapping rate is still being measured (not yet proof).
- Web → MISA orders: ~500/month, growing each month.
- CRM ↔ Magento sync: ~1,000 records/day.
- AI visibility: 45% SoV (49 of 109 industry questions, W37/2026 snapshot).
One architectural rule runs through all of it: start at the cheapest thing that works (monthly CSV by hand first, API later), let the CRM own the customer data, and give every integration a health preview plus reconcile. No big bang.
FAQ
Q:What platform is this built on?
Magento 2 (or Shopify Plus, depending on scale), headless Next.js when performance calls for it. The platform's a technical detail. What decides the outcome is the ERP/CRM/accounting integration layers on top.
Q:We're on SAP — can you integrate with it?
Yes. We start with a monthly manual CSV export (minimum cost, runs right away), then move up to an API with SKU/customer/unit mapping and a health preview before anything's pushed.
Q:How long until we have something running?
There's no “build it all once and it's done”. We ship layer by layer: ordering and pricing first, the ERP bridge after, each layer live and measurable.
Q:Every dealer has their own price — how's that managed?
A multi-tier shared catalog plus custom pricing imported per company. PLP, PDP, and promotions all respect the assigned price and the price-hiding rules.
Q:How's this different from off-the-shelf DMS/ERP software?
Packaged DMS/ERP solves one piece. This ties those pieces together around the ordering website, built to your real operation. We've got ~1,150 real operating decisions to draw on.
Book an audit of your B2B system
We'll point to exactly which layer is leaking — double data entry, wrong prices, stuck orders — and the patch order, cheapest fix first.