You're encountering a "Conflict" error when trying to downgrade from an Ecommerce Basic plan to a CMS plan, likely due to residual ecommerce settings or products still active in the project.
1. Remove All Ecommerce Features
- Go to the Ecommerce panel in the Designer.
- Delete all products, product categories, and collections associated with ecommerce.
- Remove any custom checkout or cart pages from your Pages panel (you may need to delete or unassign them).
- In Settings > Ecommerce, disable or delete any connected payment gateways like Stripe.
2. Confirm Ecommerce Has Been Fully Disabled
- Once you’ve removed all ecommerce elements, go to Project Settings > Ecommerce.
- The tab should show that ecommerce is not enabled. If it's still active, check again for any remaining ecommerce-connected fields or pages (e.g., abandoned cart emails, customer accounts).
3. Publish the Site After Cleanup
- Publish the site after removing ecommerce features to make sure changes sync to the backend.
- This step is often necessary to allow billing changes.
4. Downgrade the Site Plan
- Now go to Project Settings > Billing > Site Plan.
- Click “Edit Site Plan” and select the CMS plan.
- Apply the downgrade and confirm. This should now process without the conflict error.
5. If Error Persists
- If everything is removed and you still get the conflict error:
- Try clearing your browser cache or using Incognito mode.
- Contact Webflow support directly via their support form or live chat. Mention that ecommerce was cleared and you're receiving a "Conflict" error on downgrade.
Summary
To downgrade from an Ecommerce Basic to a CMS plan in Webflow, you must completely remove all ecommerce content and settings, publish the site, and then try the downgrade. If the conflict error persists after that, contact Webflow support to resolve backend locking issues.