Skip to main content
GullySystem
Commerce · WooCommerce integration

Connect your WooCommerce shop to stock, billing and dispatch without retyping orders.

WooCommerce runs inside your own WordPress site, so the shop and the back office rarely share data by default, and staff end up copying orders between the two. GullySystem joins the shop to your business software for products, stock, orders, coupons and customers. Scope and direction are agreed for each project, and results depend on your hosting, plugins and store set-up.

At a glance

Connecting WooCommerce to the rest of your business.

A WooCommerce shop grows by plugins. That is normal. One handles payments, another shipping, a third subscriptions. Each stores a slice of the order, and none of them knows your warehouse count or what the accounts team has already booked.

We connect the shop to your own system. Since every store is configured differently, we begin by reading the plugins, the order statuses and the tax setup of yours before promising any flow.

What moves

What flows between WooCommerce and your system.

Each flow is agreed one at a time: which record, in which direction, and what happens when it fails.

New orders into the sales desk

When an order moves to processing, it is created in your system with its items, shipping lines and fees, so nobody raising the invoice opens the WordPress admin. Order notes and status changes are carried across. Staff see the same story.

Stock quantities written back

Goods received, or sold in the shop, at the counter or on a trade order, update the stock quantity on each product or variation. Out of stock follows real counts.

Product and price updates

Products, categories, attributes and price lists maintained in your system can publish to the shop, so catalogue changes are made once and reach every variation, bundle and category page. Wholesale or customer group prices are applied by rules you set, and variable products keep their own price per variation.

Coupons tied to campaigns

Coupons for a promotion can be generated from your system with usage limits, minimum spend rules and expiry dates. A campaign planned in one place is then applied the same way in the shop. Redemptions come back against the order for margin reporting. Discounts stop hiding.

Customers, refunds and invoices

Guest and registered buyers share one record. A refund in the shop creates the credit note and returns stock only where the goods are actually restocked on the shelf.

How it is built

From scoping to hand-over.

1. Scope the objects and direction

We review which plugins shape your orders and products. Then we pick objects and owners. Scope stays small.

2. Connect and test on a staging copy

A copy of your site works for testing. Test orders cover coupons, variable products, partial refunds and cancelled payments. Live shoppers see none of it.

3. Reconcile stock, coupons and orders

Plugin fields are mapped to your records. Webhook deliveries are checked for repeats so one order is never booked twice, which matters when the shop host is slow and the sender tries again. Calls that fail are queued, retried and logged.

4. Compare order counts, then hand over

Order counts and stock from the shop are compared with your system on a schedule, and any gap is listed by order number. We finish with a handover covering plugin updates and who to contact. Updates get a test first.

Common questions

Questions about connecting WooCommerce.

Is the sync one way or two way?

Both are possible. Orders typically travel from the shop to your system, and stock and prices travel back to the shop. Each record has a single owner that we fix during scoping, so edits in two places cannot collide.

What does my WooCommerce site need?

The shop must be reachable securely, and we need keys or a user with suitable rights. Hosting, plugins and WordPress configuration all affect the design, so we check them first and tell you if the current set-up needs a change before we begin.

Can I bring in orders placed before the connection?

Often yes, as a separate import checked against your shop reports. Some plugin data may not carry over cleanly, such as custom checkout fields or subscription schedules, and we tell you which before the load.

What happens when WooCommerce or a plugin changes?

Updates to the shop software or its plugins can alter data. We test connections against new versions on staging. Fixes come under a support arrangement agreed with you, one that names who approves an update before it reaches the live shop.

WooCommerce remains the trademark of its owner. The connections to it are our own work, and we are not affiliated with the company.

Start with your requirements

Tell us how you use WooCommerce.

Share your requirements and an engineer will read them before getting in touch.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements