ERP systems as the hub for your website and portal
Peter Nilsson
An order lands in the webshop late on a Friday. Stock shows three left, but the shelf is empty. On Monday the invoice goes out with a price the sales rep never approved, and the customer calls.
Three systems are showing three different versions of the same truth. None of them is wrong on its own. Nobody ever decided which system owns which job.
This post looks at the ERP system as the shared source of facts for your website, portals and ongoing maintenance. You get the modules, a model for data ownership and a breakdown of what actually costs money after go-live.
An ERP system is the company's shared record of facts
An ERP system gathers items, prices, stock, customers and orders in one place, so every department works from the same numbers. ERP stands for Enterprise Resource Planning, and the role is the same whichever vendor you choose: the system should be the single source of what is true.
Everything else is a window into the same room. The website, customer portal, reseller portal and analytics tool each show their own view of what is in the room. If the room is messy, every window looks messy, however nicely the frame is painted.
Some things sit outside the core. Images, channel copy and enriched product attributes usually live in a PIM system, which covers what the ERP system isn't meant to handle. How responsibility is split between the systems decides whether your website and portal show the right price and the right stock level.
ERP is nothing new for Swedish companies. Statistics Sweden (SCB) tracks how many companies use ERP systems in its annual survey of ICT usage in enterprises.
If you build websites, product data and customer portals on top of the ERP system, that is a sensible starting point. The questions left are practical: which modules you need, which data needs an owner and how the channels connect to the same order flow.
ERP modules and who uses them
Picture the ERP system as a hub with finance and accounting at the centre. The general ledger, accounts receivable and payable, VAT and budget are what everything else hangs on, and it is where the CFO spends time every month.
Around the hub sit the modules each role lives in. The sales administrator works in orders and invoicing with quotes, orders, invoices and price lists. Warehouse staff work in purchasing and inventory with stock levels, picking and delivery planning. The production planner works in production with bills of materials and scheduling. The project manager works in projects and services with time billing and follow-up. HR and payroll share employees, time and pay.
The same task in several systems is a common cause of errors. The image below shows how to avoid it.

