Guides · ERP · Portals
ERP customer portal: what it is, when you need one, and how to ship it safely
An ERP customer portal is a secure web (or mobile) front door that lets your trade customers place orders, check stock, download invoices, and see account-specific pricing — with the ERP remaining the system of record.
UK manufacturers, distributors, and B2B wholesalers increasingly need this because email-and-phone order desks do not scale, while ripping out a working ERP is usually the wrong answer. A well-designed portal sits alongside the ERP and makes it usable for customers.
This guide is written for owners, ops directors, and fractional technology leads who are past brochureware and need a portal that creates real ERP orders — not a pretty form that emails a PDF into a shared inbox.
What an ERP-connected customer portal actually does
At minimum, a serious portal authenticates the buyer against your account structure, shows them only their pricing and credit status, and writes orders back into the ERP with the same validation your sales team uses. Stronger portals add live stock, delivery tracking, document packs, returns, and self-serve quote requests.
The important distinction is ERP-connected versus ERP-ish. A website that emails a PDF into a shared inbox is not a portal. A system that creates real sales orders, respects credit holds, and keeps invoices in sync is.
- Account login tied to ERP customer records
- Account-specific price lists and discount rules
- Order entry with product, pack, and delivery constraints
- Order history and status pulled from the ERP
- Invoices, credit notes, and statements as downloadable files
- Optional: live stock, call-offs, returns, and quote workflows
Who needs one (and who does not yet)
You likely need an ERP customer portal when repeat B2B buyers generate enough volume that sales admin is a bottleneck, when customers ask for 24/7 ordering, or when competitors already offer self-service. It is also a common requirement in distributor RFPs.
You may not need a full portal yet if you have a handful of key accounts served well by account managers, or if your ERP data quality is too poor to expose. Wrong stock figures destroy trust overnight. Fix the data and process first, then expose them.
Features that move the needle for UK trade buyers
Trade buyers are not browsing for inspiration. They reorder known SKUs under contract pricing, often from a van, warehouse, or phone. Favourites, reorder-from-history, and clear pack sizes beat fancy filters.
Credit visibility before checkout prevents embarrassing declines. Multi ship-to addresses and branch logins matter for regional distributors. If your commercial team still negotiates every line, keep complex quotes on the phone until the rules are solid.
- Reorder and saved lists tied to the customer account
- Credit and balance shown before order confirmation
- Depot or warehouse stock where the ERP supports it
- Document centre for invoices, PODs, and certificates
- Role separation: buyer vs accounts payable
Build vs bolt-on vs ERP vendor module
Most ERP vendors sell a portal or customer experience module. These can be fine when your processes fit the vendor's assumptions and you are happy locking deeper into that stack. They become painful when your pricing, kits, or trade workflows are idiosyncratic — common in UK manufacturing and distribution.
Bolt-on SaaS portals that sync via API can ship faster, but you still own mapping, edge cases, and support when sync fails. A bespoke portal on top of your ERP (the pattern we use at HTML Studio) costs more upfront than a template, but preserves your rules and avoids forcing customers into a lowest-common-denominator UX.
Choose based on complexity of pricing and stock rules, appetite for vendor lock-in, and whether the portal is a competitive differentiator or a hygiene feature.
A safe delivery sequence
Treat the portal as a product, not a one-off website. Start with read-only account history and documents for a pilot group, then enable order entry for a subset of SKUs or customers, then expand. Keep the ERP as source of truth; never invent a second stock ledger in the portal.
Instrument everything: failed logins, order rejection reasons, sync lag. Those metrics tell you whether the portal is reducing phone traffic or just creating a second channel for errors.
- Pilot customers with clean account data
- Read-only invoices and order history first
- Write-path orders with the same validation as internal entry
- Rollback plan if ERP posts fail
- Training for sales so they champion the portal instead of bypassing it
Security, GDPR and commercial confidentiality
A portal exposes contract pricing. Enforce HTTPS, rate-limit logins, avoid enumerable account URLs, and log staff impersonation used for support. Align retention of portal logs with your privacy policy.
Do not copy full customer and price tables into an unmanaged spreadsheet export for the web team. Prefer APIs or a controlled integration layer with least-privilege credentials.
How this ties to HTML Studio work
We regularly deliver ERP-connected portals for UK B2B firms — including customer portals that sit on live ERP data rather than shadow databases. See our customer portal case study for a concrete example of that pattern, and the related guides on self-service and account portals for deeper feature detail.
Related guides and examples
Planning an ERP customer portal?
If your trade customers still order by email and phone, we can map a portal that respects your ERP rules — and ship a pilot without a risky rip-and-replace. Start with a discovery call.
