Summary
Yes, a B2B online store can connect to NetSuite, SAP and Microsoft Dynamics. All three expose APIs that a store can use to send orders in and pull stock, prices and customer data out. The work is not in the connection itself, it is in deciding which system owns which data, mapping fields cleanly and handling the cases that break syncs. This guide covers what to sync, the three ways to connect, what usually breaks, a worked example, and a realistic timeline.
Introduction
Can your eCommerce store connect to NetSuite, SAP or Microsoft Dynamics? Yes. If your ERP has an API, a store can talk to it, and most business ERPs do. For a B2B company the real question is what should flow in each direction, how often, and what happens when the data does not match. Get those answers right and your customers see live stock, their own prices and accurate order status, while your team stops retyping orders. Get them wrong and you oversell, show the wrong prices or create duplicate orders.
Table of Contents
- Can an online store really connect to NetSuite, SAP or Microsoft Dynamics?
- What data should sync between an ERP and a B2B store?
- Which system should own which data?
- How do you connect the two: connector, middleware or custom code?
- What usually breaks in an ERP integration, and how do you prevent it?
- What does a real integration look like? A worked example
- How long does an ERP integration take?
- How should you test an ERP integration before going live?
- What should you prepare before you start?
- How do you keep the integration healthy after launch?
- Frequently asked questions
Can an online store really connect to NetSuite, SAP or Microsoft Dynamics?
Yes. These systems differ in age and design, but each offers a supported way to exchange data. The table shows the usual routes.
ERP | Typical connection method | Worth knowing |
|---|---|---|
NetSuite | REST and SOAP web services, custom RESTlets built with SuiteScript | Has API usage limits, so plan batch sizes and retries |
SAP Business One | Service Layer (REST style API) | Common in small and mid size distributors |
SAP S/4HANA and ECC | OData APIs, IDocs, BAPIs | Often needs the SAP team involved for access and mapping |
Dynamics 365 Business Central | Standard API and OData web services | Cloud based, usually the simplest of the three |
Dynamics 365 Finance and Operations | OData and data entities | Larger scope, stricter change control |
On the store side, WooCommerce offers a REST API and webhooks that fire when an order is placed or changed, which makes it a good match for these systems. If you are weighing platforms first, our overview of B2B eCommerce for manufacturers, distributors and wholesalers explains where each fits.
What data should sync between an ERP and a B2B store?
Start with a simple map. Every data type has a direction, a frequency and an owner.
Data | Direction | How often | Notes |
|---|---|---|---|
Products and catalog | ERP to store | Scheduled, such as hourly or nightly | Store keeps images, descriptions and SEO copy |
Customer specific prices | ERP to store | Scheduled or on change | Price lists, contract prices and tiers |
Inventory | ERP to store | Near real time or every few minutes | Use available to promise, not raw on hand |
Customers and credit terms | Both ways | On change | Account numbers, terms, credit holds |
Orders | Store to ERP | Immediately | Include PO number, ship to and notes |
Order status and tracking | ERP to store | On change | Partial shipments need special handling |
Invoices and payments | ERP to store | On change | Lets buyers see open balances |
You do not need all seven on day one. Many teams begin with orders into the ERP and stock out of it, then add pricing and accounts. Our page on inventory and catalog synchronization goes deeper on the catalog and stock side.
Which system should own which data?
The simplest rule that works: the ERP owns anything financial or physical, and the store owns anything the buyer sees and touches. That means stock levels, prices, credit limits, tax rules and order numbers live in the ERP. Product descriptions, images, SEO titles, carts and wishlists live in the store.
Problems start when both systems can edit the same field. If a salesperson changes a price in the ERP and a store admin changes it in WooCommerce, one change silently wins. Decide the owner for every field, then make the other side read only. In practice this means locking price and stock fields in the store admin and writing the rule down for the team.
How do you connect the two: connector, middleware or custom code?
There are three common ways to build the link, plus a fourth that is best avoided for anything live.
Approach | Best for | Strengths | Watch out for |
|---|---|---|---|
Ready made connector or iPaaS | Standard flows, fast start | Quick to set up, built in monitoring | Monthly fees, limits on custom pricing logic |
Custom middleware | Complex pricing, many rules | Full control, queues and retries | Needs a developer to build and maintain |
Direct plugin or point to point | One simple flow | Few moving parts | Hard to extend, tied to both systems |
CSV or flat file import | One time loads, small catalogs | Easy to start | Slow, error prone, not real time |
Most mid size B2B stores end up with a connector for the standard flows and a small custom layer for pricing and account rules. Our WooCommerce ERP integration service follows that pattern.
What usually breaks in an ERP integration, and how do you prevent it?
Most failures come from data that looks fine in one system and wrong in the other. These are the ones that show up most often.
What breaks | What the buyer sees | How to prevent it |
|---|---|---|
SKU or item code mismatch | Product missing or the wrong item ordered | Use one unique key, clean SKUs before the first sync |
Unit of measure differences | Case price shown as each price | Map units explicitly, test with real items |
Overselling from stale stock | Order accepted, then cancelled | Sync stock often and hold a safety buffer on fast movers |
Duplicate orders after a timeout | Two orders for one purchase | Send a unique order key and check before creating |
Customer matching errors | Wrong prices or a new account created | Match on ERP account number, not email |
API limits and slow responses | Delays or failed syncs | Batch requests, queue and retry with backoff |
Partial shipments and backorders | Status stuck on processing | Map line level status, not only order status |
If an integration is already live and orders are not arriving or emails are failing, our guides to order emails not sending and plugin conflicts cover the common causes on the store side.
What does a real integration look like? A worked example
Here is a typical scenario, not a named client. A wholesale distributor sells about 4,000 products on WooCommerce and runs NetSuite. It has roughly 300 customers with their own price lists, takes a mix of web orders and phone orders, and ships from one warehouse. Orders are retyped into the ERP, stock on the site is updated once a day and customers phone in to ask about prices.
Phase | What gets connected | What changes for the business |
|---|---|---|
1. Clean up | Fix SKUs and units, agree field ownership | One clear catalog, no duplicate items |
2. Orders and stock | Web orders flow into the ERP, stock flows back every few minutes | No retyping, far fewer oversold items |
3. Accounts and pricing | Customer accounts linked by ERP number, price lists shown after login | Buyers see their own prices without calling |
4. Status and invoices | Shipment tracking and open invoices appear in the account area | Fewer where is my order calls |
Teams that stage the work this way get value early and keep each release small enough to test properly. It also gives the finance and warehouse teams time to confirm that the numbers match before the next phase.
How long does an ERP integration take?
It depends on scope, data quality and how quickly the ERP team can grant access. The ranges below are typical starting points, not promises.
Scope | Typical range | What drives it |
|---|---|---|
Orders into the ERP plus stock back | About 3 to 6 weeks | Clean SKUs, sandbox access |
Add catalog sync and customer accounts | About 6 to 10 weeks | Account matching, credit rules |
Add customer specific pricing | About 8 to 14 weeks | Number and complexity of price lists |
Full lifecycle with invoices, returns and approvals | About 3 to 5 months | Approval flows, multiple warehouses |
The biggest delays rarely come from coding. They come from waiting for ERP credentials, unclean item data and late decisions about who owns which field. Preparing those three things before the project starts is the cheapest way to save time.
How should you test an ERP integration before going live?
Test with real data in a sandbox, not with a handful of sample items.
- Place orders with every payment method and shipping option, and confirm each appears in the ERP with the right totals and tax.
- Change stock in the ERP and watch the store update within the agreed time.
- Place the same order twice on purpose to check that duplicates are blocked.
- Test a customer with special prices, a credit hold and a different ship to address.
- Simulate the ERP being offline and confirm orders queue and retry instead of disappearing.
- Ship an order in two parts and confirm the status updates correctly.
Run the final pass on a staging copy of the store connected to the ERP sandbox, then repeat a short check on live at a quiet hour.
What should you prepare before you start?
A short checklist saves weeks.
- Sandbox or test company in the ERP, with API credentials and a named ERP contact.
- An export of products, prices, customers and open orders for mapping.
- A written list of who owns each field.
- Your pricing rules in plain language: tiers, contract prices, minimum orders and net terms.
- A decision on how fast stock must update and what counts as available.
- A list of reports and emails your team relies on, so nothing gets lost in the switch.
If you want a sense of budget before you decide, our guide to WooCommerce development costs shows how scope drives price, and you can hire a WooCommerce developer from Virtina for the build.
How do you keep the integration healthy after launch?
An integration is a living part of your business. Set up alerts for failed syncs, a daily check that order counts match between the store and the ERP, and a log someone actually reads. Re-test after every WooCommerce, WordPress or ERP update, because a changed field or a new API limit can quietly stop a flow. A monthly website maintenance plan covers updates and monitoring so small issues are caught before customers notice.
Frequently asked questions
Does a WooCommerce store need middleware to talk to an ERP?
Not always. A simple flow can use a direct connector, but stores with customer specific pricing, approvals or several systems usually benefit from a middleware layer with queues and retries.
Should stock sync in real time or on a schedule?
Fast moving items suit near real time updates, every few minutes. Slow movers can sync hourly or nightly. Use available to promise and a small safety buffer to avoid overselling.
Can each customer see their own prices?
Yes. Prices live in the ERP, are linked to the customer account number and appear in the store after the buyer logs in.
What happens if the ERP is down?
A well built integration queues orders and retries when the ERP returns, so no order is lost. Buyers still get an order confirmation from the store.
Does Microsoft Dynamics Business Central need a different approach from NetSuite?
The method is similar, but the APIs, limits and field names differ, so the mapping and error handling are built for each system.
Is a sandbox really necessary?
Yes. Testing against live ERP data risks creating real orders and stock movements, so a sandbox is the safe way to test.
Can the integration handle several warehouses?
Yes, but it needs rules for which warehouse stock is shown and how orders are allocated, so plan this before the build.
Conclusion
Connecting NetSuite, SAP or Microsoft Dynamics to a B2B online store is very doable, and the effort pays off in live stock, correct prices and fewer retyped orders. Decide who owns each field, start with orders and stock, test with real data in a sandbox, and keep the link monitored after launch. To explore your own setup, see our WooCommerce ERP integration service or send us a note for a short review.
Virtina is an eCommerce agency that helps wholesalers and distributors build and connect B2B online stores to their ERP.
