FBT Button Variables and Pricing Display
What this setting controls
Your FBT (Frequently Bought Together) button is the main call-to-action shoppers click to add the bundle (or suggested items). You can update the button text and insert price variables so the button can show live pricing like a discounted price, the original price, or how much the shopper saves.
Where to edit the FBT button text
Common variables you can use
The exact variable names can differ by setup, but most stores use variables like these:
- Discounted price: the price the shopper will pay after the FBT discount
- Original price: the total price before the discount
- Saved amount: how much money the shopper saves
- Saved percentage: the percent the shopper saves
CTA templates that stay clear
Use short text that answers: what happens + what it costs. Here are clear patterns you can copy and then swap in your variables.
Best for most stores (simple)
- Add bundle — {discounted price}
- Add all to cart — {discounted price}
When you want to highlight savings
- Add bundle — Save {saved amount}
- Add bundle — Save {saved percentage}
When showing both prices (use carefully)
- Add bundle — {discounted price} (was {original price})
Keep messaging clear (rules of thumb)
- Keep it under one line on mobile. Long buttons get cut off and can lower clicks.
- Use one main number. Either show the discounted price OR the savings. Too many numbers can confuse shoppers.
- Match the offer type. If your FBT adds multiple items, use “Add bundle” or “Add all”. If it adds one extra item, “Add to cart” may be clearer.
- Avoid unclear wording like “Get deal” or “Buy now” when the shopper is adding items to the cart (not checking out yet).
Examples: good vs confusing
- Add bundle — {discounted price}
- Add all — Save {saved amount}
- Add bundle — Save {saved percentage}
Why these work: short, one main value, and clear action.
- Buy now — {original price} {discounted price} {saved amount} (too many numbers)
- Claim discount (doesn’t say what gets added)
- Add — {saved percentage} (missing the final price)
These can confuse shoppers or look like an error when the button is too long.
Formatting tips (so it looks professional)
- Use the right currency formatting: let the variable handle it (don’t type a $ sign before a price variable unless your app tells you to).
- Use parentheses for “was” pricing: it’s easier to scan (example: “{discounted price} (was {original price})”).
- Do not add extra math in the text. If you need “per item” or “each”, use a shorter layout or show that information elsewhere in the FBT card.
Quick checklist before you publish
- Button text fits on mobile (no cut-off)
- The discounted price matches the offer you expect
- Savings show only when a discount is actually applied
- Your message matches the action (“Add bundle” vs “Checkout”)