Check how the promotion link is meant to apply the coupon

Separate distributing a code from applying it

A campaign can tell buyers about a coupon, send them to a product or cart, and promise that a discount will already be present. Those are different functions. A code printed in a message tells the buyer which code exists; it does not show that the store applied it. Preserve the actual promotion wording and destination rather than relying on the campaign’s internal name.

WooCommerce’s coupon-management documentation describes the standard entry flow: the buyer opens the coupon control in the cart or checkout, enters the code and applies it. If that is the flow your store supports, instructions need to identify the code and the entry step. Wording that says the discount is already applied should be checked against an actual application mechanism.

A buyer who never entered a code and received no automatic discount has a different problem from a buyer who entered it and received a rejection. Record whether application was attempted before investigating the coupon’s eligibility rules.

Identify the mechanism behind the exact destination

Check the actual promotion link and the page reached after any redirects. Determine what the link asks the store to do and which installed feature, if any, handles that request. A campaign tracking label or the mere presence of extra text in a URL does not establish that checkout understands a coupon instruction.

Where an extension supplies automatic application, record its name, installed version, relevant setting and vendor instructions. Identify the link or event that the feature is documented to handle, and compare it with the destination the promotion actually uses. An installed coupon-related extension alone does not establish that its automatic-application feature is configured for this offer.

If the mechanism is custom or cannot be identified, leave automatic application unconfirmed. Ask the maintainer to identify the implementation and its supported entry process before attributing a failure to it. The ordinary coupon-entry instructions do not establish the behavior of every additional feature in a particular store.

Locate the break between arrival and the discount

Compare the original destination, the actual arrival page and the cart or order’s coupon record for the same reported journey. Preserve any existing observation that shows whether the code appeared, whether an error was shown and whether the discount remained in the final summary. Do not claim a link stripped a coupon instruction unless the actual URL comparison establishes that change.

If the link provides no supported automatic mechanism, the issue is the promised entry process: the promotion describes an action that arrival alone does not perform. If a supported mechanism attempted the coupon and received an error, the task moves to the saved coupon’s validity and restrictions. Keep that error rather than diagnosing the failure as a missing extension.

If the coupon is already listed but the final amount is disputed, automatic application may have succeeded. The next comparison concerns the discount calculation or combination rules. Conversely, a smaller total with no identifiable coupon is not proof that this promotion applied: match the reduction to its actual recorded source.

When no genuine cart or order observation exists, the configuration and documentation can establish the intended path, but its observed result remains unknown. Do not turn a planned handoff into a completed buyer journey.

Align the instructions with the path the store supports

For a manual-entry offer, state the code and where the buyer must apply it, and confirm that the relevant entry control is available on the actual cart or checkout. For a supported automatic link, make the promise only for that configured entry path and retain the coupon’s eligibility conditions. Neither distribution by a campaign nor automatic application removes those conditions.

If an automatic promise has no identified mechanism, the merchant can authorize a wording correction or scope the missing integration work with the maintainer. If the mechanism exists but the link does not reach it correctly, preserve the failed handoff before changing the destination. Keep a dated record of the approved correction so support knows which instructions accompanied an earlier buyer report.

For a Prism checkout-review consultation, summarize the promotion’s promise, destination type and point where the discount failed to appear. Confirm any requested investigation or implementation scope, responsible party, fees and terms before work. Send a public storefront URL and a non-sensitive description; do not send private payment links, customer records or account access details. Follow-up is by email; sending the request does not book an appointment, purchase a service or submit a processing application.

Promotion-to-coupon handoff

Follow one genuine promotion from its approved wording to the recorded discount. Fill the last column from the actual link, installation and available buyer-journey evidence. Mark an unobserved step unknown. Keep private or customer-specific URLs in authorized records rather than copying them here.

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.