iPaaS

iPaaS is a cloud service that connects business systems to each other. It sits between an ERP, a commerce platform, a warehouse system, a CRM, and any other software a merchant runs, and moves data between them on a schedule or in real time. The classic use case is keeping stock, orders, and customer records in sync across systems that were never designed to talk to each other directly. ## Why iPaaS exists Merchants rarely run a single system. A typical ecommerce operation has an ERP for finance and inventory, a commerce platform for the storefront, a warehouse management system for fulfillment, a CRM for customer service, and often a marketplace connector or two. Each system owns some of the data. Each system needs some of the data the others own. In the past, integration meant custom point-to-point scripts. Every new system meant new scripts, new failure modes, and new maintenance work. iPaaS replaces the tangle with a central hub that speaks to each system through documented connectors. Merchants can add or replace systems without rebuilding integrations from scratch. ## What iPaaS actually does A good iPaaS handles a few core patterns. Scheduled data sync runs on a cadence (every 5 minutes, every hour, every night) and moves data between systems in bulk. Event-driven sync reacts to changes in real time: when an order is placed in the commerce platform, the iPaaS pushes it to the ERP within seconds. Transformation reshapes data between systems that use different schemas. Error handling retries failed calls, alerts operators when something breaks, and provides audit logs for compliance. Good iPaaS platforms ship pre-built connectors for common systems (SAP, Dynamics, NetSuite, Shopify, Norce, Shopware, Salesforce) so merchants do not have to build every integration from scratch. Custom connectors are still possible when a system is unusual. ## iPaaS vs middleware vs custom integration Middleware is the older term. It usually refers to on-premise integration software that lived on the merchant's own servers. iPaaS is cloud-native middleware, delivered as a service. Custom integration is what merchants build when neither middleware nor iPaaS is used: bespoke scripts, cron jobs, and API calls that connect two specific systems. Custom integration is fine for one or two connections. It becomes a maintenance burden past that. ## iPaaS in a headless commerce stack A headless commerce setup is naturally friendly to iPaaS. Both the commerce backend and the iPaaS live behind APIs. Data flows through the iPaaS between the commerce platform, ERP, WMS, and any other system. The frontend does not need to know or care that these integrations exist. It just talks to the commerce platform's Storefront API for shopper-facing operations. Everything downstream is orchestrated by the iPaaS. ## How Frntkey relates Frntkey is often paired with Junipeer, an iPaaS built by Nordic Web Team. Junipeer connects Norce to affärssystems like Fortnox, Visma, Business Central, and SAP, plus warehouse and shipping systems. Merchants who choose the Frntkey + Norce + Junipeer stack get a headless storefront on the front, a modern commerce engine in the middle, and clean data flow between the backend and their existing business systems. Junipeer is not required; any iPaaS that supports the merchant's backend can play the same role. ## Related terms ERP integration · Headless commerce · API-first commerce · Order management system