Webflow Ecommerce or Just a Stripe Payment Link?

Do you need Webflow Ecommerce or just a Stripe link?

If you sell a handful of things to businesses, a Stripe payment link is usually enough. Webflow Ecommerce earns its cost when you have a real catalogue, a cart that holds several items, and a checkout that has to feel like part of your site. Below that, you are paying for a store you do not have.

This comes up on B2B projects more than you would think. A company wants to sell one training course, a report or an annual membership, and the default assumption is that selling needs an ecommerce plan.

It often does not. The numbers are worth doing before you commit.

What does Webflow Ecommerce actually cost?

A monthly plan plus a transaction fee on the lowest tier, on top of whatever your payment processor charges. Webflow's pricing page lists the Standard ecommerce plan at 29 dollars a month billed yearly, with "500 ecommerce items" and a "2% transaction fee."

The higher tiers remove that fee. Plus is listed at 74 dollars a month billed yearly with "5,000 ecommerce items" and a "0% transaction fee," and Advanced at 212 dollars a month billed yearly with "15,000 ecommerce items" and the same zero fee. Both add unbranded transaction emails.

The critical detail is that the transaction fee stacks. Webflow's own note on that row says it applies "In addition to Stripe or Paypal processing fees." So on Standard you are paying Webflow 2 percent and your processor its own cut on the same sale.

Webflow also states the plans carry no revenue ceiling, describing unlimited sales volume as "No cap on your store's gross merchandise value (GMV)." All prices on the page are noted as USD, per site, per month, plus applicable taxes.

What does a Stripe Payment Link cost?

Processing fees only. Stripe's pricing page lists standard card processing at "2.9% + 30¢ per successful transaction" for domestic cards, adding 1.5 percent for international cards and 1 percent where currency conversion is required. Payment acceptance is listed as "Included with Payments."

There is no platform charge on top. Stripe states it does not charge setup fees, monthly fees or hidden fees under standard pricing, which means a payment link has no fixed monthly cost at all.

That is the whole comparison in one line. A payment link costs you the processing fee. Webflow Ecommerce costs you the processing fee plus a plan, and on the cheapest plan a second percentage as well.

At what revenue does the Webflow plan pay for itself?

Run the arithmetic on the published prices and the answer is clearer than it feels. Moving from Standard to Plus costs an extra 45 dollars a month and removes a 2 percent fee. Two percent of 2,250 dollars is 45 dollars, so around that monthly revenue the upgrade starts saving you money.

Below that figure, Standard is the cheaper Webflow tier. Above it, Plus is, and the gap widens quickly as volume grows. This is the calculation we see teams skip, and it is the one that decides which plan is right.

Comparing either plan against a plain payment link is a different question, because you are no longer only comparing cost. You are comparing cost against what the store gives you, and that trade is not a number.

What do you give up with a payment link?

Control of the checkout experience and anything resembling a catalogue. Stripe's own documentation is upfront that Payment Links use a "Stripe-hosted page" with customisation it describes as "Limited." The footnote defines that limit as "20 preset fonts, 3 preset border radius options, and custom logo, background, and button colors."

What you need	Stripe Payment Link	Webflow Ecommerce
Checkout on your own domain and design	No, Stripe hosted	Yes, custom cart and checkout
Cart holding several products	No	Yes
Products managed as site content	No	Yes, as ecommerce items
Subscriptions	Yes	Via Webflow plans and processors
Monthly platform cost	None	29 to 212 dollars per site
Extra percentage on top of processing	None	2 percent on Standard, 0 on higher tiers
Setup effort	Stripe rates it 1 out of 5	A build

Worth noting that a payment link is not as limited as people assume. Stripe's docs say you can "sell a product, a subscription, or accept a donation," reuse a link "multiple times with multiple customers, or limit the number of purchases," and even "create an embeddable buy button for your website."

What do you give up without Webflow Ecommerce?

The parts that make a store feel like a store. Webflow's pricing describes its custom shopping cart as the ability to "Take full control of your shopping cart design and layout," and a real cart is the thing a payment link fundamentally cannot do.

You also lose products as managed content. Ecommerce items behave like CMS content, which means your team can add a product without a developer and the product can appear across the site in collection lists. A payment link lives in your Stripe dashboard, disconnected from your site content.

And you lose the operational furniture. Webflow's ecommerce plans list custom shipping rules, staff accounts, order emails you can brand, and integrations with Meta, Google Shopping and Mailchimp. None of that matters for one report. All of it matters for forty products. We covered the wider feature set in our guide to Webflow Ecommerce.

Which one fits a B2B company?

Usually the payment link, because most B2B selling is not retail. You are selling a course, a report, a workshop seat or a membership. That is a small number of items at a considered price, often after a conversation, and it does not need a cart.

The exception is when the thing you sell has genuine variety. A company selling physical kit, training in multiple formats, or a product range with options has a catalogue, and catalogues want a store.

Our rule of thumb is the cart test. If a buyer would ever add two different things and check out once, you need ecommerce. If every purchase is one item, a link handles it and you keep the monthly cost.

What about tax and VAT?

Both routes handle it, so this should not decide the question. Webflow's pricing lists automatic tax calculation as the ability to "Automatically calculate sales tax and VAT at checkout." On the other side, Stripe's documentation lists Stripe Tax as supported on Payment Links.

So the choice is about who you would rather configure it with, not about capability. Both add their own cost and their own setup, and neither removes your obligation to know where you have a tax liability.

What we would say plainly is that cross border digital sales are the part worth getting advice on. The tooling calculates what you tell it to calculate.

Can you start with one and move to the other?

Yes, and that asymmetry should shape the decision. Starting with a payment link and adding Webflow Ecommerce later costs you a build when you need it. Starting with an ecommerce plan you do not need costs you money every month until someone cancels it.

Moving up is also easier than people fear, because the product data is usually small. Twelve items retyped into ecommerce items is an afternoon, not a migration.

The one thing to keep clean either way is your URLs. Put the purchase page somewhere stable from the start so links in emails and decks survive a change of mechanism. Our notes on Webflow plan limits cover the related constraints.

What would we recommend?

Start with a Stripe payment link for anything under roughly ten products, and reach for Webflow Ecommerce when a cart becomes genuinely necessary rather than merely tidy. That order keeps your fixed monthly costs at zero while you are still finding out whether people actually buy the thing.

If you do go to Webflow Ecommerce, check the transaction fee arithmetic against your expected volume rather than defaulting to the cheapest plan. On Standard, that 2 percent quietly becomes the largest line in the comparison once revenue grows.

If you are weighing this up for a specific product, or your pricing page needs to carry the decision well, we are happy to work through it with you. You can find us at phoenix.studio, and our notes on pricing page design cover the page itself.