Taking orders from the delivery marketplaces

Orders placed on a delivery marketplace can land on your kitchen display like any other ticket, so you stop running a separate tablet for each app. Read the limits below before you rely on it - they are real and they are on the screen too.

How it is connected:
Through one connection that reaches many marketplaces at once. The big delivery apps only let approved partners push orders into a point-of-sale, and one of them keeps its specification under a non-disclosure agreement, so Turtini connects through an aggregator whose contract is published and the apps arrive through it as channels. You sign up with the aggregator, they connect your Uber Eats, DoorDash or Grubhub store, and the orders come to us.

Every order still records which app it came from, by name, so your reporting can tell them apart.

Setting it up:
Restaurant -> Settings -> Marketplace ordering. Paste your aggregator credentials, and choose whether they are test or live credentials - that decides which of their servers we talk to, and guessing sends real orders at a test server. Turtini tries to sign in with them before saving; a credential that cannot sign in is not stored, because a stored one reads as connected on every screen.

Then copy the Register URL from that card into the aggregator's own setup screen. When your store connects there, it appears on the same card as a registered store, and you press Attach to this restaurant.

Why you have to press Attach:
Because a signed request proves who is calling, not which of your restaurants they meant. If you run two locations, a store attached automatically could send tickets to the wrong kitchen and nobody would find out until the food was made. One click at setup, once.

Taking an order:
A marketplace order appears in a Marketplace orders panel at the top of the Kitchen board, with a countdown. Press Accept and it moves onto the kitchen board as a normal ticket, prints on your printer if you have one, and comes out of your stock through your recipes. Press Reject and you have to say why - the customer is told, and the marketplace records it against your store, so "sold out of the brisket" and "we are closed" must not look the same.

The countdown is the thing that matters:
The marketplace cancels an order nobody accepts, inside a window it chooses. Turtini also texts and emails you about an unconfirmed order, and for a marketplace order it moves that alarm earlier so it arrives before the order dies rather than after. But that alert runs on a timer shared with other reminders, so it can never be faster than that timer. The countdown on the screen is what actually gets a Saturday order accepted in time. Keep the Kitchen board up.

Handing it over:
Press Mark ready when the food is up, and Handed over when the courier takes it. Handed over is what closes the order, puts it in the day's revenue, and takes the ingredients out of stock.

The money is theirs, and we do not restate it:
The marketplace priced the order, applied its own promotions, worked out the tax, charged the customer and kept its commission before we heard about any of it. So Turtini RECORDS their numbers instead of calculating its own. The tax on a marketplace order is theirs, under their own tax names - your tax categories are not applied to it, because two different tax figures for one sale is one of them being wrong. There is no commission on the order either: that comes off their statement, not from here. Press "About the money" on any order to see this spelled out for that order.

No loyalty points:
A marketplace keeps the customer's identity. We cannot award points to somebody we cannot name, so a marketplace order earns none - for the diner or towards your own lifetime-spend figures.

Your menu going out:
The aggregator asks Turtini for your menu and we answer with it as it is at that moment, including anything you have 86'd. When you run out of something mid-service it now goes dark on the storefront BY ITSELF, within seconds, and comes back by itself when the stock does - you do not have to remember anything. "Push sold-out items now" on the store's card in Settings is the same thing forced, for when you want it this second and want to see the answer. See "Sold-out items reaching the delivery apps" for exactly what travels, how fast, and what you see when it cannot get through.

Items priced by weight are never published to a marketplace. Nobody knows what a cut costs until it is on the scale, which is the same reason they are not offered on your own online menu.

If an item on an incoming order does not match your menu:
The card says so, and nothing comes out of stock for that item. It usually means the item was added on the marketplace's own dashboard rather than in Turtini. Press "What would be published" in Settings to see what Turtini would send them.

What is honestly not proven yet:
Turtini has no credentials for any of this and no test account, so none of it has ever exchanged a message with a real aggregator. Every address, header and code was written from their published documentation. Everything fails loudly rather than quietly: an order we cannot read is refused and the marketplace is told it failed, an acceptance is only recorded after they confirm it, and an order whose signature cannot be verified is rejected at the door and never reaches your kitchen. You will find out the first day you connect a real account, and you will find out from an error message rather than from a customer.