Flower shop order tracking comes down to one job: answering "where is my order?" before the customer picks up the phone. On Mother's Day and Easter week, those calls bury the people who should be designing arrangements. The fix is small. Give every order four statuses, assign each to one person or event, and send a text and a link when the status changes. This is the phone-pileup cause we name in our guide to florist order management software. Below: who updates each status, how the driver's phone fits, and what a plain version costs you in effort.
The four statuses a customer actually needs
Most florists track more than four things internally: wire orders, substitutions, card messages, cooler space. The customer does not need that. They need to know whether you have the order, whether it is being made, whether it left the shop, and whether it arrived.
Four statuses cover that. Each one needs exactly one owner, because a status nobody owns is a status that is wrong at 2 p.m. on a Saturday.
| Status | Who updates it | What triggers the change | What the customer gets |
|---|---|---|---|
| Received | The system, automatically | Payment or order saved with a date and slot | Text and email with the status link |
| In design | The designer or the shop lead | One tap when the arrangement is started | Status page changes; text is optional |
| Out for delivery | The driver | One tap when the van leaves with the order | Text with the delivery window |
| Delivered | The driver | One tap at the door, with a photo if you want one | Text confirming delivery |
Notice what is missing: nobody types a status message. A person taps a button, and the system writes and sends the text. That is what keeps it alive during a rush.
Received: the one status nobody should touch
"Received" should fire the moment an order is saved. If a staff member has to remember to send it, it will be skipped on the busiest day, and that is exactly when customers worry most.
The confirmation should repeat the facts the buyer will want to check: delivery date, the slot or window, the recipient's first name, the card message, and your shop phone number. It should also carry the link to the status page.
Orders arrive from several places: your website, the phone, walk-ins and possibly wire services. Phone and walk-in orders are where the status chain breaks, because someone has to enter the order and the buyer's mobile number. Make the mobile number a required field on the order form. Check whether your wire-service orders carry a buyer number at all; if they do not, those orders sit outside this system, and you should say so on your own process sheet.
The slot on the confirmation matters too. If you cap how many deliveries fit in a window, the promise in that text is only as good as the cap. We walk through setting those caps in a one-evening Valentine's Day dry run.
In design: the status the shop forgets
This is the hardest status to keep honest, because designers have flowers in both hands. If it needs a laptop, it will not happen.
There are two workable ways to trigger it:
- A tap on the production ticket. The designer or lead taps "started" on a tablet or phone mounted at the design bench.
- A batch move. The shop lead moves all of the morning's orders to "in design" at the start of the production run, then corrects exceptions.
The batch move is less accurate but far more likely to get done. For a small shop, accuracy on this one status matters least. A customer who sees "in design" a little early is not upset. A customer who sees "received" at 3 p.m. for an order due at noon will call.
You can also make "in design" a silent status. It updates the page but sends no text. Customers get texts on the two moments they act on: the van left, and the flowers arrived. That keeps message volume down and keeps the shop out of the "too many texts" complaint.
The production ticket itself, with the recipe, the card and the cooler location, is a bigger topic. It sits inside the florist CRM we scope, which connects inquiries, production and delivery in one place.
Out for delivery: where the driver's phone does the work
This status is the one that ends the most calls, and it depends entirely on the driver. If drivers have to call the shop to say they left, you have traded one phone call for another.
What the driver sees
The driver needs a list of stops in route order, each showing the address, delivery instructions, recipient name and any card or gate notes. Each stop has two buttons: "Start" and "Delivered." Tapping "Start" on a stop, or "Start route" for the whole run, flips those orders to "out for delivery" and fires the text.
A phone-friendly web page can do this without an app store download, which matters when you hire seasonal drivers for one week. A native app makes sense if you need background location, offline use or push notifications. That is a scoping decision, and it is what our mobile app work covers when a web page is not enough.
What the customer sees
The text says the order is on its way, gives a delivery window rather than a promised minute, and links to the status page. We would avoid live map tracking for flowers. Arrangements are delivered in clusters, stops reorder, and a dot on a map invites more calls when it sits still near a traffic light.
The window is where your zone planning pays off. If you have built delivery zones and a driver count, the window is the slot the customer already chose. Our Mother's Day post on working backward from driver count to slot caps and zones covers that arithmetic.
Delivered: proof, exceptions and the fifth state
"Delivered" is the status competitors usually stop at, with a photo of the arrangement on a porch. A photo is useful, but it is one input, not the whole system.
When the driver taps "Delivered," capture three things: the time, who received it (recipient, neighbor, front desk, left at door), and an optional photo. The buyer gets a text with the time and the receiver. That answers the second most common call, "did she get them?"
Photos of a recipient's doorway or home can include people and private details. Decide your own policy on what drivers photograph, and check it with your own advisor if you are unsure.
Now the fifth state, which the customer never sees as a status: needs attention. The recipient is not home. The address is wrong. The building has a locked lobby. The driver taps "Problem" instead of "Delivered," picks a reason, and the order lands in a queue on the shop's screen, where a person decides: call the buyer, retry, reroute. The customer text for these cases should be written by a human or from a short set of reviewed templates, never auto-sent with a guess.
This is the same design principle behind any exception queue: automate the normal path, route the abnormal path to a person with the facts attached. We apply it in the omnichannel support hub inside WRAPT, the wholesale operations platform, which has a client portal and a 9-stage lead-to-delivery pipeline. WRAPT is a wholesale build, not a florist one, and we mention it for the pattern, not the industry.
The status page: what goes on it, what stays off
The status page is a single web page the text links to. No login, no account, no password to forget. Each order gets its own link with a long random token in the address, so one customer cannot guess another's.
Put on it:
- The order number and the four-step progress bar with the current step highlighted
- The delivery date and window
- The recipient's first name and the arrangement name
- Timestamps for each completed step
- A tap-to-call button for the shop and a short note on what to do if the order is late
Leave off the full delivery address, the card message and payment details. The link will be forwarded, screenshotted and opened on shared phones. Show the neighborhood or town at most.
The page also gives you a place to answer the questions behind the calls. A line such as "Deliveries run between 9 a.m. and 5 p.m. in your selected window" removes a whole category of calls without any staff time.
For a small shop, this is usually a page on your existing website plus a database table of orders and statuses. It is not a large build. If your site runs on a platform that already has order tracking, check what it supports before building anything. Many store platforms are built around shipped parcels, not same-day local delivery with slots and drivers. Check whether yours handles "in design" and driver taps.
Text updates: keep them short and keep them informational
Use an SMS provider with an API, such as Twilio, to send the messages from one business number. The system sends a text on "received," "out for delivery" and "delivered." A text on "in design" is optional.
Keep the texts informational. A status update that also pitches a Mother's Day upsell stops being a plain status update. The Federal Trade Commission explains this for email. When a message mixes promotion with order information, the subject line and where the order information sits decide how the message is treated. The rule text sits in eCFR, 16 CFR Part 316. That guidance covers email, not text messages, and the rules for texting differ. Ask your own attorney how consent and opt-out apply to your texts. We do not give legal advice.
A practical approach, separate from the legal question: keep promotional messages on a separate list, with their own opt-in, and send status texts only about the order in hand. Include your shop name at the start of every text and a way to reach a human.
The recipient is a special case. The buyer gave you the recipient's name and address, not necessarily permission to text the recipient. Default to texting the buyer, and make texting the recipient an explicit choice at checkout.
Measuring whether it worked
We have no florist benchmark to quote you, and we will not invent one. Measure your own shop instead. For the two weeks before your next busy period, keep a tally sheet at the phone: each call gets a tick under "where is my order," "did it arrive," "change my order," or "other." After you launch the status page, repeat the tally for the same kind of week.
Two comparisons matter: calls per hundred orders, and how many calls happen in the two hours before your slots close. If "where is my order" drops but "did it arrive" does not, your delivered text or driver tap is the weak link.
The calls that remain should be changes and problems, which need a human anyway. If you run a support inbox as well as a phone, our post on customer service automation for small business covers what to fix first.
Build it, buy it, or bolt it on
You have three honest options. First, a florist point-of-sale or delivery product that already includes tracking. Second, a general delivery-tracking tool connected to your order source. Third, a custom build. We build the third kind: a status page, driver page and texting connected to a custom CRM, owned by you under the project agreement.
Custom makes sense when your orders come from several places, your slots and zones are specific, or you would rather not pay a subscription per user or per message on top of your volume. It makes less sense for a shop with a few dozen deliveries a week and an off-the-shelf tool that already does the four statuses. Hosting, the SMS provider and any third-party subscriptions are separate costs, and ongoing support is scoped in the proposal. Before you decide, count your order sources and drivers. That count tells you which option fits.
If you are planning for the Easter window, the date is fixed and the order-intake cutoffs come first. See Easter 2027 pre-order cutoffs and what to close first before you plan the tracking build.
Frequently Asked Questions
What is the simplest flower shop order tracking setup?
Four statuses (received, in design, out for delivery, delivered), a text to the buyer on the moments that matter, and one link to a status page with no login. The system sends "received" automatically. The shop lead taps "in design," and the driver taps the last two from a phone.
Should a florist text the buyer or the recipient?
Text the buyer by default, since they placed the order and gave you their number. Texting the recipient is a separate choice that should be made at checkout. Whether you need written consent for either is a question for your own attorney, because the rules for texts differ from email.
Do I need live map tracking for flower deliveries?
Usually not. Drivers batch stops, routes change, and a map dot that sits still can prompt more calls. A delivery window plus an "out for delivery" text and a "delivered" confirmation answers most questions. Consider live location only if your customers ask for it and your drivers have reliable phone data.
Can the status page work for phone and walk-in orders?
Yes, if staff enter those orders into the same system and capture a buyer mobile number. The common failure is a missing number or an order kept on paper. Make the mobile field required on the order form so every order can receive a status text and a link.
Next step
If you want to see what a four-status page and driver tap would look like for your shop, start with the order sources and drivers you have now. Our team in Medford builds custom software for businesses across Burlington County, South Jersey and the Philadelphia area, and for clients nationwide. Tell us how orders move through your shop and we will scope the page, the driver view and the texts around that. Start with the custom florist CRM we scope for flower shops, then get in touch.
Sources
Every outside claim in this article links to where it came from. These open in a new tab.
- Federal Trade Commissionftc.gov
- eCFR, 16 CFR Part 316ecfr.gov