On this page

A program quote includes a monthly minimum, a usage rate and a separate service charge. At high volume, the usage rate may dominate. At low volume, the minimum can make the cost per reward much larger than the headline rate. The merchant needs to model the exact billing relationship before choosing a campaign volume assumption.

The phrase minimum fee is not a complete formula. It might be a floor against usage, an additional fixed charge or another contractual structure. This worksheet uses one clearly defined fictional schedule and shows how volume changes unit cost.

Separate fixed charges from per-event charges

Assume the following illustrative monthly schedule: a $100 fixed service charge, plus the greater of a $300 usage minimum or $0.60 per delivered reward. Reward face value is $10 each and is additional to those charges. These numbers are not RebateCardX prices or provider market estimates.

The usage minimum is a floor, not a charge added on top of all usage. At 200 delivered rewards, usage calculated at $0.60 is $120, so the usage charge becomes $300. At 1,000 delivered rewards, usage is $600, so the usage charge is $600 rather than $900.

Write the formula in words before calculating: service charge plus the larger of the minimum and calculated usage. If an actual contract defines an additive minimum or a different event basis, use that schedule instead. A familiar phrase cannot substitute for the actual commercial definition.

The RebateCardX terms provide a starting point for a program discussion, but specific fees must come from the actual proposed schedule. This article models a hypothetical relationship; it does not imply a published minimum or unit price.

Spread the fixed component across reward volumes

Calculate the program charges and then divide by delivered rewards. Keep the $10 customer face value separate so the effect of the fee structure remains visible.

Monthly delivered rewards Usage at $0.60 Usage charge after $300 floor Plus $100 service charge Program cost per reward Total including $10 face value per reward
50 $30 $300 $400 $8.00 $18.00
200 $120 $300 $400 $2.00 $12.00
500 $300 $300 $400 $0.80 $10.80
1,000 $600 $600 $700 $0.70 $10.70
2,500 $1,500 $1,500 $1,600 $0.64 $10.64

The usage floor stops dominating at 500 rewards because $300 divided by $0.60 equals 500. Above that point, the usage component remains $0.60 per reward, while the separate $100 service charge is spread over more rewards.

Below 500, delivering another reward does not increase the modeled usage charge until the floor is exceeded, but it still adds the $10 face value and any other actual costs not included here. A minimum-fee schedule does not make extra rewards free.

At zero delivered rewards, the schedule would still produce $400 of program charges under the stated assumptions, but cost per delivered reward is undefined because the denominator is zero. Do not display zero unit cost or divide by an artificial recipient count. Show the fixed outlay and the absence of deliveries separately.

A difficult case involves a campaign spanning two billing months. Delivering 200 rewards in each month creates two $400 program charges, or $800 total, under this schedule. Delivering 400 in one month creates one $400 charge. The economic difference follows the billing periods, not merely total campaign volume.

This does not justify moving customer delivery dates in conflict with the promised experience. It identifies a planning dependency to assess before launch. The merchant should use the actual billing periods and approved customer timing rather than optimizing fees after obligations have been made.

Identify the volume range the business can support

Suppose the merchant’s planning limit for program charges is $1 per delivered reward, excluding face value. Under the fictional schedule, the below-floor total is $400, so at least 400 delivered rewards are needed to bring that allocation to $1. This is a chosen business threshold for the example, not a recommended universal volume.

At 300 deliveries, the program charge per reward would be about $1.33. At 400, it is $1. At 500, it is $0.80. The merchant can now compare its plausible monthly delivery range with the range that supports its own cost requirement.

Do not approve the campaign using an aspirational volume without a downside case. If the central forecast is 1,000 but a plausible lower outcome is 200, the modeled program charge per reward ranges from $0.70 to $2.00. That uncertainty may matter more than a small difference in the quoted usage rate.

Also identify which event the actual usage rate counts. Issued, delivered and claimed rewards can have different counts. The table assumes delivered rewards both trigger usage and serve as the denominator. A real schedule may require separate event and outcome counts, as shown in the fee-event model.

For the fictional campaign, a decision note could read: “The selected cost requirement is met at 400 or more deliveries per month under the sample schedule. The expected volume range must be validated, and billing-month allocation must be included in the budget. Do not quote the $0.60 usage rate as the full low-volume cost.”

The practical output is a volume-versus-unit-cost table with the minimum formula stated explicitly. It lets the merchant assess the proposed schedule against realistic delivery volumes without confusing a usage floor with an additive fee or treating a headline unit rate as the entire cost.

Discuss program economics using the reward volume your store can realistically support. 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.