The shop stops being a separate business with its own stock figure.
CubeERP and WooCommerce
WordPress and WooCommerce connected to real stock, real pricing and real despatch - without a plugin stack held together by hope.
- E-commerce
- No per-connector licence
- 01234 672 617
WooCommerce stores tend to accumulate plugins: one for stock, one for trade pricing, one for shipping rules, each updating on its own schedule. CubeERP replaces that stack with a single source. Orders arrive as sales orders, stock and pricing are published from the one place they are maintained, and despatch pushes tracking back so the customer is notified without anybody copying a number between two admin screens.
What moves
Exactly what is synced, and which way
Being specific about this up front avoids the single most common integration disappointment - discovering after go-live that one field never travelled.
- Into CubeERP
Orders and customers
Orders arrive as sales orders with customer, addresses, payment status and chosen shipping, ready to pick.
- Out of CubeERP
Stock levels
Free stock published as it changes, so the shop sells what exists rather than what a nightly sync last believed.
- Out of CubeERP
Products, variations and prices
Product data, variations and price lists published from CubeERP, including account-specific trade pricing for logged-in customers.
- Out of CubeERP
Despatch and tracking
Order status and tracking number pushed back on despatch, triggering the customer notification automatically.
How it behaves
The detail that decides whether it is actually useful
Standard REST connection
Uses WooCommerce’s own REST API with a dedicated key, so there is no bespoke plugin to break on the next WordPress update.
Trade pricing for accounts
Logged-in trade customers see their contract pricing, driven by the same rules as phone and counter orders.
Event-driven, not scheduled
Changes push when they happen. Scheduled syncs are where oversells live, and they are avoidable.
Failures reported
Connection problems raise an alert rather than quietly stopping, which is the usual failure mode of plugin-based syncing.
Setting it up
Three steps, done during implementation
- 1
Generate a WooCommerce REST API key with the required permissions - no plugin installation is required.
- 2
Reconcile SKUs between CubeERP and the store before go-live; mismatches are the main source of trouble.
- 3
Decide what the shop masters (usually content and imagery) and what CubeERP masters (stock, price, product codes).
Questions
What people ask about this one
No. The connection uses WooCommerce’s standard REST API with an API key, which means WordPress and Woo updates do not put the integration at risk.
Yes. The integration deals with data, not presentation, so your theme, checkout and payment gateway are unaffected.
Usually, yes - and that is normally the point. Fewer plugins doing overlapping jobs is a reliability improvement in itself.
Variations map to CubeERP items, so stock and price are correct per variation rather than per parent product.
Yes. Retail through WooCommerce and account customers through the CubeERP portal, on the same stock, pricing rules and despatch process.
Related
Usually set up at the same time
- ShopifyOrders in, stock and pricing out, fulfilment and tracking back - so the website sells what you actually have.
- Adobe Commerce (Magento)Adobe Commerce and Magento Open Source connected to CubeERP stock, customer-specific pricing, order processing and fulfilment.
- CubeERP API & WebhooksA documented REST API and webhooks covering the whole system - the same interface the product itself is built on.
WooCommerce
Check the WooCommerce detail before you commit
Send us the specifics - your chart of accounts, your tax treatment, your product structure - and we will tell you exactly how it maps rather than promising it will be fine.