On this page
A campaign formula can look clear in a presentation and still produce three different answers in three departments. Sales may use the original product price, finance may apply a cap before adding a bonus, and engineering may interpret a threshold as strictly greater than the stated amount. The formula is not ready until its business owner can resolve those differences.
A short arithmetic specification with agreed examples is more useful than a paragraph full of percentages. It defines the intended amount without prescribing code, testing frameworks or release procedures.
Write the formula with named units and inputs
Use a fictional design: calculate 8% of an approved eligible merchandise amount, provided that amount is at least $75, with a maximum reward of $20 per order. Round the final positive reward once to the nearest cent; exact half-cent ties round upward. The eligible amount is already defined and supplied to this worksheet.
Name the input eligible merchandise amount in USD. Name the output proposed reward amount in USD. State the threshold as inclusive. State that the $20 cap applies to the calculated reward, not to merchandise value. Those unit labels prevent several common interpretation errors before examples are added.
The calculation sequence in plain language is: compare the approved base with $75; if it is below the threshold, produce zero; otherwise calculate 8% of that base, limit the reward to $20 and apply the stated final rounding convention. If a real program requires a different sequence, the business owner must specify it explicitly.
The RebateCardX Shopify integration overview is a program-discussion starting point. This is an original arithmetic specification, not a claim that the displayed names are API fields or that the proposed formula is already supported. Actual program compatibility is a separate confirmation.
Select boundary and ordinary purchase examples
Six carefully chosen inputs can expose more ambiguity than many convenient round numbers. Include a below-threshold case, the exact threshold, an ordinary amount, a fractional-cent case, the cap boundary and an above-cap amount.
| Case | Approved eligible base | Relevant calculation | Expected reward | Why this case matters |
|---|---|---|---|---|
| 1 | $74.99 | Below inclusive $75 threshold | $0.00 | Confirms the lower boundary |
| 2 | $75.00 | $75 × 8% = $6 | $6.00 | Confirms that equality qualifies for the amount rule |
| 3 | $123.45 | $123.45 × 8% = $9.876 | $9.88 | Confirms final rounding on an ordinary non-round base |
| 4 | $75.19 | $75.19 × 8% = $6.0152 | $6.02 | Exposes a fractional-cent result near the threshold |
| 5 | $250.00 | $250 × 8% = $20 | $20.00 | Confirms the exact cap point |
| 6 | $310.00 | Raw reward $24.80, limited to $20 | $20.00 | Confirms that the reward, not the purchase, is capped |
These outputs are derived from the same named input and sequence. A reviewer should not insert shipping, a current catalog price or an earlier undiscounted amount into one row. If the input definition changes, that is a specification change, not an alternative calculation of the same example.
The exact half-cent tie rule is stated even though these six cases do not create a tie. If a formula’s available cent inputs can produce one, add a dedicated example. The purpose is not to force every edge case into six rows; it is to make the important decisions visible with a compact reference set.
A difficult case is a team that rounds the input before applying the threshold while another compares an unrounded internal amount. The specification must say what the authoritative input represents. In this example, the base is supplied as an approved cent amount. That assumption should remain explicit so engineering does not have to infer commercial meaning from data precision.
Another case is a line-level formula hidden beneath an order-level description. If the merchant expects each line’s reward to be rounded separately, the $123.45 aggregate input alone may be insufficient to reproduce the total. The formula owner must either provide line components and a line-rounding rule or retain the one-final-rounding design described here.
Resolve disagreements in expected reward amounts
Ask each department to calculate the six rows independently using the written specification. Record any difference as a question about an input, operation or boundary. Do not settle it by majority vote or by choosing whichever result the current system happens to produce.
For example, a zero result at $75 indicates a greater-than interpretation where the specification says at least. A $24.80 result at $310 indicates that the final cap was missed. A $9.87 result at $123.45 indicates a different rounding convention or truncation. Each disagreement points to a specific business rule that can be corrected.
The owner should then publish one authoritative amount note containing the selected formula, units, sequence and expected examples. Remove superseded informal descriptions from the working brief so a later reviewer does not find two competing versions and choose one arbitrarily.
Keep the note focused on arithmetic. It does not decide who qualifies, when a reward is issued, which staff member approves a release or how automated tests are written. Those processes can use the note as an input. Expanding it into a general launch checklist would make the amount rule harder to find.
For the fictional campaign, completion means every reviewer can obtain $0, $6, $9.88, $6.02, $20 and $20 from the six inputs and explain the relevant operation. Agreement on the numbers is necessary, but agreement on why they occur is what makes the specification reusable.
The practical output is a business-owned reward arithmetic reference that survives handoffs. When a new basket appears, the teams apply the same named inputs and sequence instead of reconstructing the offer from a headline or copying a prior example that happened to look similar.
Bring a reproducible reward formula to your program discussion with Rebate Card X. Discuss program fit.
Source references
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.
