Eventually Ticketing
Integrations

How Squarespace sync works

When your Squarespace site is connected to Eventually, data syncs both ways automatically. This keeps your registrations, inventory, and Squarespace product stock in sync without manual updates.

What syncs automatically

For connected sites, Eventually keeps the following in sync:

  • Orders: New orders placed through Squarespace Commerce are imported into Eventually as registrations.

  • Registrations: Registrations added in Eventually update your Squarespace product inventory for the whole event.

  • Cancellations and refunds: When a registration is canceled or refunded in Eventually, Squarespace stock for every ticket variant on that event is refreshed.

  • Capacity changes: If you adjust Total Event Capacity, a ticket limit, or a ticket capacity mode in Eventually, Squarespace stock updates to match.

  • Product fallback links: The stored checkout URL for each paid event is refreshed daily and after paid checkouts so it does not go stale when products move or domains change.

How Squarespace stock is calculated

Squarespace product stock is the remaining seats Eventually pushes to each ticket variant in your Squarespace store. That number is based on active registrations only, and for Standard seat tiers it also respects shared room capacity. During ordinary sales and synchronization, Eventually never raises a finite variant's stock above the quantity Squarespace already holds, so a sale or other decrease can't be undone by a stale registration count. Genuine releases (refunds, cancellations, removing a ticket tier, or raising capacity) can still restore or increase stock when seats actually free up.

A linked class that has ended is the exception: it stops selling on Squarespace and its stock stays at zero. Squarespace stock for a linked class is set to zero for every ticket variant linked to a Squarespace product when the class reaches its end time, or, if the class has no end time, at the end of its start day in the event's own timezone. Legacy multi-date classes close after their last date, and tiers left unlimited receive zero stock like every other linked tier. Past classes that were already linked to Squarespace are closed automatically the same way, with nothing to configure. After a class closes, refunds, cancellations, capacity changes, and other inventory syncs still refresh its variants, but the stock they push stays at zero, so freed seats do not put the class back on sale in Squarespace. Rescheduling the class into the future releases its Squarespace stock and puts it back on sale; moving it back to a past date closes it again on the next sync. This is a Squarespace stock rule only: the class's status, its event page, and your widget are unchanged.

When you remove a ticket tier, its Squarespace store variant is marked sold out (set to zero availability) rather than deleted, so it stays recoverable even when it has no active registrations. Add the tier again to restore it.

For each Standard seat ticket type, the stock pushed to Squarespace is the lower of:

  • Seats left under that tier’s own Ticket Limit (if you set one)

  • Seats left under the event’s Total Event Capacity after counting active registrations on all Standard seat tiers

With Total Event Capacity blank, the shared room comes from the ticket-type limits instead when every Standard seat ticket type has its own Ticket Limit. Active seats without a ticket type, such as redeemed show passes, host comps added without a tier, store-order lines that did not map to a ticket type, or moves with no destination ticket type, count against that room. Squarespace stock excludes the seats those registrations have consumed, so paid sales cannot fill room capacity they have already taken.

If a tier has no ticket limit (left blank for unlimited) but the event has a total capacity, Squarespace still receives a finite remaining count for that tier. The cart blocks over-buys up front instead of letting a buyer pay for more seats than the room has left.

Virtual and Add-on tiers do not use the shared room capacity. Their Squarespace stock follows only their own ticket limits (or stays unlimited when no limit is set).

Example: an event capped at 14 seats with one unlimited General Admission tier and 12 active guests shows 2 remaining in the Squarespace cart, not unlimited stock. Two Incomplete holds on that same event do not lower the pushed number further.

Active registrations vs pending holds

Only active registrations reduce the stock Eventually pushes to Squarespace. An Incomplete checkout hold still blocks availability inside Eventually (widget, sold-out checks, and host capacity checks), but it does not lower the stock number shown in Squarespace checkout.

That split is deliberate. Squarespace validates the buyer’s cart against one stock number per product variant. If pending holds reduced that number, a buyer who already holds the last seats could fail checkout as out of stock.

Creating or expiring a pending hold does not by itself refresh Squarespace stock, because the active-only count has not changed. Completing checkout, free RSVP, manual guest add, cancellation, refund, capacity edit, or a ticket move does refresh it.

When stock refreshes for the whole event

When active occupancy changes, Eventually re-syncs every ticket variant on the event in one update. Shared room capacity couples standard tiers together, so a sale or cancellation on one tier can change the remaining stock shown for the others.

Actions that refresh Squarespace stock for the event include:

  • Paid orders imported from Squarespace

  • Free RSVP registrations

  • Manually added guests

  • Cancellations and refunds that free seats

  • Edits to total capacity, ticket limits, or capacity mode

  • Changing a guest’s ticket tier or moving them to another class

For more on capacity settings, see Set event capacity and ticket limits. For incomplete holds that block seats only inside Eventually, see A pending registration is holding a seat.

Prerequisites for sync

Automatic sync only works when:

  • Your Squarespace site is connected to Eventually via Settings → Payments → Squarespace Commerce.

  • Your event and ticket types are linked to Squarespace products.

If your site is not connected, orders and registrations will not sync between platforms.

After disconnecting and reconnecting

What happens after a disconnect depends on which store you connect next: reconnecting the same Squarespace site keeps your existing setup, while connecting a different store starts that store fresh.

If you reconnect the same Squarespace site:

  • Each previously synced event is re-linked to its existing Eventually-created product when there is a unique match, instead of creating a duplicate product. If no unique match is available, Eventually creates a new product.

  • The image links for your event covers and galleries are kept, so images are not re-uploaded.

  • Sync status and connection IDs may be cleared, requiring a refresh of the connection.

If you connect a different Squarespace store, Eventually clears the old store's event and product links so the new store starts clean. Your events sync to the new store as new products, and their cover and gallery images upload to the new store.

To refresh the connection after reconnecting, go to Settings → Payments → Squarespace Commerce and follow the prompts to re-authorize your Squarespace site.

What doesn't sync

Sync applies to orders, inventory, and event and ticket data between Eventually and Squarespace for connected sites. It does not:

  • Manage events or ticket types from Squarespace: you create and manage those in Eventually. The sync pushes each event to Squarespace as a Squarespace Commerce product and your kept ticket types as product variants, including their names and prices.

  • Sync attendee custom field data back to Squarespace: that data lives in Eventually.

  • Apply to disconnected sites or sites that were never connected.

  • Push pending Incomplete holds as reduced Squarespace stock; those holds stay on Eventually surfaces only.

Ticket SKUs

A ticket tier's SKU lives in Eventually, and Eventually pushes it to the tier's Squarespace product variant. Saving a SKU on a tier queues an event-level sync, and the push runs in the background. While the push is pending, buyers keep using the last SKU confirmed in your Squarespace store, so checkout never fails against a value the store does not carry yet.

If you edit a variant's SKU directly in Squarespace, Eventually's next sync overwrites that edit. For the store to carry a custom SKU, enter the same value on the ticket tier in Eventually. For the field rules, see Set a custom SKU for a ticket type.

Events created before connecting

Published events that existed before you connected your Squarespace site are included in sync automatically. An hourly background sweep backfills any missed events so they appear in your Squarespace store without requiring a manual reconnect.

Same-order duplicate registrations

If a buyer checks out rapidly multiple times on the same Squarespace order, the sync may encounter duplicate pending registrations for the same attendee and ticket tier. Eventually detects these duplicates automatically during order sync, discards the redundant reservation, and releases the held seat back to inventory. The rest of the batch continues processing normally. Repeat purchases across different orders are not affected and still create separate, valid registrations.

Was this helpful?
Was this helpful?