Disable/Remove Ecommerce Functionality

Have the ability to remove/disable the ecommerce functionality on a project.

If you enable this to try it out, or download a template which has it enabled, there's currently no way to disable it. Especially frustrating if you have a client that is using the editor.

  • Alex Dixon
  • Mar 20 2020
  • Reviewed
  • Gage Media commented
    19 Jun 05:59pm

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

  • William Gen commented
    29 Apr 07:53pm

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

  • Denes Papp commented
    2 Apr 08:26pm

    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

  • Denes Papp commented
    2 Apr 08:22pm

    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

  • Marcel Acunis Zuker commented
    1 Mar 01:41am

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

  • Edwin Brito commented
    12 Feb 10:34pm

    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

  • Ana Ramos commented
    29 Jan 04:35pm


  • Nicolas Mondré commented
    25 Dec, 2023 05:34pm

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

  • Duncan Hamra commented
    21 Nov, 2023 03:59pm

    This would be pretty handy.

  • X4RM Biz commented
    28 Sep, 2023 08:58pm

    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.

  • Geovany Gameros commented
    28 Sep, 2023 08:57pm

    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?

  • X4RM Biz commented
    28 Sep, 2023 08:55pm

    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.

  • Online Appeal commented
    16 Sep, 2023 05:59pm

    Really annoying!

  • Alec Zimmer commented
    12 Jul, 2023 08:03pm

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

  • Shawn Meyer commented
    22 Jun, 2023 03:03pm

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

  • Lindsey commented
    2 Jun, 2023 04:16pm

    Upvote. This is so confusing for clients who don't use the ecommerce portion of a template.

  • Mark Drever commented
    30 May, 2023 01:52am

    Ridiculous bug that needs to be fixed asap

  • Sheree Dillon commented
    29 May, 2023 02:33am

    I can't believe this isn't a thing. I downloaded an eCommerce template thinking, surely I would be able to remove the eCommerce functionality pretty easily but turns out you can't. Starting to think I have to somehow start a new site. Not even sure I can now. Pretty disappointing for me and my client.

  • Rosie FreelanceFlow commented
    25 May, 2023 05:04am

    I hope this will be implemented soon. It is a bummer.

  • John Mitchell commented
    17 May, 2023 10:03am

    Upvoting! I love Webflow to bits, going all the way back to 2014. I rarely have complaints about the platform, but this one is hitting.

    It's becoming increasingly difficult to achieve sufficient Lighthouse Performance scores, without having any control over customising render-blocking scripts (and the amount of scripts loaded by WF in general).

    The amount of additional code + the sheer number of additional requests from Webflow Ecommerce takes a toll on performance and thus the UX/CS & SEO.

    Even after removing the Cart and any Ecommerce functionality off non-ecomm product pages, there are still so many scripts loading from Stripe & PayPal, as well as additional fonts they rely on, iFrames and extra DOM elements. This is especially an issue on Mobile, where bandwidth can be far more limited for users.

    The fact that Stripe & PayPal scripts take priority over loading Fonts (and just about everything else) is another real annoyance.

    Lacking the ability to disable certain functionality/preventing certain features/scripts from loading on pages feels far away from the reason Webflow felt so magical in the beginning; unlike other platforms, Webflow was not overwhelmed by bloat. Sadly, it's starting to feel like WF is losing its charm in this regard. Further, the simple fact there is little WF designers/devs can do about this, seems too restrictive. It's not a good feeling, looking at massive waterfalls of requests or performance reports full of red, knowing there is nothing that can be done.

    Don't get me wrong, I still love Webflow and all the additions that have been added over the years. It would just be great for us to have more control over what's packaged together and loaded in the final build, instead of having to accept bloat, suboptimal performance and a lesser customer experience.

    Investing some serious time in foundational work like this (and many other areas people bring up), would be much preferred over seeing yet a new feature released, which adds to the codebase/requests, with no ability to opt out.

    That's my two cents, anyhow. Lots of love to the WF team.

  • Load older comments
  • +1024