Squarespace integrations for commerce data in 2026
Need Squarespace products and orders in another tool? Check extensions, APIs and exports, including their limits for variants, stock and shopper support.
- Published
- Last updated
Squarespace integrations can exchange commerce data through extensions, authenticated application programming interfaces (APIs) or CSV files. Choose an extension for a supported business task, an API connection for custom data flows and exports for a one-time transfer. An embedded widget needs its own data connection before it can use your store’s records.
Separate commerce data from site embeds
Start with the records another tool needs and the changes it must send back. A shipping tool needs orders and fulfilment details. A downstream catalogue needs products, their variants and stock. Customer management needs contact records, with marketing preferences kept separate from order history.
Write down which system owns each record. If Squarespace owns stock, another tool must read its updates without overwriting them with an older quantity. If an inventory system owns stock, define how its accepted changes reach Squarespace.
Code injection adds HTML or scripts to your pages. It can display a widget, but displaying one grants no permission to read private orders or change inventory. Squarespace’s code injection guide lists Core, Plus, Advanced and some legacy plans as eligible. That permission is separate from commerce API access.
For storefront installation and shopper conversations, read the Squarespace AI chatbot guide. For connections on other platforms, use the catalogue integrations directory.
Check available connection methods
Choose the method by its supported records and direction of travel. A connection that reads orders does not automatically update products or stock.
| Method | What it connects | Update behaviour | Setup and cost model |
|---|---|---|---|
| Squarespace extension | The objects supported by that provider’s connector | Direction and schedule depend on the extension | Authorise the selected site, then complete provider setup. A separate subscription can apply. |
| Custom commerce API connection | Authorised product, inventory, order or customer records | Your developer controls retrieval and supported writes | Requires eligible API access, credentials and ongoing development. |
| Product or order export | The records and columns included in the selected file | A snapshot that needs another export or import to change | Download a CSV and map it to the destination’s format. |
Squarespace’s extension guide says extensions connect on all plans without an additional Squarespace connection charge. Providers can charge separately. Extensions are built by third parties, with their own object coverage and support. Use the listing’s supported task and the provider’s setup documentation to decide whether it covers your records.
For API access, the Squarespace API keys guide lists Orders, Inventory and Transactions on Core, Plus, Advanced and Commerce Advanced. Its developer authentication guide still describes custom applications under Commerce Advanced. Match the required API to the permissions available for your site before commissioning a connection. Code injection eligibility does not establish Products API eligibility.
The API permissions reference separates read access from write access. Products covers product details and variants. Inventory covers stock levels, while Orders covers order and fulfilment information. Customer contact access has its own permissions. A read-only catalogue connection needs no authority to edit orders.
Extensions use OAuth authorisation. Custom applications can use an API key or OAuth access token. Keep credentials in the connecting service’s secure configuration, never in browser scripts or a downloadable CSV. Authorisation applies to the selected website, so a successful login alone does not prove you connected the right store.
Retain variant and inventory meaning
Map the product and each sellable variant separately. A product identifier groups the range, while a variant identifier distinguishes a particular option combination. Keep the stock-keeping unit (SKU), option names and option values beside that variant.
Consider a hypothetical T-shirt in navy and white, each available in small and medium. Those combinations need four distinct destination variants. Matching only the product title can merge their stock. A renamed title must still update the same product instead of creating another one.
Use the Products API documentation for the product structure and the Inventory API documentation for variant stock. Inventory responses identify the variant and include quantity plus an unlimited-stock flag. Preserve that flag separately. An unlimited variant with a quantity of zero must not become sold out through a numeric-only import.
For each mapped variant, compare its identifier, SKU and options with the destination record. Then compare stock and the unlimited flag. Handle missing identifiers as import errors that someone can resolve, rather than quietly joining unrelated records.
The Squarespace’s CSV export instructions covers physical and service products and permits exports of up to 10,000 products. Its CSV omits additional product information and customer reviews. Variant images are also excluded, alongside featured images and image alt text.
A CSV can flatten relationships that the destination expects as separate records. Inspect its headers and a multi-variant product before mapping it. Store the product-to-variant relationship explicitly in the destination. Changes to the exported file and Squarespace do not automatically sync in either direction.
Check the information shoppers receive
Follow a correction through the full connection to the place a shopper sees it. An import success message proves little if a downstream product page still shows the old material or stock.
Use a small acceptance sample in a safe test environment. Correct a product’s material description in the source, then run the connection. Open the destination product page and confirm the corrected text appears on the existing record. If a separate search index or cache supplies the displayed result, include that output in the check.
Next, change one finite-stock variant from two available units to zero. Confirm the matching destination variant becomes unavailable within your agreed update interval. Its other size must retain its own quantity. This checks the option mapping as well as the inventory transfer.
Delivery answers need the current delivery policy, including handling time and any destination restrictions. Order-status answers need the order source. Use the Orders API documentation to identify the order and fulfilment fields your connection reads. An order’s fulfilment state and a carrier’s delivery confirmation answer different questions.
Squarespace’s order export guide says auto-exported orders do not update when their status changes. Download another CSV to obtain current statuses. A previous export cannot support a claim that a later cancellation or shipment has already reached the destination.
Verify ongoing reliability
Agree on an update interval and a recovery owner before calling the connection a live sync. Record the last successful transfer and unresolved errors where staff can find them. Define what happens when the source and destination disagree.
Use these acceptance cases before relying on the connection:
- Add a variant to an existing product. It must arrive with its own identifier and options, without duplicating the parent product.
- Cancel a test order after its first transfer. The destination must reflect the cancellation according to the connector’s supported workflow and stop any conflicting fulfilment action.
- Simulate an expired access token or revoke a test credential. The connection must report an authentication failure and stop treating old data as a successful update.
- Restore test access and replay pending work. Previously accepted records must remain single records, and missed changes must reach the destination.
Squarespace states that API keys do not expire while the merchant site remains active. Use revoked access for that failure case when testing a key-based connection. OAuth token expiry is a separate credential case. Keep these checks within a test account or environment that cannot send real fulfilment instructions.
Assign catalogue reconciliation to the person who owns product data. Give the connection provider or developer responsibility for failed transfers and recovery. Store staff need a contact for disputed orders, while a named account owner controls credential replacement.
Compare source and destination variant counts after the initial transfer, then inspect failed records and a sample of changed quantities on a regular schedule. If the task only needs a one-time export, record who repeats it and when. Treat it as a transfer until continuing updates and recovery have passed the acceptance cases.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.