PinwheelThe £79–£99 per month subscription fee isn't the problem. It's reasonable for what it covers: hosting, a basic storefront, a simple admin panel. Most florists running Florist Touch or Florist Pro don't feel the squeeze from the subscription itself.
The hidden costs are what accumulate quietly alongside it.
1. Transaction Fees at Volume
Most florist platforms charge per-order fees on top of the monthly subscription. Florist Touch charges a percentage per order processed. Florist Pro similarly applies processing fees.
This is easy to ignore when you're doing 15–20 orders a week. It becomes significant when you scale.
Take a florist processing 200 orders a week at an average order value of £60. That's £12,000 per week in revenue — roughly £50,000 per month. A 1% platform transaction fee on that volume is £500 per month. At 2%, it's £1,000 per month. On top of your subscription. On top of your payment processor's fees.
Over a year at the lower figure, that's £6,000 in platform fees alone — not including the Stripe or card processing fees that run separately.
A self-hosted Medusa.js backend on Railway costs approximately £80 per month in infrastructure. There are no per-order platform fees. Your only transaction cost is the payment processor (Stripe), which you'd be paying anyway on any platform.
At high enough volume, the infrastructure cost comparison alone makes the case.
2. Developer Costs for Things That Should Be Standard
Here's where the hidden costs become genuinely frustrating: features that should be table stakes on a modern e-commerce platform require developer intervention on legacy florist platforms.
Examples we've seen clients pay for:
- Custom delivery zones — the default postcode groups don't match the client's actual delivery area. A developer charges £200–£400 to write a custom zone script.
- Same-day cut-off logic — the platform's built-in cut-off doesn't account for weekends, bank holidays, or seasonal variation. Another custom job.
- Gift message formatting — the standard gift message field doesn't print cleanly in the right format for the team's process. Hours of developer time to sort it.
- A second product category structure — the platform's product taxonomy doesn't support the way the florist wants to organise their seasonal and event ranges.
None of these are edge cases. They're all things a reasonably complex florist business needs. And on a template platform, each one is a custom project with a quote attached to it.
Over two to three years, the accumulated developer fees for "small tweaks" often exceed the cost of a complete rebuild on infrastructure that doesn't require them.
3. Seasonal Infrastructure Risk
Florist platforms are shared infrastructure. Your storefront, and 500 other florists' storefronts, share the same servers.
Most of the time, this is fine.
On Mother's Day, Valentine's Day, and Christmas Eve, it is not fine.
These are precisely the moments when your platform needs to perform flawlessly — when every customer who gets a slow-loading checkout page or an error message is a lost order. They're also precisely the moments when shared infrastructure is under maximum stress from the aggregate traffic of every florist on the platform simultaneously.
We've spoken to florists who experienced checkout errors and slow load times on Mother's Day while running on shared platform infrastructure. The platform vendor's support team is responding to dozens of similar tickets at the same time.
A dedicated, self-hosted deployment doesn't share its resources with anyone. Your platform performs exactly as well on Mother's Day as it does on a Tuesday in November.
4. The Opportunity Cost of Manual Workarounds
This is the hardest hidden cost to quantify, but often the largest.
Every manual workaround your team runs around a platform limitation is operational time that doesn't exist in a better-architected system.
Examples from florist operations we've worked with:
- Manual WhatsApp relay — staff manually forwarding order details to the fulfilment team because the platform doesn't support real-time team notifications. 30–60 minutes per day across the team.
- Spreadsheet inventory reconciliation — running two storefronts on separate platform instances, reconciling stock manually between them. Several hours per week.
- Phone order entry — the platform doesn't have a clean way to enter phone orders into the same system as web orders, so phone orders go into a separate spreadsheet and get managed separately. More administrative overhead, more reconciliation.
- Manual customer updates — calling or emailing customers because the platform's notification system can't be customised sufficiently to give customers accurate, stage-appropriate updates.
These aren't failures of the business. They're rational adaptations to platform limitations. But they represent real staff time with real cost — and they don't disappear unless the underlying platform limitation is resolved.
5. Lost Conversion from Performance
Page speed is a conversion rate factor. Google's research consistently shows a correlation between load time and bounce rate — and specifically that conversion rates fall sharply as page load time increases beyond 2–3 seconds.
Legacy florist platforms, running on shared PHP hosting behind WordPress-style themes, typically score in the 40–60 range on Google PageSpeed Insights. A well-built Next.js storefront with edge caching scores 90+.
If your conversion rate improves by even 0.5% at the same traffic level, on £50,000 per month in revenue, that's £250/month in additional revenue. Over a year, that's £3,000. The platform's performance isn't just a technical metric — it has a direct commercial value.
Putting It Together
| Cost category | Template platform | Headless (Medusa.js) |
|---|---|---|
| Monthly subscription | £79–£99 | £0 (infrastructure only) |
| Infrastructure (hosting) | Included | ~£80/mo (Railway) |
| Per-order platform fees | 0.5–2% of revenue | £0 |
| Custom development for standard features | Recurring | One-off (built into initial build) |
| Seasonal infrastructure risk | Shared (real) | Dedicated (eliminated) |
| Manual workflow overhead | High | Automated |
| Conversion rate impact | Moderate performance | High performance |
The subscription fee comparison isn't where the argument lives. The argument lives in the compound effect of transaction fees at volume, recurring developer costs for platform workarounds, manual staff overhead, and the lost revenue from lower conversion rates and seasonal failures.
Run your own numbers with our ROI calculator →
For high-volume florists, the maths often lands on a significantly higher true cost of ownership for the "cheaper" template platform option — and a shorter payback period for a custom build than most florists expect.
We're not in the business of selling unnecessary complexity. If your platform is working well for your operation, change nothing. But if you're recognising any of these costs in your business, it's worth a conversation.