Description
DineSync for Clover connects your WooCommerce store to your Clover POS. Orders arrive on your Clover device once they are paid or accepted. Product and price changes you make in WooCommerce are pushed to Clover. Your Clover menu — items, categories, prices and modifier groups — can be imported into WooCommerce whenever you need it.
Clover’s North American platform only. DineSync connects to api.clover.com, which serves Clover accounts in the United States and Canada. Merchants on Clover’s European platform cannot connect.
DineSync works with WooCommerce rather than replacing it. Your products, orders, customers, payment gateways and shipping methods stay where they are.
Built for restaurants, cafes, bakeries, and food businesses that take orders online through WooCommerce and run Clover POS in-store.
What DineSync does
Being precise about this matters more than sounding impressive, so here is the actual scope:
- Paid orders go to Clover. A card order reaches your Clover POS the moment the payment completes — not when the checkout form is submitted, so a declined card never reaches your kitchen. Cash on delivery, direct bank transfer and check orders reach Clover as soon as WooCommerce accepts the order at checkout – there is no separate step for you to approve – with no payment recorded on Clover, because none has been taken. An order DineSync will not send – canceled, refunded or failed, or with sync switched off – says why in the sync log. Orders carry line items, modifier selections, customer details, fees, shipping and discounts.
- A broken item link never costs you the food. If a product’s link to Clover is no longer valid — most often because the links were made against a different Clover account — DineSync sends that line by name instead, so the item still appears on the ticket, and removes the dead link.
- Product and price changes push to Clover when you save. Edit a product in WooCommerce and the changed fields are sent to Clover. Only what actually changed is sent.
- Your Clover menu imports into WooCommerce on demand. Click Import from Clover to pull items, categories, prices, stock levels and modifier groups across.
- Clover’s In stock switch reaches your website. Switch an item off on your Clover device and, at your next import, it shows Out of stock on your website; switch it back on and it is In stock again. Stock counts are never touched. With DineSync Pro this happens on its own every 5 minutes.
- Orders that need you come to you. An order that could not reach Clover, or whose Clover total differs from the website’s, is listed at the top of the Dashboard with numbered steps, and a red count shows in the menu.
- Modifiers come across and display on your storefront. Clover modifier groups become selectable options on the product page.
- How modifiers appear on the Clover ticket depends on where they came from. Modifiers imported from Clover are attached to the item they belong to, exactly as they would be if the order had been rung up in store. Modifiers managed by a third-party add-on plugin have no matching record in Clover, so their cost stays in the item’s price and their names are printed in the item’s note. Either way the ticket totals are correct.
- Orders can print to your Clover kitchen printer automatically when they arrive.
What DineSync does not do
- In the free plugin, changes made on your Clover POS do not flow back to WooCommerce on their own. There is no live Clover-to-WooCommerce feed. If you change a price, the In stock switch or a stock level on the Clover device, run Import from Clover to bring it across. DineSync Pro can check Clover every 5 minutes instead, for the In stock switch only or for every change.
- A void or refund made on your Clover device does not reach WooCommerce, and Clover does not put that stock back by itself. Correct both counts by hand.
- It is not a replacement checkout, cart or ordering system.
Why DineSync?
- Keep WooCommerce — Your products, orders and customers stay in WooCommerce. Use any of the WooCommerce payment gateways, shipping plugins and marketing tools you already rely on.
- Push to Clover, not just pull from it — Update a price in WooCommerce and it reaches your Clover POS on save.
- No vendor lock-in — Sync data is stored as ordinary WooCommerce product metadata. Deactivate DineSync and your products, orders and customer history are untouched.
- Per-field control — Under Product changes to Clover, choose exactly what a product save sends to Clover: name, price, category, description, options and SKU. Modifier groups are read from Clover, never written to it.
- Smart updates — Only changed fields are sent to Clover, minimizing API calls and avoiding unnecessary overwrites.
Key Features
Order Sync (WooCommerce to Clover)
- WooCommerce orders appear on your Clover POS with full details
- Line items, modifier selections, customer info (name, email, phone), fees, shipping and discounts included
- Payment recorded on Clover for orders that have actually been paid, with the correct amount
- Auto-print to a Clover printer you select
- Each order is claimed in the database before it is sent, so a refreshed checkout page cannot produce a second Clover order. A send that succeeds keeps the claim for good; one that fails releases it, so the order can be retried
- If some line items reach Clover and others do not, the order is marked Partly synced rather than synced, the order screen lists what is missing and why, and Send missing items adds only those lines to the Clover order that already exists — never a second order
- Works with both the classic WooCommerce checkout and block-based checkout
Order Status (WooCommerce to Clover)
- WooCommerce “Completed” marks the Clover order fulfilled
- WooCommerce “Cancelled” and “Refunded” cancel the Clover order
- An order canceled on Clover is not reopened there if you move it back to Processing in WooCommerce; the order’s DineSync panel tells you to reopen or re-enter it on Clover by hand
- Editing an order’s lines after it reached Clover does not change the Clover ticket; the order’s panel tells you to update it there
Product Push (WooCommerce to Clover)
- Push products to Clover with diff-based updates — only changed fields are sent
- Saving a product sends its changes to Clover if that product is already linked. New Clover items are only ever created by an explicit Push to Clover
- Push also runs in bulk with Send all products to Clover on the DineSync > Tools page
- Bulk pushes are batched (30 items at a time) to avoid timeouts
- A product that is out of stock and does not track stock quantity is marked unavailable on Clover. For a product that tracks stock, a sale sends nothing – Clover counts it at payment – and a stock change you make is sent to Clover: as your quantity, once DineSync has confirmed the two counts agree; after linking an existing Clover item, the change you made is applied to the count your till already holds instead. Sending your quantity writes over any in-store sales since your last import, so run Import from Clover first if the till has been busy. Both require the matching field to be ticked under Product changes to Clover
- If a product tracks stock and its Clover item does not yet, the first save starts a stock record on Clover at the product’s quantity and names it in the sync log
- WooCommerce short descriptions map to Clover’s alternateName field, stripped of HTML and trimmed to Clover’s 127-character limit
- WooCommerce categories are created on Clover if they do not already exist
Menu Import (Clover to WooCommerce, on demand)
- Import items, categories, prices, stock levels and modifier groups from Clover
- Existing products are matched by Clover ID, then SKU, then exact name. Items sharing a name are left alone rather than guessed at, so an import will not silently duplicate or relink your products — the sync log names the clash so you can give them distinct names or SKUs
- A product with no Clover link still sells and still reaches the kitchen — its line is sent by name at the price paid. It just does not receive price or stock updates until it is linked
- A Clover link column on the Products list shows which Clover item each product is linked to. Choose offers the matching items when a link is missing; Unlink removes one without touching Clover
- Link Clover items to products (on DineSync > Tools) links products to Clover items without adding anything to either side
- An import follows the In stock switch for products that do not track stock. Stock counts and options are the only other settings an import obeys; the fields under Product changes to Clover apply to the push from WooCommerce to Clover, not to imports
- Start over (on DineSync > Tools) clears every Clover link and imports your menu again, so you can start from a clean slate. It reads Clover first, and changes nothing if Clover cannot be read
Modifier Groups
- Clover modifier groups (toppings, sizes, extras) import with your menu
- Built-in storefront renderer with radio buttons, checkboxes and live price adjustment
- Adapter support for WooFood / Flavor and WC Product Add-Ons — the plugin detects which is active and writes modifiers in that format
- Works with no configuration
Built for WooCommerce
- Uses native WooCommerce products, cart, checkout and orders
- Compatible with WooCommerce High-Performance Order Storage (HPOS / Custom Order Tables)
- Works with any WooCommerce-compatible theme
- A Dashboard with connection status, orders needing attention and recent orders; an Activity log grouped by order; one Settings page with one Save; and a Tools page for one-off jobs
How It Works
- Install the plugin and go to DineSync > Settings
-
Enter your Clover Merchant ID and API token, choose Live or Sandbox, and click Connect to Clover
If you have been testing in Sandbox, clear your product links before switching to Live. Links made against a sandbox account do not exist on a live account, and orders will reach Clover with no items on them. DineSync detects this and offers to clear them, but clearing them first avoids the problem entirely.
-
Click Import from Clover to pull your menu into WooCommerce
- Make sure Send website orders to Clover is on — paid orders now flow to your Clover POS
- Re-run Import from Clover whenever you change your menu on the Clover device (DineSync Pro can do this for you every 5 minutes)
Who Is It For?
Restaurants, cafes, bakeries, food trucks and food businesses that:
- Already use WooCommerce (or want to) for online ordering
- Use Clover POS in-store and want online orders to reach it
- Want to keep the WooCommerce ecosystem — payment gateways, shipping plugins, marketing tools
- Want control over exactly what data is sent to Clover
Third-Party Services
1. Clover POS API (api.clover.com / apisandbox.dev.clover.com)
The official Clover API. This is the only external service DineSync contacts, on any installation.
- Used for: reading and writing inventory items, modifier groups, categories, orders and merchant data
- API endpoints: https://api.clover.com/v3 (production) and https://apisandbox.dev.clover.com/v3 (sandbox)
- Region: DineSync uses Clover’s North American API. Accounts on Clover’s European platform are not supported.
- Data sent: product names, prices, SKUs, stock levels, descriptions, categories, order details, customer names, emails and phone numbers
- Data received: Clover items, categories, modifier groups, stock levels, printers, employees, order statuses
- Privacy Policy
- Terms of Service
Support
For help, email info@monirtechsolutions.com or visit monirtechsolutions.com/plugins/dinesync-for-clover/support.
Installation
- Upload the
dinesync-for-cloverfolder to/wp-content/plugins/, or install directly from the WordPress plugin repository. - Activate the plugin through the Plugins menu in WordPress.
- Navigate to DineSync > Settings.
- Enter your Clover Merchant ID and API token:
- Your Merchant ID is in the Clover Dashboard address bar after
/m/, and under Account & Setup. - Create an API token in the Clover Dashboard under Account & Setup → API Tokens, with read and write access to Inventory, Orders, Merchant and Customers.
- Choose Live or Sandbox to match the account the token was created in.
- DineSync works with Clover accounts in the United States and Canada. Accounts on Clover’s European platform cannot connect.
- If you test in Sandbox first, clear your product links before switching to Live.
- Your Merchant ID is in the Clover Dashboard address bar after
- Click Import from Clover to pull your menu into WooCommerce.
- On the Settings page, under Website orders, choose your kitchen printer. Under Menu from Clover, choose how your website follows your Clover menu, and under Product changes to Clover, choose whether a product save updates Clover.
- Orders placed in WooCommerce will now be sent to your Clover POS.
FAQ
How is DineSync different from other Clover plugins?
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.
What do I need to use this plugin?
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.
How do I get an API token?
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.
Does it work with the Clover sandbox environment?
Yes. Create your token in the Clover sandbox, choose Sandbox when you connect, and you can test before going live.
Do changes I make on my Clover POS appear in WooCommerce automatically?
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.
Can my website follow the In stock switch on my Clover device?
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.
Do stock levels update in WooCommerce when someone buys in-store?
Not automatically. In-store sales change stock on Clover, and you bring that across by running Import from Clover.
How is a website sale counted on my Clover stock?
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.
What happens to the Clover order when I cancel or refund in WooCommerce?
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.
Can I sync WooCommerce products TO Clover?
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.
What data gets sent to Clover?
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.
What add-on plugins are supported for modifiers?
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.
Will my existing WooCommerce products be duplicated?
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.
Can I get duplicate orders?
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.
Does this plugin work with WooCommerce HPOS?
Yes. DineSync is compatible with WooCommerce High-Performance Order Storage (Custom Order Tables).
Does it work with block-based checkout?
Yes, with both the classic WooCommerce checkout and the block-based checkout introduced in WooCommerce 8.3+.
What happens if I deactivate the plugin?
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.
How do I start fresh if something goes wrong?
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.
How do I disconnect from Clover?
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.
Screenshots









