Guides · ERP · Portals
ERP portal guide: what an ERP customer portal 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. For a real example, see our customer portal case study: a portal on a long-established ERP that took over £30m of trade orders in 2025.
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 is an ERP portal?
An ERP portal is a secure website that gives people outside your back office — usually trade customers, sometimes suppliers or field staff — controlled access to data and transactions held in your ERP. Customers log in and see their own prices, stock, orders, invoices and statements, and anything they submit becomes a real ERP transaction rather than an email someone re-keys.
The ERP stays the system of record; the portal is the front door. That is the difference between an ERP portal and a standalone web shop, which keeps its own product, price and order data and has to be synced back by hand or by batch import.
When people say "ERP portal" they usually mean a customer portal (ordering, account history and documents), a supplier portal (purchase orders, ASNs and invoices), or an employee or field portal. This guide focuses on the customer portal, which is where most UK B2B firms see the quickest return.
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
Customer account portal: logins, pricing, history and documents
Some firms search for a "customer account portal" rather than an ordering portal. The emphasis is different — login, account history and documents first, ordering later — but it is the same product on the same ERP data, so most projects deliver both in phases.
The account area is where each trade buyer sees their world: their prices, their orders, their invoices and their users. Identity comes first: invite users per account, separate roles (buyer versus accounts payable), password resets, and optional single sign-on later. Then commercial truth: price lists, open orders, invoices, credit notes and statements sourced from the ERP.
Many UK B2B firms also need proof of delivery, batch or lot certificates and quote history. Those documents should be retrieved or generated from systems you already trust — not re-keyed into a CMS.
The common failure mode is cloning customer and price tables into the portal database and letting them drift. Prefer API or integration reads (cached where needed) with clear refresh rules, and route writes — new users, new orders — through validated ERP transactions so there is never a second source of truth.
- Multi-user accounts with role permissions
- Account-specific catalogues and prices
- Order and invoice history with filters
- Document downloads with audit logging
- Accounts payable users who can see invoices without placing orders
- Optional punch-out or procurement integrations later
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, the self-service ordering portal guide for distributors for order-desk detail, and website–ERP integration for the integration layer itself.
ERP self-service portal: the ordering-first slice
When people search for an ERP self-service portal, they usually mean the ordering-first slice of a customer portal: repeat buyers place call-offs against live stock and contract prices, download paperwork, and stop ringing the order desk. That is the same architecture as a full ERP customer portal, scoped to the workflows that move revenue first.
We cover that pattern in depth in the self-service ordering portal guide for distributors, including what to put in a pilot and how to measure adoption. Use that guide when the brief is to get trade orders off the phone; use this page when you need the wider account, documents and credit picture.
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.
