Title: DineSync for Clover Author: Monir Tech Solutions Published: apríl 16, 2026 Last modified: september 26, 2026 --- Search plugins ![](https://ps.w.org/dinesync-for-clover/assets/banner-772x250.png?rev=3507557) ![](https://ps.w.org/dinesync-for-clover/assets/icon-256x256.png?rev=3507558) # DineSync for Clover By [Monir Tech Solutions](https://profiles.wordpress.org/monirkhan07/) [Download](https://downloads.wordpress.org/plugin/dinesync-for-clover.1.0.11.zip) * [Details](https://fao.wordpress.org/plugins/dinesync-for-clover/#description) * [Reviews](https://fao.wordpress.org/plugins/dinesync-for-clover/#reviews) * [Installation](https://fao.wordpress.org/plugins/dinesync-for-clover/#installation) * [Development](https://fao.wordpress.org/plugins/dinesync-for-clover/#developers) [Support](https://wordpress.org/support/plugin/dinesync-for-clover/) ## 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 cheque orders arrive when you accept them, with **no payment recorded on Clover**, because none has been taken. Every order that is held back 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. * **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 * **Changes made on your Clover POS do not flow back to WooCommerce automatically.** There is no live Clover-to-WooCommerce feed. If you change a price or stock level on the Clover device, run **Import from Clover** to bring it across. This is a deliberate statement of scope, not a temporary outage. * 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** — Choose exactly which fields are pushed to Clover: price, name, SKU, categories, stock, availability, description and modifiers. * **Smart updates** — Only changed fields are sent to Clover, minimising 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 before it is sent and released only once it succeeds, so a refreshed checkout page cannot produce a second Clover order * 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 **Product Push (WooCommerce to Clover)** * Push products to Clover with diff-based updates — only changed fields are sent * Push happens when you save a product, and in bulk from the Inventory Actions panel * 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. A product that tracks stock sends its quantity instead. Both require the matching field to be enabled in Fields to Sync * 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 WooCommerce products are matched to Clover items by Clover ID, then SKU, then exact name, so importing usually will not duplicate products you already have. A Clover catalogue with duplicate item names and no SKUs can still produce duplicates — give items distinct names or SKUs before a large import * The **Stock** and **Modifiers** toggles govern what an import may overwrite. The other field toggles apply to the push from WooCommerce to Clover, not to imports * Clean & Re-Sync resets all mappings so you can start from a clean slate **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 * Settings dashboard with connection status, sync statistics and an activity log #### How It Works 1. Install the plugin and go to **DineSync > Settings** 2. Enter your Clover **Merchant ID** and **API token**, choose Sandbox or Production, and click **Connect to Clover** 3. **If you have been testing in Sandbox, clear your product links before switching to Production.** Links made against a sandbox account do not exist on a production 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. 4. Click **Import from Clover** to pull your menu into WooCommerce 5. Enable order sync — paid orders now flow to your Clover POS 6. Re-run **Import from Clover** whenever you change your menu on the Clover device #### 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 a new installation contacts. * Used for: reading and writing inventory items, modifier groups, categories, orders and merchant data * API endpoints: [https://api.clover.com/v3](https://api.clover.com/v3) (production) and [https://apisandbox.dev.clover.com/v3](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](https://www.clover.com/privacy) * [Terms of Service](https://www.clover.com/terms) **2. DineSync Hub** (hub.monirtechsolutions.com) — legacy connections only Earlier versions of DineSync offered a hosted connection option that routed through our own middleware. **Connecting with a Merchant ID and API token, which is the only method this version offers, does not contact the Hub at all.** This entry remains for stores that were linked using the older method and still hold Hub credentials. * Used for: relaying requests and status pings for stores still linked by the legacy method * Service URL: [https://hub.monirtechsolutions.com](https://hub.monirtechsolutions.com) * Data sent (legacy connections only): site URL, admin email, Clover merchant ID, plugin version, order sync counts, heartbeat status * [Privacy Policy](https://monirtechsolutions.com/plugins/dinesync-for-clover/privacy) * [Terms of Service](https://monirtechsolutions.com/plugins/dinesync-for-clover/terms) #### Support For help, email info@monirtechsolutions.com or visit [monirtechsolutions.com/plugins/dinesync-for-clover/support](https://monirtechsolutions.com/plugins/dinesync-for-clover/support). ## Screenshots [⌊Connect to Clover — enter your Merchant ID and API token⌉⌊Connect to Clover — enter your Merchant ID and API token⌉[ Connect to Clover — enter your Merchant ID and API token [⌊Settings dashboard — connection status, sync direction, per-field toggles, order settings and inventory actions⌉⌊Settings dashboard — connection status, sync direction, per-field toggles, order settings and inventory actions⌉[ Settings dashboard — connection status, sync direction, per-field toggles, order settings and inventory actions [⌊Sync statistics — orders synced, last sync time, inventory action buttons and recent activity⌉⌊Sync statistics — orders synced, last sync time, inventory action buttons and recent activity⌉[ Sync statistics — orders synced, last sync time, inventory action buttons and recent activity [⌊WooCommerce checkout — Clover-synced products with customer info⌉⌊WooCommerce checkout — Clover-synced products with customer info⌉[ WooCommerce checkout — Clover-synced products with customer info [⌊Sync Logs — order sync history with timestamps, log levels and order references⌉⌊ Sync Logs — order sync history with timestamps, log levels and order references⌉[ Sync Logs — order sync history with timestamps, log levels and order references ## Installation 1. Upload the `dinesync-for-clover` folder to `/wp-content/plugins/`, or install directly from the WordPress plugin repository. 2. Activate the plugin through the **Plugins** menu in WordPress. 3. Navigate to **DineSync > Settings**. 4. Enter your Clover **Merchant ID** and **API token**: 5. * 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 **Sandbox** or **Production** 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 Production. 6. Click **Import from Clover** to pull your menu into WooCommerce. 7. Configure sync settings: enable order sync, choose which fields sync, and optionally select a printer for auto-print. 8. 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 the Environment setting matches the account the token was created in. ### Does it work with the Clover sandbox environment? Yes. Create your token in the Clover sandbox, select **Sandbox** as the Environment, and you can test before going live. ### Do changes I make on my Clover POS appear in WooCommerce automatically? No. DineSync does not receive live updates from Clover. When you change your menu, prices or stock on the Clover device, run **Import from Clover** from the Inventory Actions panel to bring those changes into WooCommerce. ### 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**. ### 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 from the Inventory Actions panel. ### What data gets sent to Clover? Product names, prices, SKUs, categories, stock levels, availability, descriptions and modifier groups. 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. Per-field toggles control which product fields are pushed to Clover; on imports, only the Stock and Modifiers toggles apply. ### 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 catalogue 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 **Map Clover Items** at any time from the dashboard to link up an existing catalogue in one pass. ### Can I get duplicate orders? No. DineSync claims each order in the database before sending it and only releases the claim once the send has finished, so refreshing the checkout page cannot send it twice. ### 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 **Clean & Re-Sync** in the settings dashboard. This clears item mappings and sync metadata so you can import again from a clean slate. 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. Your synced products and orders stay in WooCommerce but are no longer linked to Clover. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “DineSync for Clover” is open source software. The following people have contributed to this plugin. Contributors * [ Monir Tech Solutions ](https://profiles.wordpress.org/monirkhan07/) [Translate “DineSync for Clover” into your language.](https://translate.wordpress.org/projects/wp-plugins/dinesync-for-clover) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/dinesync-for-clover/), check out the [SVN repository](https://plugins.svn.wordpress.org/dinesync-for-clover/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/dinesync-for-clover/) by [RSS](https://plugins.trac.wordpress.org/log/dinesync-for-clover/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.11 * Fixed: **1.0.10 could fail partway through an import if any item on your till is priced at zero.** The import stopped at the first free item with an error, so some of your menu was brought in and the rest was not. Items priced at zero are common — a till function, a gift card, a delivery charge, a “price on the day” dish. * **If you imported while on 1.0.10, check your menu.** You may have a partly imported catalogue: some products present, others missing, and no message to say so. Running Import from Clover again on this version will bring in whatever did not arrive the first time. * Added an extension point so the paid add-on can import new products as drafts for review instead of publishing them straight to your shop. On its own this release changes nothing: with the add-on inactive, importing behaves exactly as it did before. #### 1.0.10 * Fixed: **Clean & Re-Sync could break the link between your orders and Clover.** On stores that keep orders in the older WordPress posts storage rather than WooCommerce’s high-performance order tables, resetting your product mappings also erased every order’s record of which Clover order it became. With that record gone, a retry could send the same sale to Clover a second time, and Clover does not allow either copy to be deleted once a payment is attached. Clean & Re-Sync now clears product records only, and cannot reach an order. * Clean & Re-Sync now also clears each product’s stored copy of its last known Clover values, which it previously left behind. A leftover copy described a link that had just been removed, which could make a later save believe it knew what Clover held when it did not. * Fixed: **an import did not link the products it matched.** Importing recorded a Clover link for products it created, but not for products it found and updated— so Clean & Re-Sync, which clears the links and imports again, finished with no links at all. Every product an import matches is now linked, and the Clover account it was matched against is recorded with it. * Fixed: **after an import, saving a product sent every field to Clover instead of only what changed.** An import did not record what it had just read from Clover, so the next save had nothing to compare against and sent the lot — including category assignments. Imports now record what they read. * Clean & Re-Sync reports how many product records it cleared, and says that orders were not touched. #### 1.0.9 * Fixed: orders could reach your kitchen with a total and no food on them. If your product links were made while connected to one Clover account and you later connected to another – switching from Sandbox to Production is the usual way – every line referred to an item that account does not have, and Clover refused each one while keeping the order. * A line whose Clover item link is no longer valid is now sent by name instead, so the food still reaches the kitchen, and the dead link is removed. * DineSync now records which Clover account each product link was made against, and tells you when the account you are connected to no longer matches, with a button to clear the affected links. * On first run, DineSync records which Clover account your existing product links belong to, assuming the account you are connected to now, and tells you once.“ Check my links” tests a few of them against Clover and reports whether they resolve, so you can find out rather than guess. * An order where some items did not reach Clover is now marked “Partly synced” rather than synced. The order screen shows how many items arrived, which ones did not and why, and offers to send the missing ones to the Clover order that already exists – never a second order. #### 1.0.8 * Fixed: an order that was not paid could still be sent to Clover and printed in the kitchen, and Clover could be told a payment had been taken. A card that the gateway declined was treated as paid, because the plugin asked whether the payment method was Cash on delivery rather than whether the order was paid. It now asks whether the order is paid, which covers every gateway. * Orders paid by card are sent when the payment completes, not when the checkout form is submitted. An order that pays a minute later – 3-D Secure, a redirect, a bank confirmation – is sent at that moment instead. * Cash on delivery, Direct bank transfer and Cheque orders still reach the kitchen as soon as you accept them, and no payment is recorded in Clover for them, because none has been taken. Direct bank transfer and Cheque were previously recorded as paid. * An order that is held back now says so in the sync log, with the reason. #### 1.0.7 * Fixed: stock. If an item tracks stock in Clover, importing it could set that product to zero in WooCommerce and take it off sale, and saving the product afterwards could then write that zero back into Clover. Clover reports the real count in a different field from the one the plugin read; it now reads the right one, and it will never send Clover a stock number it has not first confirmed. * Fixed: Fields to Sync could not be saved. Unticking a field had no effect, and every save switched all eight back on. Present since 1.0.1.1. * The Stock setting now governs imports as well, which it did not before. * Added a one-time check for products an earlier version may have set out of stock. If any are found, DineSync says how many and offers to compare each one with Clover and put back the count Clover holds. Nothing changes unless you press the button, and every change is written to the sync log with the old and new value. #### 1.0.6 * Fixed a crash when saving a product. With WooCommerce to Clover sync turned on, saving a product could end on “There has been a critical error on this website”. The change had already reached Clover, but the page failed. The Sync to Clover link on the Products list failed the same way. Earlier versions are affected, and updating is recommended. * The sync direction setting no longer offers “Two-way Sync”, which read as a promise that both directions happen live. They do not: WooCommerce to Clover happens on its own when you save a product, and Clover to WooCommerce happens when you run Import from Clover. The setting now says so. * Fixed: admin buttons could be left disabled for ever if a request never came back. Every action in the admin now has a time limit and gives the button back whether it succeeds, fails or times out. * Added Upgrade to Pro in three places: an item in the DineSync menu, a link in DineSync’s own row on the Plugins screen, and a card on the DineSync dashboard. The card can be dismissed permanently. All three disappear if you have the Pro add-on. * When an admin action fails, the message now says why: no response in time (and that the work may still have finished, so check Sync Logs before retrying), the HTTP error the server returned, no response at all, or a reply that could not be read. Most used to say only that the request failed, and Disconnect said nothing at all. * Clicking Disconnect a second time, before the page had reloaded, no longer logs a second disconnection. #### 1.0.4 * WooCommerce is now declared as a required plugin, so WordPress will not let DineSync activate without it instead of activating into a state where nothing works. * Fixed: an order that failed once and then synced successfully kept its old error details, so it still looked broken to anything reading it. * Fixed: importing from Clover could trigger a push straight back to Clover for each imported item. * Add-ons can now show what they are in the DineSync header, and be told when a push is starting, instead of reaching into the page to do it. #### 1.0.3 * Fixed: modifiers now arrive on your Clover ticket attached to the item they belong to, instead of as a confusing extra line. The line items on a Clover order now add up to the order total exactly, including on orders with a quantity of more than one. * Fixed: pushing products to Clover no longer creates a second copy of an item that is already there. DineSync now matches on SKU, then on an exact name, before creating anything new. * Fixed: **Map Clover Items** now works on a real menu. It runs in batches with progress, and if something does go wrong it tells you what happened instead of failing silently. * Fixed: disconnecting now clears the order and import counters, so a new connection starts from zero instead of showing the previous store’s numbers. Your product links to Clover are kept — if you connect to a different Clover merchant, DineSync tells you how many products are affected and lets you decide. * Fixed: modifier groups that allow any number of choices no longer show up as a single-choice list with the first option already ticked. * Changed: sync is now switched ON by default when you connect, and auto-print is OFF by default. Existing settings are untouched — this only affects new installs. * Added: a setup checklist on the DineSync dashboard that walks a new store from installing WooCommerce to a first test order, with the connection form built in. * Added: a connection health strip showing which merchant you are connected to, which environment, whether sync is on, and when the last order went across. * Fixed: reconnecting to Clover now switches order sync back on. Previously, disconnecting left sync off and reconnecting did not turn it back on, so orders were quietly skipped. If sync is ever off while you are connected, the dashboard now says so plainly and offers a single button to turn it back on, and every skipped order is written to the sync log. * Added: a **Sync to Clover** link on each row of the Products list, for pushing one product without opening it. * Added: extension points so future add-ons can plug in without modifying the plugin. #### 1.0.2 * Fixed: DineSync now reports its correct version number on the dashboard and in WordPress. * Improved: connecting to Clover is one clear step. Enter your Merchant ID and API token — the second, confusing connection option has been removed from the setup screen. * Improved: when a connection attempt is refused, DineSync now tells you what to check — whether the token was copied in full, whether it belongs to that Merchant ID, and whether Sandbox or Production is selected — instead of showing a bare error code. * Improved: the Merchant ID and API token fields no longer trigger browser autofill, which could quietly drop an email address into the Merchant ID box. * Improved: setup help now points to the Clover Dashboard, where your Merchant ID and API tokens actually live. * Changed: this page now sets out the sync directions precisely. Orders and product changes travel from WooCommerce to Clover as they happen, and your Clover menu comes into WooCommerce whenever you run **Import from Clover**. Syncing behaves exactly as it did in 1.0.1 — this is a documentation update, not a change to how DineSync works. #### 1.0.1 * Fixed: order item quantities greater than 1 now sync to Clover correctly. Previously, multi-quantity items were recorded as a single unit, causing incorrect kitchen tickets and understated Clover order totals. #### 1.0.0 * Initial release * Order sync from WooCommerce to Clover POS with payment recording * Auto-print to a Clover kitchen printer * Order status sync from WooCommerce to Clover (completed / cancelled / refunded) * Duplicate order prevention — each order is claimed in the database before it is sent, and the claim is released only once the send has finished * Product push to Clover with diff-based updates — only changed fields sent * Auto-create Clover items for new WooCommerce products * Category creation on Clover when pushing products * Description sync (WooCommerce short description to Clover alternateName) * Availability sync (a product that is out of stock and does not track stock quantity is marked unavailable on Clover) * Menu import from Clover — items, categories, prices, stock and modifier groups * Modifier groups with a built-in storefront renderer * Adapter support for WooFood and WC Product Add-Ons * Auto-mapping of existing products to Clover items by name or SKU during import * Per-field sync toggles and configurable sync direction * Bulk import and push with batched processing * Clean & Re-Sync to reset mappings * Activity log with detailed sync history * HPOS compatible (WooCommerce High-Performance Order Storage) * Works with both classic and block-based WooCommerce checkout ## Meta * Version **1.0.11** * Last updated **21 tímar ago** * Active installations **10+** * WordPress version ** 5.8 or higher ** * Tested up to **7.1.2** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/dinesync-for-clover/) * Tags * [clover](https://fao.wordpress.org/plugins/tags/clover/)[online ordering](https://fao.wordpress.org/plugins/tags/online-ordering/) [pos](https://fao.wordpress.org/plugins/tags/pos/)[restaurant](https://fao.wordpress.org/plugins/tags/restaurant/) [woocommerce](https://fao.wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://fao.wordpress.org/plugins/dinesync-for-clover/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/dinesync-for-clover/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/dinesync-for-clover/reviews/) ## Contributors * [ Monir Tech Solutions ](https://profiles.wordpress.org/monirkhan07/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/dinesync-for-clover/)