Repeated Rebate Claims: Distinguish a Duplicate Request from a New Purchase

Three messages from one customer do not necessarily represent three requests for reward value. They may be three attempts to locate the same award. At the same time, one customer can make several real qualifying purchases. A review based only on customer identity or message count can therefore both create duplicate rewards and deny legitimate additional ones.

The useful unit of review is the relationship between purchase, claim and award. Determine what each request refers to, whether an award already exists and whether another purchase creates a separate entitlement under the published conditions. This is an operational review of commercial records, not a method for deduplicating software events.

Match claims to actual purchase references

Begin with a claim-to-purchase table. Preserve each incoming request reference, but connect requests that concern the same purchase. A support conversation, claim form and follow-up email may all refer to order O-210. They remain separate contacts while sharing one commercial context.

In a hypothetical case, a customer has two orders: O-210 and O-244. The first qualifies for a $20 reward and the second for a $15 reward under the applicable offer. The customer sends three requests: CL-1 asks about O-210, CL-2 repeats O-210 after no reply, and CL-3 concerns O-244. The contact count is three; the purchase count is two.

The table prevents the reviewer from treating CL-2 as a new $20 award. It also prevents CL-3 from being rejected merely because the same customer already received value for another purchase.

If the request lacks a usable order reference, ask for the minimum purchase information needed to locate it. Avoid guessing from a similar amount or date when several orders match. An unresolved purchase match should remain an evidence question, not a duplicate finding.

Identify an existing award before creating value

Search the authorized award record using the confirmed purchase reference and campaign context. Check for approved, issued, canceled under a documented decision or unresolved award states. An award that is not visible in one support screen may still exist in the controlling record.

When an award exists, determine whether the customer needs access, an explanation of status or a review of its amount. These are different tasks from creating new value. A resend or access-recovery request should preserve the original award reference, and the responsible team should follow the actual approved recovery process.

Do not assume that an unanswered customer means the first request failed to create an award. The customer may not have received the message, may have used another email address or may not recognize the sender. Before any manual action that could create additional value, verify the existing award state and the authority for the proposed action.

Keep a record of the review that ruled out duplication. For CL-3, write “Separate purchase O-244 confirmed; no existing award found in the authorized source at the stated cutoff; eligibility review continues.” This is stronger than “not duplicate” because it identifies the evidence and the scope of the search.

A difficult case involves an order number reused across storefronts or displayed without its store context. “Order 1042” may not uniquely identify a purchase across the merchant’s operations. Include the relevant store reference and campaign before connecting claims. Otherwise two legitimate purchases can be collapsed into one merely because their display numbers match.

Resolve genuine additional qualifying purchases separately

After identifying a new purchase, apply the published eligibility rules normally. A separate order does not automatically mean another reward is due: the offer may include an existing recipient limit or other condition. The repeated-claim review establishes the correct purchase relationship; the eligibility review determines the entitlement.

For the example, suppose the applicable campaign permits both O-210 and O-244 and the customer’s confirmed remaining entitlement supports the $15 request. CL-3 can proceed through the authorized award process, while CL-1 and CL-2 remain attached to AW-210’s access case. The result follows the actual commercial facts rather than either blanket acceptance or blanket rejection.

Communicate the distinction plainly. “Your two messages about order O-210 relate to reward AW-210, so we have joined them into one support case. Your question about order O-244 is being reviewed separately.” This explains why the customer sees one case for repeated contact without implying that they did something wrong.

If the review confirms a request for duplicate value, state the existing award and the applicable condition without speculating about motive. A customer can misunderstand the process. The supported operational outcome is that the same entitlement should not be issued twice unless a separately authorized correction establishes otherwise.

Close each request with a link to its commercial outcome: existing award access, new purchase review, missing evidence or confirmed duplicate entitlement request. This creates a useful history if the customer contacts support again. The next reviewer can see what the prior messages represented instead of starting a new award or repeating the same questions.

A reliable repeated-claim review therefore preserves three counts: contacts, purchases and awards. Their relationship explains the case. Keeping them distinct is the simplest way to protect both legitimate additional rewards and the integrity of value already issued.

Explore how purchase and award references can support duplicate claim review.

Explore capabilities

Back to contents