Florist Operations,
Automated Dispatch

• Individual and corporate orders — retail orders and account orders are handled separately, with per-account pricing and payment terms applied to corporate clients.
• Required fields standardised — item and size, ribbon wording (left and right), delivery address, arrival date and time, and special requests are always captured.
• External orders consolidated — orders arriving by phone, KakaoTalk or Instagram DM are registered in the same format so everything downstream is one flow.
• Order ledger — intake time, customer, item and delivery details accumulate automatically.

• Zone definitions — delivery zones are defined at city and district level with a designated shop for each.
• Primary and backup shops — each zone is ranked, so an unavailable primary is swapped automatically and sent for approval again.
• Price table per item — wholesale prices agreed with each shop, by item and size, are kept in a table. When a price changes, only the table changes.
• Purchase order generated — the order is completed with ribbon wording and delivery details, and held back until approval.

For the managerCalling around for a local shop and re-negotiating the price disappears.

• Approval message — ribbon wording, order value, wholesale cost and assigned shop are sent to the manager in one message. KakaoTalk by default, SMS if preferred.
• Approve · hold · amend — the manager's reply decides whether the order is dispatched, held, or revised for another review.
• Approval log — approver, timestamp and the amounts at the moment of approval are recorded as evidence.
• Pending reminders — if delivery time is approaching and no approval has arrived, the request is repeated.
• Conditional auto-approval — value thresholds, regular accounts or standard items can be configured to dispatch without approval.

For the managerYou control dispatch from your phone without being in the office.

• Margin per order — the difference between order value and wholesale cost is calculated per order.
• Payables per shop — amounts owed to each shop are grouped by period, making settlement straightforward.
• Revenue per account — corporate revenue and outstanding balances are tracked separately.
• Bluma bookkeeping — linked to the existing ledger so accounting work is reduced.

• 24/7 consultation — wreath types, price ranges, deliverable areas and times, and how to word a ribbon are answered automatically.
• Google Sheets knowledge base — answers are managed in a spreadsheet, so the owner edits them directly and changes take effect immediately. Facts absent from the sheet are not invented.
• Order straight from chat — item, ribbon wording, address and time are collected in conversation and registered as an order, entering the same dispatch-and-approval flow.
• Unanswered learning loop — questions the bot could not answer are collected and reported, and once answered they are handled from then on.
• Proven engine reused — the consultation engine running in the hospitality system is applied with floristry knowledge in place of lodging.

For the managerNothing arriving overnight is missed, and consultation turns into orders.

• Partner matching by country — exactly like domestic zone matching, a local partner is designated per country and city.
• Availability and lead time — deliverable items and required days per country are stated at the ordering stage.
• Currency and pricing — wholesale prices in local currency are managed separately from the exchange-rate basis.
• Multilingual ordering — English ordering pages and English chatbot responses for overseas customers.

• Channel analytics — traffic from the shop, the chatbot, Instagram and the blog is counted per channel and compared month to month.
• Admin chat commands — type a command in KakaoTalk to check statistics, unanswered questions or orders awaiting approval.
• Messaging account upkeep — Kakao alert tokens refresh automatically with an advance expiry warning.
• Cloud infrastructure — Google Cloud Run zero-downtime deployment, your own domain, HTTPS, and masked personal data in logs.