Inventory Tools moves products in bulk in either direction: Export to Clover creates Clover items from WooCommerce products, and Import from Clover creates WooCommerce products from Clover items. The page describes itself as "Move products between WooCommerce and Clover in bulk."

 

It lives in your WordPress admin under WeeConnectPay → Inventory Tools, and needs WeeConnectPay plugin version 4.12.0 or newer. Transfers need the Advanced plan: without it the page says "Inventory transfers need a subscription upgrade" and keeps your selection, so you can upgrade and submit again without picking everything a second time.

 

 

The one rule that shapes everything: transfers only create

A transfer only ever creates something that does not exist on the other side yet.

 

  • Export creates Clover items from products that are not linked yet: "Create Clover items from WooCommerce products that are not linked yet. Prices, stock and tax classes come from your live catalog."
  • Import creates WooCommerce products from items that are not linked yet: "Create WooCommerce products from Clover items that are not linked yet."
  • An already-linked product or item is skipped with "Already linked to a Clover item". It is not re-created and not updated.
  • A transfer never deletes anything, and never overwrites an existing Clover item's name, price, stock or taxes. Keeping the two catalogs in step after the initial move is what the sync modes do.

 

Each created pair is linked for you as it is created, so exported and imported products are ready for sync straight away. Your WeeConnectPay dashboard keeps a record of what an export added to your Clover catalog, under Items created in your Clover catalog. That panel only keeps the record: nothing on it changes or removes anything. Releasing a store from your Clover account is the one place you can choose to have the items that store created removed from your catalog, and the same panel then shows what happened to each of them.

 

 

How a run goes

The page walks four steps: Choose, Pick, Review, Run.

 

  • A transfer is limited to 1000 products: "A transfer is limited to 1000 products. Trim the selection and run another transfer for the rest."
  • One transfer per direction at a time. If one is already going, the page attaches to it rather than starting a second.
  • Review summarizes what will happen before you submit, including how many products carry a SKU, how many carry stock quantities, and how many will be left out.
  • Run shows live progress, and Cancel run stops it. Items already being processed finish first.

 

Exports keep going without you: "You can close this page. The export keeps running, and this page catches up whenever you come back."

 

Imports need the page open: "Keep this page open while products are being created. If you leave, the import pauses and resumes where it left off when you come back." Reopening the page and pressing Resume import continues where it stopped. Nothing is lost and nothing is created twice. If items were held by an earlier import, the page says so: "Some items are still held by an earlier import. They free up within 15 minutes, and this import keeps waiting for them."

 

 

What comes across

Exporting to Clover takes each product's price, its stock quantity when the product manages stock, its SKU, and its taxes, mapped from its WooCommerce tax class through your tax rate links.

 

Importing from Clover creates the product with the item's name, price, SKU and stock quantity, and picks the WooCommerce tax class whose rates match the item's Clover rates. Imported products are created as Draft by default ("Hidden from your store until you publish them."), and you can choose Published instead before you start. A product created as a draft is in your store but not visible to shoppers until you publish it.

 

If your sync mode is Off when you transfer, the page says what that means: "Stock sync is off right now. Transferred products are still created and linked, and stock starts syncing once you pick a sync mode on the WeeConnectPay settings page."

 

 

What a skipped item means

A run reports each item on its own. Skipped means that one item was deliberately left out and the rest of the run carried on. It is not a failure of the run, and nothing was half-created: a run that leaves items out finishes as "Completed with errors" and names a reason per item.

 

Reason shown What it means
Already linked to a Clover item This pair already exists. Nothing to transfer.
Tax rates could not be mapped to Clover The taxes on the two sides cannot be matched yet, so transferring the product would give it the wrong taxes. See the next section.
A Clover item already uses this SKU Clover will not take a second item with that SKU. Change the SKU on one side, or link the two instead of exporting.
Name is missing or longer than Clover allows Give the product a name Clover accepts, then run it again.
Clover rejected the tax association The item was created but its tax rates could not be attached to it, so it was not linked. Contact us with the product name.
Stock quantity could not be written The item exists and only its opening count is missing. The next sync or a manual edit trues it up.
Item no longer exists The Clover item was deleted between picking it and importing it.
WooCommerce product could not be created Your store refused the new product. Check the product name and SKU for conflicts in WooCommerce.
Skipped by your choice You skipped this one during the run.

 

Nothing on this list affects your payments, your existing products or your existing Clover items.

 

 

Items left out for tax reasons

Taxes are the most common reason an item is left out, and it is deliberate: a transferred product with the wrong taxes would charge the wrong amount, so the run leaves that one out and finishes the rest. The page states it before you submit: "Each item's tax class comes from its Clover rates and your rate links. An item we cannot match is left out on its own rather than given the wrong taxes, and the run still finishes."

 

The detail per item names the tax involved:

 

  • Exporting, when a rate is not linked yet: "%d selected product(s) will be left out. Their WooCommerce tax rates are not linked to Clover rates yet, so transferring them would give them the wrong taxes. Link the rates on the Taxes tab and run those again later."
  • Importing, when a rate is not linked yet: "This Clover item applies [rate names], which has no linked WooCommerce tax rate yet. Create or link a matching rate, then run the import again."
  • Importing, when every rate is linked but no tax class matches: "All rates on this item are linked, but none of your WooCommerce tax classes combines exactly this set: [rate names]. Create a tax class with exactly these rates, then run the import again."

 

That last one is where stores charging different taxes per province land. A WooCommerce tax class holds a row per province and picks the right one per customer, while a Clover item applies its rates to every sale, so no class can ever combine exactly the item's set without changing what some customer is charged. Creating those products in WooCommerce by hand, with your normal tax class, is a perfectly good answer: checkout taxes are unaffected either way.

 

 

After a transfer

Exported and imported products are linked, so they follow whatever your sync mode is from that point on. Imported drafts still need publishing. If a product came across without the stock you expected, When your stock updates, and how fast covers where counts come from.

 

If a run ends with items you cannot place, email support@weeconnectpay.com with the product names and we can tell you exactly what each row reported.