still open? hmm 🤨

Please! It affects our performance, allow us to delete or remove e-commerce.

Need this too!

Really needed.

This needs to be fixed ASAP. Essentially Webflow is allowing template creators to charge more by adding e-commerce features that no one uses. Then if you have an agency plan it makes white label useless and gives no option to remove the e-commerce features that rarely anyone ever uses.

I understand Webflow trying to increase e-commerce usage, but it's not working and there are better options for e-commerce. Do the right thing and allow people to remove the e-commerce features/pages.

A lot of the templates now have ecommerce on categories that are not even necessary just to charge more. This is not right!

Are there any updates here? This is a major inconvenience for new Webflow users who rely on templates.

Please move this from 'Reviewed' to 'In Progress'

This is such a big annoyance that I'm wondering if the nice page builder UI is worth it or if I should switch to some other platform where I can really optimize page load speed.

Page load speed should be an absolute priority, but all that Webflow does is provide a CDN. There should be much more (just look at what else Cloudflare can optimize). The CI build process should really remove all unused JS code (including Ecommerce), as well as optimize images in next-gen formats (instead of and slow old PNG/JPG), lazy-LCP/FCP scores and overall speed scores, etc

Bloated Ecommerce JS code makes my Lighthouse score bad even though I'm not using Ecommerce at all. It was enabled because I imported a template that I purchased. Since then I deleted all the Ecommerce and CMS things but the Webflow JS file is still bloated with unused Ecommerce code (GraphQL, moment.js, etc).

My whole site is optimized, cached and further optimized in Cloudflare, and this 287kb Webflow JS file singlehandedly degrades my Lighthouse score :(((((

There should be a feature to turn off all the features that we don't need and let us have as little Webflow Javascript embedded as possible. The best would be if JS wouldn't be needed at all unless it's used. Even then, tree shaking should remove all the unused code during your CI build when we publish pages

Absolutely essential and needs to be implemented asap, I can't believe that I'm facing this limitation right now

Using a template shouldn't force you to get an ecommerce plan just because it was designed like with ecommerce features.
Include a toggle to easily enable/disable the ecommerce features please

Upvote

Absolutely essential and needs to be implemented asap, I can't believe that I'm facing this limitation right now

This would be pretty handy.

One more thing... you could probably save money (and increase profit) by simply leaning into the Designer product and allowing integrations with more robust (or widely used open source) CMS such as WordPress or Ghost, or even Substack, etc... additionally E-Commerce (Shopify, Magento).

You'll actually keep the competitive advantage of the Designer but encourage other customers to go after a deeper feature set for visual/UX. Better strategy imho.

It's very annoying to have all the E-commerce routes like "/checkout", "/order-confirmation", "/paypal-checkout" in the generated sitemap. This is lowering the site's SEO ranking.

Is there a plan to add an opt-out option?

Webflow's primary feature set is the designer... it's why we chose Webflow.

The extra feature sets (CMS, E-commerce) should be as simple "Enable / Disable E-commerce" and "Enable / Disable CMS". Any connections would simply show "E-commerce or CMS Disconnected" in place of text/data items.

Treat them as 3 complimentary (but separate) products and you'll retain the customers who love Webflow for design... then maybe as the CMS and E-commerce products improve, we'll consider using those.

Please fix, as it hinders the user experience and ease of publishing. Thanks.

Really annoying!

Surprising that this isn't resolved, agree that this is basic functionality and very confusing to a new user considering plans.

It's frustrating that webflow doesn't consider this basic functionality