Changelog
1.0.19
A clearer order box for DineSync Pro’s card payments. Order syncing is unchanged.
- Changed: DineSync Pro can now word the DineSync – Clover Sync box on an order. With Pro 0.7.1, a card order whose kitchen ticket did not print says “Paid by card; the kitchen ticket didn’t print” and gives Clover’s own words, instead of “Failed”. It no longer offers Sync to Clover, which could only refuse: the order is already on Clover and paid. A card order voided on Clover says “Voided on Clover” and the amount, with no printer error and no Sync to Clover. Every other order’s box is unchanged.
1.0.18
Ready for card payments through Clover, which DineSync Pro 0.7.0 adds. Order syncing is unchanged for every order that is not paid by card through Clover.
- New: a Card payments page in the DineSync menu, after Import from Clover. Without DineSync Pro it says what the feature does; with Pro 0.7.0 it is where you switch card payments on. An older Pro sees “Needs Pro 0.7.0”.
- New: the add-on can put an order on Clover without printing it, take the card payment, and only then print the kitchen ticket. A declined card leaves nothing on Clover and prints nothing. Cash, pay-at-pickup and every other payment method are sent exactly as before: fired, printed, and paid on Clover only where money was taken.
- New: a tip paid with such a card reaches Clover as a tip. On every other order the tip stays a line on the ticket, as before.
- Changed: with DineSync Pro installed but older than a page needs, that page says which Pro version to install instead of offering an upgrade.
1.0.17
Clover’s In stock switch now reaches your website, and Settings asks plain questions on one page. Order syncing is unchanged, and so are your settings.
- New: an import brings in the In stock switch from your Clover device. Switched off there, the product is Out of stock on your website; switched back on, it is In stock again. This applies to products that do not track stock. Stock counts are never changed.
- New: Settings is one page in the order you set up: Get started (until it is done), Clover connection, Website orders, Cancelled orders, Menu from Clover, Product changes to Clover and Alerts, with one Save bar that stays at the bottom of the screen and says “All settings saved.” With DineSync Pro 0.6.1 it saves the Pro settings too.
- New: Menu from Clover asks one question, “How should your website follow your Clover menu?”: when you press Import, follow the In stock switch automatically (Pro), or copy every change automatically (Pro).
- Changed: Sync Direction is now one switch, “When I save a product on the website, update it in Clover”, with the fields it sends shown only while it is on. Your current setting is kept as it is.
- New: a Tools page between Settings and Help & Account: Find duplicates (Pro), Check products stuck at zero stock (with the count; it replaces the “may have been set out of stock” notice, which no longer shows on any page), Link Clover items to products, Send all products to Clover, and Start over (was Clean & Re-Sync). Each asks before it changes anything.
- Changed: the Merchant ID is shown as its first and last 4 characters and the API token as its last 4 only, with Change token to replace it. The token is never printed on the page.
- Fixed: the kitchen printer showed as its Clover ID on Settings, and as “chosen” on the Dashboard. Both show its name now; a printer with no name in Clover is called by what it is.
- Fixed: old addresses such as admin.php?page=dinesync-catalogue-health said “not allowed” instead of opening the page they were renamed to.
- Fixed: saving a product that was Out of stock could tell Clover the item was available, which undid the switch on your Clover device. Marking such a product In stock on your website now tells Clover it is available.
- Changed: when Clover does not confirm that a CANCELLED slip printed, the order note now says that, instead of saying the slip did not print. Needs DineSync Pro 0.6.1.
- Fixed: with DineSync Pro installed, whatever its version, nothing offers an upgrade any more. A Pro older than 0.6.1 gets one notice on DineSync’s pages saying to update it, and its options read “Needs Pro 0.6.1”.
- Changed: every Upgrade to Pro link opens in a new tab.
