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
  • Online Appeal commented
    16 Sep 05:59pm

    Really annoying!

  • Alec Zimmer commented
    12 Jul 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 03:03pm

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

  • Lindsey commented
    2 Jun 04:16pm

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

  • Mark Drever commented
    30 May 01:52am

    Ridiculous bug that needs to be fixed asap

  • Sheree Dillon commented
    29 May 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 05:04am

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

  • John Mitchell commented
    17 May 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.

  • Mathieu Preau commented
    9 May 08:44am

    I clicked by mistake on a button an a whole ecommerce feature that is impossible to delete, with a lot of unused templates pages are now here, permanently. I hope you are working on that insane behaviour.

  • Nathan Hovatter commented
    27 Apr 12:48am

    Need to get this in the works asap

  • Michelle Kreil commented
    17 Apr 10:24pm

    Is this gonna be available soon? The most frustrating thing is that the JS is huge (over 1MB) because of all that ecommerce stuff. Pageload sucks! Although I don't use ecommerce anymore, it's still in the JS. I will copy-paste all my (very much) content into blank template now. Please stop me, if you soon manage to develop an easier way than that. THANK YOU!

  • Nick Houldsworth commented
    14 Apr 03:56am

    Honestly, this is such an unusual limitation in an otherwise excellent product. The offered workaround is to cross-site copy paste all the pages I want to keep, then switch plans and domains over the new site... all because I can't deactive 2 default ecommerce pages.

    What's more, because I purchased a template that had ecommerce enabled, when I upgraded from trial to paid, I was default presented with the ecommerce options.. it wasn't until after I put in my credit card that I realised I was paying for a plan I don't need, and now I'm stuck with ecommerce features I don't want

  • Dylan Worrall commented
    16 Mar 07:05pm

    Very frustrating when trying to port website to other platforms using udesly

  • Dylan Worrall commented
    16 Mar 07:05pm

    how is this still not a thing

  • Klaus Bartosch commented
    9 Feb 01:12am

    We never use the ecommerce pages on our website and we cannot delete those pages means it is totally frustrating. When copy pasted the URL mentioned in the ecommerce pages the sites navigates to a blank page and it is not good for our SEO. However, I have added the <meta name="robots" content="noindex"> then with the URL it navigates to our site pointing out to a page. ETA for the feature to be implemented ?

  • Guest commented
    8 Feb 05:55pm
  • Web Wizard commented
    24 Jan 06:43pm

    My only choice is to pay $42/mo or unpublish the site completely?! This is insane!

  • Isaac commented
    19 Jan 09:44am

    Really disappointing. My first project looks dead in the water after PAYING! for a premium template that has a sales page that cannot be deleted!

  • Sorakthun Ly commented
    19 Jan 03:44am

    How many more votes do you need?

  • Vinny Pizzi commented
    12 Jan 09:46pm

    Two years later and this has still not been implemented? Seems like an easy win. Ridiculous.

  • Load older comments
  • +913