Give your delivery-heavy restaurants a reason to choose you.
Delivery tools in a POS tend to focus on marketplaces and outside couriers. The independent restaurant that delivers with its own drivers is left to sort out who takes which order, by hand, on its busiest nights. BottomLine’s Delivery Display Screen (DDS) builds the runs for those drivers, and gives your sales team a delivery answer for the restaurants that care most. Think of it as the kitchen display screen for delivery.
Start a conversationSee the gap
Independent restaurants that deliver for themselves
Marketplaces and courier networks plug into the POS. The restaurant with its own drivers mostly gets a tablet and a shout across the kitchen.
Orders arrive, someone else delivers
App orders flow into the POS and the app's couriers carry them out.
Orders go out, someone else drives
Outside couriers can be added to the POS, so the restaurant never touches the route.
Orders wait for a decision
The restaurant employs its drivers, so someone decides who takes what and in what order. Drivers grab the tickets they like, leave half-loaded, or stand at the door deciding.
These are the high-volume, delivery-dependent restaurants where a POS's delivery tools get tested hardest, and where a better answer wins the deal.
Runs built for the drivers, a scan to go
Orders come in
The DDS reads the restaurant's delivery orders from the POS and shows them on a map.
Runs build themselves
Ready orders headed the same way are clustered into runs, in driving order, using limits the restaurant sets.
Drivers scan and go
Two QR codes, one for Apple Maps and one for Google Maps, open the route. Stops come in order and end at the restaurant.
The whole DDS runs on read access
The DDS does not need to change anything inside your POS to do its job. Read access to delivery orders is enough to build the runs and hand them to the drivers. That is how it runs today at Ice House.
Write access is what makes the transition seamless. It lets the DDS close the loop, so the restaurant's staff never do a second step.
| With read access (works today) | With write access (what it adds) | |
|---|---|---|
| Orders into the DDS | Delivery orders are read from the POS in near real time | Same |
| Runs and routes | Built and handed to the driver with a scan | Same |
| When an order leaves the DDS | When staff sign it out to a driver in the POS | When the driver takes the run, with no extra step |
| Order status in the POS | Staff keep it up to date as they do now | Updated automatically as the driver leaves |
| Extra steps for staff | One: sign the delivery out in the POS, as today | None |
Start with read. Add the narrowest write permissions only where they remove a step, and only when you are comfortable.
Why give us the access
A delivery answer that wins accounts
When a prospect says delivery is where they struggle, your reps can show a system that builds the runs and hands drivers a route. It gives your reps something to demo to the owners who make the decision.
A reason for the restaurant to stay
A restaurant that runs its drivers through your system has one more reason to keep it.
More orders on your rails
When a restaurant moves regulars off the apps and onto ordering direct, those orders run through the restaurant's own POS. App orders run through the app.
No threat to your product
The DDS does not take payments, own the menu, or hold the customer relationship. Your POS stays the system the restaurant runs on.
Built and run in a pizzeria
At Ice House Steaks & Pizza, an in-house delivery kept about 90% of the order. A DoorDash order kept 79% and an Uber Eats order 76%.
One restaurant, June 1 to September 20, 2026. Ice House runs on Toast, where the DDS has been tested the most. The Clover version has been tested as an Android app, with a Clover App Market launch planned for March 2027. See the full breakdown.
Start small, measure it
A conversation
Tell us what your partner program involves, and what access you can offer for a delivery integration.
A few pilot restaurants
An introduction to two or three delivery-heavy accounts that run their own drivers.
A result you can show
We measure deliveries per driver-hour before and after, and share what we find.
FAQ
Do you replace any part of our POS?
No. The DDS sits beside your POS. It does not process payments, manage menus or replace your system.
What do you read?
Delivery orders: what was ordered, where it goes and when it is ready. That is what it takes to build a run.
How do restaurants connect today?
On Toast, a restaurant connects with its own read-only API credentials. On Clover, the DDS is built as an App Market app, with the launch planned for March 2027.
What would you need from us?
Documentation, a sandbox, a named contact, and a path to the access level your program offers. We are happy to start with read access.
Is there anything to sign up for?
No terms are set. Tell us how you usually work with partners, and we will work out the rest together.
Bring us your busiest delivery restaurants.
Email either of us. We reply fast.
Email GrantEmail Phillipgrant.smith@bottomlinedeliveries.com
phillip.bolinger@bottomlinedeliveries.com
Toast, Clover and other product names are trademarks of their respective owners. BottomLine is not affiliated with or endorsed by them.