We connect your WooCommerce store to the ERP or till system that holds your stock, so items, prices, quantities and orders move between them automatically and failures are caught the day they happen.

One stock sourceOrders sent onWebhook health watched

Start a project

One stock sourceOrders sent onWebhook health watched

Start a project

01Our Approach

A WooCommerce store is software you host yourself, which means its integration has to respect the server it runs on.

02Overview

WooCommerce linked to stock and orders

01One stock source
02Orders sent on
03Webhook health watched

WooCommerce ERP integration sends orders from your store to the system that fulfils and invoices them, and brings items, prices and stock quantities back. The same service covers shops whose stock master is a till system instead of an ERP. We build on the WooCommerce REST API and webhooks, with a separate service that maps, queues and retries, so heavy work does not run inside WordPress.

It suits stores that have grown on WooCommerce and now copy orders by hand or upload stock files. Because the store runs on your own hosting, the design differs from a hosted platform. Plugins change order data, security tools can block API calls and a large import can slow the site for shoppers. We measure what your server can take and pace the integration accordingly.

Talk to us about your project

03What We Do

Capabilities, End to End

Field and meta mapping

Products, variations, attributes, tax classes, coupons and the custom fields your plugins add to orders are mapped to ERP items, price lists and sales documents.

Master system rules

The ERP or till system normally owns items, prices and stock, WooCommerce owns orders and customers, and each field moves in one agreed direction only.

API keys and roles

The service uses REST API keys with the narrowest permission that works, tied to a dedicated WordPress user, over HTTPS, with keys stored outside the site.

Order exception queue

Orders with an unmapped product, an invalid address or a tax mismatch wait in a queue outside WordPress, where staff can correct and resend them.

Paced retries

Calls are throttled to what your hosting handles, failed calls retry with growing delays and each order carries a reference so the ERP never receives it twice.

Webhook watch

WooCommerce switches a webhook off after repeated failed deliveries, so the service checks webhook status, polls for anything missed and alerts when one is disabled.

04In Production

What It Looks Like When It Ships

app.novashop.io/overview

Live

Nova Shop

Store / Overview

Search...

⌘K

WORKSPACE

Overview

Orders

Products

Customers

Discounts

Analytics

Settings

Usage

72% of plan

Inventory

1,204 SKUs across 3 warehouses

AllLowOut

Reorder

3 items below reorder point - suggested PO ready

Review

Product

SKU

Stock level

Status

Sneaker Low

SKU-1042

82 units

In stock

Canvas Tote

SKU-1043

34 units

In stock

Wool Runner

SKU-1044

12 units

Low

Trail Jacket

SKU-1045

0 units

Out

One stock source

Orders sent on

Webhook health watched

Order mappingStock updatesWebhook statusOrder queue

05What You Receive

Handed Over, Ready to Run

SCROLL

Field and meta mapping

Master data and direction rules

Integration service with source code

Order exception queue

Webhook status monitoring

Catch-up polling for missed events

Staging site test results

Runbook and handover session

06How It Runs

From Kickoff to Launch

Audit the store

Map and build

Test and pilot

Go live

Audit the store

We review hosting capacity, the plugins that alter products, orders and tax, the order storage mode and any existing imports, then list what the ERP needs from each order.

Map and build

Mapping is agreed with operations and finance, and the service is built against a staging copy of your site and a test ERP company with realistic orders.

Test and pilot

We measure how the site responds while stock updates run, tune the pace, then process live orders in parallel with your current method and compare the results.

Go live

Manual entry ends on an agreed day. Queues, webhook status and site response are watched closely afterwards, and the runbook and dashboard pass to your team.

07Technology

The Stack We Use

WooCommerce sideREST APIWebhooksOrder storage (HPOS)Action SchedulerIntegration serviceNode.jsTypeScriptPostgreSQLMessage queuesWooCommerce sideREST APIWebhooksOrder storage (HPOS)Action SchedulerIntegration serviceNode.jsTypeScriptPostgreSQLMessage queues

Back officeREST and OData APIsSOAP servicesCSV and SFTP exchangeTill system APIsOperationsWebhook checksAlertingReplay toolsLoad pacingBack officeREST and OData APIsSOAP servicesCSV and SFTP exchangeTill system APIsOperationsWebhook checksAlertingReplay toolsLoad pacing

08Who It Is For

Built for Teams Like Yours

FLAGSHIP

Orders are retyped and stock files uploaded by hand

Someone exports orders each morning and enters them into the ERP. Stock is updated from a spreadsheet and is already wrong by lunchtime. A plugin promised to connect the two and stopped working after an update, without telling anyone.

Stores outgrowing spreadsheets

Shops with a till system

Wholesale price lists

Variable and bundled products

Fulfilment from several warehouses

Stores with many plugins

09Questions

What buyers ask before they start

If yours is not here, ask us directly. The first conversation is free and useful whether or not we work together.

Book a call

A current WooCommerce version served over HTTPS, REST API keys created for a dedicated user and hosting that allows API traffic through its firewall and caching layers. On the ERP side, a licensed integration user or API module and a test company. WooCommerce itself needs no paid plan for API access. We check your hosting capacity first, because it sets how fast updates can safely run.

A maintained plugin for your ERP is worth trying first if your products and pricing are simple. Problems tend to appear with variable products, customer-specific prices, several warehouses or order data altered by other plugins. Plugins also run inside WordPress, where a heavy sync competes with shoppers for the server. A separate service avoids that and survives updates to the site more calmly.

Yes. Many shops run stock in their point of sale system and have no ERP. The integration treats that system as the master, sends its quantities and prices to WooCommerce and passes online orders back so the shop sees one stock figure. How current the website is depends on what the till offers, whether live events, an API or scheduled export files.

It should not, and we measure to be sure. The mapping and queueing run on separate infrastructure, and calls to the site are limited to a pace your hosting handles comfortably. Large jobs, such as a full price update, run in small batches outside busy periods. During the pilot we watch page response times while the sync runs and adjust before going live.

Updates are the main cause of broken WooCommerce integrations, so we plan for them. The service depends only on the documented REST API, not on internal database tables. A set of automated checks runs against your staging site, where updates should be applied first. If a plugin changes the shape of order data, the affected orders stop in the exception queue instead of reaching the ERP wrongly.

GuidesFree to use with any company