DineSync for Clover

Many Clover plugins replace WooCommerce with their own ordering system — separate cart, checkout and database. DineSync works with WooCommerce instead, so your products, orders and customers stay in WooCommerce and you keep your existing payment gateways, shipping plugins and marketing tools. DineSync also pushes WooCommerce products to Clover rather than only importing from it.

A Clover POS account on Clover's North American platform (United States or Canada), production or sandbox; a WooCommerce store on WordPress 5.8+ and WooCommerce 5.0+; PHP 7.4 or later; and a Clover API token with your Merchant ID.

Sign in to the Clover Dashboard and go to Account & Setup → API Tokens. Create a token with read and write access to Inventory, Orders, Merchant and Customers, then copy the whole token into DineSync along with your Merchant ID. Make sure Live or Sandbox matches the account the token was created in.

Yes. Create your token in the Clover sandbox, choose Sandbox when you connect, and you can test before going live.

Not in the free plugin. DineSync does not receive live updates from Clover. When you change your menu, prices, the In stock switch or stock on the Clover device, run Import from Clover from the DineSync Dashboard to bring those changes into WooCommerce. DineSync Pro can check Clover every 5 minutes instead, either for the In stock switch only or for every change.

Yes. When you switch an item off on your Clover device, the next import marks the product Out of stock on your website, and switching it back on marks it In stock. This applies to products that do not track a stock quantity, and stock counts are never changed. In the free plugin it happens when you run Import from Clover; with DineSync Pro, choose Follow the In stock switch automatically under Menu from Clover and it is checked every 5 minutes.

Not automatically. In-store sales change stock on Clover, and you bring that across by running Import from Clover.

Once. Clover takes a linked item off its own count when the order is paid there, so DineSync sends nothing to Clover for a sale. A cash order's stock comes off Clover when it is paid at the counter, not when the order arrives. A canceled order, or a refund with "Restock refunded items", is put back on Clover once, and only the units Clover counted: Clover does not restock by itself, and an order that was never paid there was never taken off. A Failed or trashed order is put back the same way. Moving an order to Pending payment to edit it is not a cancel, so nothing moves on Clover, and an order you bring back to Processing after a cancel has its units taken off Clover again. The order's DineSync panel says what was put back, or why nothing was. If DineSync cannot tell whether Clover counted the order, or Clover's count changed while it was being put back, nothing is written and the panel tells you what to check. If Clover could not be read or refused the write, it is tried again the next time that order's stock or status changes. What DineSync does not count: an item that reached Clover without its link, items added with Send missing items, lines you edit after the order reached Clover, product variations, an order that did not reach Clover at all, and a void or refund made on the Clover device. Correct those counts on Clover by hand. One case to avoid: if you change a product's stock in WooCommerce while a cash order for it is still waiting to be paid on Clover, your figure is written to Clover and the counter payment then takes one more off, so Clover ends one short. Take the payment first, or correct the count on Clover afterwards. More generally, a stock change you make is written over any in-store sales since your last import, so run Import from Clover first if the till has been busy.

When you cancel an order, or refund it in full, DineSync marks the Clover order canceled and, for a refund, changes the ticket's note to say Refunded. A cancel puts the order's stock back on Clover if Clover had counted it (see above); a refund, full or partial, puts back only what you restock with "Restock refunded items". DineSync does not refund or void a payment on Clover, and it does not delete the ticket: do that on your Clover device if you need to.

Yes. When you save a product in WooCommerce, only the changed fields are sent to Clover, which keeps API calls low and avoids overwriting unrelated fields. You can also push in bulk with Send all products to Clover on the DineSync > Tools page.

Product names, prices, SKUs, categories, stock levels, availability and descriptions. Modifier groups are read from Clover and never sent to it, so changing a modifier group in WooCommerce does not change it on your POS. Orders send line items, customer name, email and phone, modifier selections, fees, shipping and discounts. A payment is recorded only for orders that have actually been paid. The fields under Product changes to Clover control what a product save sends; an import follows the In stock switch, and otherwise obeys only the stock count and options settings.

DineSync includes a built-in modifier renderer that works out of the box with radio buttons, checkboxes and price adjustment. It also has adapters for WooFood / Flavor and WC Product Add-Ons, and detects which is active automatically.

Usually not. Importing matches existing products by Clover ID, then SKU, then exact name before creating anything, and pushing checks your Clover catalog before creating an item. Duplicates are still possible where item names repeat and SKUs are missing, so tidy those before a large import. You can also run Link Clover items to products at any time from the Tools page to link up an existing catalog in one pass.

Not from refreshing the checkout page, and not from two requests arriving at once: DineSync claims each order in the database before sending it, and a claim that succeeds is never released. A send that fails releases its claim so you can retry it, and a retry after a failed send looks for the Clover order that send may already have made, and uses it instead of making another. The honest answer is that the ordinary causes are closed rather than that it can never happen - if you ever see two, the sync log names the order and what it did.

Yes. DineSync is compatible with WooCommerce High-Performance Order Storage (Custom Order Tables).

Yes, with both the classic WooCommerce checkout and the block-based checkout introduced in WooCommerce 8.3+.

Your WooCommerce products, orders and customer data remain exactly as they are. DineSync stores sync data as metadata on your existing products — there is no proprietary database and no lock-in.

Use Start over on the DineSync > Tools page. It clears item mappings and sync metadata and imports your menu again, overwriting product names, prices, categories, and stock if that toggle is on. It reads Clover first and changes nothing if Clover cannot be read. Your products and orders are not deleted.

Go to DineSync > Settings and click Disconnect. This clears the stored credentials and switches sync off, so no order is sent and no product is pushed. Your products and orders stay in WooCommerce, and each product keeps the record of which Clover item it was linked to - on purpose, so reconnecting the same Clover account picks up where you left off instead of matching everything again. To remove those links as well, use Unlink in the Clover link column of the Products list, or Start over on the Tools page, which forgets every link and imports your menu again.