# Order bumps
Add a one-click companion product inside the same checkout, then test the selected line item, invoice, taxes, coupons, webhooks, and automation context.
Source: /docs/offers/order-bumps
Last modified: 2026-06-19
An order bump is a companion product the buyer can add before payment. In Plandalf, bumps are modeled as offer add-ons, so the selected line item stays attached to the same payment, invoice, webhook payload, and Sequence context as the main purchase.


> **Bumps are not a second checkout**
>

  Use a bump when the extra item belongs in the same buying decision. Use an upsell page when the upgrade should appear after the first purchase step.


## The path


### Choose the companion product


    Pick something that makes the main offer more useful: an implementation kit, audit call, warranty, workbook, template pack, or priority support.


### Add an add-on block


    In the offer editor, place an add-on/order bump block in the payment flow and connect it to the product and price the customer can select.


### Write the short pitch


    Keep the bump copy specific. The buyer should understand the extra outcome without leaving the checkout.


### Run a test session


    Toggle the bump on and off, then confirm totals, selected line items, invoice rows, coupon behavior, and post-purchase automation triggers.


## What to configure


### Bump setup


- `Product` (offer item; required):
    The companion product or service added when the buyer accepts the bump.


- `Price` (price; required):
    The price attached to the selected add-on line item.


- `Default state` (selected | unselected):
    Whether the bump starts selected. Most checkouts should start unselected unless the choice is part of a clear bundle.


- `Select and unselect behavior` (interaction):
    Add-on blocks have select and unselect events so totals and line items can update before payment.


## Good bump candidates


  - [Implementation kit](/docs/offers/products): Templates, launch docs, or assets that help the buyer use the main product.
  - [Priority support](/docs/offers/pricing): A one-time service add-on for a course, template, audit, or setup package.
  - [Extended access](/docs/timers/overview): Extra time, bonus material, or a deadline-bound upgrade attached to the offer.
  - [Related product](/docs/offers/add-ons): A companion product that belongs in the same invoice and fulfillment workflow.


## Test checklist


### Selected totals change


    The visible total should update before the buyer pays.


### Line items are preserved


    The completed session should include the selected bump in `line_items`.


### Coupons still behave correctly


    Confirm whether the coupon should apply to the whole checkout or only specific products.


### Automation receives the context


    Fulfillment, receipts, CRM updates, and internal records should know whether the bump was accepted.


> **Keep the bump tightly related**
>

  A bump should reduce friction, not add a second decision tree. If the customer needs a full explanation, make it an upsell page or a separate offer.


## Related docs


### [Add-ons and variants](/docs/offers/add-ons)


    Understand how optional line items appear in checkout and completion data.


### [Pricing models](/docs/offers/pricing)


    Choose the price model that belongs on the bump.


### [Live events](/docs/sdk/events)


    React after checkout completes with the selected bump context.