Gulf Florist CRM Dilemma: Building an Order System That Never Forgets a Customer with AI

On the evening of March 20 at a Dubai flower shop, Mother's Day orders poured in from WhatsApp voice notes, Instagram DMs, and the phone book. A regular customer had ordered peonies for her mother three years running, but this year received no reminder—because she was buried in chat history. This isn't an isolated case; it's the CRM (customer relationship management) dilemma facing florists across the Gulf region: the problem isn't storing contacts, but remembering occasions, recipients, and promises across channels.

Orders Scattered Across Chat Logs

Most Gulf florists don't have an order system—just a phone loaded with WhatsApp Business, Instagram, and call history. According to the original article's observation, WhatsApp is the main channel, because customers are used to sending photos, asking about prices, revising card messages, and finally confirming with a thumbs-up.

On ordinary days the owner can scroll back through chat history. But during the last week of Ramadan, Eid al-Fitr, Valentine's Day, or Mother's Day on March 21, searching becomes a bottleneck. Orders live in chats, payment status lives in someone's head, and addresses are location pins only one person has opened.

A spreadsheet gives you a list for the day, but it doesn't know that the same customer also ordered last March, doesn't know that "Mama" and "Umm Khalid" are the same recipient, and doesn't know that the 10 a.m. delivery slot is already full.

An Order Is Not a Customer: The Core Difference in Florist CRM

The biggest blind spot of generic CRMs in the florist context is: the person who pays is usually not the person who receives the flowers. A son in Riyadh orders for his mother in Jeddah; a company in Abu Dhabi sends forty flower baskets to clients; a husband orders flowers every year on his wedding anniversary. If the system only stores "customer, phone, last order," it loses the most valuable part: who the flowers are for, and why.

According to the original article's analysis, a florist CRM needs to split what a sales CRM merges into one into three elements of a single transaction:

• Buyer: name, phone (usually WhatsApp), preferred language, and whether it's an individual or a company account.
• Recipient: name, phone, address or location pin, area, delivery notes (e.g., "call this number when you arrive at the door," "deliver after Asr"). One buyer can have multiple recipients.
• Occasion: birthday, anniversary, Mother's Day, Eid al-Fitr, new baby, bereavement, corporate event. Some occasions repeat on the same Gregorian date each year; Ramadan and Eid al-Fitr follow the Hijri calendar and move about 11 days earlier each year, so reminders must move with them.

Once the three are separated, the useful questions become simple: whose anniversary order from last year is due in ten days? Which corporate clients sent Eid gifts last time?

Hijri calendar (Islamic calendar) is a lunar calendar based on moon phases, with about 354 days per year—roughly 11 days fewer than the Gregorian calendar. As a result, religious holidays like Ramadan, Eid al-Fitr, and Eid al-Adha fall about 11 days earlier each year on the Gregorian calendar. This directly affects a florist CRM's reminder logic: if the system sets reminders on fixed Gregorian dates, holiday reminders will drift year by year and eventually fail. The right approach is to have the system store the Hijri dates of holidays, or allow the shop owner to manually set the Gregorian start and end dates of each holiday every year, and automatically link reminders to these dynamic dates. This is also why prompt 3 in the original article asks to "let me set the start date for each holiday this year"—the AI-built system needs manual input of the Gregorian dates corresponding to that year's holidays in order to generate an accurate reminder list.

Six Things a Gulf Florist CRM Must Track

Beyond buyer, recipient, and occasion, Gulf florists also need features most off-the-shelf tools lack:

• Capped delivery slots. Same-day delivery means slots, and each slot can only take a fixed number of orders per area or per driver. The system should warn before promising over capacity.
• Payment status, including cash on delivery. Card links, bank transfer, in-store payment, or cash on delivery. Drivers need to see how much to collect, and the owner needs to see which cash has come back.
• VAT per order. 5% in the UAE, 15% in Saudi Arabia, shown separately on the receipt.
• Card messages, printed exactly as written. Commonly Arabic, sometimes English, occasionally bilingual. Must print as the customer wrote it, right-to-left when needed.
• Arrangement and photo. What was ordered, at what price, and a photo of the finished arrangement taken before the bouquet leaves. That photo settles any argument about rose color.
• Team role separation. The owner sees all data, the florist sees the production queue and cards but not revenue, and the driver only sees their own deliveries for today.

