A Clover item carries its own price in your Clover catalog, and Clover prices any sale of that item from it. So when your store sells the same product for a different amount, a sale price, a coupon or a cart discount, that line is reported to Clover without naming the item, because naming it would build a Clover order at the catalog price instead of the amount your customer agreed to.
This is a pricing rule of Clover's item catalog, not a problem with your links, and it applies however healthy the link is.
What your customer pays does not change
Your customer is charged the WooCommerce total, discount included. The amount taken, the order in your store, and your customer's receipt are all exactly what WooCommerce calculated. Nothing about the discount is lost, and nothing about the payment is affected.
What you see in Clover
| Line sold at the Clover item's price | Line sold at a different price | |
|---|---|---|
| Clover reporting | Counted as a sale of that item, in your item sales figures | Appears under the product's name on the order, not against the Clover item |
| Tax detail | Follows the item's own tax rates, named on the order | Reported like any other line that is not counted against a Clover item, so it follows your tax forwarding mode |
| Clover stock | Clover deducts the units itself when the order is paid | The units are still deducted, right after payment, on Follow Clover and Two-way with a healthy link |
So a discounted sale costs you the item-level reporting for that line, and nothing else. On Follow Clover or Two-way with a healthy link, your Clover count keeps following your sales either way.
The paid order also gets a note in WooCommerce that says so: "Some items on this order were not matched to Clover inventory." and "The payment and order totals are correct and unaffected."
What counts as a different price
Anything that makes the amount per unit differ from the Clover item's catalog price:
- a WooCommerce sale price;
- a coupon or a cart-level discount spread over the lines;
- role-based, tiered or per-customer pricing;
- a price you changed in one system and not the other.
Two shapes of Clover item are also never counted against the item, whatever the price on the order: an item whose Clover price is zero, and an item priced per unit of measure.
The two ways to have discounted lines counted against the item
Both are yours to choose between, and neither is a default we set for you.
Make the two prices agree. When the amount per unit on the order equals the Clover item's catalog price, the line is counted against the item as usual. This is the natural answer when a price simply drifted apart between the two systems.
Price the Clover item as a variable-priced item. A variable-priced Clover item takes the amount sent with the sale as its price, taxes that amount with the item's own rates, and deducts the units from its stock, so a discounted line is counted against the item at the price the customer actually paid.
The trade-off is on the counter side: a variable-priced item has no price of its own at your Clover register, so your staff key the amount on every in-store sale of it. That makes it a good fit for products you sell online at changing prices, and a poor one for products your staff ring up all day.
If a whole category of your sales is affected
Stores that run permanent sale pricing, or price by customer group, will see this on most of their online orders. Nothing accumulates and nothing degrades: each order is reported on its own, your Clover count keeps following your sales on Follow Clover and Two-way, and your tax reporting keeps working through your tax forwarding mode, described in How WeeConnectPay reports your taxes to Clover.
If you want to work out which of the two routes fits your catalog, email support@weeconnectpay.com with a recent order number and we can tell you exactly which lines were counted against their items and which were not.