Title: DineSync for Clover Author: Monir Tech Solutions Published: Апрель 16, 2026-ж. Last modified: Октябрь 13, 2026-ж. --- Плагиндерди издөө ![](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 Автору [Monir Tech Solutions](https://profiles.wordpress.org/monirkhan07/) [Жүктөө](https://downloads.wordpress.org/plugin/dinesync-for-clover.1.0.14.zip) * [Кенен маалымат](https://ky.wordpress.org/plugins/dinesync-for-clover/#description) * [Сын-пикирлер](https://ky.wordpress.org/plugins/dinesync-for-clover/#reviews) * [Орнотуу](https://ky.wordpress.org/plugins/dinesync-for-clover/#installation) * [Development](https://ky.wordpress.org/plugins/dinesync-for-clover/#developers) [Колдоо](https://wordpress.org/support/plugin/dinesync-for-clover/) ## Сүрөттөө **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. * **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. * **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** — Choose exactly which fields are pushed to Clover: price, name, SKU, categories, stock, availability and description. The Modifiers toggle governs what an import from Clover may overwrite; 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, or by a Full Sync * Push also runs 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. 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 enabled in Fields pushed 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 * **Full Sync** runs Map, then Import, then Push. Import adds Clover items to your shop and Push adds shop products to Clover, so use it when you want both menus to hold everything. To link without adding anything, use **Map** * 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 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 * 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 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](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) #### Support For help, email info@monirtechsolutions.com or visit [monirtechsolutions.com/plugins/dinesync-for-clover/support](https://monirtechsolutions.com/plugins/dinesync-for-clover/support). ## Скриншоттор [⌊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 ## Орнотуу 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.KG ### 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**. ### 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 from the Inventory Actions panel. ### 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. 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 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 **Map Clover Items** at any time from the dashboard 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 **Clean & Re-Sync** in the settings dashboard. 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 **Clear item mappings** on the Settings page. ## Сын-пикирлер There are no reviews for this plugin. ## Contributors & Developers “DineSync for Clover” is open source software. The following people have contributed to this plugin. Мүчөлөрү * [ 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). ## Өзгөртүүлөр #### 1.0.14 Stock on your Clover POS: * Fixed: a website sale of an item tracked on both sides came off your Clover count twice. DineSync now sends nothing to Clover for a sale, because Clover takes each linked item off its own count when the order is paid there, online at checkout or at the counter for a cash order. * New: canceling an order, or refunding it with “Restock refunded items”, puts its stock back on Clover, once, and only the units Clover actually counted. An order Clover never took a payment for has nothing put back, because Clover never took it off. * New: a Failed or trashed order has its stock put back the same way, and a canceled order you move back to Processing has those units taken off Clover again. * New: moving a paid order to Pending payment to edit it changes nothing on Clover. Clover is settled only if the order is then canceled or fails. * New: the order’s DineSync panel has a Stock line saying what was put back, why nothing was, or what to correct by hand. If DineSync cannot tell whether Clover counted the order, or Clover’s count changed while stock was being put back, it writes nothing and says so there. * Fixed: a dish with portions left could be sent to your till as zero, and then stop syncing altogether. WooCommerce marks a product out of stock at any quantity at or below your **Out of stock threshold**, and DineSync read that as “none left”; your real count is sent now, right down to zero. * Fixed: a product sold out at zero could leave its old count on your till. It now sends 0, while a dish on backorder keeps its count. * Fixed: a product that tracks stock, whose Clover item did not, was never synced at all. The first save now starts the stock record on Clover at your quantity and names it in the sync log. * Fixed: after **Map Clover Items** or **Choose**, the first stock change wrote WooCommerce’s whole count over your till’s, so with 3 on your till and 50 in WooCommerce, one website order sent 49. A product that was not tracking stock when it was linked also ignored every later change. * Changed: after Map or Choose, each stock change you make is applied to the count your till already holds, until the two counts agree. If it cannot read your till it sends nothing and says so. * Changed: the sync log says what a stock change moved and where your till ended, where it used to say “+0”. A sale’s line says it moved with the order and that nothing was sent. * Fixed: saving a product that tracks stock sent a request to Clover every time, through a field Clover treats as out of date. Stock now has its own update, sent only when the Stock toggle is on and the count has changed. Known limits for stock: * A void or refund made on your Clover device is not seen by DineSync, and Clover does not restock for it either, so correct both counts by hand. * Items that reached Clover without their link, items added with Send missing items, and order lines you edit after the order reached Clover are not counted or put back by DineSync. Correct those counts on Clover by hand. * Changing a product’s stock in WooCommerce sends your number to Clover over any in-store sales since your last import. That includes a cash order still waiting to be paid at the counter, which leaves Clover one short once it is paid. * Product variations are not linked to Clover, so their stock is never changed there. * If Clover cannot be read, or refuses a put-back, it is tried again only when that order’s stock or status next changes. Otherwise the order’s panel tells you to correct the count by hand. Your orders: * Fixed: when Clover’s reply to a new order was lost, a retry could put a second copy of the order on your till. Every Clover order now carries a reference, and a retry looks for it and uses the order Clover already has. * Fixed: two requests arriving at once could both send the same order, and a crash part-way through a send left the order stuck with no Retry button. Only one send can run now, and an order stuck for five minutes is marked Failed with a note to check Clover before sending it again. * Fixed: an order Clover already holds could be sent again by a status change or a retry. It never is now, and Sync to Clover on such an order says so, pointing a partly synced order at Send missing items. * Fixed: an order Clover could not fire to the kitchen was still marked Synced. It is now marked Failed, with a note to fire it in Clover, and no payment is recorded. * Fixed: an order where no food reached Clover was still fired and paid. It is now marked Failed, and the order says nothing reached the kitchen. * Fixed: a canceled, refunded, failed or trashed order could still be sent by a retry. It never is now, and the order says why. * Fixed: the Clover ticket said “Paid via” even for an order that was not paid yet. It now says “To pay” until the payment is taken online, and “Refunded” after a full refund. * New: an order with no payment method, such as one you enter yourself, is sent once it is On hold, Processing or Completed, with no payment recorded on Clover. * Changed: editing the lines of an order that already reached Clover does not change the Clover ticket, and the order’s panel now tells you to update it there by hand. An order canceled on Clover and then reopened in WooCommerce is not reopened on Clover, and says so. * Fixed: a paid modifier canceled a product’s sale price, so a dish on sale at 8.00 with a 2.00 extra charged 12.00 instead of 10.00. The extra is now added to the price the customer is actually charged, on your storefront and on the Clover line. * Fixed: a discount entered on the order rather than by coupon reached Clover at full price, so the ticket came to more than the sale. A discount now reaches Clover as a discount on the order, named after the coupon where there is one, so the receipt and Clover’s reports match what the customer paid. * Fixed: on a discounted order where part of it had not reached Clover, **Send missing items** sent the food without its discount and the order was marked Synced anyway. The repair now sends the discount with the food, and an order is not marked Synced while any line is still missing. * Fixed: a paid order’s Clover receipt showed no order reference. The payment now carries the same reference as its Clover order. * Fixed: emoji and other characters Clover cannot print came out as “?” on the ticket, and line breaks in a note ran words together. Accented letters are converted rather than dropped, so “Café Latte” stays readable, and a name in a script Clover cannot print is kept rather than sent blank. * Fixed: the note sent to Clover did not say whether an order was a Pickup or a Delivery on an ordinary WooCommerce shop. It now works that out from the shipping method, including the block checkout’s pickup, and shows the customer’s address only on a delivery. * Changed: each line’s price is checked against what Clover recorded. A line Clover will not price as sent is sent again in a form Clover always accepts, and where Clover accepts a different price the log names both prices. * Fixed: an order waiting for payment was logged as though it had failed, sometimes several times for one checkout. Only a refusal that will not clear on its own is logged now, with statuses named the way WooCommerce names them. * Changed: the sync log no longer keeps Clover’s copy of an order, with the customer’s name, phone and address, each time the order’s status changes. Your Clover links: * Fixed: importing or mapping could move a product’s Clover link to a different item, and a name matching more than one item was settled by guessing. A link is never moved automatically now, and a clash is left alone and named in the sync log. * Fixed: a push whose reply did not name the Clover item erased the product’s link, and Clear item mappings left behind the record of what Clover last held. A link is now written only when Clover names the item, and clearing links clears that record with it. * Fixed: a Clover item could be linked to a product variation, which was then renamed and repriced while nothing could show or remove the link. Only products are matched now. * Fixed: an import renamed and repriced a product before checking whether that Clover item already belonged to a different product. It checks first now and leaves the product alone. * Fixed: editing a product that was not linked to Clover created a new item there, and one save could push a product more than once. Saving now updates only an item the product is already linked to, once; new items are created only by Push to Clover or Full Sync. * Fixed: a product in the Trash was not always recognized, so importing could bring it back as a new published product. Matching now compares titles exactly, and works after Clean & Re-Sync has cleared every link. * New: a Clover link column on the Products list shows each product’s Clover item or “Not linked”. **Choose** picks the right item when a name matches more than one, and **Unlink** clears a link without touching Clover. Your categories: * Fixed: every import renamed your product categories to Clover’s names and changed their web addresses, so a category you had renamed went back and links to it broke. Names change only when they genuinely differ, web addresses are left alone, and a rename is logged with both names. * Fixed: a category name containing “&” or an apostrophe was renamed on every import and could be created a second time on Clover. Both sides now compare the name as you typed it. * Fixed: if DineSync could not read your Clover categories it created a second category with a name you already had. It now leaves categories alone for that run and says why. * Fixed: a push could remove category assignments on your Clover POS that DineSync never made, such as a kitchen-printer group. Only assignments DineSync added are ever removed. * Fixed: saving a product could send its categories to Clover when only its stock had changed. Categories are sent only when you change them, including on the first save after Map or Choose, and the log names each one added or removed. Your settings: * Changed: Fields to Sync is now called Fields pushed to Clover, because that is what it governs. An import writes what Clover holds whichever boxes are ticked, except Stock and Modifiers, and the screen now says so. * Fixed: Enable Sync and Sync Direction did not hold, so with direction set to WooCommerce to Clover only, automatic syncing still pulled your Clover menu over your shop. Both settings now govern everything that runs on its own, while the buttons under Inventory Actions say first when a setting points the other way. On your screens: * Fixed: names coming from your Clover POS could run web code in your browser on Sync Logs and Settings. Everything from Clover is now shown as plain text. * Changed: the hosted “connect with one click” option has been removed, with the middleware behind it; it needed a Clover app that was never published, so no store used it. Connections made with a Merchant ID and API token are untouched, and DineSync now contacts nothing but Clover itself. * Changed: every inventory action now asks before it runs, and says what it adds and where. Clean & Re-Sync is marked as the one that destroys something, and its confirmation names the product fields its re-import will overwrite. * Fixed: Clean & Re-Sync cleared every link before reading Clover, so a busy or unreachable Clover left your shop with no links at all. It now reads Clover first and changes nothing if it cannot. * Fixed: Full Sync reported success even when its push step had failed. It now says which step stopped and what did finish. * Fixed: the Products list’s Send action said a product had been sent to Clover when nothing was sent. It now says what actually happened and points at Push to Clover. * Changed: the push summary and the list of products Map could not link now appear on screen as well as in the sync log. The push summary also counts the whole run, not only the last batch of thirty. * Changed: the stock repair notice also counts damaged products that are not linked to Clover, and points you at Map Clover Items. Those are reported rather than repaired, because without a link there is no way to ask Clover what they should hold. * Changed: notices about your product links appear only on DineSync’s screens, the Products list and the product editor. * Fixed: after an update, your admin screens could keep the previous version’s stylesheet and script until you emptied your browser cache. They now change when the files do. * Changed: Synced Products on the Dashboard no longer counts products in the Trash, and every screen and log line now says Clover, or your Clover POS. * New: a description of DineSync Pro on the Dashboard, under Inventory Actions. It can be dismissed, appears on DineSync’s own screens only, and is absent when Pro is installed. #### 1.0.13 * Fixed: importing your Clover menu could create a second copy of a product you had put in the Trash. The import only ever looked at products that were on your shop, so anything in the Trash was invisible to it — the till item looked new, a fresh product was made, and you ended up with two products claiming the same till item. The import now recognises a trashed product and leaves the item alone, saying so in the sync log and naming the product. Nothing is taken out of the Trash: if you want one back on your menu, restore it yourself and import again. * Fixed: the Clean & Re-Sync confirmation only told you what it was about to remove. It now says how many products’ Clover links will be cleared, and that your products, orders and customers are not affected and nothing is sent to Clover — which is the half you actually need before pressing it. * For developers: the automatic push that runs when a product is saved now asks the `dinesync_should_push_product` filter first, as the bulk push already did. It is also told whether it is answering a save or a bulk push. This is what lets DineSync for Clover Pro stop a product that is still waiting for review in Menu Staging from reaching your till when you open it in the product editor and save it. #### 1.0.12 * Sync log entries that count something now say how many were attempted as well as how many succeeded — “cleared 2 of 2” rather than “cleared 2”. A bare count gives you nothing to check it against. * Tested with WooCommerce 11.1. * For developers: a new `dinesync_should_import_item` filter lets other code keep a Clover item out of an import. DineSync for Clover Pro uses it in Menu Staging so that a till item linked to a product you have put in your bin is left alone instead of being brought in again as a second copy. On the free plugin by itself, importing such an item still creates a new product — the filter is the hook that makes leaving it alone possible, not a change to what the free import does on its own. The full history of every version is in [changelog.txt](https://plugins.svn.wordpress.org/dinesync-for-clover/trunk/changelog.txt). ## Мета * Нуска **1.0.14** * Акыркы жаңыртуу **13 саат мурун** * Активдүү орнотуулар **10+** * WordPress нускасы ** 5.8 же андан жогору ** * Tested up to **7.1.3** * PHP нускасы ** 7.4 же андан жогору ** * Тил * [English (US)](https://wordpress.org/plugins/dinesync-for-clover/) * Тег: * [clover](https://ky.wordpress.org/plugins/tags/clover/)[online ordering](https://ky.wordpress.org/plugins/tags/online-ordering/) [pos](https://ky.wordpress.org/plugins/tags/pos/)[restaurant](https://ky.wordpress.org/plugins/tags/restaurant/) [woocommerce](https://ky.wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://ky.wordpress.org/plugins/dinesync-for-clover/advanced/) ## Рейтинг Азырынча эч кандай сын-пикир жок. [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/) ## Мүчөлөрү * [ Monir Tech Solutions ](https://profiles.wordpress.org/monirkhan07/) ## Колдоо Комментарийлер барбы? Жардам керекпи? [Колдоо форумун көрүү](https://wordpress.org/support/plugin/dinesync-for-clover/)