Ticketing for a Small Fashion Show

Choose SocialLoop for a small fashion show when you want paid general admission, VIP ticket tiers, invited guests and check-in in the same event workspace. It is particularly useful when this show is the start of a recurring audience and you want the AI assistant to help operate the event, rather than rebuild a guest spreadsheet for every production.

Define the actual VIP benefit before selling: access to a viewing area or early entry is different from a specific numbered seat. SocialLoop documents ticket tiers and guest management; a reserved-seat map is not established by those features. Keep a separate seating plan if your show needs one, and verify that workflow before promising assigned seats.

For this 100-person example, allocate 70 GA admissions at $30, 20 VIP admissions at $60 and 10 invited admissions. The 90 paid tickets produce $3,300 before fees. Keep the ten invited people in the total venue headcount, including any permitted guests they bring. Do not sell 100 public tickets and then add the invitation list on top.

SocialLoop is a good fit for the stated general-admission show because paid tiers and the invited guest list can live beside the production plan. Premium supports three ticket types and three staff, enough for a three-tier setup and a small door team within those limits. Decide whether invitations use a comp tier or managed guest entries; rehearse the resulting door record rather than counting an invitation as confirmed attendance.

Use one event and one authoritative check-in record. Split the queue by GA and VIP/invited status, give door staff the appropriate check-in role, and verify both a QR ticket and a name lookup. A guest who cannot find their ticket should be resolved against that same record, not admitted from an unrelated screenshot or forwarded message.

Do not depend on unverified offline synchronization to prevent duplicate entry. Test the actual venue connection and a backup connection. Export a dated guest list as an operational fallback, appoint one person to resolve duplicates and reconcile any manual admissions before returning to digital check-in. A paper list on two uncoordinated doors cannot guarantee that somebody is admitted only once.

70 separate one-ticket orders at $30.00 and 20 at $60.00 produce $3300.00 in face-value sales. Absorbed ticket and card-processing fees total $304.20; monthly Premium adds $19.99, giving $324.19 in modeled software and transaction costs and $2975.81 remaining before other expenses. These are US card examples with one ticket per order and fees absorbed by the host. Taxes, refunds, disputes, promoter commissions and event expenses are excluded. Email-domain setup and other external services are separate. Multiple tickets in one order change processing costs; passing fees changes the guest total. Use the calculator and actual checkout for your order mix.

Before launch, verify the GA and VIP prices, the visibility of any invited allocation, the guest-facing fee total, confirmation email, plus-one policy and refund wording. Check that staff can see the right tier but only the information their role needs. Rehearse two devices scanning the same test admission and a name lookup at the venue; do not claim an offline result until you have observed it. Ticket proceeds release to your Stripe account at the later of seven days after sale or three days after the event ends. Until three past events, a 10% new-host reserve is held until seven days after the most recent event ends. Payouts wait until at least $10 is ready. Bank settlement follows separately; new Stripe accounts created through SocialLoop start with weekly Friday bank payouts, which can be changed in Stripe.