Skip to content

Main content

Offer Stack Order Difference Tool

Compare uncapped additive and fractional discount order; negative intermediate prices are retained.

Loading tool…

Description

Compute (price - fixedDiscount) × (1 - fractionDiscount) and price × (1 - fractionDiscount) - fixedDiscount.

Fixed and percentage discounts act differently and may produce different prices when their order changes. Threshold pricing also depends on whether a new rate applies to all units.

Compute (price - fixedDiscount) × (1 - fractionDiscount) and price × (1 - fractionDiscount) - fixedDiscount.

When to use this tool

Use Offer Stack Order Difference when you need a transparent promotional price or eligibility term.

How to use the tool and how it works

  1. Enter price, fixedDiscount, fractionDiscount. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read fixedThenFraction, fractionThenFixed, difference. Use the output convention below.

Compute (price - fixedDiscount) × (1 - fractionDiscount) and price × (1 - fractionDiscount) - fixedDiscount. Return fixedDiscount × fractionDiscount as their difference.1

Input fieldMeaning and unitsAccepted input
pricePriceRequired. Finite number; minimum 0.
fixedDiscountFixed DiscountRequired. Finite number; minimum 0.
fractionDiscountFraction DiscountRequired. Finite number; minimum 0; maximum 1.
Output fieldInterpretationReturned shape
fixedThenFractionFixed Then FractionRequired. Finite number.
fractionThenFixedFraction Then FixedRequired. Finite number.
differenceFixed-then-fraction price minus fraction-then-fixed price.Required. Finite number.
json
{
  "input": {
    "price": 100,
    "fixedDiscount": 10,
    "fractionDiscount": 0.2
  },
  "output": {
    "fixedThenFraction": 72,
    "fractionThenFixed": 70,
    "difference": 2
  }
}

Limitations and assumptions

  • Prices are not floored at zero and the fixed discount can exceed price; retailer eligibility, tax, and rounding rules are not modeled.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Check actual offer terms, item eligibility, taxes, and monetary rounding before applying a computed price.

References

  1. Calculation and input contract: marketing/offer-stack-order-difference — tool.io

Similar or alternative tools