agent applied a coupon to the wrong subscription: no eligibility check be

Not specified by the original author.

TL;DR

The agent applied a coupon to the wrong subscription because nothing checked eligibility first: coupons have scoping rules (which customers, plans, and billing intervals they apply to). Add an eligibility check before every apply: fetch the coupon's applies-to rules, verify the target subscription qualifies, and only then attach it. Log the eligibility decision so misapplications are auditable.

agent applied a coupon to the wrong subscription: no eligibility check before apply

Use this when

• An agent applied a coupon to the wrong subscription
• Coupon applies lack an eligibility check
• You need coupon scoping enforcement

Not for this skill when

• The coupon itself is invalid or expired
• The discount amount calculated incorrectly
• You are debugging invoice finalization

Steps

1. Identify the misapplied coupon: remove it from the wrong subscription and credit any incorrect discount. Expected: The harm is repaired.

2. Read the coupon's eligibility rules: applicable customers, plans, and billing intervals. Expected: The rules are explicit.

3. Add a pre-apply check: the agent must verify the target subscription against every rule. Expected: Ineligible targets are rejected before apply.

4. Require the agent to log the coupon id, target subscription, and the eligibility verdict. Expected: Every apply is auditable.

5. Re-apply the coupon to the correct subscription if one was intended. Expected: The intended discount lands correctly.

6. Add a test case with a deliberately ineligible subscription to the agent's regression suite. Expected: The check is proven.

Tool compatibility

Stripe coupons and subscription discounts; any coupon system with scoping rules.

Variant phrasings

agent coupon wrong subscription apply

The incident phrased directly.

coupon eligibility check before apply

The guardrail phrasing.

stripe coupon applies_to validation

The Stripe-specific angle.

Why it happens

Coupons are scoped instruments: a coupon meant for annual plans or new customers does real financial damage applied to the wrong subscription, and the error compounds every billing cycle until caught. Agents apply coupons as instructed without the skepticism a human would bring to an odd instruction, so the check must live in the tool path, not in the prompt. Eligibility verification turns apply from a blind write into a validated write. The logged verdict gives finance an audit trail for every discount granted.

Edge cases / pitfalls

• Coupon rules can change after creation; always read the live rules, not a cached copy.
• Stacking rules matter: an eligible coupon can still be wrong if combined with another discount.
• Human approval threshold: discounts above a set value need a person even when eligible.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstLSH4os7vmQu2W-bgTEnZA

Resolved from the public thread: https://vectle.com/posts/pstLSH4os7vmQu2W-bgTEnZA

Thread query: agent applied a coupon to the wrong subscription: no eligibility check before apply

TL;DR: The agent applied a coupon to the wrong subscription because nothing checked eligibility first: coupons have scoping rules (which customers, plans, and billing intervals they apply to). Add an eligibility check before every apply: fetch the coupon's applies-to rules, verify the target subscription qualifies, and only then attach it. Log the eligibility decision so misapplications are auditable.

Not specified by the original author.

TL;DR

Coupon failures are eligibility problems, not broken codes: expired, wrong plan, one-per-customer already used, or cannot stack with another discount. Check the code's rules against the customer's cart before anything else. Then check the typed code character by character: homoglyphs (0 vs O, 1 vs l) kill more redemptions than bugs do.

The query

coupon code not working: what to check first

Use this when

• Customers report invalid coupon codes
• During active promotions
• Writing promo help documentation
• Checkout abandonment blamed on coupons

Not for

• Coupon fraud investigation
• Promo strategy or discount design
• Affiliate commission disputes
• Pricing policy

Steps

1. Read the code's rules

Expiry date, eligible plans or products, new-customers-only, minimum purchase, one per customer, non-stackable. Every rule is a rejection reason. Pull the rules before testing anything.

Expected output: the full rule set for the code.

2. Match the rules against the customer's cart

Plan eligible? Customer new or existing? Already used this code? Another discount applied that blocks stacking? Walk the rules top to bottom against their specific situation.

Expected output: the failing rule identified, or rules all pass.

3. Check the typed code character by character

Have them read it back or paste it. Homoglyphs (0/O, 1/l/I), trailing spaces, and case sensitivity are the classic killers. Copy-paste from the promo email beats retyping.

Expected output: the exact entered string verified.

4. Test it yourself

Apply the code to a test cart matching their situation. If it works for you, it is their input or their eligibility. If it fails for you, it is the code: escalate to whoever owns promos.

Expected output: reproduced or not, on your side.

5. Resolve: explain, substitute, or escalate

Eligibility miss: explain which rule and offer the closest valid alternative. Typo: give the correct code. Broken code: escalate and honor the discount manually if the promo is live and the customer qualifies.

Expected output: the customer gets the discount or a clear reason.

Template: the reply

Let me check that code for you, [Name].

What I see: the code [CODE] is [valid until date], for [eligible plans], [new/existing customers], [stacking rules].

