A coupon item limit was configured without its product scope
WooCommerce documents that Limit usage to X items works only when specific products are entered in the Products field under Usage Restrictions. A saved item cap without that product scope does not meet the documented condition. Check those two settings together, then compare the affected cart's eligible product quantities with the recorded discount. A coupon-wide usage limit or per-user limit answers a different question and does not substitute for this product-scoped item control.
For: A research-only store owner or WooCommerce administrator investigating a coupon that discounts more items than intended.
Open the saved coupon and record its discount type, amount and item cap before changing anything. Next inspect Products under Usage Restrictions. WooCommerce's core coupon guide explicitly ties the item-limit field to specific products entered there. A category selection by itself does not satisfy the stated specific-product prerequisite. Neither does merely putting a number in the item-limit field.
The missing product list is a configuration finding you can establish from the coupon itself. It does not tell you which products the merchant meant to discount. Recover that intended scope from the actual approved offer and its owner. Adding arbitrary products just to activate the cap could create a different promotion from the one buyers were shown.
Keep the three kinds of limit separate
WooCommerce distinguishes uses across the coupon, uses by a customer and the number of items to which the coupon applies. The first two concern coupon usage, while this investigation concerns eligible item quantities. Individual use only is another separate setting: it controls combination with other coupons. Its label does not mean one discounted item or one use per customer.
Record each relevant setting under its own name. If someone used the per-user field to express the maximum item quantity, the configuration does not represent the intended control. Do not change the discount amount to compensate. A different amount changes the price concession while leaving the item-scope question unanswered.
Compare eligible quantities with the affected record
Use the real affected cart or saved order details to list product identities, quantities and the discount actually recorded. Count quantities separately from the number of distinct product lines. Compare the identities with the specified Products list, and retain any exclusions or sale-item restrictions that also apply. The total number of units in a mixed cart is not automatically the number eligible for this coupon.
Match the settings to the time of the observation. Today's edited coupon cannot establish what was saved when an earlier order received its discount. If no earlier configuration record exists, label the historical setting unknown and preserve what the order does show. Record the WooCommerce version and any extension or customization that owns additional coupon behavior; the core guide warns that these can change the settings and behavior being examined.
Once the specific-product prerequisite is present, an unexplained quantity or discount remains a separate finding. The prerequisite alone does not prove every other rule was satisfied or explain which units an extension selected. Keep the actual line-level result for the maintainer instead of inventing an allocation rule from the order total.
Choose a correction that preserves the intended offer
When the product scope is absent, give the offer owner the exact mismatch: an item cap was requested, but the documented product prerequisite is missing. The owner can authorize the intended product list and cap together, or reconsider the offer if that scope is not what was promised. Keep the previous configuration and the authorized change in the store's records. A saved correction does not by itself revise earlier orders.
When the scope was already present, send the maintainer the saved settings, eligible quantities, observed discount and installed discount components. Those facts define the remaining problem more precisely than saying the coupon limit is broken. A Prism checkout consultation can start from that summary and the public offer wording; confirm any configuration or implementation work, responsibilities, fees and terms before it begins.
Coupon cap configuration
Use the affected cart or order and the configuration that applied at that time. Complete the final column with your own findings. Missing historical settings remain unknown; a present cap with no specified Products list fails the documented prerequisite.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Coupon cap configuration. The last column is for temporary notes.
Check
Record to inspect
Decision it supports
Your finding
Item cap
Record to inspectThe saved Limit usage to X items value and coupon discount type.
Decision it supportsEstablish the requested item control without substituting a coupon-wide or per-user limit.
Specified eligible products
Record to inspectProducts under Usage Restrictions, including the exact saved product identities.
Decision it supportsAn empty list leaves the documented prerequisite unmet; a category list alone is not the stated requirement.
Other eligibility restrictions
Record to inspectProduct exclusions, category rules and sale-item restrictions that apply to this coupon.
Decision it supportsIdentify which cart quantities remain eligible without treating every unit as eligible.
Actual eligible quantities
Record to inspectProduct identity and quantity from the affected cart or order, compared with the saved rules.
Decision it supportsDistinguish units from distinct product lines and retain any uncertain eligibility match.
Applied discount
Record to inspectThe actual coupon and line-level discount recorded for the affected cart or order.
Decision it supportsDescribe the quantity or amount discrepancy without guessing which items an extension selected.
Configuration timing and software
Record to inspectThe dated settings record, WooCommerce version and relevant coupon extensions or customizations.
Decision it supportsSeparate an earlier order's evidence from settings edited later and core behavior from added rules.
Configuration owner
Record to inspectThe person authorized to define the offer and the person authorized to save a correction.
Decision it supportsRecord the approved scope and cap, or the unresolved decision, before changing the amount or product list.
These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.
Limits
The specific-product condition comes from WooCommerce core coupon documentation. Extensions and custom code need their own behavior checked.
This worksheet does not predict an unseen cart's discount or establish how a prior order should be adjusted.
Keep customer identities, private coupon credentials, card details and order exports out of shared worksheets and the public consultation form.
WooCommerce coupon management — checked 2026-09-29. The item usage limit requires specific products in the Products field under Usage Restrictions. Core distinguishes coupon-wide, per-user and item limits, combination restrictions and product eligibility; extensions or customizations can alter behavior.