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
  • Jonas Börste commented
    04 Dec 18:35

    Why is this important and basic functionality STILL not fixed yet @webflow? :(

  • Krystian Blaszczyk commented
    20 Oct 19:38

    still open? hmm 🤨

  • Eugene Guye commented
    17 Oct 17:14

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

  • Georg Kirbis commented
    12 Aug 12:35

    Need this too!

  • Ahmed Maher commented
    28 Jul 13:37

    Really needed.

  • Mark Johnson commented
    11 Jul 19:30

    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!

  • Gage Media commented
    19 Jun 17:59

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

  • William Gen commented
    29 Apr 19:53

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

  • Denes Papp commented
    02 Apr 20:26

    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
    02 Apr 20:22

    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
    01 Mar 01:41

    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 22:34

    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 16:35

    Upvote

  • Nicolas Mondré commented
    December 25, 2023 17:34

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

  • Duncan Hamra commented
    November 21, 2023 15:59

    This would be pretty handy.

  • X4RM Biz commented
    September 28, 2023 20:58

    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
    September 28, 2023 20:57

    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
    September 28, 2023 20:55

    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
    September 16, 2023 17:59

    Really annoying!

  • Alec Zimmer commented
    July 12, 2023 20:03

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

  • Load older comments
  • +1063