Squarespace Commerce Limitations: What Squarespace Cannot Do in 2026

Squarespace approaches ecommerce from the opposite direction of most commerce platforms. It is a design-led website builder with selling built in, not a commerce engine with a website on top — and that architecture shapes everything from its locked checkout to the absence of any viable headless commerce path. For design-forward brands with small-to-mid catalogs selling in one country and one currency, the trade-off is often favorable. For merchants beyond that profile, it creates predictable pressure points.

The 2025 plan lineup revamp deserves credit for moving real commerce capability downmarket. All four current plans — Basic, Core, Plus, and Advanced — include selling, and features once reserved for a top tier, including subscription products, abandoned checkout recovery, customer accounts, and point of sale, now ship on every plan. What the revamp did not change is the architecture: one currency per store, a nine-API back office with no checkout endpoint, and a payment stack capped at four processors.

This guide maps where those ceilings sit in 2026, using plan names, prices, and limits drawn from Squarespace's own documentation, and contrasts each with how API-first platforms such as Swell approach the same problem. The point is not that Squarespace is a poor product — it is that its constraints are structural, and worth understanding before they intersect a growth roadmap.

Key Takeaways

• Every Squarespace product is capped at six variant options and 250 variant combinations, and version 7.1 store pages are each capped at 10,000 products — with hidden products counting toward the limit.
• The $19-per-month Basic plan adds a 2% commerce transaction fee to physical sales on top of card processing, and digital products carry a separate platform fee of 7%, 5%, 1%, or 0% by plan tier.
• The complete Commerce API suite is nine back-office APIs with no cart, checkout, or storefront endpoints, and the Orders, Inventory, and Transactions APIs are unavailable on the Basic plan.
• Each store sells in exactly one currency, Squarespace Payments operates in roughly 17 countries, and carrier-calculated shipping covers only US domestic shipments on Core plans and above.
• Payment processing is limited to Squarespace Payments, Stripe, PayPal, and Square, and Payments Terms §3.8 adopts Stripe's restricted-businesses list — leaving CBD, vape, and firearms merchants without an on-platform checkout.
• Subscriptions now work on all four plans following the 2025 revamp, but customers can buy only one subscription product per checkout, with no PayPal, Apple Pay, or ACH support — a contrast with API-first platforms like Swell, where native subscription billing is included on every plan.

Variant Ceilings and Catalog Caps That Constrain Product Strategy

Six options and 250 combinations per product

Squarespace caps every product at six variant options and 250 variant combinations — with matching limits on variant images and SKUs — whether products are added through the editor or the CSV importer. Variant names top out at 100 characters. Notably, the 100-variant ceiling still cited in older forum threads was raised to 250, so many third-party comparisons understate the current limit — but 250 remains modest. A product with sizes, colors, materials, and lengths can exceed the cap with unremarkable ranges in each dimension.

The standard workaround, splitting one product into several listings, fragments inventory reporting and forces customers to hunt across multiple pages for what is really a single item.

A 10,000-product cap behind unlimited-product marketing

Catalog scale has hard edges too. Squarespace 7.1 store pages are capped at 10,000 products each, with hidden products counting toward the total, while legacy 7.0 store pages hold up to 200 products each. Sites are also limited to 1,000 pages, with Squarespace recommending no more than 400 pages for performance — figures that sit awkwardly beside marketing copy about selling unlimited products.

Platforms built API-first remove these decisions from the roadmap. Swell supports unlimited variants and options per product, managed through both the dashboard and the product options editor or API, and its model editor and custom fields let merchants extend any data model rather than restructure a catalog around a fixed schema.

Transaction Fees and Their Impact on Profit Margins

The Basic plan's 2% surcharge and the digital products ladder

Squarespace's entry Basic plan ($19 per month billed annually) charges a 2% commerce transaction fee on physical and service product sales, in addition to payment processing. Core ($29), Plus ($49), and Advanced ($99, all billed annually) remove that fee, which effectively makes $29 per month the floor for fee-free physical selling.

Digital products follow a steeper ladder. Courses, memberships, and paywalled content carry a platform fee of 7% on Basic, 5% on Core, 1% on Plus, and 0% only on Advanced — again on top of processing. A creator selling $5,000 per month in courses on Basic hands over $350 monthly before card costs even begin.

Processing rates that improve only with plan spend

Card processing through Squarespace Payments follows the same gradient: 2.9% + $0.30 per domestic card transaction on Basic and Core, 2.7% + $0.30 on Plus, and 2.5% + $0.30 on Advanced. Reaching the best rate requires the $99-per-month plan, so processing economics are tied to subscription tier rather than to volume.

API-first platforms tend to structure this differently. Swell uses revenue-based fee structures that apply only above defined thresholds on each plan — a revenue ceiling per plan, with per-order overage fees beyond it — rather than a percentage on every sale from the first dollar. Merchants comparing platforms should model their own volume against each structure, alongside the feature set each plan actually unlocks.

Nine Back-Office APIs and No Path to Headless

An API suite that manages the store but cannot run it

