The short answer: Squarespace Commerce is built around the order, not the individual attendee. That's the right design for most of what it handles. For events where individual guest details matter, it means you get one name, one email, and one set of details for the buyer. The other guests are invisible until you build a system to find them.
If someone buys four seats for their team, you get one name, one email, one set of answers. The other three are invisible to you. This guide explains why that happens, what it costs you in practice, and what your real options are for collecting what you need from every person walking through your door.
The Midnight Before the Event
I want to tell you about a printer.
When my company, Week of the Website, was doing professional event production alongside website design, we took real pride in running the best check-in experience our clients had ever seen. For galas, nonprofit fundraisers, summits, and food festivals, hospitality wasn't a nice-to-have. It was a core part of what clients hired us for. Guests should feel welcomed from the moment they arrived. Names should be known. Dietary needs should be handled gracefully. Nobody should be standing in a slow line while a volunteer squints at a laptop.
What guests didn't see was what it took to make that happen.
Because we often built event sites on Squarespace, we'd run into the same wall every time. Squarespace only captures the buyer's information at checkout, not each guest's. So if someone bought a table of eight for a gala, we had one person's details and seven unknowns. To collect what we actually needed, including dietary restrictions, accessibility needs, meal selections, and organizational affiliation, we'd send a follow-up email after purchase with a link to a third-party form. Then we'd wait. Then we'd chase. Then we'd reconcile whatever came back against the order list by hand and build a check-in document from scratch.
That document got built at midnight. Because that's when the last stragglers sent in their forms. And then, inevitably, someone would email at 7am: "My guest Maggie is actually bringing her brother now instead of her husband, and he's allergic to dairy."
I own a WiFi-enabled printer, an HP OfficeJet 250 mobile all-in-one to be specific, because we had to reprint check-in lists so close to doors that a regular printer tethered to a desk wasn't going to cut it. We needed to print from wherever we were, whenever the last change came in.
I tell you this not to complain, but because I think a lot of event coordinators reading this have their own version of this story. The frantic spreadsheet. The late-night reconciliation. The morning-of reprint. The volunteer at the door working off a list that was already out of date.
This is what attendee management looks like when your ticketing platform wasn't built for it.
What Squarespace actually captures at checkout
When someone completes a purchase through Squarespace Commerce, here's what you get:
The buyer's name
The buyer's email address
Billing address, if required
Any custom form fields you've added to the product or checkout
That last one sounds promising, and it is, with an important limit. Squarespace does let you add custom fields to a product or checkout form. You can ask for dietary restrictions, t-shirt size, accessibility needs, whatever you need. The problem is those fields apply once per order, not once per ticket.
So when someone buys a single ticket, you're fine. You get their name, email, meal preference, and any other fields you set up. But when someone buys four tickets, which happens constantly at galas, corporate events, team workshops, and anywhere group purchases are common, you get one set of answers for the entire order. One meal choice. One dietary note. One accessibility request. For four people.
Which four people? You don't know. You have the buyer. The other three are a mystery until you go find them.
For a 20-person workshop, this is manageable if annoying. For a 200-person fundraising gala where half the guests were brought by corporate table sponsors, it's a logistical problem that has to be solved before anyone walks in the door.
The cascade: how one gap becomes three problems
The missing per-guest data isn't one inconvenience. It creates a cascade that compounds as your event gets closer.
Problem 1: you don't know who's coming
Your guest list is incomplete. You have buyers, not guests. For any event where individual identity matters, where you need to greet people by name, match them to seats, or make sure the right person gets the right meal, you're working from a partial picture the moment tickets are sold.
The workaround is almost always a follow-up email with a separate form. Which means asking guests to do something after they've already completed a transaction. Response rates on those forms are rarely 100%. Some people miss the email. Some ignore it. Some fill it out for themselves but not their plus-ones. And every response that comes in is a reconciliation task.
Problem 2: your data lives in five different places
Even with good form completion, you now have guest information scattered across:
Squarespace order confirmations, holding buyer info
Your follow-up form responses, in a separate system
Email threads from people who replied directly instead of using the form
Last-minute change requests sent by email or text
The spreadsheet you built by hand trying to reconcile all of the above
None of these talk to each other. If someone cancels a ticket, the cancellation is in Squarespace but the form response is still in your Google Sheet. If someone updates a dietary restriction at the last minute, that update is in an email you have to find and apply yourself.
This is the data fragmentation problem, and it isn't abstract. It's the midnight spreadsheet. It's the reprint. It's the volunteer at check-in asking "what's your last name?" while a line forms behind the guest.
Problem 3: check-in has no foundation
Check-in is where all of this comes to a head. A smooth check-in needs one thing above all else: a single, accurate, current list of who is supposed to be there and what you need to know about them.
When your data is scattered, that list doesn't exist until you build it by hand. And because you're building it from multiple sources, it's already slightly wrong before the event starts. Guests make last-minute changes, so it gets more wrong as the day approaches.
The result puts unnecessary pressure on your staff, slows entry, and occasionally produces the exact hospitality failure you were trying to prevent: a guest with a dairy allergy handed the wrong meal because the update came in after the list was printed.
The workarounds people actually use, and their honest tradeoffs
If you're managing events on Squarespace without an extension, you're probably using one of these. They all work, to a degree. They all have real costs.
The follow-up form
Send a post-purchase email with a link to a Google Form, Typeform, or JotForm asking for guest details. Collect the responses. Reconcile by hand.
What works: Flexible. You can ask for anything. Works with any ticketing setup.
What breaks: Requires a second action from buyers after purchase. Response rates are inconsistent. Each response is a reconciliation task. Changes come in by email and have to be tracked separately. The form doesn't know about cancellations.
Custom checkout fields, per order
Add custom fields to your Squarespace product or checkout asking for dietary restrictions, accessibility needs, and other details. Capture it at the point of purchase.
What works: No extra friction. Guests answer at checkout, no follow-up needed. Data lives in Squarespace orders.
What breaks: Fields apply once per order, not per ticket. If someone buys multiple tickets, you get one answer for all of them. Where group purchases are common, this doesn't solve the problem.
A separate registration platform
Skip Squarespace ticketing entirely for guest data. Use a dedicated event registration platform such as RSVPify or Eventbrite that handles per-guest data natively.
What works: These platforms are built for this. Per-guest fields, management dashboards, check-in tools, all of it exists.
What breaks: Now you're off Squarespace. Checkout happens on another platform. Your brand consistency breaks. For nonprofits especially, you're adding per-ticket fees back into the equation. You've traded the data problem for the brand fragmentation problem.
Manual spreadsheet reconciliation
Export your Squarespace orders, combine with form responses and email updates, build a master check-in document. Repeat for every event.
What works: Total control. You know exactly what's in the document because you built it.
What breaks: It's midnight. You're printing from a mobile printer because the last change came in an hour before doors. This is not a system. This is survival.
What good Squarespace attendee management actually looks like
The goal isn't to patch the gaps. It's to have one system that handles guest data from purchase through check-in, without asking guests to do extra work or asking you to reconcile five sources the night before.
Here's what that requires:
Per-ticket registration fields. When someone buys multiple tickets, each ticket should trigger its own set of fields. Not per order, per ticket. The buyer fills out their own information plus prompts for each additional guest. You end up with individual records for everyone rather than one record for the group.
This matters most where individual details are operationally significant: dietary restrictions that affect catering, accessibility needs that require advance preparation, meal selections for plated dinners, organizational affiliation for networking or badges.
A single dashboard. All guest information in one place, connected to the original order, updated as things change. If someone cancels, their record updates. If someone changes a meal preference, that change is reflected in the same system you're using for check-in.
Searchable, exportable lists. On event day, your check-in team needs to find names fast. A searchable list, filterable by ticket type, checked-in status, or any custom field, means the line moves. Exportable to CSV means you can print a backup, generate a badge list, or hand off to a caterer without rebuilding anything.
Check-in tools connected to the real data. Check-in should be an action taken against your guest list, not a separate process running off a printed document. When you check someone in, their status updates. When a cancellation happens, it's reflected. The check-in tool and the guest list are the same system.
Automated confirmations that set expectations. Where you need details from group purchases, the confirmation email is your best chance to collect them while purchase intent is highest. An automated email that goes out immediately after purchase, with clear instructions, will get better response rates than a follow-up sent hours or days later.
What Eventually does differently
Eventually is a Squarespace-first extension built by Week of the Website that adds event ticketing and attendee management to Squarespace Commerce. This problem is one of the core reasons we built it, because we lived it, and because it's solvable if you design for it from the start.
Checkout still happens through your Squarespace store, using Squarespace Payments. But when a buyer purchases multiple tickets, Eventually prompts for individual details for each one rather than once for the order. Dietary restrictions, accessibility needs, meal selections, organizational affiliation, whatever fields you've set up for that event, collected per ticket at the point of purchase.
Those responses feed a single dashboard. Searchable. Exportable to CSV. Connected to QR code check-in that updates as you go. If someone cancels a ticket, their record reflects it. If a guest updates their information, it's in the same place your check-in team is working from.
For nonprofit and community organizations, the free tier covers free events and RSVPs. Not everything is a paid ticket, and collecting information for a free community gathering shouldn't require a workaround any more than a paid gala should.
If you'd rather not change platforms
Maybe you have an event in three weeks and switching anything right now is out of the question. Here's the most functional version of the workaround:
Add custom checkout fields to your Squarespace product for the buyer's own details: dietary restriction, meal choice, accessibility needs. This gets you clean data for single-ticket purchases.
In your order confirmation email, include a clearly worded prompt for group purchasers: "Bought tickets for others? Please complete their details here," with a link to a form. Make this the first thing in the email, not buried below the order details.
Build your form to ask for the order number, each guest's name and email, and the specific fields you need per person. Requiring the order number helps with reconciliation.
Set a firm deadline for submissions, something like 48 hours before the event, and send one reminder to anyone with a multi-ticket order who hasn't submitted.
Build your check-in document from a merged export of Squarespace orders and form responses. Keep it in Google Sheets so you can update it from any device and print the final version as late as you need to.
Is this ideal? No. It's the midnight spreadsheet, slightly optimized. But it's the most reliable version of the workaround, and if you're running an event next month, it'll get you through.
Just maybe invest in a WiFi printer.
The bottom line
Squarespace's per-order limitation is real, and it affects everyone running events where individual guest information matters, which is most serious events. It isn't a bug or a setting you can change. It's how the commerce system is built.
The workarounds work, with real costs in time, data quality, and the kind of late-night labor nobody accounts for in an event budget. The better answer is a ticketing system designed to collect details per ticket at the point of purchase, feed them into one dashboard, and connect that directly to check-in, so the list you're working from on event day is accurate, complete, and current.
That's what Eventually does. Because nobody should be reprinting their check-in list at midnight.
Keep reading:
→ How to Sell Event Tickets on Squarespace
→ Recurring Events on Squarespace: Why It's So Hard and What to Do About It
Collect details from every guest, check them in with a QR code, and keep checkout on your own site. Build your first event at eventuallyticketing.com.