sales-squarespace

name	sales-squarespace
description	Squarespace platform help — the design-first website builder's ecommerce/online-store backend, automated through the Squarespace Commerce APIs (Orders, Inventory, Products, Transactions, Contacts) plus OAuth-gated webhooks with HMAC-SHA256 signature verification. Use when wiring Squarespace orders, inventory, or customers into a CRM or data warehouse via the API, a Squarespace webhook fails Squarespace-Signature HMAC verification, an order.create webhook won't register (it needs OAuth, not an API key), the Commerce API returns nothing because the site is below the required commerce plan, payments stuck on a Squarespace Payments hold, choosing a Squarespace plan (Basic vs Core vs Plus vs Advanced) or weighing transaction/digital-product fees, or comparing Squarespace vs Shopify/Wix/Square Online for a creative or service business. Do NOT use for cross-tool checkout-conversion strategy (use /sales-checkout) or picking a Merchant of Record for global tax (use /sales-merchant-of-record).
argument-hint	[describe what you need help with in Squarespace]
license	MIT
version	1.0.0
tags	["sales","ecommerce","checkout","platform"]
github	https://github.com/Squarespace

Squarespace Platform Help

Squarespace is a design-first, all-in-one website builder with a built-in commerce layer — online store, memberships, digital downloads, gift cards, donations, subscriptions, and (via bundled Acuity Scheduling) bookings. You don't automate the site builder (pages/themes are UI-only); you automate the commerce layer with the Squarespace Commerce APIs (Orders, Inventory, Products, Transactions, Contacts) plus OAuth-gated webhooks. It's not a Merchant of Record (you own tax). This skill covers that integration surface and the pain points — the commerce-plan API gate, OAuth-only webhooks, HMAC verification, Squarespace Payments holds — that trip people up.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

Ask only what you need (skip if the prompt already says):

1. What's the goal? (a) automate/integrate via the API or webhooks, (b) fix a store/payments/inventory problem, (c) pick a Squarespace plan or weigh fees, (d) compare Squarespace vs another platform.
2. Build context — automating your own site (an API key works, OAuth for webhooks) or a third-party app across other sites (OAuth)? Which objects — orders, products, inventory, transactions, contacts?
3. What plan is the site on? Commerce APIs require a paid commerce plan; a personal/Basic plan has no API.

Skip-ahead rule: if the user's prompt already contains enough context, go straight to Step 2.

Step 2 — Route or answer directly

Map the request to the right home. When routing, give the exact command.

The user's real problem	Route to
Checkout-conversion strategy across tools (order bumps, AOV, cart abandonment tactics)	/sales-checkout {question}
Migrating a store off (or onto) Squarespace — data export, redirects, SEO	/sales-checkout {question} (migration mechanics)
Choosing a Merchant of Record for global tax / VAT instead	/sales-merchant-of-record {question}
Memberships / paid gated-content strategy across tools	/sales-membership {question}
Selling digital downloads strategy across tools	/sales-digital-products {question}