How to connect Quantic POS to a WooCommerce store

No. Quantic's Ecommerce product is Quantic's own online ordering website, built to work with its POS (getquantic.com/ecommerce). It replaces your website's store rather than connecting to it. When the shop asked in October 2026, Quantic confirmed it doesn't integrate with an outside e-commerce site, and its online ordering links out to its own ordering page.

Running both would mean two online stores selling the same stock. If you already have a WooCommerce store you want to keep, the stock has to come out of Quantic on a schedule, which is what this build does.

1. At 6am, the job reads the full Quantic inventory report, about 6,600 to 6,750 rows.
2. It checks for online sales not yet entered at the register. Any item with an unentered online sale is held, and that item's count waits for the next run.
3. It matches every row to the website by barcode and works out what changed.
4. It takes a dated snapshot of the website's stock, so any run can be put back.
5. It updates stock and status on the website and clears the cache, so shoppers see the new counts.
6. It retries on its own if a connection is interrupted, and each step is safe to run twice.
7. It reports what changed after every run: how many matched, how many changed, how many exceptions and how many items were held.

A full run takes about 14 minutes.

One way, Quantic to the website. Nothing on the website writes into Quantic, so an online order doesn't lower the Quantic count on its own. Each evening, the day's online sales are entered into Quantic from a report the website produces, listing each item's barcode, name and quantity sold online. The report leaves out unpaid orders, nets out refunds, and lists a put-back when a reported order is cancelled.

Quantic stays the source of truth in both directions. Orders go into Quantic, and counts come back out to the website. We don't let the website lower its own stock, because the next morning's read would overwrite it.

Online sales have to be entered into Quantic before the inventory is read. If the read runs while an online sale is missing from the register, the website's count goes back up and the item can sell twice until the next run. The hold in step 2 enforces that rule every morning, so it doesn't depend on anyone remembering.

There are three layers, and each one is proven a different way.

The sync can't fix a register that's wrong on its own. If the register shows a count below zero, the sync shows it as zero on the website.

• Barcodes as SKUs. The sync matches on barcode, so each website product's SKU has to be its Quantic barcode. Where an item has no barcode yet, printing your own UPC labels fixes that at the source, and label printing has its own section on the Lightspeed page.
• Items that exist in Quantic. A well-formed barcode can still be missing from Quantic entirely, and an item sold online before it was added to Quantic has nothing to match.
• Dropship items kept apart. Products a supplier ships direct use the supplier's item number, so they're left out of the register report and never go into Quantic.
• A bigger register than website. The shop's register holds about four times as many items as its website. About 1,880 matched out of about 6,600 rows is the expected shape, so the match rate isn't a health measure.
• Weights before an item goes live. New Quantic items come onto the website with a shipping weight, and anything over five pounds gets the heavy shipping class.
• No blank re-imports. A product spreadsheet re-imported with a blank SKU column erases the SKUs, and the sync loses every match. Keep a dated snapshot before any import.

Read the daily line and check that the counts moved. A job can report success over an empty result if one step fails inside it, so a green status alone isn't proof. We read the dated log, and a failed read posts its own message so it can't fail quietly.

For the bigger picture on registers and websites, see POS website integration. Once the stock is right, ecommerce SEO covers getting the products found.