Coupon stacking rules for bank offers, coupons and sale prices
Sets clear rules for which discounts can combine during a sale: sale prices, coupon codes, bank card offers, wallet cashback and loyalty points, checks the worst-case margin for every allowed combination, and writes the customer-facing terms. Use it before a festive or seasonal sale, when stacked offers can quietly push orders below cost.
The output this prompt produced, unedited.
The prompt
What to give
Discount types in the sale: [e.g. 20% sale price, code FEST10 for 10% off, 10% instant bank discount up to 1,500, loyalty points]
Product margins by category: [paste rows: category, average price, cost, margin]
Who funds each offer: [e.g. bank offer funded by the bank, coupons by the store]
Order limits: [e.g. one code per order, minimum order 999]
Check each combination
Can it be applied together at checkout, technically and by the offer terms.
Discount order: which applies first, and on what amount.
Worst-case final price for the lowest-margin category.
Whether the order is still profitable after shipping and payment fees.
Whether a returned item claws back points or cashback correctly.
Output format
| Offer | Combines with sale price | With coupon | With bank offer | With points |, each cell yes or no.
| Combination | Example order | Final price | Margin left | Allow? |
Recommended rules in five lines or fewer.
Customer-facing offer terms under 150 words, in plain language.
Guardrails
Show all arithmetic so it can be checked.
Flag any combination that sells below cost, even if it is rare.
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.