VAT is a consumption tax introduced in recent years by Gulf Cooperation Council (GCC) countries. The UAE has levied 5% VAT on most goods and services since 2018, while Saudi Arabia raised its rate from 5% to 15% in July 2020. For florists, every order must show the VAT amount separately on the receipt rather than presenting a lump sum inclusive of tax. This requires the CRM system to add a "tax amount" field to its data model and automatically calculate and display it when generating receipts. In addition, Saudi tax invoices are subject to ZATCA (Zakat, Tax and Customs Authority) e-invoicing rules, requiring specific elements such as QR codes and invoice numbers; the UAE is also advancing its own e-invoicing system. Therefore, the VAT data recorded by a florist CRM is mainly used for internal accounting and driver collection reference—official tax invoices still need to be issued from compliant POS or accounting software, a point also emphasized in the "Boundaries and Limitations" section of the original article.

Building with AI: From Prompts to a Working System

The original author works at Mythex (an AI app builder), so the following approach should be weighed accordingly. Users describe the app in English or Arabic, it writes the code, previews it running live, attaches a Postgres database and file storage, and publishes it to a public address or a custom domain. These prompts also serve as specifications for a developer.

Prompt 1: Data Model

Build an order and customer system for a Dubai flower shop. Buyers have a name, WhatsApp number, preferred language (Arabic or English), and type (individual or company). Each buyer can have multiple recipients, with name, phone, address, area, map link, and delivery notes. Orders link a buyer to a recipient and include: occasion (birthday, anniversary, Mother's Day, Eid al-Fitr, Ramadan, Valentine's Day, new baby, bereavement, wedding, corporate, other), arrangement, price, 5% VAT listed separately, card message, delivery date, delivery slot (9–12, 12–3, 3–6, 6–9), payment method (card link, bank transfer, in-store, cash on delivery), payment status, and order status (new, confirmed, in progress, ready, out for delivery, delivered, issue). Staff upload a photo of the finished arrangement to each order.

Prompt 2: Slots That Can't Be Overbooked

Each delivery slot takes a maximum of 6 orders per day per area. When staff select a full slot for that area, show a warning and suggest the next available slot. Add a "Today" board grouped by slot, then by area, showing each driver's assigned orders.

Prompt 3: Recurring Occasion List

Add an "Upcoming" page. For all birthday or anniversary orders in the past two years, show the buyer when the same date falls 7 to 14 days away this year. For Mother's Day, list everyone who ordered on March 21 last year starting March 1. For Ramadan and Eid al-Fitr, list last year's buyers and let me set the start date for each holiday this year. Each row has a WhatsApp button that opens a chat with the buyer, pre-filled with a message in their preferred language.

That button is a plain click-to-chat link: it opens the chat with the text filled in, and a human presses send. It is not an automated message (see limitations below).

Prompt 4: Arabic, Written in Arabic

Mythex builds entirely in Arabic, so you can describe this part in the customer's language: add a fully Arabic right-to-left interface with a button to switch to English. Print gift cards exactly in the customer's written language, show prices in dirhams with VAT listed separately on the receipt. If in Riyadh or Jeddah, replace dirhams in the first prompt with riyals and 5% with 15%.

Prompt 5: Driver View

Add a driver page that shows only the logged-in driver's orders for today, sorted by slot, including recipient phone, map link, delivery notes, and the cash amount to collect on delivery. Drivers can mark as delivered and upload a photo at the door, or flag an issue with a reason.

After the first build, most work is single-sentence fixes: "corporate orders need a PO number," "don't send bereavement reminders the following year," "no evening slots on Fridays." Each change is visible in the live preview first.

According to the original article, what the florist ends up with is: a Postgres database holding buyers, recipients, occasions, and orders; file storage for arrangement and delivery photos; staff login, with customer phones and addresses kept private; a full Arabic interface alongside English; a custom domain available from the Pro plan up; and code that can be exported or handed to a developer.

