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.

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

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 & Sites.

  • 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

If you disconnect your Squarespace site and later reconnect it:

  • Squarespace will need to re-link products to your events.

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

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

What doesn't sync

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

  • Sync events or ticket types themselves — you create and manage those in Eventually.

  • 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.

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?