Build ecommerce that fits your Monitor ERP

Why Monitor ERP customers need a deliberate ecommerce approach

Monitor ERP gives you a single system for production, purchasing, warehousing, and financials. It is widely adopted among Swedish manufacturers and wholesale businesses precisely because it handles operational complexity well. When you decide to sell online — whether B2B, aftermarket, or a hybrid of both — the question is not whether Monitor can support it. The question is how you build the commercial layer so it draws on Monitor’s data without creating manual workarounds or brittle point-to-point connections.

Many companies in this position already have some form of digital sales channel. The goal is not to start from scratch but to make the next version more connected, more maintainable, and better aligned with how your team actually works. That means understanding which data lives in Monitor, which data belongs in the ecommerce platform, and where you need a reliable bridge between the two.

Nordic Web Team works with companies at exactly this stage. We are not a Monitor reseller and we do not sell a single ecommerce platform. We help you evaluate the options, design the architecture, and deliver a store that fits your operations — not the other way around.

What Monitor ERP covers — and where ecommerce fits in

Monitor ERP is a Swedish ERP system that has been developed specifically for manufacturers since the 1980s. It is used primarily by metalworking, machining, plastics, and machine-building companies where production planning, costing, and MRP flows are central. The depth of its manufacturing modules is the main reason companies choose Monitor over more general-purpose ERPs.

Monitor today comes in two versions: G4, the mature version that many customers still run in production, and G5, the newer version that Monitor actively develops. Both have APIs that can be used for integration, but they differ in how data is exposed and which prebuilt connectors are available out of the box. Before an integration architecture is drawn, you need to know which version you run — and whether a G5 migration is on the table. The timing of a G5 migration often affects what makes sense to build on the ecommerce side.

What Monitor does not handle is the sales channel toward end customers. Product descriptions are technical, images are often drawings or missing, and the system is not designed to present articles to a buying audience. That is where an ecommerce platform comes in — as a complement to Monitor ERP, not a replacement.

How Nordic Web Team and Junipeer build the Monitor integration

The integration between Monitor and your ecommerce platform is built on Junipeer as the connector layer. Junipeer is an integration platform with prebuilt API connectors for the ERPs, payment providers, and shipping systems most Nordic merchants run. The Monitor connector is on the Junipeer roadmap — coming soon. Contact us for the current timeline. The architecture, data mapping, and surrounding work below apply equally to a Monitor project we scope today, with the technical bridge plugged in when the connector ships.

The data flows we set up

A typical Monitor integration moves five core data domains. Article master data flows from Monitor into the storefront on a defined cadence — usually every few minutes for changed articles, with a full reconciliation overnight. Stock levels sync more frequently, often every 1–5 minutes for fast-moving SKUs and on-demand at checkout for high-value items where overselling is unacceptable. Customer-specific prices and price lists are pulled from Monitor in real time when a logged-in B2B customer views a product or adds to cart, so the price the buyer sees is always the contracted price.

Customer accounts and credit limits flow from Monitor into the storefront so existing buyers see their agreed terms and credit headroom. New customers created online are written back to Monitor as customer records ready for credit assessment. Orders flow back to Monitor as sales orders with the correct customer reference, PO number, delivery address, and line items. From there, Monitor handles picking, packing, and invoicing through its standard workflows.

For companies with large or complex catalogues, a dedicated PIM system is often the right layer to manage product enrichment as a structured layer between Monitor and the storefront. See our PIM systems comparison to find the right platform for your catalogue.

How we handle the hard parts

Three areas need explicit design choices before any code runs.

Pricing logic. Many Monitor customers run agreement-based pricing with customer-specific discounts, volume tiers, and project pricing. We decide early whether prices are pulled live from Monitor on every product view (most accurate, more API load), cached at the customer level with periodic refresh (lighter load, slight staleness risk), or hybridized by product category. The right answer depends on order volume and how often pricing changes.

Credit assessment. For B2B with invoice payment, the credit limit lookup happens in checkout — the customer sees credit headroom before submitting the order. If the limit is exceeded, the flow either blocks the order, escalates it to sales for manual handling, or approves a partial order up to the limit. We define this together with your finance team, not after the fact.

Quote-to-order flows. If your B2B sales include quotes — common for project-based or configured products — the storefront supports a quote cart that submits as a request, your sales team prices it in Monitor, and the customer converts the quote to an order without re-entering products. The platform choice (Norce, Shopware, Magento with Hyvä) affects how natively this works versus how much custom configuration is needed.

What we deliver in each phase

The project follows four phases. Discovery and architecture takes 2–4 weeks: we map your Monitor configuration, audit data quality, decide platform fit, and define the data flows above. You get a written architecture document and a fixed scope for the build. Build and integration takes 8–16 weeks depending on catalogue size and pricing complexity: we configure the platform, set up Junipeer with the field mappings, develop the storefront, and implement the order flow end to end. QA runs in parallel and intensifies in the final 2 weeks: we test article sync, price calculations under different customer scenarios, order placement, credit edge cases, and the full loop back into Monitor. Launch and stabilisation is phased — we go live with a controlled customer segment first, monitor for 2–4 weeks, then open up to the rest. Post-launch we keep monitoring sync health and order success rates, and we address issues as they surface.

The result is an integration that is documented, monitored, and maintainable by your team and ours together — not a black box that only the original developer understands.

Choosing the right ecommerce platform for a Monitor setup

We typically evaluate three platforms for companies running Monitor ERP: Norce, Shopware, and Magento with Hyvä. Each has strengths that matter differently depending on your business model, catalogue complexity, and growth plans.

Norce is a commerce platform built in the Nordics with strong support for multi-market, multi-currency, and complex product structures. It works well for companies that need a robust product information layer and plan to serve both B2B and B2C from one backend. If you have a large catalogue with many variants and customer-specific pricing, Norce handles that natively.

Shopware is an open-source platform with a growing presence in Europe. It offers a flexible architecture, a modern storefront, and a strong ecosystem of extensions. For companies that want ownership of their codebase and prefer a platform with an active developer community, Shopware is a solid option — particularly if your primary market is B2B with plans to expand into direct-to-consumer.

Magento paired with Hyvä gives you a mature, feature-rich commerce engine with a modern, lightweight frontend. It suits companies with complex catalogue requirements, advanced promotion logic, or the need for deep customisation. The tradeoff is that Magento projects typically require more development effort, so it fits best when you have the budget and ambition to match.

We do not pick the platform for you in advance. We evaluate your data model, your buyer journeys, your internal capacity, and your roadmap before recommending where to invest.

What stays unchanged is that you do not have to replace your ERP. Monitor remains your operational backbone. The ecommerce layer is built around it — not on top of it.