WooCommerce POS integration: stock, orders and payments

Connect a WooCommerce POS around declared stock, order and payment owners, then verify online and counter sales, returns and failures in the actual setup.

Yes, WooCommerce POS connections can share product and stock data between your online store and counter. Choose the connector around the records it actually transfers. Square’s WooCommerce extension syncs products and inventory, while counter sales orders remain in Square.

A payment terminal takes the customer’s payment. The point-of-sale connection must separately tell the online store what sold and how much stock remains.

Define the POS and record owners

Your point of sale (POS) is where staff complete a counter purchase, from selecting the product to recording payment and issuing a receipt. POS software can also hold stock and customer records. A card terminal’s payment approval alone establishes none of those records in WooCommerce.

Before importing products, assign a master system for each record. The master is where staff make the change that other systems must follow. One system needn’t own every field.

Record ownership worksheet

RecordDecide before connectingAcceptance check
Product identifiersThe master stock keeping unit (SKU) for each sellable variantA navy medium shirt maps to one variant in each system
LocationsThe location supplying online stockA sale reduces the intended shop’s quantity
PricesWhere regular and sale prices are editedBoth channels use the intended price and tax basis
StockWhere receipts and stocktake corrections are enteredThe next sync preserves the correction
CustomersWhere staff update customer detailsStaff can find the correct customer without merging unrelated people
OrdersWhich system records each channel’s saleStaff can locate the original receipt for a return
PaymentsThe processor and reference used for reconciliationThe order can be matched to its payment and refund

A shared email address doesn’t prove that customer records merge. Record the connector’s actual customer behaviour separately from its stock behaviour. Broader omnichannel commerce also covers how staff use those records across the customer journey.

Choose the supported method

Use a documented connector for your exact POS edition when its transfer rules match your workflow. An intermediary adds another place where mappings and failed jobs need an owner. A manual export can support a controlled batch update, but it leaves stock stale between imports.

Square and WooCommerce

The WooCommerce Square extension has separate payment and inventory functions. Enabling Square at checkout doesn’t by itself configure product synchronisation.

Its sync settings choose the product-data source and Square business location. Match existing products before importing an entire catalogue. Keep each sellable variant’s SKU unique.

WooCommerce’s Square FAQ states that inventory is pulled from Square hourly when inventory sync is enabled. That also happens when WooCommerce owns product data. Square counter orders aren’t copied into WooCommerce, so staff still need access to the original Square sale for counter enquiries.

Choose this method when shared products and stock meet your need and separate channel sales records are acceptable. If you need every counter receipt in WooCommerce, the extension’s documented behaviour doesn’t meet that requirement.

Lightspeed Retail and WooCommerce

Lightspeed POS for WooCommerce supports Lightspeed Retail R-Series and X-Series. Its overview excludes Lightspeed eCom and Restaurant. Identify the series in the POS dashboard before following setup instructions.

The overview lists minimum requirements of WordPress 6.0, WooCommerce 8.0 and PHP 7.4, plus an active supported Retail account. Record your installed versions and connector entitlement before buying hardware or starting an import.

The R-Series setup guide uses a selected primary inventory store. It syncs that location’s stock, not a combined native WooCommerce multi-location balance. The authorising Lightspeed employee needs inventory privileges.

For R-Series, enable WooCommerce stock management and review selective sync settings before importing. Those settings affect changes sent back after checkout, refund or cancellation. Product edits and counter payments remain separate configuration questions.

Verify the same product across channels

Run a controlled transaction sequence with one mapped variant before opening the connection to the full catalogue. The following fictional example uses a navy medium shirt, SKU SHIRT-NAVY-M, with ten sellable units at the selected location.

Fictional stock and payment check

EventExpected sellable stockWhat to compare
Starting count10Same variant and location in both views
One paid online sale9Online order, payment reference and one stock reduction
One counter sale8POS receipt and the updated online quantity after sync
Stocktake finds one damaged unit7Correction entered in the stock master and retained after sync
Online customer returns one resellable shirt8Original order refund and one restock movement

For the return step, use a supported route for the original payment. WooCommerce documents refunds through Square for WooCommerce orders. The payment refund appears in Square. That doesn’t establish a universal counter-return workflow for every online or POS sale.

Keep the WooCommerce order number beside its Square Transaction ID when Square processes the online payment. Record the counter receipt separately. Compare gross amount and refund amount on the same currency and tax basis, including goods and services tax (GST) where applicable.

Incorrect mapping: the parent shirt and its medium variant both use one SKU, so staff can’t distinguish their stock movements. Correct mapping: each sellable size and colour has its own identifier, linked to the corresponding POS item.

Check one discounted sale too. A tax-inclusive counter price and tax-exclusive online price can look different even when their final totals agree. Compare the tax settings before changing prices to make two screens look alike.

Handle interruption and recovery

Treat delayed stock updates and offline payments as separate failure paths. WooCommerce’s Square FAQ says automatic sync relies on WordPress’s scheduled jobs and site traffic. A quiet site can therefore delay a scheduled update. Configure a system scheduler when that traffic dependency is unsuitable.

Square’s Australian offline-payment instructions limit offline acceptance by device and payment type. Pending payments upload when the device reconnects. Staff must follow the device’s upload deadline and keep pending payments intact. An offline payment can later be declined.

In a controlled rehearsal, interrupt the connection after a sale has been recorded. Note the receipt and stock before restoring connectivity. Once queued work completes, confirm that the receipt exists once and stock falls once. A delayed screen is a reason to inspect transaction history before entering another sale.

Give the counter manager responsibility for pending payments and physical stock. Assign the online-store administrator the sync queue and mapping errors. Finance reconciles payment references. Limit connector access to the staff who maintain it.

When records conflict, the stock owner checks the physical count and outstanding sales before changing the master quantity. Keep uncertain units unavailable for online sale until that check finishes. Customer-facing staff then use the corrected available quantity when promising collection or delivery.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup