Flower Order Dispatch Automation

Florist Operations,
Automated Dispatch

When an individual or a corporate client places an order on Bluma, a purchase order is generated automatically for the contracted shop covering that delivery area, at the agreed wholesale price. Before it goes out, the ribbon wording, the order value and the wholesale cost are sent to the manager on KakaoTalk, and the order is released only once it is approved. Automation does the preparation; the decision stays with a person.

Built on Bluma · flowerteam.kr Approval-gated dispatch after review In development phase 1 Planned AI chatbot · overseas delivery
Enquire or partner See the order flow

Why

What people do by hand today

A single order takes several calls and handwritten notes before it is delivered. When something goes wrong, it goes wrong in the ribbon wording or the price.

Finding a shop in the area

Depending on the delivery address, someone calls a shop in that region, confirms availability and timing, then negotiates the price again.

Ribbon wording errors

For funeral and celebration wreaths the ribbon is the whole point. Taking it down by phone and relaying it introduces mistakes in titles and company names.

Prices and margin on paper

The amount received and the amount owed to the shop are worked out order by order. Once volume builds, nobody can say what was actually earned.

Orders scattered across channels

Phone, KakaoTalk, Instagram DM and platforms all bring orders in separately, so the first task is always collecting them in one place.

Order Pipeline

How one order flows

Of seven steps, a person intervenes at exactly one — step 5, approval. Everything else is prepared automatically.

01
Order intake Bluma

Individual customers and corporate accounts order through Bluma. Item, ribbon wording, delivery address, delivery date and time, and special requests arrive as a single record. Orders taken by phone or KakaoTalk are registered in the same format.

02
Delivery area resolved automatic

The delivery address determines the covering area. Zones are defined at city and district level, so the same zone is always assigned on the same basis.

03
Partner shop and contract price matched automatic

The designated shop for that area is retrieved along with the wholesale price agreed with them for that item. Each zone holds a primary and a backup shop, so an unavailable primary falls through to the next.

04
Purchase order generated automatic

The order to be sent to the shop is completed: item and size, ribbon wording (left and right), delivery address and arrival time, and the wholesale price. It is not sent yet.

05
Approval requested a person decides

Three things are sent to the manager on KakaoTalk (or by SMS) in one message — the ribbon wording, the order value and the wholesale cost. Approve and it moves on; hold and it waits; amend and the details are corrected and sent for review again.

06
Dispatch automatic after approval

The approved purchase order is sent to the designated shop. The dispatch time, the approver and the amounts at the moment of approval are recorded together, leaving an audit trail.

07
Delivery confirmation · settlement automatic

Marking a delivery complete turns the order value and wholesale cost directly into settlement data. Amounts payable per shop and margin per order accumulate on their own.

Approval Gate

Nothing is dispatched without approval

This is the heart of the system. Automation does not replace the person — it leaves only the decision and prepares everything around it.

[Bluma · dispatch approval request]

Order 20260904-017

Item 3-tier congratulatory wreath

Ribbon (left) Congratulations on your opening

Ribbon (right) Balancetech · CEO Park

Delivery Fri 09/05, arrive 10:00

Address Giheung-gu, Yongin-si …

Order value KRW 150,000

Wholesale cost KRW 95,000

Assigned shop Giheung ○○ Flowers (area primary)

Reply with approve / hold / amend

※ Example of the actual message. The fields and wording are adjusted to how each business operates.

  • Three things on one screen. Ribbon wording is where mistakes happen most, and the order value only makes sense next to the wholesale cost. Both are in the same message so nothing has to be looked up separately.
  • Approve — the purchase order is sent to the designated shop. Approver, timestamp and amounts are recorded with it.
  • Hold — nothing is dispatched and the order waits. Used when the customer needs to confirm something.
  • Amend — change the ribbon wording, the price or the assigned shop and receive a fresh approval request. If the area's primary shop cannot take it, it is swapped for the backup and re-sent.
  • There is a record. Who approved what, when, and at which amount accumulates in the approval log — the evidence you need in a pricing dispute or a delivery incident.
  • Automatic dispatch is optional. For trusted accounts and standard items you can allow dispatch without approval based on a value threshold.

System Modules

