Set a custom SKU for a ticket type
Each ticket tier has an optional SKU field. Leave it blank and Eventually uses its own generated SKU; enter a value and Eventually pushes it to the tier's Squarespace product variant so your Squarespace sales reports can segment tickets by your own product code. The field is available on every plan.
The SKU is reporting metadata only. It is not the ticket name buyers see and not the price they pay. If you need to add or edit tiers themselves, start with Creating ticket tiers and pricing. A SKU is also not an access code: it never hides a ticket type or unlocks one for buyers. To hide a ticket type behind a code, see Set up access codes for ticket types.
Enter a SKU in the event editor
The SKU field lives on each ticket tier in the event page's Tickets & capacity section.
Open your event for editing and scroll to the Tickets & capacity section.
Click the ticket tier you want to label.
Enter your product code in the SKU field.
Click Save ticket. Saving queues a Squarespace sync for the event (see below).
Enter a SKU in the event wizard
You can set the same SKU field from the ticket step of the event wizard when creating or editing an event there.
In the event wizard, open the step where you set up ticket types.
Click the ticket tier you want to label.
Enter your product code in the SKU field.
Continue through the wizard and save. The SKU syncs to Squarespace the same way as a change saved in the event editor.
SKU rules
Validation runs when you save, and problems show beside the affected tier row or field instead of blocking the whole editor.
Optional. Leaving the field blank uses Eventually's generated SKU. Clearing a custom value removes the override and restores the generated SKU. Tiers without a custom SKU are unchanged.
Up to 64 characters, using only letters, numbers, dots, dashes, and underscores.
Unique per Squarespace site. Two ticket types on the same site cannot share a SKU.
Reserved formats rejected. A value that matches the format Eventually uses for its own generated SKUs is not accepted.
How the SKU syncs to Squarespace
Saving a SKU queues an event-level Squarespace sync, and the push to the matching product variant runs in the background. Your ticket tier in Eventually is the source of truth: the store carries the SKU we last confirmed there.
While the push is pending, or if it has not succeeded yet, buyers keep checking out against the last SKU confirmed in your Squarespace store, so checkout does not fail against a value the store does not carry yet.
Editing a variant's SKU directly in Squarespace does not stick. Our sync overwrites that edit until you enter the same value on the ticket tier in Eventually.
For how the rest of the event data moves between the two platforms, see How Squarespace sync works.
Duplicates and recurring series
Custom SKUs are Squarespace-specific and are not copied automatically when you duplicate an event or when you update the occurrences of a recurring series. Set the SKU on each event's ticket tier where you want it to apply.