Webflow Logic Is Discontinued: Ecommerce Workflows

Webflow Logic is discontinued. If a tutorial, an agency proposal or an old site handover tells you to run your store's rules in Logic, that plan no longer works. Your first action is a test on any Logic-era store you own: place a test order, submit the newsletter form and confirm that the downstream thing you assume still happens actually happens.

That makes the comparison in most older articles one-sided, and this post is the updated version. The useful question is which surviving path each ecommerce workflow belongs on, and how much of your store's behavior you are willing to hand to something you cannot debug. The dates and limits below were checked against Webflow's own pages on 30 September 2026.

Is Webflow Logic Still Available for Ecommerce?

No. Webflow sunset Logic on June 27, 2025: it is disabled on all sites, existing flows are disabled and forms that were connected to Logic are now standard Webflow forms.

Webflow's deprecation update, launched on December 11, 2024, set that date and allowed customers to keep activating Logic through January 31, 2025. The Logic sunset help article says you must rebuild flows in an alternative such as Zapier or Make, and that Webflow's recommended partners are those two.

The failure mode is quiet. Consider a store where a Logic flow tagged customers after checkout. After the sunset the form still submits and the submission still lands in Webflow, but the branch that did the tagging no longer runs, and nothing announces it. That is why the test order matters more than opening the Designer.

What Replaces Logic in a Webflow Ecommerce Stack?

Four paths absorb the workload and they are not interchangeable: external automation, vetted Webflow Apps, your own code on Webflow Cloud, or a commerce engine outside Webflow.

Pick per workflow, not per site. Most stores I would design end up running two of these at once, which works as long as you can say which system owns which rule.

Consider a two-person team selling forty products in one currency. Order notifications and CRM sync go to Zapier or Make, one vetted app covers reviews, and nothing else is needed. Now consider a store that sells the same item through a shop, a marketplace and Webflow. The stock rule needs code and a schedule, and the notifications can still stay in the automation tool. That split, with each rule owned by exactly one system, is the whole method. Both examples are hypotheticals, not client stories.

The third row is the newest option. Webflow Cloud deploys a Next.js app (version 15 or higher), an Astro app (version 6 or 7), a Vite app (version 6.1 or higher) or a static app from GitHub, on an Edge runtime. That is a sanctioned place for the server-side logic Logic used to cover.

It has sharp edges that the documentation states plainly. Only npm is supported. Webflow Cloud runs the framework's own build and ignores a custom build script in your package.json. Cache headers set by your app are overridden. On the Edge runtime, stick to fetch for API calls, because clients like axios may not be compatible. Read that list before you plan the migration, not during it.

When Does Ecommerce Need Custom Code?

Custom code becomes necessary when a rule needs state, an outside data source or a decision the checkout cannot express, such as multi-currency pricing, tax engines, inventory reconciliation and fraud checks.

Can Webflow Ecommerce Handle Multiple Currencies?

Webflow's store setup guide describes a single store currency that is appended to product prices and shipping rates. The request for multiple currencies on the Webflow Wishlist was filed on April 9, 2019, has 371 votes and carries the status Reviewed. Developers in the comments discuss stitching the feature together outside Webflow, which is a second system to maintain, not a setting to toggle.

Why Does Inventory Need a Job, Not a Zap?

Inventory reconciliation needs code because the rule has to hold state and decide which system wins. If a shop's point-of-sale system, a marketplace listing and a Webflow store all decrement the same shelf, you can oversell whenever two of them sell the last unit at nearly the same time. A scheduled job that reads each system, compares counts and applies one winner fits that shape. A trigger-and-action automation does not. This is my recommendation from how the pieces work, not a measured result.

Tax follows the same logic as currency. If you need a tax engine's answer instead of a table you typed in, you need a place to call that engine from, and a Webflow Cloud app or a small worker is that place. Check Webflow's tax settings for your regions first, because a domestic store selling physical goods may not need anything more.

Fraud checks sit in the same bucket. You want to look at an order before it is fulfilled, compare it to history and act on it. Tools can score an order, but the acting part usually lives in your code.

What Do Webflow's Ecommerce Plans Cap?

The pricing page lists three ecommerce plans, and the item cap is the first thing to compare against your catalogue.

These are added on top of a site plan. A store that thinks in tens of thousands of SKUs is outside the published range.

The Webhook-and-Worker Pattern

For anything that must be reliable, stop trying to express the rule in a builder and run it as a small service triggered by the order itself. The steps are boring on purpose.

1. Register a webhook for the ecomm_new_order trigger. Webflow's docs list it as the event for a new order.
2. Have the handler do one thing: write the raw payload to a queue or table and return quickly. A handler that does work inline is the one that times out and gets retried into duplicates.
3. Key every downstream action on the order ID, because retries are normal and every action must be safe to run twice.
4. Read money fields carefully. In the orders API example, a price object carries a unit, a value of 21155 and a string of $211.55 USD, so the value is in cents. Treating it as dollars is the classic first bug.
5. Reconcile on a schedule as well as on the webhook. The orders endpoint needs the ecommerce:read scope and pages its results, and the docs example uses a limit of 100, so a nightly sweep needs pagination and a stored offset.
6. Alert on your own failures. A silent workflow is exactly what a Logic-era store had after June 2025, and finding out is the point of owning the code.

Should You Leave Webflow When the Workflow Is the Product?

Yes, when the ordering rules are the value and the storefront is the smaller half of the job. That was the case for a project on this site.

Pizzeria Bestek is a React and Supabase ordering platform for a family-run pizzeria in Biograd na Moru, replacing a third-party ordering platform with a build the restaurant owns. Its case study lists rules a builder would struggle with. Delivery-zone validation runs at the address field before submission, not as a decline email afterward. The pickup-time picker respects a rolling kitchen window, so nobody can book a pizza five minutes out. Email templates branch across four languages depending on whether the order is pickup or delivery, because the alternative offered to a declined customer differs.

The case study reports that the site went live in September 2025, handles five to ten orders a day, seven days a week, and that each order is 100% revenue instead of roughly 70% after aggregator commission. The workflow logic was the reason to write code, and the site came with it.

Most Webflow stores should not build any of this. If you sell a few dozen products in one currency to one country, native tools plus one app cover you. The signal to move is a rule you have already written down twice in two systems, for example a promo that exists as a Webflow discount code and again in an automation that emails a different discount to a different segment. That is the week to consolidate.

If the automation is light, keep it light: pairing Webflow with Zapier handles a lot and runs off the page. If the constraint is the CMS rather than the workflows, the best CMS platforms for marketing sites shows where Webflow fits, and WordPress versus a custom website covers the self-hosted fork. Before committing to custom work, what a website build costs tells you whether it fits this year's budget.

List every automation that touches an order on your store today, and next to each one write the name of the person who would fix it on your busiest sales day. Which row is blank?