If you're seeing a "Conflict" error message when trying to downgrade your Webflow Ecommerce Basic site to a CMS Plan, the issue is most likely tied to settings or active eCommerce features on your site that must be removed before downgrading.
1. Understand the Conflict Error
- Webflow throws a Conflict error when you try to downgrade an account that still has Ecommerce features enabled, even if you're not actively selling on the site.
- The platform requires that all Ecommerce-specific content and functionality be removed before switching to a lower-tier plan like CMS.
2. Remove Ecommerce Features From Your Site
To downgrade, you must permanently delete Ecommerce-related data:
- Go to the Designer, then open the Ecommerce panel (shopping cart icon on the left).
- Delete all:
- Products
- Categories
- Coupons
- Shipping methods
- Taxes
- Payment providers (disconnect Stripe or PayPal)
- Delete the Ecommerce cart and checkout pages from the Pages panel.
- Remove Ecommerce elements (e.g., Add to Cart buttons, product lists, etc.) from all pages.
Note: You must remove all Ecommerce data completely. Simply hiding pages or disabling products is not enough.
3. Check CMS Limitations
Ensure your site:
- Uses fewer than the CMS plan limits (e.g., 2,000 CMS items max).
- Does not exceed CMS bandwidth or page limits.
4. Clear Billing Conflict
If you've tried switching cards and still see a conflict:
- Go to Site Settings > Billing > Current Plan
- Confirm there are no overlapping billing cycles or add-ons causing a management conflict.
- Try removing the existing site plan first (this makes the project unhosted) and then re-purchase the CMS Plan.
5. Contact Webflow Support
If the error persists after all cleanup:
- Submit a ticket at Webflow Support
- Provide your site URL, screenshots of your Ecommerce panel, and the exact error message.
Summary
To downgrade from Ecommerce Basic to CMS in Webflow, fully remove all Ecommerce products, elements, and data from your site. If you've done this and still get a conflict error, consider removing the existing site plan, checking for CMS limit violations, and contacting support for plan override assistance.