When two coupons combine against the approved offer

Turn the approved offer into a precise combination rule

Keep the wording the merchant approved and the wording buyers actually saw. Determine whether the promise concerned combining coupon codes, combining a coupon with a sale price, or limiting how many times one buyer could redeem a code. Those decisions use different controls. A phrase such as one use is too ambiguous to establish which control was intended.

WooCommerce separates Individual use only from usage limits per coupon and per user. It also has a separate sale-item exclusion. Restricting redemption count does not express a prohibition on combining coupons. Likewise, a sale price plus one coupon does not establish that two coupon codes were accepted. Identify each reduction by the feature that produced it before changing a limit.

Compare saved flags with the final applied codes

Open each coupon that appears in the affected record and record its individual-use flag. Include when you inspected the setting. A current configuration is not proof of what was saved when an older order was placed. If an existing change record documents a later edit, preserve that distinction; if the historical setting is unavailable, leave it unknown.

Use the final applied-code list and recorded discount amounts for one cart or order. Two success messages at different moments do not establish that both codes remained applied together. Preserve any existing sequence showing which code was entered first, which remained afterward and what the final total showed. Do not invent a sequence from the final amount.

If both flags were off at the relevant time, the individual-use control did not express the intended restriction. If an individual-use flag was on and two coupon discounts remained, the observed record conflicts with the documented core combination rule. That is a reason to investigate the implementation, not proof that a particular plugin caused it.

Name the feature responsible for each reduction

List active coupon or pricing extensions, their installed versions and any known coupon customizations. WooCommerce warns that additional plugins and customizations can change the settings presented. Read the applicable extension rule for combination handling and record whether it explains this exact combination. The mere presence of an extension does not establish an override.

Keep a coupon discount, a sale-price reduction and another pricing adjustment separate in the comparison. A rule that governs coupons cannot be assumed to govern every reduction that appears in the total. Where the installed feature is undocumented or its rule cannot be matched to the order, preserve that as the specific unresolved question for the maintainer.

The amount matters, but do not work backward from a large discount to assume stacking. Record the original item values, each identified discount and the final total in the merchant’s authorized system. The combination decision here is which discounts were allowed together; the calculation basis for a single coupon needs its own check.

Correct the mismatch that the records establish

If the approved rule was never configured, have the authorized store owner confirm the intended restriction before it is saved. If a documented extension rule explains the combination, decide whether that rule or the approved promotion needs to change. If neither explanation fits, give the maintainer the affected record, dated settings and unexplained result. Changing several coupon controls at once makes that comparison harder.

Keep the old order and promotion evidence intact. A future settings change does not resolve what the business will do about a discount already accepted. Record that order decision separately under the merchant’s applicable procedure, without treating an unexpected combination as permission to collect another payment.

For a Prism checkout-review consultation, summarize the combination buyers received, the restriction the merchant intended and the remaining configuration question. Confirm investigation or implementation responsibilities, scope, fees and terms before work begins. Keep order exports and customer details out of the public inquiry.

Coupon-combination record

Complete one sheet for one real combination. Keep original order and configuration evidence privately. The final column is for your comparison result or an unresolved fact. A missing historical setting cannot be filled with today’s setting.

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.

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.