PinwheelIf you're a florist running on Florist Touch, Florist Pro, or Florist Window, this isn't an attack on those platforms. They got you online. For many independent florists, they're exactly the right tool.
But there's a pattern we see repeatedly: a florist grows, their operation gets more complex, and they start hitting limits they can't engineer around. They pay for a developer to bolt on a workaround. Six months later, they need another workaround for the workaround. Eventually, they're spending more time managing their software than running their business.
This article is for florists at that inflection point.
What the Legacy Platforms Are Good At
Florist Touch, Florist Pro, and Florist Window share a core strength: they're purpose-built for florists, they're quick to set up, and they handle the basics well. Product listings, a basic delivery checkout, order management in a simple admin panel.
If you're running a single-location florist doing straightforward local delivery with consistent slot times and a manageable order volume, they're probably fine.
The ceiling appears when your business stops being simple.
Where the Ceiling Actually Is
1. Delivery Logic That Matches Your Operation
Florist delivery is genuinely complex. Most platforms assume: customer selects a date, you deliver, done.
Real operations look more like this:
- Local delivery up to 5 miles, same-day if ordered before 1pm
- Regional delivery to 40+ named postcodes, next-day, order before midnight
- National courier, 2–3 day lead time, minimum order £60
- No delivery to certain postcodes (EC1, W1, etc.) on weekends
- Valentine's Day and Mother's Day have different cut-off times and different product availability
- Some products (large arrangements, sympathy tributes) can't go national courier
Template platforms handle the basic version of this. They cannot handle all of it accurately without manual intervention on edge-case orders — which means your team is constantly fielding calls from customers whose postcode wasn't handled correctly at checkout.
A headless build encodes all of these rules directly into the checkout logic. The customer either gets a valid delivery slot or they don't — there's no ambiguity and no manual correction needed.
2. Multi-Recipient Orders
Wedding clients. Corporate gifting. A customer sending flowers to their mum, their sister, and their grandmother in a single order.
Multi-recipient checkout — where a single order contains multiple delivery addresses, individual gift messages, and separate delivery dates — is a feature that simply doesn't exist in standard florist platforms.
We built this for our clients. It's one of the most operationally significant changes they experienced: corporate clients moved from placing multiple separate orders (three orders, three sets of confirmations, three separate tracking lines) to a single unified order that your team processes once.
3. A Second Storefront
This is the question that exposes the limits of template platforms faster than anything else: "We want to launch a second brand."
On Shopify, you pay for a second full subscription. On WooCommerce, you maintain two separate sites with two separate backends. On Florist Touch, you essentially start from scratch.
Headless architecture approaches this differently. The backend — products, inventory, orders, pricing — is shared infrastructure. A second storefront is a second Next.js frontend that connects to the same Medusa.js backend. You don't duplicate your inventory management. You don't run separate order management systems. Your staff use one portal for everything.
We run this in production with the Blooms group: three storefronts, one backend, one admin dashboard.
4. Internal Automation
Every florist operation involves manual communication that doesn't need to be manual.
Order comes in → someone types the details into WhatsApp → fulfilment team reads it → prepares the arrangement → updates the order status manually → customer has no idea where their order is.
This is a solved problem. Medusa.js supports workflow hooks that fire on order events. When an order is placed, confirmed, dispatched, or delivered — those events can trigger WhatsApp notifications to your team and transactional emails to your customer, automatically, every time.
Your team still does the arrangement and the delivery. They just stop spending 45 minutes a day on manual order communication.
5. The Admin Panel Problem
Florist Touch and Florist Pro's admin panels are designed for a generic small retail business. They weren't designed for:
- A fulfilment coordinator who needs to see all orders for tomorrow sorted by delivery slot, flagged by zone, with any special instructions highlighted
- A manager who wants to see revenue split by storefront and by product category this week vs. last week
- A driver who needs a route-ordered list of addresses for the afternoon delivery run
A bespoke staff portal is built around how your team actually works. Not around what a platform vendor thought a generic small business might want.
What Headless Architecture Actually Means for a Florist
"Headless" is a technical term that means the storefront (what customers see and interact with) is decoupled from the commerce backend (products, orders, inventory, fulfilment). They communicate via API rather than being the same monolithic application.
For a florist, this means:
The storefront (Next.js) is custom-designed, extremely fast, and entirely yours. Your delivery logic, your product structure, your checkout flow — all engineered to your operational requirements, not constrained by a template.
The backend (Medusa.js) manages your products, inventory, pricing rules, promotions, order lifecycle, and fulfilment workflows. It's programmable, so any operational requirement you have can be built into it.
The result is a platform that does exactly what you need and nothing you don't — with no workarounds, no plugin dependencies, and no hard ceiling.
The Honest Trade-Off
This isn't for every florist. The headless approach involves a higher upfront build cost, requires an ongoing technical partner to manage the infrastructure, and takes longer to set up than buying a Florist Touch subscription.
It's the right choice if:
- You're processing a high volume of orders and operational errors are costing you time and reputation
- You have (or want) more than one storefront
- Your delivery logic is complex enough that it can't be accurately expressed in a template platform
- You want automation that eliminates manual communication overhead
- You're planning to scale the business and need infrastructure that scales with it
If you're a single-location florist doing 30–40 orders a week with straightforward local delivery, Florist Touch is probably the right call. Genuinely.
If you're past that, we should talk.
What the Transition Actually Looks Like
We've migrated florist businesses off legacy platforms. The process typically involves:
- Discovery — mapping your current delivery zones, cut-off rules, product structure, staff workflows, and integration requirements
- Architecture design — defining how Medusa.js backend structures reflect your actual business model
- Storefront build — Next.js frontend designed to your brand, engineered to your delivery requirements
- Staff portal — custom admin interface built around how your team works
- Data migration — products, customer records, order history
- Parallel testing — both systems run simultaneously before cutover
- Launch + onboarding — we don't hand over and disappear
The result is a platform you own, on infrastructure you control, with no per-order fees to a third-party platform.