How sponsors browse and claim packages

Edited

Overview

Sponsors discover packages either on your public storefront or through a direct link sent by your team. Claiming flows differ slightly between online and reservation payment modes, but the experience is unified through the cart.

Where sponsors see packages

  • Your chamber storefront — featured in the Packages tab and surfaced on event pages when relevant.

  • The sponsor account dashboard — under Available packages.

  • Direct claim links delivered by email send.

Step-by-step: Claiming online

  1. Sponsor opens the package page and clicks Add to cart.

  2. Cart shows each child sponsorship as a line item with the package discount applied.

  3. Sponsor proceeds to Checkout, enters payment via Stripe, and submits.

  4. Order status moves pendingcommittedcompleted after Stripe confirms the charge.

  5. Sponsor receives a receipt email with all included sponsorships listed.

Step-by-step: Claiming in reservation mode

  1. Sponsor adds the package to the cart and clicks Reserve.

  2. Order is created in committed status with no payment captured.

  3. Chamber admin receives a notification and can mark the order paid externally when funds arrive.

Tips & best practices

  • Make sure the package description spells out exactly which sponsorships are included to reduce inbound questions.

  • If a sponsor has unused first-rights credits, those apply automatically to qualifying child sponsorships in the package.

FAQ

Can a sponsor partially claim a package?
No. Packages are all-or-nothing. To split, build separate packages or sell individual sponsorships.

What if a sponsor already owns one of the child sponsorships?
Chamberly warns at checkout but allows the purchase since some sponsors want multiple slots.

Related articles

  • Publishing and sending packages

  • Reservation mode (no payment required)

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.