Connecting B2B sales, a B2B portal, and the ERP for a distributor
A reference scenario for a wholesale distributor: automated PO intake, ERP-driven customer pricing on a B2B portal, and account briefings for sales reps.
This is an illustrative scenario based on situations we commonly see. It does not describe a specific client, and it contains no client results.
The scenario
This reference scenario describes a common situation in wholesale and distribution. The business is representative, not a specific client.
A distributor sells several thousand products to retailers and contractors. The ERP holds inventory across two warehouses, contract pricing, and customer accounts. A B2B portal on Magento 2 lets customers reorder online, but most orders still arrive as PDF purchase orders by email. Sales reps work from a CRM that has no visibility into orders or invoices.
The challenge
- Manual order entry. Inside sales re-keys every emailed PO into the ERP, translating each customer’s own part numbers into the distributor’s SKUs.
- Pricing drift. Contract prices updated in the ERP reach the B2B portal through a manual export, so customers sometimes see the wrong price online.
- Reps without context. Preparing a quarterly account review means pulling orders from the ERP, invoices from accounting, and notes from the CRM.
The approach
Purchase order intake
- A PO arrives at a dedicated inbox.
- An extraction step reads the customer, line items, quantities, and requested dates, with a confidence level for every field.
- Lines are matched to SKUs using the customer’s cross-reference table held in the ERP. New mappings confirmed by staff are saved for next time.
- Contract pricing and availability by warehouse are applied.
- A draft sales order is created in the ERP. Low-confidence or unmatched lines are flagged.
Inside sales reviews flagged lines and releases the order. Clean orders take seconds to confirm.
Pricing synchronized from the ERP
The ERP remains the only place prices are edited. Changes are pushed to the B2B portal’s shared catalogs and customer groups automatically. Large price changes generate a summary for approval before publishing, and every sync is logged.
Account briefing agent
Reps ask, “Prepare me for my call with this customer.” A read-only agent uses tools exposed through an MCP server to pull:
- 12 months of orders compared with the prior year
- Open quotes and backorders
- Overdue invoices and credit status
- Products the customer used to order but hasn’t recently
The agent produces a one-page briefing with sources. It cannot change any data.
Where people stay in control
- Inside sales releases every order created from a PDF.
- Price changes above a threshold require approval before reaching the portal.
- The rep agent is read-only by design.
What we would measure
- Time from PO received to order confirmed
- Order-entry corrections and credit notes caused by keying errors
- Pricing discrepancies between the ERP and the portal
- Time spent preparing account reviews
Every engagement starts by recording these as a baseline, so improvements are measured, not estimated.