Skip to main content

Sell Plans with the Staff App (Kiosk Mode) by PushPress

Here’s a streamlined guide for enabling and using the Kiosk Mode Membership Purchase Feature in the Staff App.

Written by Jessica Hamel

Summary

The Staff App’s Kiosk Mode allows your team to sell membership plans directly at the front desk. In one seamless flow, you can select a plan, collect signatures, and process payment. This makes it easier to convert walk-ins and drop-ins while keeping all revenue and member records synced in Core.


Why use Kiosk Mode to Sell Plans?

  • Faster conversions: Turn a prospect into a paying member in minutes.

  • Seamless experience: Plan → signature → payment in one guided flow.

  • Accurate reporting: All sales, payments, and documents are tied back to the member's profile in Core.

  • Flexible payment options: Support full checkout or QR code hand-off.

  • Family and youth program support: Create sub-accounts for children, spouses, or training partners directly from the checkout flow.


How to Sell Plans in the Staff App

1. Enable Kiosk Mode

  • Open the Staff App.

  • Navigate to Settings.

  • Turn on Kiosk Mode for plan sales.


2. Choose Payment Options

  • Allow one or both of these checkout flows:

    • Full Payment Flow: Enter card payment directly in the kiosk.

    • QR Hand-Off: Generate a QR code so the member can complete checkout on their own device.

    • Tap to Pay: Contactless payments directly in Kiosk Mode using Tap to Pay or a connected Stripe Terminal. Supports both plan sales and retail items.

(Insert screenshot of payment method settings)


3. Confirm Available Plans

  • Make sure the membership plans you want to sell are active.

  • Verify pricing, tax settings, and plan details in Core.

(Insert screenshot of plan list in kiosk view)


4. Walk the Customer Through Checkout

  1. Launch Kiosk Mode on the Staff App.

  2. Prospect selects their membership plan.

  3. Customer completes required documents (waivers, agreements).

  4. Specify who the plan is for:

    • If the plan is for the purchaser, proceed normally.

    • If the plan is for someone else (child, spouse, training partner), member indicates this during checkout.

  5. Create a sub-account if needed:

    • If the recipient doesn't already have a linked PushPress account, a new one can be created in this step.

    • Member enters the recipient's basic information (name, email).

    • The account is automatically linked to the purchaser's profile.

  6. Process payment:

    • If paying in kiosk: enter card details.

    • If using QR hand-off: member scans QR code and finishes checkout.

    • If using Tap to Pay: complete contactless payment at the counter.


5. Verify Confirmation in Core

  • After payment, the new member's profile is automatically updated in Core.

  • For sub-account purchases, the primary member and the new sub-account are linked and visible in both profiles.

  • Plan, payment details, signed documents, and linked account information are all stored in Core.

Sub-Account Creation During Checkout

Members can now create a new sub-account for a child, spouse, or training partner directly during Kiosk checkout without interrupting the flow.

What is a sub-account?

A sub-account is a linked member profile connected to a primary account. This allows one person (parent, spouse, etc.) to manage multiple related member records.

When to use sub-account creation:

  • A parent signing up a child who doesn't yet have a PushPress account.

  • Spouses purchasing plans for one another.

  • Training partners or buddies enrolling together.

  • Youth programs enrolling new participants.

Sub-account creation workflow:

  1. Member selects their membership plan during Kiosk checkout.

  2. When asked "Who is this plan for?", member indicates it's for someone else.

  3. If that person doesn't already have a linked account, member creates a new sub-account on the spot with basic info (name, email).

  4. The new sub-account is automatically linked to the primary member.

  5. Member completes document signatures and payment as normal.

  6. The purchase is assigned to the newly created sub-account, and all data syncs to Core.

Key benefits:

  • Complete the entire signup in one flow—no staff intervention needed.

  • No back-office setup required.

  • Reduces errors from plans being assigned to the wrong person.

  • Streamlines family and youth program enrollments.

  • Works seamlessly with existing QR and landing-page checkout experiences.

Frequently Asked Questions

Can members add a new payment card during checkout?

Yes. In QR hand-off flow, members can add and save a card before completing payment.

Are signatures collected during checkout?

Yes, required documents are signed directly in Kiosk Mode.

Does this support tax calculation?

Yes, checkout totals include tax automatically.

Can a member create a sub-account during Kiosk checkout?

Yes. If the plan is for someone else and that person doesn't already have a linked PushPress account, a new sub-account can be created in the checkout flow.

Who can a sub-account be created for?

A child, spouse, training partner, or anyone whose account should be linked to the purchaser.

Does staff need to create the sub-account from a computer?

No. The entire sub-account creation and plan purchase happens directly on the Staff App tablet during checkout.

What happens after a sub-account is created?

It's automatically linked to the primary member, and checkout continues with the plan assigned to the newly created sub-account.

Troubleshooting

Payment not completing?

Confirm the correct payment method (QR vs card vs Tap to Pay) is enabled.

Missing signatures?

Check that documents are set up and assigned in Core.

Incorrect pricing?

Verify plan details and tax setup before publishing to kiosk.

Sub-account not creating during checkout?

Confirm the recipient's information (name, email) is entered correctly. If the issue persists, verify the primary member account is active and in good standing.

Sub-account appears linked incorrectly?

Check in Core that the accounts are showing the correct relationship. If needed, contact support to verify the link.

Testing tip: Run a test checkout on a staff device before launch, including a test sub-account creation.


Did this answer your question?