At 9:05 a cafe sells its last banana loaf, number 12 of 12, at the counter. At 9:07 a web customer orders one. The website still shows a loaf in stock because the count lives only in Clover.
Clover inventory management will not update your website by itself, so a shop that sells in-store and on WooCommerce needs a connector. Often, overselling between Clover and WooCommerce comes from a messy catalog, not from the sync. You can fix the catalog before you connect anything.
Key Takeaways
- Clover is your in-store system of record. It does not push stock to a website without an app.
- Low-stock alerts and sync are different things. An alert tells you; it does not update your website.
- Clean SKUs, one source of truth and a short test script matter more than any setting.
- CloverWoo syncs stock about every 5 minutes, and products and customers about hourly. It is never instant.
Table of Contents
- How Clover Inventory Management Works
- Stock Counts, Alerts and Receiving
- Avoid These Common Clover Inventory Mistakes
- Selling Online Too? Add WooCommerce Sync
- Frequently Asked Questions
How Clover Inventory Management Works
Clover tracks stock per item. Each item has a name, a price, a category and an optional stock count. Clover's help center covers item setup step by step.
Items and categories
Items sit inside categories. Keep one clear category per item. If you want to use subcategories, test one item first: put it under a subcategory in Clover and wait for the next hourly product sync.
Then open WooCommerce > Products > Categories. If the item lands under a child category, subcategories work for you. If it lands flat or in no category, keep to one category per item.
Variants and modifiers
A variant is a size or colour of one item. A modifier is an add-on or choice. Clover counts stock on the item, and a modifier has no count of its own.
That causes a real mapping failure. Say you have one "Latte" item with a size modifier group: Small, Medium, Large. Clover holds one count for Latte. If that becomes a WooCommerce variable product, each size gets its own count, and none of them match Clover's single number.
The safer setup is one Clover item per size (or Clover's item variants), each with its own SKU. Each then maps to one variation and keeps its own honest count.
Where Clover stops
Clover is the in-store system of record. It does not update a website on its own. To keep an outside website in step, you need an app that talks to Clover. That is why a connector is part of any online plan.
Stock Counts, Alerts and Receiving
In the web dashboard, go to Inventory > Items, select the item and turn on stock tracking. Menus can change, so if a name differs, search Clover's help center for "inventory items". Then set a starting count. Count the shelf first. Enter that number second. The system then starts from a true figure instead of a guess.
Low-stock alerts
Set a low-stock threshold per item. You then hear about a shortage before you run out. But an alert only tells you. It does not change the count on your website. So an alert and a sync are not the same thing.
Receiving stock
When a delivery arrives, add the delivered quantity to the count. Say 12 arrive and 3 are on hand. Enter +12 rather than retyping 15. A sale rung up while you count is then not wiped out. For bulk changes, use the Clover inventory spreadsheet guide rather than editing items one by one.
Count, availability or sold out?
These are three separate ideas:
- Stock count: a real number that drops with each sale.
- Item availability: an on or off switch.
- Menu sold out: a restaurant telling guests an item is gone.
A cafe selling prepared food may only need the on/off switch. A shop selling boxed goods needs real counts. Rule of thumb: if you would reorder it from a supplier, count it. If you make it to order, switch it.
Avoid These Common Clover Inventory Mistakes
Four common mistakes cause a lot of the trouble. All four are cheap to fix before you connect a website.
- Duplicate items and messy SKUs. Use one format: product, colour, size, like TEE-BLK-M. Give each sellable size its own SKU. Never reuse a SKU, even for a retired item. Here is what goes wrong without that rule. "Black Tee" shows 6 and "Tee – Black" shows 4, both for medium. The real count is 10, but each record looks nearly empty and a sale hits the wrong one. After cleanup, one TEE-BLK-M record shows 10.
- Skipping tracking on fast sellers. Your best sellers run out first. Also avoid quick corrections with no note of why. Keep one person in charge of receiving and counting.
- Mixing up variants and modifiers. The mess shows later, when your catalog meets a web store's variable products, as the Latte example above shows. The modifier groups to WooCommerce variations post covers the mapping.
- Going live without a test. On your own account, test one sale, one return and one manual change. Then check the numbers.
Pro Tip: Run the launch checklist in order before any sync. Normalize SKUs, then set up variable products, then decide how modifiers map. Next, check tax classes and categories. Last, pick your source of truth.
Selling Online Too? Add WooCommerce Sync
Clover alone does not update a WooCommerce shop. You need a connector. With CloverWoo, Clover stock reaches WooCommerce about every 5 minutes. Products and customers sync about hourly. It is not instant, and nobody should promise that it is.
What the delay means
A shop sale shows online within minutes, not seconds. Here is a worked example. You have 3 tarts left. At 12:00 the counter sells 2, so Clover shows 1. WooCommerce still shows 3 until the next sync. At 12:02 a web customer orders 2.
You have now sold 4 tarts and had 3. During a lunch rush, that gap fills fast. The same timing applies to refunds and cancellations, so test them once.
Set a buffer for the gap
WooCommerce has two settings that look alike. The low-stock threshold only emails you. The out-of-stock threshold, under WooCommerce > Settings > Products > Inventory, marks the product out of stock once stock falls to that number. It applies store-wide, not per item.
Use one rule to set it. Buffer = the most units the counter can sell in one 5-minute sync window at peak. In the tart example the counter sold 2 in one window, so the buffer is 2.
Set the threshold to 2 and the web store shows the tarts as out of stock once WooCommerce counts 2 or fewer. Those last tarts stay for the counter. For the banana loaf, if the counter never sells more than 1 loaf in 5 minutes, a threshold of 1 stops online sales once 1 is left.
A buffer is not perfect. While the count is above the threshold, one web customer can still buy several at once. For small batches, also limit how many one order can take, or mark the item sold out online at rush hour.
Two limits apply. The threshold is one number for the whole store, so base it on your fastest seller. And if an item's total stock is no higher than the buffer, a buffer cannot help. That covers one-of-a-kind items and anything with 1 to 2 units. Mark those sold out on the web at lunch and other busy hours. Then put them back when you restock.
Pick one source of truth
Make Clover the source of truth for names, prices and stock, and edit them only there. In CloverWoo you choose this under Clover > Settings > Sync > Conflict Resolution: "Clover wins" or "WooCommerce wins". The counter is where items sell fastest, and the register is where the true count lives. A WooCommerce edit made in between is the one that gets overwritten at the next sync.
If one person fixes a count in WooCommerce and another fixes it in Clover the same afternoon, one edit is lost. Skip any setup where both systems edit the same number by hand.
The exception is a shop that sells mostly online and rings up only a few sales in person. There, WooCommerce is where most changes happen, so it can make sense to treat it as the main record. Pick whichever system takes most of your sales and stick to it.
Run this test script after you connect:
- One sale in Clover.
- One WooCommerce order.
- One refund and one cancellation.
- One manual stock change.
- One out-of-stock event.
- A check for duplicate orders and correct taxes.
Compare the count in both places after each step.
Several locations
Each Clover location keeps its own stock count. The Multi-Location add-on costs $30/month on top of the $60/month plugin. The full walkthrough is in the Clover WooCommerce inventory sync guide.
CloverWoo is one plugin for Clover payments plus product, stock, order and customer sync with WooCommerce, with free setup help after purchase. It does not replace purchase orders, forecasting or warehouse workflows. Retailers who need those should look at a dedicated inventory platform.
If you run a cafe, restaurant or small shop on Clover, see CloverWoo pricing. It is $60/month per store, and card payments work in the US and Canada.
Frequently Asked Questions
Does Clover inventory sync with WooCommerce on its own, or do I need an app?
You need an app. Clover does not update an outside website on its own.
Which system should hold the master stock count?
Pick one. Clover is the simple default for shops that sell in person first.
Will a WooCommerce sale change my Clover count right away?
Do not count on it being instant. Stock syncs about every 5 minutes. Keep a buffer on items with very few units.
What happens to stock when an online order is refunded or cancelled?
Test it once. Refund one order and cancel another. Then check the count in both Clover and WooCommerce before you trust it.
Can I update many items at once?
Yes, through a spreadsheet. Follow the steps in the Clover inventory spreadsheet post.