Choose the right promo mechanic

choose the right promo mechanic use this page when planning a window in promo planner and deciding whether default, n+1, multibuy, or bundle best fits the customer action and pricing structure you need which promo mechanic should i use? choose the mechanic that matches the customer action you want to reward a simple promotional price, one fixed threshold, multiple quantity tiers, or a defined product combination create the resulting window in promo planner docid\ swfaxzwu2fj8vbgay6dou , then assess its expected effect in promo analytics docid\ pkwefzyh06ygitzc9iepm before finalizing the promo plan attribute default n+1 multibuy bundle choose it when one promo price or discount % is enough one fixed purchase threshold is the offer prices need to vary by basket quantity a defined product combination is the offer customer action buy the promoted product at the promotional condition reach the fixed threshold buy multiple units to reach a tier buy the products together price structure single promo price or discount % single threshold based offer base price plus one or more discounted tiers a price for the defined product combination best planning signal need for a simple promotional price a clear single threshold quantity in basket distribution products that customers should purchase together avoid when the offer needs a threshold or quantity tiers you need different prices at several quantities customers rarely buy multiple units in one basket the value is really a single product discount or quantity tier choose by the offer you need to communicate default use default when the promotion can be expressed as one promo price or one discount % this is the right starting point for a conventional product promotion without a required basket quantity or product combination use linked products when several products in the window must share the same promo price or discount % linked products are required for the promo simulator to run in multi product windows choose default over n+1 or multibuy when the customer should receive the offer without first reaching a quantity threshold n+1 use n+1 when the promotion has one fixed purchase threshold pick it when the threshold itself is the message you want customers to understand and operational teams to execute choose n+1 over multibuy when there is only one threshold if the price or reward must change as the basket quantity increases, use multibuy instead multibuy use multibuy when customers can receive different prices at different basket quantities a multibuy offer has a required base price and one or more discounted tiers, with each tier pairing a minimum basket quantity and a tier price check promo analytics docid\ pkwefzyh06ygitzc9iepm before setting thresholds use quantity in basket breakpoints near quantities customers already buy together; do not add tiers merely because more tiers are available review the resulting tier level margin, market positioning, and sales contribution in multibuy pricing docid\ iyuhdqzuhm2uwym0i5egb choose multibuy over n+1 when the commercial objective requires a progression across quantities rather than one fixed threshold bundle use bundle when the offer is built around a defined set of products purchased together choose it when the intended customer action is to combine products, not to buy more units to reach a quantity tier choose bundle over default when the relationship between products is essential to the offer choose multibuy instead when the main incentive is basket quantity for the same or related products validate the choice before finalizing set the window in the relevant section of the promo plan, including the correct dates and zone scope use promo simulation in promo analytics docid\ pkwefzyh06ygitzc9iepm to compare expected sales during promo with without promo under the selected assumptions review both expected uplift and cannibalization headline revenue can look attractive even when sales shift away from other products in the same category for multibuy, confirm the base price, every minimum basket quantity, and every tier price in multibuy pricing docid\ iyuhdqzuhm2uwym0i5egb check tier level margin and active validity before the offer takes effect common pitfalls choosing multibuy for a product that customers almost always buy one unit at a time; check quantity in basket first using n+1 when the offer actually needs different values at several quantities; use multibuy tiers instead treating a bundle as a quantity offer when the intended value is a product combination, or vice versa creating a multi product default window without linked products, then expecting the promo simulator to run reviewing uplift without cannibalization, which can overstate the promotion’s net commercial value