Webflow ecommerce and CMS for retail sites
Evaluate Webflow ecommerce beside its CMS. Check product and content records, checkout needs, integrations and the limits that affect your store.
- Published
- Last updated
Webflow ecommerce suits a content-led retail site when its catalogue fits the item and variant limits and its checkout supports the store’s buying flow. Its content management system (CMS) connects buying guides to products, but editorial records and purchasable variants have different jobs.
Choose Webflow when your team needs direct visual control over those pages and can manage the documented payment and fulfilment setup. Choose Shopify when a larger variant range or its Australian commerce workflow decides the platform choice.
The store Webflow can support
Webflow can support a retailer that sells through its native cart and checkout while publishing structured editorial content beside the catalogue. The decision starts with what customers buy and how staff handle the resulting orders.
Webflow’s product-options documentation limits each product to 50 variants across up to three option sets. A hypothetical shirt in six sizes and eight colours needs 48 variants. Adding a ninth colour takes it to 54, beyond that product limit.
Shopify’s variant documentation allows up to 2,048 variants and three options per product. It also warns that some themes and apps need updates above 100 variants. That difference makes Shopify the stronger starting point for a range with many combinations.
Webflow and Shopify by operating need
| Requirement | Webflow | Shopify |
|---|---|---|
| Editorial control | CMS Collection fields connect to visually designed templates and lists | Metaobjects hold reusable structured content that a theme can display |
| Catalogue shape | 50 variants per product, with a separate plan-wide ecommerce item allowance | Up to 2,048 variants per product, subject to theme and app compatibility |
| Checkout | Native cart and checkout with visual design control | Hosted checkout, with advanced information, shipping and payment-page customisation tied to Plus |
| Australian payments | Stripe and PayPal connections, subject to account and payment-method eligibility | Shopify Payments in Australia supports cards and accelerated checkouts |
| Fulfilment | Order handling and tracking in Webflow, with integrations for additional workflows | Australia Post label purchasing through a connected MyPost Business account |
| Maintenance | Own the CMS templates, commerce configuration and any added scripts | Own the theme, apps and their compatibility with commerce changes |
Shopify’s metaobjects guide confirms that structured editorial content is possible within its commerce platform. Webflow’s visual CMS control is a reason to choose it when that editing model suits the team, not evidence that Shopify cannot publish retail content.
For an Australian retailer already using MyPost Business, Shopify’s Australia Post connection brings rates and label purchasing into the admin. Webflow’s order-management guide instead describes packing orders, entering tracking and connecting other fulfilment workflows. Account for that daily staff work before choosing on page design.
CMS collections and ecommerce products
Webflow CMS Collections store repeated editorial records, while Ecommerce Collections add the fields and behaviour needed to sell products. A Collection is the content type, and a Collection item is one record within it.
For example, a hypothetical Buying guides Collection can hold a title, introduction, body and related products. Webflow’s Collection-fields documentation supports reference and multi-reference fields that connect to Ecommerce Collections. A guide can therefore point to the actual Products records used by the store.
The product holds commerce information such as its price and options. A variant identifies the particular combination the customer buys, with its own price and inventory information. An editorial item describing a navy shirt does not become that shirt’s purchasable variant.
Use the distinction this way:
- Incorrect: create a guide item for each colour and use its text field as the stock count. Updating that text doesn’t manage commerce inventory.
- Correct: keep the purchasable colours and sizes in product variants. Reference the product from the guide and display the connected commerce data where needed.
Keep stable product identifiers when exporting data to search or shopping assistance. A guide supplies advice, while the commerce record supplies the item the customer can buy. Copying a price into prose creates a second value that someone must update.
Checkout, payments and fulfilment requirements
Webflow’s native checkout requires an Ecommerce Site plan, a connected payment provider and checkout enabled on the published site. A CMS-capable hosting plan alone does not enable sales.
Webflow documents Stripe and PayPal as its payment providers. It supports card payments and eligible wallets through those connections. Stripe’s availability list includes Australia, while Webflow’s payment guide makes merchant-country and provider restrictions explicit. Seller eligibility, customer payment methods and the countries you ship to are separate decisions.
Webflow shipping zones define where you fulfil orders. Its native methods can charge a flat rate or use order value, quantity, weight or a percentage. Choose rules that reproduce your actual delivery charges. A weight rule needs accurate product weights, while a price threshold needs the correct order subtotal.
Webflow’s tax guide lists automatic calculation for Australia, Canada, the European Union and the United States when the relevant shipping zones are configured. It also allows tax-inclusive product prices. Outside the supported countries, the guide requires calculation outside Webflow, which adds operating work for an international store.
For comparison, Shopify Payments in Australia combines payment processing with order management in the Shopify admin. Shopify’s checkout customisation rules also put advanced changes to the information, shipping and payment pages behind Plus. Choose on the payment and checkout behaviour you need, alongside its design.
Subscriptions and external services
Webflow’s legacy subscription instructions depend on User Accounts, which Webflow has retired. Those instructions are not a supported setup path for a new subscription store. Its sunset notice says existing paid subscriptions continue charging through Stripe, so retiring the website account system does not itself cancel billing.
If recurring purchases are central to your store, choose a separate subscription solution with an explicit account and billing workflow. Assign responsibility for cancellations and failed payments before selecting the storefront. A separate service is an integration dependency, not a native Webflow subscription feature.
Webflow also documents embedding Shopify products into a Webflow site using Shopify-generated code and CMS fields for product identifiers. In that arrangement, Shopify owns the commerce operation. Maintaining Webflow content alongside the embed is a different architecture from using Webflow Ecommerce, and the embed instructions do not promise automatic two-way catalogue sync.
Content delivery and API boundaries
Webflow’s CMS application programming interface (API) can read and change Collection items, with staged content kept separate from live content. Saving an item through the API does not by itself prove the public page changed.
The API’s permissions include cms:read and cms:write. Give a reading integration the permission it needs, and keep privileged credentials out of public browser code. A publishing workflow must also use the required endpoint permissions and publish operation.
A live item can retain its published version while an edit waits in staged content. An integration displaying public policy text needs the live version. An editorial tool preparing a revision needs the staged version. Record that choice explicitly so an unpublished correction does not appear in customer-facing answers.
Webflow’s rate-limit reference lists 120 requests per minute for Ecommerce plans. Its API returns a retry instruction when requests exceed the allowance. Imports and downstream refresh jobs need queuing and retry handling, especially when several tools share access.
Collection lists, filters and sliders
Webflow’s native Slider does not automatically create a slide for every CMS item, according to its Slider documentation. The documented workaround places a Collection list inside each manually created slide and limits it to the intended item.
Finsweet Attributes is a third-party JavaScript library. Its current directory names List Filter and List Slider for filtering lists and connecting CMS Collection lists to sliders. Older searches for Finsweet CMS Filter or CMS Slider can lead to legacy instructions, so use documentation for the installed version.
The extra script becomes part of the storefront’s maintenance. Confirm which fields the list supplies, how empty results display and whether keyboard controls still work after filtering. An API connection cannot configure those design components on its own.
Plan limits and the ongoing workload
Webflow’s Ecommerce plans set separate allowances for commerce items and editorial CMS items. Workspace billing covers a different part of the service from the Site plan that hosts and enables checkout.
Ecommerce plan allowances
| Plan | Ecommerce items | CMS items | Webflow transaction fee |
|---|---|---|---|
| Standard | 500 | 2,000 | 2% |
| Plus | 5,000 | Up to 10,000 | 0% |
| Advanced | 15,000 | Up to 10,000 | 0% |
Webflow counts products, variants and categories within the ecommerce allowance. The CMS allowance applies separately to editorial records. Count the imported catalogue and its variants before choosing a plan, leaving room for additions.
The Webflow transaction fee is separate from payment-provider processing fees. Budget for the Site plan’s billing term and applicable taxes, bandwidth, staff access and any external subscription or fulfilment service. A CMS-focused plan’s content allowance does not replace an Ecommerce plan’s checkout requirement.
Before committing to the platform, run two acceptance checks with a representative product and guide:
- Make a test purchase using the provider’s supported test flow. Select a variant and a delivery address in each intended shipping zone. Confirm the charged total, order record and stock behaviour, then verify the fulfilment and refund path.
- Correct a guide that references that product. Save it as a draft and confirm the public guide remains unchanged. Publish it and verify that the live page and each connected content consumer receive the correction.
Choose Webflow when both workflows fit your catalogue and the staff who will maintain it. If either requires a separate service, include its owner and running cost in the platform decision.
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.