Connecting Your Online Store to Your ERP: What Changes and How
Many online stores start with a simple routine: orders arrive by email, someone types them into the ERP, stock is updated from a spreadsheet, and prices are changed by hand on the website. It works, until it does not. Orders grow, a product sells out online while the warehouse is empty, a price change reaches the store a week late, and the team spends more time copying data than serving customers.
Connecting your online store to your ERP removes that manual layer. At Cactus we have connected many of the more than 400 online stores we have built to the ERP systems their owners already use. Here is what changes, and how a project like this typically runs.
What an ERP integration changes
An integration makes the ERP the single source of truth for the data it already owns, and makes the store the source for what happens online. In practice, that usually covers:
- Stock: available quantities flow from the ERP to the store automatically, so customers see what you can actually ship.
- Products: codes, basic descriptions, attributes, weights and barcodes come from the ERP, while the store keeps the marketing content, images and SEO text.
- Prices: retail prices, discounts and, for B2B, customer-specific price lists follow the ERP.
- Orders: online orders are created in the ERP with the right customer, products, shipping and payment details, ready for picking and invoicing.
- Customers: new customers are created or matched in the ERP, avoiding duplicates.
- Order status and documents: shipping status, tracking numbers and invoices can flow back to the store and to the customer.
The result is fewer errors, faster dispatch, no overselling and a team that works on growth instead of data entry.
Signs it is time to integrate
- Someone spends hours every day keying in orders.
- You regularly sell products that are out of stock.
- Prices or availability on the site are often out of date.
- You want to add a B2B portal, marketplaces or new countries, and the manual process cannot scale.
- Your accountant regularly finds mismatches between the store and the books.
How a typical integration project runs
1. Discovery and data mapping
We start by mapping how data should flow: which system owns each piece of information, how often it changes and what happens in edge cases. Product codes, variants, units, VAT categories, shipping methods, payment methods and customer types all need a clear match on both sides. This is the most important phase. A good map prevents most later problems.
2. Choosing the connection method
How the systems talk depends on what the ERP offers. Common options are:
- A documented web API provided by the ERP vendor
- A middleware or integration layer built for the project
- Scheduled file exchange (CSV or XML) when no API exists
- Webhooks from the store for events such as new orders
We also decide timing: stock might sync every few minutes, prices nightly, orders in near real time.
3. Cleaning up the data
Integrations expose messy data. Duplicate product codes, missing weights, inconsistent attributes or customers entered three different ways must be cleaned before launch. Plan time for this. It always takes longer than expected, and it is worth it.
4. Building and testing
The integration is built against a test copy of the ERP whenever possible. We test normal flows and the awkward ones: cancellations, partial shipments, returns, coupons, free products, orders from new countries, failed payments. Each case should have a defined, predictable outcome.
5. Error handling and monitoring
Every integration will occasionally meet a problem: the ERP is down for maintenance, a product code is missing, a network call times out. A good integration retries automatically, logs what happened, and alerts a person when it cannot fix the problem itself. Ask about this explicitly before the project starts.
6. Go-live and handover
Go-live is planned for a quieter period, with a clear rollback option. The first days are monitored closely. Your team receives simple documentation: what syncs, how often, where to look when something seems wrong and who to call.
Questions to ask before you start
- Does our ERP have an API, and is it included in our licence or an add-on?
- Which system is the master for products, prices, stock and customers?
- How do we handle products that exist online but not in the ERP, such as bundles or gift cards?
- What happens to orders if the connection fails for an hour?
- Who maintains the integration when the ERP or the store is updated?
Typical pitfalls
- Syncing everything in both directions. Two masters for the same data lead to conflicts. Decide ownership per field.
- Ignoring performance. Pulling the entire catalog every few minutes can slow both systems. Sync changes, not everything.
- Skipping the edge cases. Returns, partial deliveries and VAT for other EU countries need clear rules.
- No owner after launch. Integrations need light ongoing care as both systems evolve.
Start with a conversation
An ERP integration is one of the investments that pays back most clearly in time saved and errors avoided, as long as it is planned well. If you are thinking about connecting your store to your ERP, or your current integration is causing more trouble than it saves, book a free 15-minute call with Cactus. We will tell you what is realistic for your systems and how we would approach it.