Ordering portals: how they work and what to demand
Kenneth Lyngshede
A reseller calls to ask what price she has on an item. Someone in the sales office opens the spreadsheet, searches for her customer number and reads out the row. Next week another customer asks the same question, and the answer sits in a different sheet.
That is everyday life for many companies that sell on to resellers, installers and service workshops. Order values are high and customers are relatively few, but every order needs a phone call, an email and a manual check of price and stock. The work repeats every week without anyone really getting better at it.
How an ordering portal works in practice
An ordering portal is a logged-in space where customers see their contract prices, stock levels and previous orders, and place new orders themselves. The customer gets the same agreement and the same delivery as before, but no longer has to wait in a phone queue to find out the price.
The best way to picture it is the regulars' counter. The customer has the same agreement as everyone else in their customer group, but stands at the counter alone with their own price list in hand. Nobody on the staff has to look anything up, and nobody has to guess which discount applies.
What sets it apart from an open webshop is the customer login and the customer-specific price. A portal is built for repeat buyers with their own terms, their own delivery addresses and their own permissions. That is why a portal often starts as a small project and grows as customers start using it.
Web self-service is already common among Swedish companies. In 2024, 30 per cent of Swedish companies with at least ten employees received orders via their own website or an app, according to SCB's statistics on e-commerce. In manufacturing the share was 21 per cent, while motor vehicle trade and repair reached 54 per cent. The same statistics show that 8 per cent of companies sold via an external marketplace, and 4 per cent in manufacturing.

This post covers which functions remove manual work, how an order gets into the ERP system, when EDI is the better choice, what the portal requires of you and how to measure whether it pays off. How the order flow fits with the rest of your e-commerce is covered in our post on order management in e-commerce.
The functions that replace email, phone calls and paperwork
Each function corresponds to a recurring step in order handling, and each one comes with a metric that shows the work actually moved. That could be reorders per customer, invoice requests per month, delivery status calls per week, share of orders with address changes, gaps between contract price and order price, orders placed outside office hours, error reports per order, certificate requests per month and searches with no results.
Count the metrics before launch and again after a few months. If invoice requests don't fall, the function exists on paper but isn't being used, or customers can't find it. The portal's search data shows what customers search for, how often and where they get stuck, which turns zero-result searches into a shopping list for range and content. Use the metrics as a worklist when you choose what goes into the first version, and let the numbers decide the order.
The first group covers repeat purchases. With order history, a reseller can reorder the same ten items without digging through old emails, and a buyer who takes over from a colleague doesn't have to learn the range from scratch. Invoice downloads and delivery tracking remove a large share of calls to the sales office, because customers find the answer themselves without waiting for office hours.
The second group covers permissions. User management lets the customer's own administrator add and remove users without anyone on your side having to do it. Multiple delivery addresses send the order to the right receiving point straight away. A wrong address is a common reason an order has to be corrected before picking, and that correction disappears entirely when the address is chosen in the portal instead of being fixed afterwards.
The third group covers price and accountability. Customer-specific contract prices should be pulled from the ERP system, so the portal shows the right price to the right customer. Error reporting on orders captures problems where they occur, with order number and line, so the fix starts in the right place.
The fourth group covers access and documentation. Round-the-clock ordering means orders from customers on shifts or in other time zones don't have to wait for office hours. Documentation linked to purchased products lets quality and purchasing managers fetch certificates and guides themselves, without searching through emails and binders.
A function only earns its place if someone uses it every week. Consider starting with order history and reordering, since they often remove the most manual work, and add the rest when the metrics show the need. Product data is the foundation for all of these functions, and how to gather it is covered in our post on product information management.
How an order travels from the portal to the ERP system
The order flow has six steps.
Step one: the customer logs in and sees their contract prices and stock levels on the first screen. The price has to be their own from the start, otherwise they go looking for a price list in their inbox and the self-service is gone.
Step two: they add order lines and the portal checks item number, quantity and price against the customer's price agreement before the order is sent on. The most common mistake is price data missing in the ERP system, which produces a wrong price that only shows up on the invoice.
Step three: the order is sent to the ERP system, for example Business Central or Monitor, and gets an order number there. Step four: confirmation and status go back to the portal, so the customer can see the order has landed and doesn't need to call to check.

