Send Flowers, Food or a Gift to Someone Else
August 16, 2026 · 5 min read
You want to send something to someone who isn't you
Say your sister is in Toronto and you're in Mississauga. It's her birthday, you can't make it over, and you're not going to send another gift card that sits unused in an inbox.
Or your girlfriend had a hard week and you want cake at her door tonight, not a card that arrives Thursday.
Or a colleague covered for you last minute and you want to say thank you with something real, today, without asking her for her address in a Slack message that makes the whole thing less of a surprise.
This is the moment most ecommerce quietly ignores. Almost every checkout flow on earth assumes the person paying is the person receiving. Type your address, type your card, get your box. That assumption is fine for restocking paper towels. It falls apart the second you want to do something for someone else.
Ordering for someone else, on Yaha
On Yaha, you don't need the recipient's address, and you don't need to be in the same city as them. You find the shop, whether it's a bakery, a florist, a restaurant, or a gift shop, and at checkout you enter the recipient's Yaha username instead of your own delivery details. The order, and the notification that it's arrived, go straight to them. You pay. They receive.
That's the whole mechanic, and it's the reason the rest of this is possible: birthday cakes sent across a city, dinner sent to a partner working late, flowers sent to a parent on their anniversary, a thank-you gift sent to someone who did you a real favour, a Valentine's order sent to someone you can't be next to that day. None of it requires the sender to know a street address. It only requires knowing a name.
Buying for yourself is not the whole story
Most of what gets built for online ordering assumes the transaction is selfish in the neutral sense: I want food, I buy food, I eat food. That's true most of the time. But a meaningful share of why people spend money is to do something for somebody else, and that intention usually gets bolted onto ecommerce badly, if at all. Flower sites solved it decades ago because flowers are almost always for someone else. Food and everyday local shopping never really did.
Yaha treats "send this to someone" as a first-class order, not an edge case. A shop that sells cakes, like a bakery on the platform, or scents, the way <cite index="0-0">Gora Scents</cite> does out of Nairobi, or flowers, or a full dinner from a restaurant like <cite index="0-0">Salaama Hut</cite> in Toronto, doesn't need to build anything different to support this. The shop just takes an order. Yaha handles the part where the person paying and the person eating are two different people in two different places.
The problem this actually solves, underneath
This sounds simple until you try to build it, because ordering for someone else quietly breaks three things that every checkout normally assumes are the same person: who is paying, who the order belongs to for support and history purposes, and who the shop should actually contact and deliver to.
A payment needs a payer, with their card and their receipt. A fulfillment needs a real recipient, with their phone number, their delivery preference, their notification. And a shop needs to know, unambiguously, who to hand the order to when it's ready, without confusing it with the sender's own order history. Get this wrong and you get the classic failure mode of every "send a gift" feature bolted onto an existing platform: the recipient never finds out, or the notification goes to the wrong inbox, or the shop calls the person who paid instead of the person waiting for the cake.
Solving it means treating identity as two roles instead of one role duplicated. The person who pays is a customer. The person who receives is also a customer, with their own account, their own notification, their own order sitting in their own history, as if they'd ordered it themselves, because in every way that matters to them, they did. The sender's job ends at checkout. The shop's job is unchanged, they fulfil an order the same way they always do. The only new thing in the system is a second identity attached to a single order, and making sure every downstream step, the notification, the receipt, the delivery, points at the right one.
A category with its own shape
Once ordering-for-someone-else works cleanly, it stops being a feature and starts being a category. Call it social commerce if you want a name for it: commerce that runs between two people, not just between a person and a shop. A Valentine's order sent across town. A birthday dinner sent instead of carried. A surprise delivery timed to land while someone's still at their desk. A thank-you gift that shows up before the thank-you text does.
It's also good for the shops. A florist or a bakery or a restaurant that can receive orders from people who aren't local, sent to recipients who are, reaches a customer they'd otherwise never see: the one who wants to spend money in this city while sitting in another one entirely. That's a second, quieter reason to have a real order page in the first place, the kind we've written about in <a href="/blog/the-order-page-is-the-product-not-the-dashboard">The Order Page Is the Product, Not the Dashboard</a>. A page built well enough to take an order from anyone can take one from someone who isn't even standing in the same country as the person it's for.
Try it before you need it
The best time to find this out isn't the day you actually need to send something. It's now, so that the next time someone's birthday sneaks up on you, or you want to say thank you properly, or it's February 14th and you're not where you want to be, you already know how.
Find a shop on Yaha, get their recipient's username, and send it. Or if you run a shop and you're not on Yaha yet, start at yaha.app/join and let your customers start sending your food, your flowers, or your cake to the people they can't be with.