Then there are the outbound connections: CRM for customer relationships and analytics for decision support. That is where the sales director and the CFO sit, often in the same report and rarely in the same system.
No module is mandatory. A services company can start with finance and projects and get by on that for a long time. A trading company nearly always starts with finance, orders and inventory, because the order flow is the business.
Module names vary between vendors. One calls it inventory, another calls it logistics, and the contents differ more than the names do. Compare modules on what they actually include. The name on the price list tells you less than what is inside.
We work with Business Central and Monitor in our integrations. The modules a customer has in production decide what data there is to connect, and that is always where an integration discussion starts.
Every data domain needs a system that owns it
An item can have three prices. One sits in the ERP system, one in last year's spreadsheet and one in the website's content tool. All three are true for someone, and the customer sees whichever price happens to win in that channel.
Write down which systems you run today: the ERP system, PIM, website and portal, plus the spreadsheets nobody owns but everyone uses. Decide which system should own which data and how you manage master data across systems. Record the decision somewhere people outside IT can read it.
The map below shows the same principle in four nodes and one shared point of failure.
Mark where the same information lives in more than one place. That is where the conflict already is, even if nobody has reported it.
The ERP system owns items and item numbers, stock and stock levels, accounting-relevant prices and order status. PIM owns enriched product attributes, images and channel copy. CRM owns sales contacts and customer interactions. The website and portal own the published content and show prices and stock levels from the ERP system.
The customer number is the decision that takes longest. CRM creates a contact when a sales rep books a meeting. The ERP system creates a customer number when the order is invoiced. If both can write the number, the same company ends up with two identities, and orders, prices and the sales ledger point in different directions. We recommend letting the ERP system own the number that orders and invoices use. CRM keeps sales contacts and interactions and stores the ERP customer number as a reference rather than as its own master field.
Without a written owner, two systems end up writing to the same field. The conflict shows up at sync, and the error lands with whoever happened to look last. Nobody owns it, which is why it gets expensive.
Four metrics from the start are enough: sync delay between systems, share of successful messages, number of manual corrections per week and discrepancies between ERP data and what the channel shows. Few companies have their own analytics team to lean on, so the numbers need to be simple enough for the people already working in the flow to keep track of.
Glanser keeps 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. That decides whether ownership holds over time. For Business Central, the connection is available as a ready-made integration at a fixed price.
Website, portals and EDI as channels into the same order
A manufacturer with three entry points is a common setup. Smaller customers order in the webshop. The wholesaler sends EDI. The reseller logs in and sees their own prices and stock. All three have to land in the same order flow, against the same stock and the same pricing logic.
SCB's statistics on e-commerce in enterprises show that 36.7 per cent of companies with at least ten employees in the surveyed industries had e-commerce sales in 2024. In the same group, 31.2 per cent sold via the web, 11.2 per cent via EDI and 5.7 per cent via both.
The figures show something practical: web and EDI exist side by side, and a smaller share of companies runs both.
EDI suits recurring wholesale orders in a fixed format. The webshop suits smaller, irregular purchases. The portal suits customers who need to see their own agreement, stock levels and open orders. When a purchase ends up in the wrong channel, manual handling goes up.
If each channel has its own price list, the error shows straight away. The customer sees one price in the portal and another on the invoice, and the sales rep has to explain the gap. Pricing logic belongs in the ERP system. The channel shows the price, stock level and order status the system has already set.
A self-service customer portal and a spare parts portal for the aftermarket are technically the same thing. Both are channels into data that already exists, with permissions controlling what each customer can see. The portal replaces a flow of phone calls and emails. Customers look up status, prices and stock themselves.
Three checkpoints decide whether it holds: when stock levels update after an order is placed, which orders get stuck in the queue and who owns error handling when an order is rejected. The answers say more about integration quality than any feature list.
The real cost of an ERP system comes after go-live
SCB's statistics on cloud services in enterprises show that 72 per cent of Swedish companies with at least ten employees bought paid cloud services in 2025. It is easy to read that as modernisation being done the moment the contract is signed.
The bigger cost comes after go-live. The question rarely asked during procurement is who owns the connections between the ERP system, website, PIM, portals and analytics when APIs, data models or versions change.
The cost drivers are platform and ERP upgrades, releases that touch the integrations, bug fixes after a release, data quality that slips, internal expertise that leaves and the testing time before each upgrade. Testing time never appears on an invoice. It appears as three days when nobody can place orders.
Most budgets have two lines: the build and a flat estimate for maintenance. The estimate is set after a year when nothing happened. It breaks in the year a platform release and an ERP upgrade land in the same month.
So calculate three years at a time. What does it cost to keep the integrations running, not just to build them? How do you test an upgrade without stopping the order flow? Those questions give a more honest total than a list of cloud benefits.
Glanser manages the solution as a product under the name Glanser Care. Platform upgrades, new ERP versions and bug fixes are included in the agreement and not billed separately. New functions are added with fixed scope and a fixed price. The responsibility covers keeping the solution working as platforms and systems are updated.
When an ERP system doesn't fit and when to wait
An ERP system won't fix a process nobody has defined. That means there are situations where installing or replacing one is the wrong next step, however keen the vendor is to sell it.
The most common is undefined processes. Nobody knows who approves credit or when an order can be released. The choice of system doesn't matter then, because the rules aren't written down. Decide them first, ideally on a single page, and look at software afterwards.
A small company with one channel and simple inventory rarely gets its money back. A spreadsheet works there, and an ERP system would cost more in time than it returns. Wait until volume or the number of channels makes the spreadsheet risky.
Sometimes the need is really a website. If you only want to publish products and take enquiries, there is no order to integrate. Start with the product website and add ordering when sales volume calls for it.
Messy data is the fourth trap. If the item register is full of duplicates and half the range has no price, a new system just moves the mess somewhere more expensive. Clean up the register first, or bring in a PIM where product information can be enriched before it goes out to the channels.
Every change in the ERP system has knock-on effects in the channels. Replacing it means rebuilding every integration, and that work is often bigger than the system replacement itself. A step-by-step build, from product website to customer portal, suits many companies better. It asks more discipline of you as the customer, because you have to keep ownership in order while the solution grows.
The system becomes necessary when the processes are settled and there are more channels than a spreadsheet can keep track of.
What the vendor should be able to answer before you sign
It is nine o'clock on a Tuesday. The portal shows the item in stock. The ERP system says it is sold out, and the customer has already placed the order. Before you sign, the vendor should be able to tell you who decides when a price change reaches the portal and in which order the channels are updated. That is a different question from which system stores the price. If nobody owns it, every discrepancy lands with you.
Then move on to the lifecycle. How is a new ERP version tested against the integrations before it goes live, and how far ahead of a release will you know what is changing? A useful answer includes a date and a named test environment. If the answer stops at the word "dialogue", every upgrade becomes a new project when it should already be part of maintenance.
Finally, scope. Which functions are in fixed scope and which become change requests? How have recent release changes been split between vendor and customer? If every change is handled as it comes, you have a variable cost with a fixed label.
Ask all three questions in the same meeting, in that order. A vendor who answers without digging through a slide deck has probably made the trade-off before.
Fixed scope makes your integrations easier to compare
Two quotes for the same order flow can look identical until one turns out to be missing stock levels. In the Glanser Function Library, functions and integrations are already built, tested and priced. Every function has fixed scope and a fixed price before work starts. That lets you compare two integrations without half the job appearing after kickoff.
Standard is the ready-made integration. Adapted means a standard function is adjusted to your process, still with fixed scope and a fixed price. Customer-unique logic is built in isolation so it doesn't affect the rest of the solution during upgrades. Keep special cases within functions that already have a fixed price. Otherwise the next release turns into a new negotiation.
A solution can start as a product website and grow into a portal on the same foundation, with the same ERP integration. New functions are added in a controlled way. What can be connected depends on which modules and data the ERP system has. If the field doesn't exist in the system, there is nothing to sync. How the integration stays stable across versions is covered in our post on ERP integration.
Glanser builds and manages the connection between your ERP system, website and portal. On our ERP and integrations page we describe which ERP systems we connect to and how scope is set from the start. Use that page as your starting point next time you compare vendors.

About Peter Nilsson
Peter Nilsson writes about integrations and product information, focusing on how business systems, PIM and the web can share the same data without duplicated work.

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
Ordering portals: how they work and what to demand
An ordering portal lets customers see their contract prices and stock levels and place orders themselves. How the order flow reaches the ERP system, when EDI is the better fit and what to demand from your vendor.
Kenneth Lyngshede
Master data management that governs your shared data
One source and one owner per attribute keep your systems giving the same answer.
Peter Nilsson