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.
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
-
Pick something that makes the main offer more useful: an implementation kit, audit call, warranty, workbook, template pack, or priority support.
-
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.
-
Keep the bump copy specific. The buyer should understand the extra outcome without leaving the checkout.
-
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
Productoffer itemrequiredThe companion product or service added when the buyer accepts the bump.
PricepricerequiredThe price attached to the selected add-on line item.
Default stateselected | unselectedWhether the bump starts selected. Most checkouts should start unselected unless the choice is part of a clear bundle.
Select and unselect behaviorinteractionAdd-on blocks have select and unselect events so totals and line items can update before payment.
Good bump candidates
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
Builder context
Build the offer beside the docs.
These pages explain the setup details. The matching product surfaces show where products, prices, checkout layout, invoices, and automation live in the app.