What is an order bump, in plain English?

What the buyer sees

One tick box on the order form, near the payment button. It names a second product and its price.

systeme.io describes it as a promotional offer displayed as a small checkbox, appearing on the order form before the payment is finalised. It is meant for something that goes with the main order, not something unrelated.

What you have to set up

On the order form page there is an Add order bump button. It asks for two things.

• An offer type. Physical product or digital product.
• A resource. What the buyer gets. For a digital product that is a course, a course bundle, a tag, or a community.

Then it needs a price. An order bump takes one price and only one. The order form itself and an upsell page both accept several price plans, so this limit belongs to the bump alone.

The step people miss

Setting the bump up in the page settings does not put it on the page. It stays invisible until you open the editor and drag the Order bump element into the body of the page.

A bump that is fully configured and still not showing is usually a missing element, not a broken setting.

What it will not sell

A calendar event cannot be the resource on an order bump. Picking one returns an error. The main order form does allow calendar events, so the restriction belongs to bumps specifically.

Physical products can be sold, but shipping is yours to arrange. systeme.io does not handle fulfilment.

What the charge looks like

The main offer and the order bump go through as two separate transactions, not one total.

One side effect is worth knowing before a customer emails about it. The payment window from a processor such as PayPal may show only the price of the main offer. systeme.io lists that as normal behaviour. Both are still charged.

Knowing who took it

Set a tag as the bump's resource and everyone who ticks the box gets that tag. An automation rule triggered by Tag assigned can then send them an email or add them to a campaign.