Choose the outcome before the mechanism.
Decide whether the offer belongs to everyone viewing a product, one customer group or a qualifying basket. Define the dates, eligible products and what can combine with it. The mechanism should implement that decision, not define it accidentally.
A sale price is visible as a product price. A coupon changes a qualifying purchase when applied. An automatic rule needs a supported way to evaluate the basket or customer. Check the specific extension and checkout compatibility before choosing it.
| Route | Suitable starting point | What to check |
|---|---|---|
| Sale price | A product offer for eligible visitors | Schedule and variation prices |
| Entered coupon | A customer receives a specific code | Restrictions and use limits |
| Automatic rule | A qualifying basket receives a benefit | Evaluation, exclusions and checkout support |
| Custom implementation | A specific unsupported requirement | Maintenance, testing and responsibility |
Make the exclusions part of the offer.
Check minimum spend, specific products, sale items, individual use and usage limits. A condition that exists in the campaign text but not in the actual rule will create a poor customer experience.
Keep shipping separate from the product discount. Free-shipping eligibility may be calculated before or after the coupon, depending on its setting. A customer should be able to understand the total benefit instead of discovering an unexpected delivery charge at the end.
Test the baskets that must not receive it.
For a fictional DYMR offer, give a defined benefit on eligible tees within a chosen period. Test a qualifying tee basket, an excluded cap-only basket and a basket containing an already-discounted item. Then test the interaction with another coupon.
Write the expected result for each case before running the test. If a basket changes, confirm the benefit recalculates correctly. Try a guest and an eligible account where the offer depends on identity. Check the resulting order, not just the displayed message.
Choose one implementation and review it end to end.
Avoid overlapping tools applying the same benefit twice. Identify the rule owner, test in staging and check product, basket, checkout and order details. Use the documented controls rather than a code snippet from an unrelated version.
After activation, review the actual response and exceptions. A larger discount total does not by itself mean the campaign worked better. Compare suitable purchases, returns and contribution, using consistent definitions.