Seven modules

Automation modules layered on top of Bluma. They are added in phases; a later phase is never deployed without the one before it. Tap a card for the full detail.

platform live MODULE 01

Order intake (Bluma)

The single entrance that collects individual and corporate orders in one format.

Details →
phase 1 · in development MODULE 02

Area, shop and price
auto-matching

Given only an address, where and at what price to dispatch is already decided.

Details →
phase 1 · in development MODULE 03

KakaoTalk · SMS
approval gate

A final check before dispatch. This is the heart of the system.

Details →
phase 1 · in development MODULE 04

Settlement and margin

What each order actually earned accumulates automatically.

Details →
phase 2 · planned MODULE 05

KakaoTalk AI
consultation and ordering

Round-the-clock consultation and order intake through a chatbot.

Details →
phase 3 · planned MODULE 06

Overseas delivery

The domestic dispatch structure extended to country level.

Details →
proven MODULE 07

Shared engine

The same foundation as the hospitality system.

Details →
All modules and reference tables The tables behind every automatic decision are on the same page.

Development Phases

Development phases

Not everything at once. Consultation and overseas delivery come after dispatch and approval are running reliably.

PHASE 1 · active

Automatic dispatch + approval

Complete the stretch where one order flows through approval to a shop dispatch automatically.

  • Area, shop and price tables
  • Purchase order generation
  • KakaoTalk / SMS approval gate
  • Approval log and settlement
PHASE 2

KakaoTalk AI ordering

Add round-the-clock consultation and let consultation turn directly into orders.

  • Google Sheets knowledge base
  • Floristry-specific answering
  • Chat order → dispatch link
  • Unanswered learning loop
PHASE 3

Overseas delivery

Extend the domestic zone-matching structure to countries and cities.

  • Partners and prices per country
  • Availability and lead time
  • Currency and exchange basis
  • English ordering and consultation
PHASE 4

Scaling accounts

Hold up as corporate accounts and partner shops multiply.

  • Per-account pricing and credit
  • Automated shop settlement
  • Conditional auto-approval rules
  • Regular operating reports

Same Engine

Same engine, different industry

Consultation, knowledge base, intake, alerts and analytics share the same foundation regardless of industry. The florist chatbot applies an engine already in production.

Airbnb Hospitality Automation System — live at Seorak Farm Private Stay. Calendar sync, a KakaoTalk AI concierge, a Google Sheets knowledge base, the unanswered learning loop and channel analytics are all running today.

See the hospitality system →

FAQ

Frequently asked

If I miss an approval, does the order stall?

Yes — nothing is dispatched before approval, which is why the request is repeated as delivery time approaches. If approving every order is a burden, you can open a rule so that value thresholds, regular accounts or standard items dispatch without approval.

What if the area's shop cannot take the order?

Each zone has a primary and a backup shop. If the primary is unavailable, the purchase order is rebuilt with the backup shop and their contract price, and sent for approval again. If the price differs, the changed amount is visible on the approval screen.

Can wholesale prices differ per shop?

Prices are managed in a table by shop, item and size. Enter the outcome of a price negotiation and it applies automatically from the next order. Nothing beyond editing the table is required.

Who is responsible if the ribbon wording is wrong?

Ribbon wording is captured as left and right at intake and shown again on the approval screen immediately before dispatch. Because the wording and the approver at the moment of approval are in the log, it is possible to see where it went wrong.

Can a florist who does not use Bluma adopt this?

The system is being built on Bluma. Without it, the order intake channel has to be built as well, which changes the scope and the schedule. Tell us your current setup and we will map out how it would apply.

When will overseas delivery be available?

It is a phase 3 item. Country partners, prices and lead times are added once domestic dispatch and approval are stable. It extends the domestic structure rather than being designed from scratch.

Start with your items and delivery areas

Tell us how orders reach you, how many partner shops you work with, and how wide your delivery area is — we will map out the scope and schedule.
We also welcome partner shops and corporate accounts.

blctech@naver.com

3F, 169 Seokseong-ro 521beon-gil, Giheung-gu, Yongin-si, Gyeonggi-do, South Korea

0505-055-1234

0504-038-0034

Get in touch Visit Bluma Other systems