On this page

A purchase matches two approved reward offers. One produces $12 and the other produces $18. Should the customer receive $30, $18 or $12? All three outcomes are possible under different commercial combination rules. The matching process alone does not choose the amount.

The merchant needs an explicit rule for resolving overlapping offers after their individual amounts are known. This article assumes both matches are valid and examines the payable value, leaving eligibility discovery and discount-engine setup outside scope.

List the independent reward amounts

Start by calculating each offer under its own approved formula. Give the offers stable names in the worksheet, such as Product Offer and Campaign Offer, and record the amount each would produce independently. Do not combine rates before you know whether their bases and conditions are the same.

For a fictional purchase, Product Offer produces $12 and Campaign Offer produces $18. Three candidate rules are under review: add both amounts, pay only the highest amount, or use a predetermined offer priority. For the priority example, Product Offer has precedence even when its amount is smaller.

That last choice may be intentional for a particular program, but the merchant should understand its consequence. A priority rule is not the same as a best-value rule. Calling both “one reward per order” leaves the amount unresolved.

The RebateCardX campaign overview can frame a discussion of the proposed arrangement. The worksheet does not assert that every combination method is supported or approved. Bring the intended conflict-resolution rule and example outputs to the program review.

Compare sum, priority and best-value outcomes

Use several amount pairs so the team sees where the rules agree and diverge.

Independent Product Offer Independent Campaign Offer Add both Highest amount only Product Offer has priority
$12 $18 $30 $18 $12
$25 $10 $35 $25 $25
$15 $15 $30 $15 $15
$8 $0 $8 $8 $8

The first row reveals the principal difference between priority and best value. The tie row reveals a different question: two equal amounts do not necessarily mean two benefits should be paid. Under the highest-only rule, the total is $15, not $30.

A tie still needs an attribution choice even when it does not change the customer amount. The merchant may need to identify which offer is considered selected for its own records. That selection should follow a documented rule, such as a predetermined priority among equal values, rather than whichever offer happens to be evaluated first. This is a commercial attribution requirement, not an implementation instruction.

The zero row also deserves attention. If one matched offer calculates zero under its own approved formula, an additive or highest-only design can still produce $8 from the other. A rigid priority rule might behave differently if the zero-producing offer had precedence. The merchant should include that case in its expected outputs rather than assuming “matched” always means positive value.

Do not infer the rule from native Shopify discount combinations. A later reward arrangement can have its own commercial amount logic. If a store also uses checkout discounts, their behavior needs to be checked separately through the relevant Shopify documentation and actual configuration.

A difficult case involves three matching offers. A pairwise decision that always picks the larger amount can express a highest-only rule, but a priority rule needs a complete ordering. An additive rule needs clarity on whether all approved components are included or only a defined subset. Extend the specification deliberately rather than assuming a two-offer example resolves every combination.

Approve an explicit conflict-resolution formula

Select the rule in language that predicts the table. An additive statement might read: “After both approved offer amounts are calculated, combine them into the proposed total reward, subject to any separately defined final limit.” A best-value statement might read: “Pay only the largest of the approved matching offer amounts; equal amounts produce one reward amount, with the documented tie priority used for attribution.”

A priority statement should name the precedence: “If Product Offer applies, use its calculated amount; otherwise use Campaign Offer.” If the team intends exceptions when the priority amount is zero, those exceptions belong in the statement. Do not let them emerge informally from customer support decisions.

For the fictional merchant, suppose the goal is to let customers receive the better of two non-additive offers. The team selects highest amount only and records expected totals of $18, $25, $15 and $8 for the four rows. It also records Product Offer as the tie winner for internal attribution when amounts are equal.

Now test whether either offer’s customer-facing description implies addition. Phrases such as “extra reward” or “on top of” can conflict with a highest-only design. The amount rule and the offer descriptions should be reviewed together so a customer is not promised two benefits while the calculation pays one.

A final cap can further change the result. If an additive formula is capped at $25, the first row’s raw $30 becomes $25. That is a separate operation and should be shown explicitly. A cap should not be used to obscure which combination rule was selected in the first place.

The practical output is a combination decision table with unequal values, ties and zero components, plus one explicit conflict-resolution formula. Once that record exists, every team can calculate the same total from the same matching offers without interpreting the phrase “cannot combine” differently.

Discuss how overlapping rebate offers should combine before either campaign launches. Discuss program fit.

Source references

Back to contents

General information only

This guide is general information, not financial, legal, tax or regulatory advice. Eligibility, card availability, permitted use and responsibilities depend on the applicable offer and card terms.