Step five: stock levels and prices update in both directions, so the portal shows the same truth as the ERP system. Step six: if an order fails, it is flagged and the customer sees an error report with the reason, so the next call doesn't have to start from scratch.
The same foundation applies to logged-in resellers, consumers and your own sales team. Everyone works with the same logic and the same master data, which is what lets an order move between channels without anyone correcting it by hand. We keep product and customer data, prices, stock levels and order flows in sync between the solution and the customer's ERP system, even when the systems are upgraded to new versions. How the connection itself stays stable across platform versions is covered in our post on ERP integration.
Portal, EDI or both as volume grows
Portals and EDI solve the same problem in different ways: both remove manual entry of recurring orders. The difference lies in who does the remaining work, and that is what decides the choice.
According to SCB's statistics on e-commerce in enterprises, 31.2 per cent of companies sold via the web in 2024, up from 29.4 per cent the year before. The share selling via EDI fell from 13.7 to 11.2 per cent, and 5.7 per cent used both channels. SCB counts orders placed via a website, app or EDI message as e-commerce, and payment doesn't have to be made electronically. The figures show how many companies use each channel, but say nothing about how much of their turnover it carries. More companies are taking orders via the web, while fewer are selling via EDI.
Five criteria decide the choice in practice. Volume tells you whether the order is worth automating. Order complexity decides whether the customer needs to see price, stock and quotes before ordering. The buyer's system maturity decides whether their ERP system can send and receive messages. A need for quote flows points towards the portal, and real-time requirements govern how often stock levels must sync. Work out where the manual work ends up: EDI moves the data entry to the buyer's system, the portal moves it to the customer and both remove the step where someone on your side types in emailed orders by hand.
An industrial customer with high-volume orders and an integrated purchasing system should go via EDI. A smaller reseller who orders a few times a month gets the portal, where they can see stock and contract price before clicking. For industrial and wholesale companies the answer is often both: the portal shows products, contract prices, quotes and order history, while EDI handles the large standard orders. Product data from the ERP system and PIM gives both channels the same basis.
When a portal fits and when it doesn't
The portal makes demands on you before it makes demands on the vendor. Three prerequisites decide whether it pays its way.
Product data has to be structured. Otherwise the portal shows incorrect descriptions, and the customer loses trust in the prices too. When product information is spread across several files, a PIM solution becomes a prerequisite.
Customer roles have to be defined. The decision on who can order, approve and see prices should be made before the portal is built.
Customer-specific prices have to exist in the ERP system. If they aren't there, the portal has nothing to show.
The need grows with company size. E-commerce sales in 2023 amounted to SEK 2,718 billion across web and EDI, equal to 26.3 per cent of turnover in companies with at least ten employees: 12.5 per cent in small companies, 18.8 per cent in medium-sized ones and 32.1 per cent in large ones, according to SCB's statistics on ICT usage in enterprises. A smaller company often manages with a simpler web flow, while a larger one needs several customer roles, contract prices, approvals and order history.
At heart, the assessment is about where the manual order work sits. A portal pays for itself by moving recurring orders from email and phone to the customer. That makes it a poorer fit when customers are few and order a few times a year, because there is too little recurring work to move. It is also a poorer fit when customers are happy with phone and email, or when the ERP system has no customer price lists. Then the portal becomes an extra channel someone has to keep filled with content.
Another option is to start smaller. A solution can begin as a product website and grow into a customer portal on the same structured foundation, with the same ERP integration. After launch the portal needs an owner: someone has to answer questions about content and permissions, and the functions need maintaining when the platform is updated.
Demand accessibility and operational reliability
The Swedish Accessibility Act for certain products and services took effect in June 2025. It applies to e-commerce services aimed at consumers. A portal aimed only at business customers isn't automatically covered, but the requirements are a good target there too. The technical target is EN 301 549 version 3.2.1, which includes WCAG 2.1 levels A and AA, according to PTS on accessible web content.
Where the law applies, it covers the whole order flow: product catalogue, search, filtering, basket, forms, login, checkout and order confirmation. A customer approving an order with a screen reader needs correctly labelled controls, visible focus indicators and understandable error messages at every step. Status messages about stock and price changes need to reach the customer without them having to look for them.
The PTS measurement shows that websites with an e-commerce service had just over three times as many accessibility errors per page as websites without e-commerce, according to PTS's report on the accessibility of Swedish websites. The cause is cumulative. A flawed product component is combined with dynamic filtering, checkout validation, authentication and asynchronous responses from the ERP system.
So write acceptance criteria that can be tested in every module, and add manual scenarios for keyboard without a mouse, screen readers and zoom. Operational reliability belongs here too. What does the customer see when login is slow, and how do they find out an order didn't go through? A clear message with an order number and the next step saves a phone call. This takes ongoing work in maintenance, and for a portal with few users a simpler setup may be enough.
Metrics that show whether the portal saves time
A high digital share doesn't prove the portal saves time. Digital sales can come from open webshops, marketplaces or automated EDI flows, and none of these says anything about self-service in a logged-in portal. What decides the value is where the manual work went.
Five metrics give the full picture. The share of order value that comes in digitally shows how much of the business goes through the channel, but not whether administration is falling. Orders customers place themselves in the portal show how often self-service is used, but not whether the order ends up correct in the ERP system. Orders via EDI or API show how much goes through without manual handling. Errors per order show how often an order has to be corrected, and the time from order message to accepted order shows how quickly the order lands in the ERP system.
The numbers need to be read together. If the share of digital orders rises but the sales office enters as many orders by hand as before, the work has moved without shrinking. A low error rate is also worthless if customers abandon the portal and phone their orders in instead. Only when digital volume rises and corrections fall has the portal taken over work that used to need a person.
The portal's own logs provide the data that order statistics lack. In Glanser's portal you can see what customers search for and how often, what they buy and where they get stuck. Zero-result searches reveal products missing from the range or named in a way customers don't use, and orders that are started but abandoned show where the flow loses them. That gives you a basis for fixing range, naming and permissions without guessing.
What to ask the vendor before you decide
Ask who is responsible for keeping the portal working when the platform and ERP system are updated, and whether that is part of a fixed agreement. The answer shows whether maintenance is planned or whether you'll get a new quote for every upgrade. Glanser Care is a contracted responsibility at a fixed monthly cost, covering version tracking, compatibility through upgrades and bug fixes.
Ask which functions are included in the fixed price and which are added as your needs grow. The answer shows whether the cost is known from the start or grows with every new request, and it decides how you compare two bids that look the same on page one.
Ask what happens when customer-specific contract prices are missing in the ERP system. The answer shows whether the vendor has thought through the failure cases, which is where most portal problems arise. If you want to calculate the maintenance cost, add it as a separate line in your TCO calculation, alongside functions and integrations.
Start by mapping your recurring orders
Pick the twenty most common ordering situations: reorders of standard items, quote requests, error corrections and address changes. Map how they work today, via email, phone, EDI or web, and how long each step takes. Measure for a month using the metrics above, so you have a baseline to compare against.
Then go back to the functions above and mark the three that would remove the most manual work for you. Write down which situations need to work in a first version and what falls outside it. That scoping is what makes a portal project possible to price and deliver.
Glanser's page on customer portals and self-service describes how a portal is built from a first version with a clear scope.
Glanser builds customer portals and reseller portals as a product with a fixed price per function, connected to your ERP system. You can start with a product website and add ordering, order history and customer-specific prices once the need is mapped. Visit Glanser to see how the Function Library and maintenance fit together over time.

About Kenneth Lyngshede
Kenneth Lyngshede writes about business models, offers and strategy, and how companies can plan their digital development with predictable costs.

ERP systems as the hub for your website and portal
Business systems consolidate finance, orders, inventory, and product data into a single source. This is then connected to the web, portals, and EDI.
Peter Nilsson
PIM for wholesalers and who owns the product data
PIM for wholesalers starts with deciding who can change what. How to split ownership between ERP and PIM, choose stable keys and set limits on where AI can enrich product data.
Peter Nilsson
Master data management that governs your shared data
One source and one owner per attribute keep your systems giving the same answer.
Peter Nilsson