Florist operations software,
and the dispatch takes care of itself

Bluma is florist operations software. When a customer or a corporate client orders through Bluma, a purchase order is drawn up for the partner shop covering that delivery area, at the price you agreed with them. Right before it goes, you see the ribbon wording, the order value and the wholesale cost in KakaoTalk, and it is sent only when you approve it. The software does the preparing; you make the call.

Built on Bluma · flowerteam.kr You approve before anything is sent Live 87 member shops Beta KakaoTalk AI ordering bot
Enquire or partner See the order flow

Example screen. Fields are adjusted to each business.

Why

How many phone calls does one order take?

One order goes through several calls and scribbled notes before it is delivered. When something goes wrong, it is nearly always the ribbon 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

What happens to one order

Of the seven steps, you only touch one: step 5, approval. Everything else is prepared for you.

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

You get the ribbon wording, the order value and the wholesale cost in one KakaoTalk message (or SMS). 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 goes out until you approve it

This is the part that matters most. It does not decide for you; it leaves you only the decision and prepares everything else.

[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, which is 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

Six things it does

Features added one at a time on top of Bluma, the florist operations software. A later phase never goes in without the one before it. Tap a card for the details.

platform live MODULE 01

Order intake (Bluma)

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

Details →
phase 1 · live 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 · live MODULE 03

KakaoTalk · SMS
approval gate

You get a final check right before it is sent. The most important part.

Details →
phase 1 · live MODULE 04

Settlement and margin

What each order actually earned accumulates automatically.

Details →
phase 2 · beta MODULE 05

KakaoTalk AI
consultation and ordering

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

Details →
proven MODULE 06

Shared engine

The same engine as StayOn, our lodging software.

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

Development Phases

Built one step at a time

Not everything at once. Dispatch and approval were made reliable first; AI consultation now runs on top of them in beta.

PHASE 1 · complete

Automatic dispatch + approval

The stretch where one order flows through approval to a shop dispatch automatically. In use at 87 member shops.

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

KakaoTalk AI ordering

Round-the-clock consultation that turns directly into orders. Development is finished and it is running in beta.

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

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

An engine already proven in StayOn

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

StayOn (lodging software): used every day 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 StayOn →

FAQ

What people usually ask

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?

It runs on Bluma, our florist operations software. 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.

Can we start using it now?

Yes. Automatic dispatch, KakaoTalk approval and settlement (phase 1) are in use at 87 member shops. The KakaoTalk AI consultation and ordering bot (phase 2) is finished and running in beta, and we apply it together with shops that want it.

Start with your items and delivery areas

Tell us how orders reach you, how many partner shops you work with, and how far you deliver, and we will work 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