A florist website carries two revenue streams in one shop window — the gift-bouquet checkout and the wedding-and-events enquiry flow — and each needs different treatment. Get the gift-bouquet checkout right and the site funds itself on volume; get the wedding flow right and the site funds the year on a handful of high-margin commissions. Most florist websites we audit do neither well, which is why the move to a properly-built site routinely doubles month-three revenue.
What is different about florist websites
Three things make florist web design distinct from generic small-business web design. First, the buying decision is visual — customers compare bouquets on imagery before they ever read the description, and the page weight and image quality of the gallery directly drive conversion. Second, the operational logic around same-day delivery cut-offs is non-trivial; getting it wrong creates a steady stream of refund-and-complaint cycles that eat the margin on every order. Third, the wedding enquiry flow is a separate business inside the same shop — it needs its own landing, its own portfolio, its own enquiry workflow and its own schema treatment.
What we ship for a florist
A bespoke florist website with the same-day-delivery checkout above the fold on mobile, a wedding enquiry landing page with portfolio gallery, individual product pages for each bouquet with Product + Offer schema, a cached Instagram feed for the visual layer, a subscription option for weekly or fortnightly bouquets, a funeral and sympathy flow with its own copy and product set, the standard contact and location block with delivery-area map embed, and the full Florist + LocalBusiness + Product schema graph. Build window is the standard same-day SLA.
The gift-bouquet checkout
Stripe direct for the checkout (1.5% + 20p on UK cards, no monthly platform fee), structured postcode-area delivery checking at the basket level, server-side cut-off enforcement for same-day delivery, structured delivery slots for next-day and scheduled orders, gift-message field that prints on the despatch label, optional add-on products (chocolates, candles, vase upgrade). Order confirmation email is plain HTML for deliverability and contains the despatch slot, the recipient address, and the gift message exactly as the customer wrote it.
The wedding enquiry flow
Wedding work behaves more like architectural commission work than retail florist work — the decision is considered, the brief is detailed, and the conversion happens by conversation rather than by checkout. The landing page leads with the wedding portfolio (typically 12-20 named weddings with venue, season, style category) and the enquiry form collects only what the florist needs for a first response (date, venue if known, indicative budget band, style references, contact). The form routes to a wedding-specific inbox or a dedicated label in the main inbox so the workflow stays separate from the retail order flow.
What we deliberately do not build
No bespoke flower-arrangement design tool — the technology does not exist at the fidelity that would help a sale, and the page-weight cost is severe. No live-chat widget — flower shops are too small to staff one, and the conversion-rate evidence does not support automated chat on this kind of site. No "augmented reality bouquet preview" gimmick — it does not convert. No loyalty programme module — Square Loyalty or the POS provider’s loyalty integration handles it cleaner than anything we would build in-house.
Pricing for a florist website
Most independent florists land on Launch (£499) — a single-shop florist site with the checkout, the wedding enquiry flow, the subscription option and the funeral flow. Multi-shop florist groups or florists with a separate event-design business arm move to Growth (£899) for the multi-location architecture. Pro (£1,499) is for premium florists or design-led brands that need a deeper editorial layer (a journal section, a behind-the-scenes content stream, named designer profiles) and a richer visual presentation than the standard Launch architecture supports.