ERP integration

ERP integration is the data flow between an ecommerce platform and an ERP (enterprise resource planning) system. The ERP is where the merchant's finance, accounting, inventory, purchasing, and often product data live. The commerce platform is where orders come in and where product data is presented to shoppers. Integration keeps the two in sync so orders reach finance, invoices reach customers, stock levels are honest, and product data stays consistent. ## What ERP integration actually moves The standard integration handles a handful of data flows. Orders flow from the commerce platform to the ERP for invoicing and fulfillment. Stock levels flow from the ERP to the commerce platform so the storefront shows real availability. Product data can flow either direction depending on where the source of truth lives. Customer records may sync so credit terms and customer categories are consistent. Prices, price lists, and B2B agreements often live in the ERP and flow to the commerce platform. Returns and credit notes flow back the other way. None of this is unique to ERP integration specifically. The same patterns apply to any two systems that need to share data. But because the ERP is usually the financial system of record, getting the integration right is especially important. Wrong orders in the ERP mean wrong invoices, which mean unhappy customers and unhappy accountants. ## Nordic ERP context In the Nordic market, common ERPs include Fortnox, Visma, Business Central (Microsoft Dynamics 365), SAP Business One, Pyramid, Monitor, and Jeeves. Each has its own API surface, its own data model, and its own quirks. Fortnox is common at small and mid-market. Business Central is common in mid-market. SAP is common at enterprise. The integration effort scales with the ERP's complexity and the merchant's specific data model. ## Direct integration vs iPaaS Two main approaches. Direct integration means custom code that calls the ERP API directly from the commerce platform (or vice versa). This is fine for one simple integration but becomes brittle as the number of data flows grows. Using an iPaaS means a middle layer that speaks to both the ERP and the commerce platform through pre-built connectors. The iPaaS handles retries, transformations, logging, and error handling. For anything past a simple two-way sync, iPaaS is usually the right choice. ## What headless changes In a headless setup, the ERP integration is a backend concern, not a frontend concern. The commerce platform's Storefront API exposes stock, prices, and orders to the frontend. Whatever iPaaS or integration layer sits behind the commerce platform is invisible to the frontend. This separation is a feature: the frontend can evolve without worrying about ERP schema changes, and the ERP integration can be reworked without touching the storefront. ## How Frntkey relates Frntkey is often paired with Junipeer, an iPaaS built by Nordic Web Team. Junipeer handles the ERP integration layer: connectors for Fortnox, Visma, Business Central, SAP, and others, plus warehouse and shipping systems. The typical Norce + Frntkey + Junipeer stack puts Frntkey on the frontend, Norce as the commerce backend, and Junipeer moving data between Norce and the merchant's existing business systems. Frntkey itself does not do ERP integration. It renders the storefront on top of whatever backend and integration layer the merchant has chosen. ## Related terms iPaaS · Order management system · Product information management · Headless commerce