AFAS software
AFAS offers a complete solution for automating business processes. It reduces manual tasks, increases efficiency, and provides real-time insights for strategic growth.
An online store integration connects your online store to your ERP, PIM, inventory, and other systems. This ensures that orders, prices, and inventory are automatically synchronized.
Orders go directly into your ERP
Inventory and prices from a single source
Integrations that keep working even if a system goes down
An online store typically relies on five systems: an ERP for orders and finances, a PIM for product information, a WMS or inventory module, an accounting package, and a shipping solution. The online store is the storefront, not the back office. That distinction determines where data belongs. A price you adjust in the online store but not in the ERP will, within a week, become a discrepancy that no one can explain. Every piece of data should have a single owner—a single source of truth. The integration ensures that all other systems adopt that value rather than maintaining their own version of it.
In B2B, there’s an additional layer to consider. Tiered pricing, customer-specific agreements, credit limits, and order history are almost always stored in the ERP system and not in the online store platform. That’s why a B2B online store
The ERP integration is the most complex and usually the first to be implemented. Orders are sent from the online store to the ERP system, and product details, prices, inventory levels, customer data, and order statuses are returned. In B2B, credit limits and customer-specific pricing agreements are added to this. The pitfall lies in the direction of data flow: an order should travel in one direction and should never be overwritten by the online store again. As soon as two systems are allowed to make the same order update, conflicts arise that aren’t noticed until months later during the financial close.
A PIM manages product information: descriptions, specifications, images, variants, and translations. The integration is almost always one-way: the PIM provides the data, and the web store displays it. This has a consequence that is often underestimated. If the synchronization overwrites the product data every time, you can no longer make any changes in the web store itself, because the next synchronization will revert them. So agree in advance which fields belong in the PIM and which in the CMS.
Inventory is the data stream with the shortest shelf life. An inventory level that’s just an hour old can already lead to sales you can’t fulfill during a busy week. With a single warehouse and low volume, a periodic update from the ERP is sufficient. As soon as you have multiple locations, reservations, or drop shipments, a WMS comes into play, and the question becomes: do you display the physical inventory, or the available inventory after deducting open orders? That second number is the only one that means anything to a buyer.
Orders must ultimately be recorded in the accounting system: invoice, VAT rate, payment status, and any credit memos. For an online store using an ERP system, this usually happens through the ERP. Without an ERP, you connect directly to the accounting software. The key point is the reconciliation between payment and invoice: the payment provider knows that funds have been received, the accounting software knows that an invoice is outstanding, and someone has to link the two.
The shipping integration creates shipping labels, returns tracking codes, and updates the order status. For the buyer, this is the most visible integration of all, because it’s the only one they actually notice. Practical note: calculating shipping costs on the front end and creating shipping labels on the back end are two separate integrations. They’re often handled by the same provider, but they can fail independently of one another and therefore require separate attention in your error handling.
If you want to offer your business customers more than just an order button, connect your online store to a portal. There, contracts, quotes, invoices, service requests, and order history are all in one place. This is where e-commerce and portal functionality converge: the ordering environment becomes part of the portal rather than a standalone web store.
Without integrations, a web store shifts work around instead of eliminating it. Orders are retyped, inventory falls behind, prices vary, and the service desk becomes the manual link between two systems. The symptoms are familiar. You sell products that are no longer in stock. An order ends up in the ERP system twice because someone wasn’t sure if the first one went through. Customer service receives the same question every day about the status of a delivery. These aren’t online store problems, they’re integration problems, and they get worse as volume grows.
Orders
From the online store to the ERP, in real time via a webhook. Delays never help here and make it harder to answer any status inquiries.
Inventory
From ERP or WMS to the online store, in real time up to every few minutes. This is where overselling occurs as soon as the delay builds up.
Prices
From ERP to online store, preferably in real time upon login. An incorrect tiered price in B2B will later result in a credit memo.
Product Data
From PIM to online store, usually in batches overnight. Only send changes; otherwise, synchronization will take longer than overnight.
Order Status
Update the online store as soon as the status changes. Track and trace is part of this and eliminates most inquiries to your service desk.
Invoices
From ERP to portal, daily is sufficient. Specify who is authorized to view the invoice, as it’s rarely everyone within a single organization.
After a merger, Nou wanted a single digital platform: website, customer portal, and online store all within one architecture, integrated with AFAS. Not a separate online store platform with a connector in between, but orders that flow directly into the accounting system.
From that first cup of coffee to the continued expansion of the digital landscape. Four clear phases that describe our collaboration and guide our growth.
At Cube, we see ourselves not just as a vendor, but as a true software development partner. We work with you to make strategic decisions, provide technological advice, and deliver solutions that make a real impact. Our approach is always tailored to your specific needs and goals. We actively contribute ideas and ensure that the technology we deliver not only works but also genuinely contributes to the growth and efficiency of your organization. From the initial ideas to the final implementation and optimization, we ensure that the solution is a perfect fit for your organization.
No obligations, just insight into which systems you can integrate and which approach suits your organization. Jarno is happy to brainstorm with you about your systems, processes, and the best way to connect them.
With boldness, a down-to-earth approach, and a focus on quality.
Amber Projectmanager
Bart Developer
Bernard Developer
Bob Test Engineer | Security & Privacy
Demi Officemanager
Dennis Full Stack Developer
Guus Full Stack Developer
Jarno Business Director
Jarno Back-end Developer
Jasper Developer
Jenne Marketing Manager
Jeroen Back-end Developer
Job CEO | Executive
Joost Tech Lead | Team Pentagon
Jordy Software Architect
Justin Tech Lead | Team Hexagon
Kevin Developer
Laura Digital Designer
Maartje Content Marketeer
Mans Operations Manager
Marcus Projectmanager
Marleen Projectmanager | Team Lead Octagon
Mart Front-end Developer
Melanie Projectmanager | Team Lead Hexagon
Mick Tech Lead | Team Nexus
Nicky Projectmanager | Team Lead Nexus
Onno Business Controller
Remi Software Architect
Rogier Business Consultant
Rosan Manager People & Organization
Roy Full Stack Developer
Ruben Full Stack Developer
Ruben Digital Designer
Sander Developer
Stijn Front-end Developer
Tamara Business Consultant
Thomas Back-end Developer
Ties Tech Lead | Team Pentagon
Tom Tech Lead | Team Octagon
Wesley Projectmanager
The cost is determined by four factors: the number of data streams, the direction of each stream, the quality of the API on both sides, and the number of exceptions in your product range. The latter is the most underestimated factor. A catalog with clear product codes and a single VAT rate integrates faster than a product range with composite items, variants, and legacy codes that no one dares to clean up anymore. That’s why there’s no fixed price list. We first map out the data streams and APIs on both sides and then provide a substantiated cost range. You should also factor in ongoing management costs: APIs change, and a connection that no one maintains will break on its own.
We can’t determine that until the data flows have been mapped out. A one-way product feed is different from handling orders, inventory, and prices simultaneously. The quality of the API on the other end is the most critical factor in this regard.
Yes. As long as there’s an API, database access, or export option, an integration can be built. With a custom ERP, the work often lies on the ERP side: the integration interface must be in place first before the online store can be connected to it.
Messages are placed in a queue and resubmitted as soon as the system is back online. A unique key for each order prevents a repeated attempt from resulting in a duplicate order. Any subsequent failures trigger a notification.
That depends on the data stream. You want orders and inventory to be synchronized in real time, because delays can lead to overselling or lost sales. Product data can be synchronized in batches overnight, as long as you only send changes.