Crosslist from Squarespace to WooCommerce — FLUF’s WordPress Plugin for Multi-Marketplace Selling
Move your Squarespace catalogue into WooCommerce — the WordPress plugin behind more online stores than any other platform — and keep both live with automatic order-based sync.
- WooCommerce is a WordPress plugin, not a marketplace. It powers roughly 6.18 million live e-commerce sites — about 38.7% of all online stores — because anyone running WordPress can add a shop to it.
- Squarespace has no native path to WooCommerce. Its Extensions directory is entirely third-party and lists nothing for WooCommerce, and Squarespace itself warns that even its one built-in integration (Etsy) does not sync inventory. Pairing the two means moving your catalogue onto infrastructure you own, in parallel or as a full migration.
- Connecting is entirely server-side on both ends. No browser extension, no logged-in tab. Squarespace uses a Developer API key; WooCommerce uses the FLUF Connect plugin for WooCommerce, installed from your own WordPress admin.
- Products fan out as simple WooCommerce products. A Squarespace product with three sizes becomes three separate simple WooCommerce products today — full variable-product (parent + size dropdown) crosslisting into WooCommerce is on the roadmap, not yet shipped.
- Sync is currently one-directional. A WooCommerce sale automatically marks the item sold on Squarespace (and every other connected channel) via WooCommerce’s order sync. A Squarespace sale does not yet automatically zero WooCommerce stock — that write-back is a known gap.
- Cost: 7 days for £1, then from £9/month (Starter, 300 products) — there’s no ongoing zero-cost tier.
On this page
- Why pair Squarespace with a WooCommerce WordPress store
- What Squarespace can’t do here on its own
- How to crosslist with the FLUF Connect plugin for WooCommerce
- What transfers — field and category mapping
- Why sizes and colours fan out as separate WooCommerce products
- What syncs, and the one direction that doesn’t — yet
- Automation on each side
- What it costs
- Sources and verification
Why pair Squarespace with a WooCommerce WordPress store
If you’re weighing WooCommerce — the WordPress e-commerce plugin that powers roughly 6.18 million live online stores, around 38.7% of all e-commerce websites by site count (Red Stag Fulfillment / Store Leads data) — the honest reason to run it alongside Squarespace rather than instead of it is control, not traffic. Squarespace is a closed, hosted platform: a beautiful, fast-to-launch storefront where the company controls the servers, the checkout and, ultimately, what you’re allowed to export if you ever leave. WordPress is the opposite kind of software — open-source, self-hosted, and installable on any host you choose — and it now runs behind roughly 43% of every website on the internet, not just stores (W3Techs usage statistics). WooCommerce is simply the plugin that turns that WordPress install into a shop.
For a seller, that difference in ownership matters most at the moment you want to change something Squarespace won’t let you: a checkout field, a custom shipping calculation, a plugin that only exists for WordPress. Squarespace itself has roughly 5.82 million subscriptions and around 88,000 live Commerce (e-commerce) sites (Backlinko — Squarespace statistics) — a large, polished platform, but a fraction of the size of the open WordPress ecosystem it sits inside comparison to. Many sellers who outgrow Squarespace’s built-in limits move their catalogue to a self-hosted WooCommerce store precisely because WordPress isn’t tied to one hosting company: you can change host, install any of tens of thousands of plugins, and keep full ownership of your product data (WP All Import — Squarespace vs WordPress comparison).
Running both isn’t an either/or decision, though. A Squarespace store can keep functioning as your polished, easy-to-maintain public storefront while a WooCommerce WordPress install becomes a second, parallel sales channel — or the destination you’re gradually migrating toward, kept live in parallel so nothing goes dark mid-move. FLUF Connect exists for exactly that overlap: read your Squarespace catalogue once, and let it populate a WooCommerce store automatically instead of manually re-entering every product a second time.
The two use cases that bring sellers to this pair are different, and both are legitimate. The first is a genuine migration: a Squarespace merchant who has decided to move their store onto self-hosted WordPress and WooCommerce for the control, the lower long-run software cost, or a specific WooCommerce extension that solves a real business problem Squarespace can’t. The second is simpler — running WooCommerce as an additional sales channel alongside a Squarespace storefront that stays exactly as it is, because WooCommerce’s WordPress ecosystem opens doors a closed platform doesn’t: bespoke checkout logic, wholesale-pricing plugins, membership gating, or a marketing stack built entirely around WordPress content. Either way, re-keying a whole catalogue by hand into a second platform is the kind of work nobody actually wants to repeat product by product, which is the entire reason this pair exists.
What Squarespace can’t do here on its own
Squarespace has no native route into WooCommerce. Its Extensions directory is entirely third-party, and searching it for “WooCommerce” or “WordPress” returns nothing — Squarespace’s only marketplace-adjacent feature is a one-way Etsy product import, and Squarespace’s own help documentation describes even that as “a one-time import, not a sync,” with inventory then “managed separately on both platforms” (Squarespace Help — using Etsy with Squarespace). Squarespace’s own advice for real synchronisation is to look at a third-party inventory tool — which is the gap FLUF Connect fills for a WooCommerce pairing specifically.
Two technical facts constrain any integration touching Squarespace, WooCommerce-bound or otherwise. Squarespace’s Commerce APIs do not support CORS — its own developer FAQ states plainly that browser-side access isn’t supported (Squarespace Commerce API FAQ) — so nothing that reads your product catalogue can run purely inside a browser tab; it has to run server-side, which is exactly how both halves of this pair work. And Commerce API access is plan-gated: it requires Squarespace’s Core tier or above, so a store still on the entry-level Basic plan can’t be connected to anything, WooCommerce included, until it upgrades.
How to crosslist from Squarespace to WooCommerce with FLUF Connect
Because both channels are server-side and API-driven, connecting this pair needs no browser extension on either end — a real point of difference from extension-bound channels like Vinted or Facebook Marketplace, where a live, logged-in browser tab has to stay open.
- Check your Squarespace plan is Core or above — Commerce API access doesn’t exist on Basic.
- Sign in to FLUF Connect and open the Channels page.
- Connect Squarespace. Paste your site’s Developer API key. This is a server-side connection — there’s no extension involved, because Squarespace’s own APIs can’t be reached from a browser.
- Install the FLUF Connect plugin from your WordPress admin. On your WooCommerce site: Plugins → Add New → search “FLUF Connect” → Install → Activate. The plugin generates a WooCommerce REST API key pair (
wc/v3, read-write) and hands it back to FLUF automatically — no manual copy-pasting of keys, no FTP. - Connect your WooCommerce store. Confirm the handshake inside FLUF Connect; your store URL now shows as connected on the Channels page.
- Choose channels and import your catalogue. FLUF walks your Squarespace products and indexes them, variant by variant, ready to select.
- Pick what goes to WooCommerce — a category to start, or the full catalogue once you’ve confirmed the mapping looks right.
- Publish. Each selected product is created as a live WooCommerce product on your WordPress site, images and all.
Start crosslisting from Squarespace to WooCommerce
One practical note that’s specific to WooCommerce among FLUF’s channels: because your store runs on your own WordPress hosting rather than a marketplace’s shared infrastructure, listing speed depends on your host. A slow, shared WordPress host uploading several product photos synchronously can genuinely take under a minute per product — FLUF gives WooCommerce creates up to 60 seconds to complete before treating an attempt as timed out, longer than most marketplace API calls need, specifically to give a modest WordPress host a fair chance before falling back to a background retry.
Done by hand, moving a catalogue from Squarespace to WooCommerce means opening each Squarespace product, copying the title and description, downloading every photo and re-uploading it to the WordPress media library, re-entering price, stock, size and colour as WooCommerce attributes, picking a WooCommerce category, and publishing — then keeping a note of which items still need updating if the Squarespace price or stock changes later. That’s realistically eight to ten minutes per product for anyone doing it carefully. Selecting the same products in FLUF Connect and clicking crosslist collapses that into seconds per item, with the field mapping already applied — the time saved compounds fast once a catalogue runs into the hundreds of products rather than a handful.
What transfers — field and category mapping
| Squarespace field | WooCommerce field | Transfer status | Notes |
|---|---|---|---|
| Product name | Product title | Automatic | WordPress post titles have no fixed character cap, unlike most marketplaces — nothing gets truncated moving into WooCommerce. |
| Description (HTML) | Description | Automatic | Carries across as WooCommerce’s own long-form description field, which — like Squarespace’s — supports rich formatting. |
| Images | Product gallery | Automatic | WooCommerce imposes no image-count limit of its own — every photo FLUF read from the Squarespace product is pushed to the WooCommerce gallery, sorted in the same order. |
| Variant price (sale ?: regular) | Regular / sale price | Automatic | FLUF reads Squarespace’s sale price where one exists, else regular price, and writes both fields on the WooCommerce side the same way. |
| Variant SKU | SKU | Automatic | The join key FLUF uses to resolve a later WooCommerce edit or sale back to the right Squarespace variant. |
| Stock quantity | Stock quantity + stock status | Automatic | Written with manage_stock=true so WooCommerce tracks quantity natively, not just an in/out-of-stock flag. |
| Store page + tags | Product category | Smart mapped | Squarespace has no dedicated category field — only a store page and free-text tags — so FLUF maps those onto the closest matching category that already exists in your own WooCommerce store’s category tree, not a fixed external taxonomy. |
| Variant attributes (size, colour, etc.) | Custom product attributes | Smart mapped | Pushed as WooCommerce non-taxonomy attributes, visible on the storefront without any per-store term setup on your end. |
| — | Weight, dimensions, tax class | Manual input | WooCommerce-only fields with no Squarespace equivalent; set a default in WooCommerce or fill them in per product after the crosslist. |
Because WooCommerce’s category tree isn’t a fixed global taxonomy the way a marketplace’s is — it’s whatever categories your own WordPress store already defines — FLUF mirrors your live WooCommerce categories first, then maps each Squarespace product onto the nearest match. A store with no matching category still lists successfully; it just arrives uncategorised until you tidy it up.
Two Squarespace-side constraints shape how the initial import runs, independent of WooCommerce: product listing returns at most 50 records per page through a cursor Squarespace itself calls dynamic — pages can shift mid-walk on a fast-changing catalogue — and the Products API has no seller-scoped search, so finding a specific product means walking the full list rather than querying for it directly. Neither is visible day to day; it just means a first import of a large catalogue takes a little longer than a single API call.
Why sizes and colours fan out as separate WooCommerce products
Squarespace models a single product with several variants — a T-shirt in three sizes is one product with three variant rows, each carrying its own SKU, price and stock. WooCommerce has a similar idea (a “variable” product with child “variations”), but building that structure through the API is a two-step process: create the parent, then register each variation and its attribute taxonomy separately. FLUF’s WooCommerce integration ships simple products first — each Squarespace variant becomes its own standalone, simple WooCommerce product, with its own title, SKU, price and stock row, rather than one parent with a size selector. True variable-product crosslisting into WooCommerce — one WordPress product page, one dropdown — is a dedicated build still on the roadmap, not yet live.
In practice this means a three-size Squarespace product currently lands on your WooCommerce store as three separate product listings rather than one page with a size picker. It’s an honest limitation worth planning around if your catalogue leans heavily on multi-size variants: each size gets full stock accuracy and its own product URL, just not the single consolidated product page a shopper browsing your WordPress store might expect.
What syncs, and the one direction that doesn’t — yet
| Event | What happens |
|---|---|
| Item sells on WooCommerce | Detected via WooCommerce’s order sync; the matching item is marked sold on Squarespace and every other connected channel. |
| Item sells on Squarespace | Detected through Squarespace’s own order-based sold-detection, which marks the item sold out on every other connected marketplace channel — but WooCommerce stock isn’t zeroed automatically yet. |
| You edit price or stock in FLUF | Pushed to WooCommerce. |
| You delete in FLUF | Removed from WooCommerce. |
| Stock changed directly in wp-admin | Not read back into FLUF automatically — WooCommerce is currently a one-way create-and-receive destination for this pair, not a live source FLUF polls for manual edits. |
This asymmetry is worth stating plainly rather than glossing over, because it’s the single most important thing to know before you rely on this pair for shared stock. WooCommerce’s order sync means a WooCommerce sale reliably closes the loop everywhere else FLUF has listed that item. The reverse — a sale on Squarespace, or on any other connected marketplace, automatically zeroing the same product’s stock on your own WooCommerce store — is not yet automated. If the same physical item is sold in both places, check your WooCommerce stock manually after a Squarespace sale until that write-back path ships. For genuinely one-of-one stock (a single vintage piece, a small-batch drop), this matters more than for a WooCommerce store restocking the same SKU regularly.
Automation on each side
| Feature | Squarespace | WooCommerce |
|---|---|---|
| Crosslisting | Source | Yes |
| Order sync | Sold-detection via orders | Yes |
| Sold elsewhere → stocked out here | Yes | Not yet automated |
| Auto-relisting | Not applicable | Not applicable |
| Offer management | Not applicable | Not applicable |
| Bulk operations | Yes | Yes |
| Minimum images | 0 | 0 |
| Connection type | Server-side API key | Server-side, via the FLUF Connect WordPress plugin |
Neither side of this pair uses auto-relisting or offer management — both are self-hosted or store-owned platforms rather than marketplaces with listing expiry or a “make an offer” buyer flow, so those features simply don’t apply to either. What both sides share is that they’re the least extension-dependent pair FLUF supports: no logged-in browser tab has to stay open on your machine for either Squarespace or your WooCommerce WordPress site to keep syncing. Automation that does apply — crosslisting, order sync, bulk operations — is included in every FLUF plan, not sold as a separate add-on.
What it costs
| Plan | Monthly | Crosslisted products |
|---|---|---|
| Starter | £9/month | 300 |
| Growth | £19/month | 1,000 |
| Seller | £49/month | 2,500 |
| Pro | £99/month | 5,000 |
| Super Seller | Custom pricing — contact sales | Unlimited |
Every new account gets 7 days for £1, then plans start at £9/month (Starter — 300 active products) — there’s no ongoing zero-cost tier. Yearly billing saves against the monthly price on every tier, with the same feature set throughout — including crosslisting between Squarespace, WooCommerce and every other channel FLUF supports, not just this one pair. Full detail on the pricing page.
Start crosslisting from Squarespace to WooCommerce
Sources and verification
- Red Stag Fulfillment — WooCommerce market share — ~6.18 million live selling sites, ~38.7% of e-commerce websites
- W3Techs — Usage statistics of WordPress — WordPress powers roughly 43% of all websites
- Backlinko — Squarespace subscriber and revenue statistics — ~5.82M subscriptions, ~88,000 live Commerce sites
- Squarespace Commerce API FAQ — no CORS/browser support
- Squarespace Help — using Etsy with Squarespace — “not possible to sync inventories” quote, applied generally
- WP All Import — Squarespace vs WordPress comparison — hosting portability and ownership
- WooCommerce.com — Managing Products — simple vs. variable product model
- Field mapping, category-mirroring, connection type and sync behaviour read from FLUF Connect’s own Squarespace and WooCommerce channel modules, August 2026
Related pages
- Crosslist from Squarespace to Depop
- Crosslist from Squarespace to Etsy
- Crosslist from Squarespace to eBay
- Crosslist from Squarespace to Vinted
- Crosslist from Shopify to WooCommerce
- Crosslist from Etsy to WooCommerce
- How to sell on Squarespace
- How to sell on WooCommerce
- Crosslisting hub
- compare with crosslisting to Shopify instead
Frequently Asked Questions
Any self-hosted WordPress site running WooCommerce works, on any host. The FLUF Connect plugin for WooCommerce talks to your store through WooCommerce's own REST API (wc/v3), so there is no dependency on a specific hosting company. The one requirement is that your store is reachable over HTTPS — FLUF rejects the handshake for a plain HTTP site because credentials should never travel unencrypted.
No background process runs on your server. FLUF calls your WooCommerce REST API only when it needs to — reading your catalogue, pushing a new listing, or writing a stock update — the same way any other admin tool using the WooCommerce API would. There is no permanent plugin overhead sitting on every page load of your WordPress site.
Reading variable products from WooCommerce isn't the direction this pair uses — Squarespace is the source here. Pushing INTO WooCommerce currently creates simple products: each Squarespace product variant (each size or colour) becomes its own simple WooCommerce product with its own SKU, price and stock, rather than one WooCommerce parent product with a size dropdown. True variable-product crosslisting into WooCommerce, where FLUF creates the parent/variation structure natively, is on the roadmap but not yet shipped.
Any WooCommerce store exposing the standard wc/v3 REST API, which has shipped in every current WooCommerce release for years. There is no separate legacy-version path to configure — if your WordPress admin can generate WooCommerce REST API keys, FLUF Connect can use them.
Every new account gets 7 days for £1, then plans start at £9/month (Starter — 300 active products). There's no ongoing zero-cost tier. Automation — including inventory sync between Squarespace and WooCommerce — is included in every plan rather than sold as a paid add-on.
One direction is automatic today: when an item sells on your WooCommerce store, FLUF detects it through WooCommerce's order sync and marks the matching listing sold on Squarespace and every other connected channel. The reverse — a Squarespace sale automatically zeroing WooCommerce stock — is not yet part of WooCommerce's automation set; check WooCommerce stock manually until that ships.
Not automatically yet. Squarespace's own sold-detection reliably marks the item sold out on every other connected marketplace channel, but WooCommerce write-back — automatically zeroing stock on your own WordPress store — is a gap in the current WooCommerce integration. Until it ships, treat WooCommerce as needing a manual stock check after a Squarespace sale on shared inventory.
No. Squarespace has no extension or plugin system for this — FLUF connects to Squarespace with a server-side Developer API key generated from your own Squarespace account, which requires the Core plan or above. Nothing installs on the Squarespace side.
Yes. The FLUF Connect plugin for WooCommerce connects your WordPress store to every channel FLUF supports — Depop, eBay, Etsy, Vinted, Shopify, Facebook Marketplace and more — from the same dashboard, not just Squarespace.
No. Both Squarespace and WooCommerce are server-side, API-driven connections — Squarespace via a Developer API key, WooCommerce via the FLUF Connect WordPress plugin's REST API handshake. Neither side needs a Chrome extension or a logged-in browser tab, unlike extension-first channels such as Vinted or Facebook Marketplace.