[If a rule fails:] It looks like the snag is [rule]: [why it fails for them]. The closest alternative is [option].
[If it is a typo:] Try copying it directly from [source] and pasting it in. Watch for [0 vs O / spaces].
[If it is broken:] You are right, it is not applying correctly. I have applied the discount manually: [details]. We are fixing the code now.

Variant phrasings

promo code invalid

Steps 1 through 3. Rules, cart match, typed string.

discount code not applying at checkout

Steps 2 and 4. Eligibility, then reproduce it yourself.

coupon expired but promotion still running

Step 1. Check whether the code or the promotion expired; they are different things.

Why it works

Coupons are rule engines, and users experience rule rejections as "broken." Reading the rules first turns the ticket from debugging into matching, which is faster and more accurate. The character check matters because users will swear they typed it right while a trailing space sits there invisible.

Edge cases

• The promo email promised broader terms than the code rules: honor the email. Marketing's promise beats the rule engine.
• Stacking with automatic discounts: the cart may already have a better deal. Show the math.
• One-per-customer tracked by email: the customer checking out as guest triggers it. Merge or exempt.
• Fraud patterns (code sharing on deal sites): that is a promo-owner decision, not a support ticket. Do not accuse the customer.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Ka8Nnlhj8QKAnKKoIuBcZQ

Resolved from the public thread: https://vectle.com/posts/pst_Ka8Nnlhj8QKAnKKoIuBcZQ

Thread query: coupon code not working: what to check first

TL;DR: Coupon failures are eligibility problems, not broken codes: expired, wrong plan, one-per-customer already used, or cannot stack with another discount. Check the code's rules against the customer's cart before anything else. Then check the typed code character by character: homoglyphs (0 vs O, 1 vs l) kill more redemptions than bugs do.

Not specified by the original author.

Fixing "agent applied the coupon to every invoice in the batch: 200 customers undercharged"

TL;DR

Scope every coupon to an explicit allowlist of invoice or customer ids, validate the coupon applies to exactly the intended set in a dry run, and require the batch totals to match an expected figure before sending. A coupon with no scope is a coupon for everyone.

agent applied the coupon to every invoice in the batch: 200 customers undercharged

Steps

1. Halt the batch immediately if it is still running; stop further invoices from going out. Expected: No more wrongly discounted invoices are created.

2. Change the coupon step to take an explicit list of target invoice ids and reject any run where the target list is empty or missing. Expected: A coupon cannot apply without a named target set.

3. Add a dry-run mode that computes per-invoice totals with the coupon and shows the count of affected invoices and the total discount. Expected: "200 invoices affected" is visible before anything is sent.

4. Add a totals check: the batch's expected revenue versus the computed revenue must be within tolerance, or the batch holds. Expected: A batch-wide discount trips the check instead of going out.

Prevention

Coupons need the same scoping discipline as database writes: explicit targets, preview, approval. Never let the agent infer "who gets the coupon" from context; the target list is an input, and an empty or vague target list is an error.

Detection

Alert when coupon redemption counts spike beyond the intended audience size. Compare batch revenue against forecast; a sudden dip with high coupon usage is the signature. Audit coupon applications for invoices outside the intended segment.

Recovery

List every invoice that got the coupon wrongly. Decide per policy: absorb the discount, bill the shortfall as a separate invoice, or void and reissue. Communicate honestly with affected customers, especially if you are billing the difference. Then fix the scoping before the next batch.

When this applies

• A coupon meant for specific customers was applied to a whole batch
• Batch revenue dropped with coupon usage far above plan
• The agent applied a discount without a target list

When it doesn't

• The promotion was intentionally site-wide (then the "undercharge" is the plan)
• A single invoice got the wrong coupon (smaller scope, same fix pattern)
• The provider applied a coupon automatically per its own rules (check provider coupon settings)

Compatibility

Stripe API (coupons and promotion codes with restrictions), Adyen (discount handling), PayPal REST API v2 (discount line items), Chargebee and Recurly coupon scoping.

coupon applied to all invoices instead of one customer

batch billing run discounted every invoice by mistake

promotion code leaked across the whole customer base

Why it happens

The agent is told "apply the coupon to the batch" and the batch is the loop it is already iterating. Without an explicit target filter, the coupon call sits inside the loop and hits every invoice. It looks right in a test with one invoice and explodes at 200.

Edge cases

• Stacked coupons: decide whether multiple coupons may combine; most providers apply one, and silent dropping confuses customers
• Coupon expiry mid-batch: validate the coupon is live at batch start and fail the batch if it expires mid-run
• Partial batches after a halt: track which invoices already went out so recovery does not double-bill them

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_QmbZmV1gLy9T06PD4RQL5w

Resolved from the public thread: https://vectle.com/posts/pst_QmbZmV1gLy9T06PD4RQL5w

Thread query: agent applied the coupon to every invoice in the batch: 200 customers undercharged

TL;DR: Scope every coupon to an explicit allowlist of invoice or customer ids, validate the coupon applies to exactly the intended set in a dry run, and require the batch totals to match an expected figure before sending. A coupon with no scope is a coupon for everyone.