Squarespace's complete Commerce API catalog is nine back-office APIs: Analytics, Contacts, Discounts, Inventory, Orders, Products, Profiles, Transactions, and Webhook Subscriptions — with Profiles already in maintenance mode. Every one manages data behind the store; none renders a product page, builds a cart, or processes a checkout. A merchant can sync inventory into an ERP or pull orders into a warehouse system, but cannot build a custom storefront that checks out through Squarespace. A true headless build is architecturally impossible.

Plan-gated keys and a developer platform frozen on 7.0

Access is further gated by plan: the Orders, Inventory, and Transactions APIs require Core, Plus, or Advanced, and the API explicitly cannot connect a third-party payment processor. There is no public app store through which developers can distribute apps. On the site itself, the Developer Platform and developer mode exist only on legacy version 7.0; every new site runs 7.1, where customization means Custom CSS and code injection — and code injection itself requires Core or above. No server-side code runs on the platform.

This is the sharpest contrast with API-first commerce. Swell exposes its unified Backend API — the same API that powers its own dashboard and hosted checkout — to external developers with full CRUD access across every data model, alongside a Frontend API for browser contexts and both REST and GraphQL access points. Because internal tools and external developer tooling share one API, any native behavior can be replicated or customized rather than merely observed from the outside.

A Locked Checkout at the Point Where Conversion Is Won or Lost

Styling half a page, editing none of it

Squarespace's checkout is a fixed split-screen layout, and merchant control extends to colors, a logo, and header alignment on the right half of the page only. Per Squarespace's own documentation, the left side cannot be customized, checkout text cannot be changed, built-in fields cannot be re-worded, and the order status page cannot be modified in Site Styles. Custom form fields can be added — but scripts and CSS cannot touch checkout at all.

Why checkout ownership compounds over time

For an early-stage store, a standardized checkout is arguably a feature: it works, and nobody maintains it. The constraint bites once conversion optimization becomes a discipline — testing field order, adapting copy for a market, or placing trust content at the decision point are levers that simply do not exist, at any plan tier or price.

Swell treats checkout as an API surface rather than a fixed page. Its Checkout API supports fully custom checkout and payment flows built on the same APIs that power Swell's hosted checkout, so a merchant can launch on the hosted flow and take control incrementally instead of hitting a wall.

Single-Currency Stores and the International Expansion Problem

One currency, locked in by the first gift card

A Squarespace store sells in exactly one currency; there is no multi-currency pricing or checkout on a single site, and Squarespace's suggested workaround is adding alternate prices as text in product descriptions. The lock deepens over time: once a store sells a single gift card — even in a test order — its currency can never be changed, and switching requires duplicating the entire site.

Regional coverage that thins outside the United States

The gaps extend across the international stack. Squarespace Payments operates in roughly 17 countries, several restricted to local-currency settlement (Canada in CAD only, India in INR with Indian bank accounts, Mexico in MXN). Carrier-calculated shipping through FedEx, UPS, and USPS works only for US domestic shipments and only on Core plans and above, leaving non-US merchants on flat or weight-based rates with no cross-border rate calculation. Specialist reviews have also flagged weak EU/UK VAT handling, including no per-product VAT rates and identical prices shown to every visitor until checkout.

International selling is where API-first platforms have invested most visibly. Swell prices across 230 currencies with explicit price rules per currency and automatic conversions, localizes content in 170 languages, and handles tax through a native Avalara AvaTax integration alongside TaxJar, plus custom tax rule groups by location and product.

Subscription Selling: Broader Availability, Narrow Mechanics

On every plan since 2025, with strings attached

Subscriptions are a genuine recent improvement: since the 2025 revamp, subscription products are available on all four current plans, so older comparisons citing a Commerce Advanced requirement are out of date. The mechanics, however, remain narrow. Subscriptions cannot be purchased with PayPal, Apple Pay, or ACH; customers can buy only one subscription product at a time; download products cannot be sold as subscriptions; free subscriptions are impossible; and free trials exist only as a 100%-off first-payment discount.

Specialist reviews have also noted that subscribers cannot pause or modify a subscription without canceling and repurchasing, and that price increases apply only to new subscribers — awkward constraints for any brand whose economics depend on retention.

What purpose-built subscription infrastructure looks like

Swell treats subscription commerce as a first-class model included on every plan: physical or virtual products sell on flexible billing intervals, invoicing and fulfillment run on separate schedules, failed payments retry automatically through dunning, and mixed carts combine subscription and one-time items in a single order — all managed from the same dashboard. Subscription payments work through an encrypted card vault directly with the payment gateway, rather than through a checkout that supports only a subset of payment methods.

Payment Processor Lock-In and the Regulated-Category Dead End

Four processors, strict pairing rules, no exceptions

Squarespace supports exactly four payment processors: Squarespace Payments, Stripe, PayPal, and Square — the last for US in-person sales only. Pairing rules apply (Squarespace Payments can connect only alongside PayPal), and the documentation is explicit that the Commerce API cannot be used to connect a third-party processor. There is no path, at any plan tier, to a gateway outside those four.

Where restricted categories hit a wall

