How flower delivery works

Search by the recipient’s city and date. The marketplace matches that request to approved sellers with eligible inventory, preparation time and fulfilment.

1 · Find

Start with place and date

Availability depends on where the flowers are going and when they are needed—not only on a national catalogue.

2 · Choose

See the local maker

Each product identifies the seller responsible for making the order. The first release keeps one seller per checkout.

3 · Confirm

Make fulfilment explicit

Pickup or delivery is confirmed against seller settings, the requested address and a current provider quote where applicable.

Ordering modes

Buy now, request a bouquet, or ask Flor

A seller may offer ready inventory, an approval-based bouquet request, or a guided custom request. The page makes the applicable mode clear before checkout.

Promises are verified

No blanket same-day claim
No invented inventory or delivery window
No hidden substitution outside the selected policy
No cross-seller cart in the first release

What happens if flowers change with the season?

Local flower supply is naturally variable. Sellers publish an explicit substitution policy, and the customer accepts the applicable choice before purchase. Flor can explain a policy but cannot authorize a seller to exceed it.

When is payment captured?

The final authorization and capture design will be published after the marketplace’s Stripe Connect configuration, request expiry rules and refund operations are verified in test mode.

Need a human decision?

Flor can guide search and gather a request, but seller commitments, payments, refunds and delivery exceptions remain backed by deterministic marketplace records and human escalation.