Postgres (PostgreSQL) is an open-source relational database management system widely used in web applications for its stability, data integrity, and support for complex queries. In AI app builders like Mythex, Postgres typically serves as the backend data store, automatically generating table structures for the app (such as buyers, recipients, and orders tables) and handling data relationships. File storage is used to save unstructured data, such as photos of finished arrangements, driver delivery confirmation photos, and card design drafts. For a florist, this means all order, customer, and delivery information is stored in a cloud database, accessed by staff via browser or phone, and doesn't depend on a single phone or chat log. The original article's mention of "attaching a Postgres database and file storage" illustrates that the AI builder configures the database and storage as infrastructure automatically, with no need for users to manually set up servers.

Boundaries and Limitations: What It Can't Do

The original article candidly lists the limitations, which are crucial for evaluating the approach:

• No WhatsApp Business API out of the box. Click-to-chat works without setup. Automated confirmations or reminders require connecting to the WhatsApp Business Platform through Meta or an approved provider, using your own account, approved templates, and per-message billing. You can ask Mythex to add the integration, but the account belongs to the florist.
• Payments require your own provider. Card links come from a provider the florist signs up with (Stripe, Tap, Checkout.com, PayTabs, or another provider serving the region). The app records amounts paid; it doesn't move funds.
• Tax invoices have rules. If VAT-registered in Saudi Arabia, tax invoices are subject to ZATCA e-invoicing requirements, and the UAE is gradually rolling out its own e-invoicing system. Keep issuing official invoices from compliant POS or accounting software.
• Importing history is manual. Old chats don't import themselves. Start from this season.
• Maintenance is on you. Someone at the shop makes each change. It's a sentence, not a project, but it's on you.

WhatsApp Business API is fundamentally different from the regular WhatsApp Business app. The regular app (the WhatsApp Business installed on your phone) only supports manual chats and simple auto-replies, and cannot send template messages in bulk. WhatsApp Business API is Meta's programming interface open to businesses, allowing systems to automatically send order confirmations, delivery reminders, and other messages—but the business needs a verified WhatsApp Business account, must use Meta-approved template messages, and pays per message. The "click-to-chat link" mentioned in the original article is a lightweight solution that requires no API: it opens a chat window via a wa.me link with text pre-filled, but a human still has to press send. This means an AI-built system can achieve semi-automated reminder preparation, but true automated sending must connect to the API, with the account and costs borne by the florist.

Team Setup: Owner, Florist, Driver

A flower shop has three types of users who shouldn't see the same things. The owner sees everything: revenue by occasion, cash per driver, the recurring occasion list. The florist sees the production queue, card messages, and photo uploads, but not revenue. The driver only sees their own deliveries for today. These roles live inside the app and should be requested early and tested with separate accounts before peak season.

Who builds the app is another matter. Mythex's Business plan offers a shared team workspace with unlimited members and Admin, Editor, and Viewer roles. Apps can be set to members-only visibility, with staff logging in through a verified company domain. Publish approvals and audit logs are available on the Enterprise plan.

According to the links in the original article, the Free plan can build a first version, Pro is $25/month, Business starts at $50/month, and Enterprise starts at $680/month.

Start Before the Next Peak

Set it up in the off-season, not the week before Mother's Day. Build the order screen first, run it alongside WhatsApp for two weeks, and add the recurring occasion list once there's data. By next March 21, last year's buyers will be a list on the screen, not a vague memory.

The original article's closing also applies to any business facing similar problems: if your shop has a rule that doesn't fit these prompts, describe it, and we can help you figure out how to phrase it.

One-line Summary

Gulf florist CRMs need to separate buyer, recipient, and occasion—and use AI to build a cross-channel order system.

Paragraph Summary

The article notes that Gulf florists generally lack order systems, with orders scattered across WhatsApp, Instagram, and phone calls, and searching chat logs becoming a bottleneck at peak times. The core problem isn't storing contacts but remembering occasions, recipients, and promises across channels. A florist CRM must split buyer, recipient, and occasion into three separate entities and track capped delivery slots, payment status, VAT, card messages, finished-arrangement photos, and team role separation. The author provides five sets of prompts based on the Mythex platform, which can generate a working system including a data model, slot overbooking prevention, recurring occasion reminders, and a driver view. The approach has clear boundaries: no built-in WhatsApp Business API, payments require your own provider, tax invoices require compliant POS, and historical data must be imported manually. The recommendation is to build in the off-season and run it alongside WhatsApp.