The consequences concentrate on regulated products. Squarespace Payments Terms §3.8 incorporates Stripe's Prohibited and Restricted Businesses list: cannabis is prohibited outright; CBD (even with negligible THC within local limits), tobacco and vape, and firearms are restricted categories requiring approval; and nutraceuticals making unsafe or harmful claims are prohibited. PayPal and Square enforce comparable policies. Because no alternative or high-risk gateway can be connected, merchants in these categories can build a Squarespace site but cannot run compliant checkout through it — industry guidance points to a separate high-risk merchant account processed off-platform.

Gateway flexibility is a structural difference, not a toggle. Swell's payment abstraction layer integrates with Stripe, PayPal, Braintree, Authorize.Net, and Amazon Pay, with Swell handling PCI compliance — and that third-party gateway support matters most precisely for merchants in restricted categories who need processor options mainstream stacks refuse.

B2B, Wholesale, and an Extensions Directory Measured in Dozens

Wholesale by workaround

Squarespace ships no native B2B machinery: as of publication there are no customer-group or wholesale price lists, no net-terms or invoice-based checkout for trade buyers, and no quantity-based pricing — the platform's pricing plans feature is a content-paywall tool, not catalog pricing. Squarespace specialists document the standard workarounds: password-protected duplicate stores for wholesale buyers, or third-party wishlist and quote extensions. Adjacent merchandising gaps compound the problem; current specialist reviews also cite no product bundles, no volume discounts or minimum quantities, and no card vaulting for deferred or partial payment — leaving no documented way to take anything other than full payment at checkout.

Roughly four dozen extensions across four categories

Nor can an app ecosystem fill the gaps. Squarespace's official Extensions directory is a curated catalog of roughly 45-50 extensions across just four categories — Sales & Marketing, Inventory & Products, Finance, and Shipping & Fulfillment — versus the thousands of apps on dedicated commerce platforms. The order of magnitude is the point: when a capability is missing, there is rarely an extension waiting to add it.

Swell folds this functionality into the core platform: native B2B and wholesale features include customer group-based pricing, custom payment terms, and quotes and draft orders via the API, while multi-vendor marketplace capabilities with split payments are built into the core rather than bolted on. More than 40 built-in service integrations — Klaviyo, ShipStation, Algolia, and Contentful among them — cover the same categories Squarespace's directory addresses, with the Backend API as the escape hatch for everything else.

Frequently Asked Questions

Does Squarespace charge transaction fees on top of card processing fees?

On the Basic plan, yes: Squarespace takes 2% of every physical or service product sale in addition to card processing, which runs 2.9% + $0.30 per domestic transaction with Squarespace Payments. Core, Plus, and Advanced drop the physical-product fee to 0%, but digital content — courses, memberships, paywalled posts — carries its own platform fee of 7%, 5%, 1%, and 0% respectively. Processing rates improve only with plan spend, bottoming out at 2.5% + $0.30 on the $99-per-month Advanced plan.

Can a Squarespace store sell in multiple currencies?

No. Squarespace's documentation states that a store can choose only one currency, and the workaround amounts to displaying alternate prices as text in product descriptions. The choice becomes permanent once any gift card is sold — including in a test order — after which changing currency requires duplicating the site. International merchants face related constraints: Squarespace Payments covers roughly 17 countries, several locked to local-currency settlement, and carrier-calculated shipping works only for US domestic shipments. Platforms like Swell handle this natively, with pricing across 230 currencies and explicit per-currency price rules.

Can merchants go headless or build custom functionality with Squarespace's APIs?

Not in any complete sense. The Commerce API suite consists of nine back-office APIs — Orders, Products, Inventory, Transactions, Contacts, Discounts, Analytics, Profiles, and Webhook Subscriptions — with no cart, checkout, or storefront API, so a custom front end cannot check out through Squarespace. The Orders, Inventory, and Transactions APIs require the Core plan or above, the API cannot connect third-party payment processors, and there is no app store for distributing custom apps. On-site customization is limited to Custom CSS and code injection on Core and above, since developer mode and custom templates exist only on legacy 7.0 sites.

Can regulated products like CBD or supplements be sold on Squarespace?

The website can be built; checkout is the problem. Squarespace Payments Terms §3.8 adopts Stripe's restricted-businesses list, under which cannabis is prohibited, CBD, tobacco and vape, and firearms are restricted pending approval, and nutraceuticals making unsafe or harmful claims are prohibited. PayPal and Square impose comparable rules, and because Squarespace supports no other gateways — and its API explicitly cannot connect one — high-risk merchants cannot process payments on-platform. Industry guides recommend a separate high-risk merchant account with payment flows handled off-platform.

Will Squarespace handle a large catalog or wholesale operation?

It strains at both. Catalogs hit a hard cap of 10,000 products per store page on 7.1 sites with hidden products included, 250 variant combinations and six options per product, and a 1,000-page ceiling with a 400-page performance recommendation. For wholesale, there are no price lists, customer-group pricing, quantity discounts, or net-terms checkout as of publication, so merchants resort to hidden duplicate stores or wishlist extensions — and a directory of roughly 47 extensions offers far fewer escape hatches than the app stores of dedicated platforms. Operations with real B2B requirements generally need purpose-built wholesale infrastructure at the platform level.