Selling add-ons alongside race entries
Photo packs, merchandise, meals, parking, and donations sold during registration.
On this page 5
What can I sell as an add-on?
Seven kinds, and they behave the same at checkout:
- A photo pack, sold before race day at a lower price than photos cost afterwards.
- A print-on-demand product.
- A donation to your charity partner.
- A meal ticket.
- Parking.
- A shirt upgrade.
- A custom fee for anything the list does not cover.
Should an add-on be per entry or per order?
Per participant for anything each runner receives: a shirt upgrade, a meal, a photo pack. Someone registering three people gets asked three times.
Per order for anything the group shares: one parking pass, one donation. It is asked once no matter how many entries are in the cart.
Getting this wrong is the most common add-on mistake, and it shows up as either three parking passes or one meal for a family of four.
How do I retire an add-on without deleting it?
Four statuses, same idea as ticket types:
- Active, on sale.
- Hidden, not shown, still configured.
- Closed, visible but no longer selling.
- Archived, out of the way entirely.
Use closed for a meal that sold out and archived for last year's shirt.
How do I know what to hand out on race day?
Add-ons carry a fulfilment state you update as you go, so the roster is the single list of who paid for what. Export it before race day and take it to the tent rather than working from order emails.
Do add-ons change what the athlete pays PodiumBase?
No. Add-ons are your revenue on your Stripe account, settled the same way entries are. See how race directors get paid.
Set your add-ons up in your organization admin.