> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/holiday-playbooks/bfcm/5-offer-planning.md). # BFCM #5 - Offer Planning to Maximize Conversions Explains offer strategies, like tiered discounts and bundles, to plan BFCM promotions that convert. Let’s talk offers - because the *right* promotion is what turns window-shoppers into buyers during BFCM. You don’t need a dozen campaigns. You need 1–3 **clear, irresistible offers** that are easy to understand, hard to resist, and designed to convert. ### Offer Strategy: What Works Best * **Tiered Discounts** Encourage bigger baskets with spend-based offers (e.g. $10 off $75 / $25 off $150) * **VIP Early Access** Let your top customers shop first - they convert faster and spend more * **Bundles & BOGOs** Great for moving slow SKUs, showcasing value, and simplifying decisions * **Gift with Purchase** Easy to implement and proven to boost loyalty (think: free sample, tote, or extra item) ### Set These Up in Recart Use Recart’s built-in discount tools to generate and apply these offers in minutes. [How to Generate Discount Codes in Recart](/discounts/create-discount-codes-in-recart.md) Once created, apply your discount or redirect users from the **Success Step** of your popup CTA: * Redirect to a landing or product page * Auto-apply a discount code * Add a product directly to the cart * Append UTM or tracking info to the URL [How to Customize Your CTA Button in Popups](/list-growth/popups/customizing-your-cta-button-in-popups.md) These options help you close the loop — from offer to conversion — with less friction. ### Finalize Your Offer This Week If you haven’t set up your BFCM offer yet, now’s the time. Keep it simple, clear, and compelling — and make sure it’s live across your popups and flows. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.recart.com/holiday-playbooks/bfcm/5-offer-planning.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.