If your Squarespace connection shows as lost, stuck, or not syncing, the issue is usually an expired authorization, an incomplete reconnect, or a missing store page configuration. Reconnect through Settings → Payments & Sites and re-authorize your Squarespace site to resolve most of these states.
Eventually displays this banner when the Squarespace OAuth connection expires or is revoked.
Cause: The authorization Eventually uses to communicate with Squarespace has expired or been revoked by an admin change in Squarespace.
Fix:
Go to Settings → Payments & Sites.
Under Squarespace Commerce, click Connect Your Squarespace Site.
Log in to Squarespace and select your site.
Click Allow to re-authorize.
New ticket orders will not sync until you complete the reconnect.
If your site status remains on “CONNECTING” after you started the authorization flow, the redirect or API response was blocked or delayed.
Cause: Browser cookies or privacy settings blocked the redirect from Squarespace back to Eventually. Squarespace API rate limiting can also delay connection completion.
Fix:
Refresh the Payments & Sites page.
Wait a few minutes and refresh again if Squarespace API rate limiting is in effect.
If the status is still stuck, try authorizing again in an incognito or private browser window.
If your site shows “NOT CONNECTED,” the authorization flow never completed or the connection was revoked.
Cause: The redirect back to Eventually failed, or an admin change in Squarespace revoked the integration.
Fix:
Go to Settings → Payments & Sites.
Click Connect Your Squarespace Site.
Complete the full authorization flow without closing the window.
Make sure to select the correct site and grant all permissions.
If you disconnected your Squarespace site and then reconnected it, product links and sync metadata may have been cleared.
Cause: Disconnecting a site removes the cached connection IDs and product links. Reconnecting restores the authorization, but the links between Squarespace products and your events must be rebuilt.
Fix:
Edit each paid event in Eventually.
Confirm that the Squarespace product is linked, or re-save the event to trigger the link.
Check that new test orders appear in your event registrations.
See How Squarespace sync works for what syncs automatically.
If Squarespace product sync is failing even though the connection appears active, the store page may not be configured in Squarespace Commerce.
Cause: Eventually uses a cached store page ID to sync products. If the store page is missing or was removed, the sync path breaks.
Fix:
Log in to your Squarespace admin and confirm Commerce is enabled and a store page exists.
In Eventually, look for the banner that says No Squarespace store page found. Click I’ve added one — check again to recheck and trigger sync automatically.
If the banner says We still don't see a published store page on your Squarespace site, verify the store page is published, then click check again once more.
You no longer need to disconnect and reconnect just to pick up a newly added store page.
An amber banner appears in Eventually when your Squarespace site is connected but has no cached store page, and at least one published event needs a store product to sell tickets.
Cause: Eventually needs a Commerce store page in Squarespace to create products for paid events, or for free events that are opted into store processing.
What you see:
Owners and admins see the message Your ticketed events can’t sell tickets until you add a Store page in Squarespace with a button labeled I’ve added one — check again.
Other team members see the notice, but the button is hidden.
Fix:
Log in to your Squarespace admin and add a published Commerce Store page.
In Eventually, click I’ve added one — check again on the banner.
If the store page is found, Eventually caches it and syncs your events automatically. You’ll see the message Store page found — syncing your events to Squarespace now.
Recovery happens two ways. Clicking the button triggers an immediate recheck. If you do nothing, an hourly background sweep also checks for a store page and syncs events automatically once one is detected.
Free-only sites that do not use the Record free tickets in your store setting will not see this banner.
Symptom: A buyer who checked out rapidly on the same Squarespace order left multiple near-identical pending registrations, and some paid seats remain stuck as Pending or Incomplete.
Cause: Rapid repeat checkouts on the same order can create duplicate pending batches. Previously, the sync could abort mid-batch when it tried to activate a duplicate that was already ticketed on the same order, leaving other paid seats stranded.
Fix: Eventually now automatically detects same-order duplicate pending registrations during sync. The redundant reservation is discarded and its seat is released back to capacity. The rest of the batch continues syncing normally, so other paid seats should complete without manual intervention. If a seat still looks blocked after sync completes, check the Guests tab for any remaining Incomplete rows and remove them manually.
Repeat purchases across different orders still work as before. Each distinct order creates its own separate registration.
Connect your Squarespace site — First-time setup and connection flow
How Squarespace sync works — What syncs automatically and what does not
Common checkout issues and solutions — Payment and checkout troubleshooting
