Fast to deploy. Built to go deep on Clover.
BottomLine’s Delivery Display Screen (DDS) goes live quickly because it sits beside your POS instead of replacing it. And Clover is where we’re leaning in hardest, because Clover’s platform is letting us make real inroads: far enough in to run delivery from the first order to the last driver back.
Built at a working pizzeria. That’s why it deploys fast.
Nothing here was designed in the abstract. It was built at a restaurant that delivers every night, tested on real orders, and tweaked again and again. That’s why a restaurant can start in minutes: about 15 on Toast, and right away by typing in addresses.
The road so far
- Where it started
A router, a $230 computer and Bing Maps at the door
Phil Bolinger’s first fix for Friday nights at his family’s restaurant. The crew went from 14 drivers to 11.
- Built
Software that tweaks and repeats
Then he asked Grant Smith to see if software could route better. Phil’s verdict: “It stood no chance. So he tweaked it. Repeat that a few times and you have a piece of software that can smoke me.”
- Live
Toast, running at Ice House
The DDS reads Toast delivery orders in near real time. It’s our most tested integration, and where we try every new feature first.
- Tested
Clover, Version 1
Listed on the Clover App Market as an Android app, and used for testing.
- Planned · March 2027
Clover, Version 2
Built for the Clover POS, and planned for the Clover App Market.
- In the works
Follow Your Order, a driver app, a live map and hands-free texts
The next features. Vote on what we build first.
The hurdle isn’t the software. It’s the back door.
For the DDS to work its best, it has to get into a restaurant’s POS. That takes a platform that lets outside developers in. Clover’s platform does, and it’s letting us make inroads. That’s why we latched on.
Toast
Read access today, with the restaurant’s own credentials. Orders show up on the DDS in near real time. Write access: not yet.
Clover, Version 1
Listed on the Clover App Market as an Android app, and used for testing.
Clover, Version 2
Built for the Clover POS, at the level the DDS needs to run delivery from start to finish.
Read access gets us started. Write access makes it seamless.
For the DDS to work its best we need both: read access to the API, so orders reach the DDS, and write access, so the DDS can move orders along in the POS. Step through one order’s trip to see where each one matters.
Read access (the API)
Delivery orders: what was ordered, where it goes and when it is ready. That is enough to build the runs and hand them to drivers, and it is how the DDS runs today at Ice House.
Write access
The ability to move orders along in the POS as drivers take runs, so the restaurant’s staff never do a second step. We ask for the narrowest permissions that remove a step.
Not a button. A roadmap.
Delivery tools in a POS tend to stop at “send this order to a courier.” The Delivery Display Screen (DDS) is built for the drivers a restaurant already employs: the literal roadmap to getting deliveries out faster and drivers back more quickly.
| Compared on | A “send it to DoorDash” button | The DDS |
|---|---|---|
| What it does | Hands one order to an outside courier | Builds the runs for your own drivers |
| Who drives | A courier you don’t employ | Your drivers |
| What your team gets | An order, assigned | A roadmap: which orders go together, in what order, and the route |
| Where the run ends | At the customer’s door | Back at your door, ready for the next run |
| What it’s for | Getting an order delivered when you don’t want to drive it yourself | Getting your own drivers out faster and back more quickly |
Deliveries out faster. Drivers back more quickly. That’s the whole job.
Where do you fit?
I run a restaurant on Clover
Join early access and we’ll tell you as soon as Version 2 is ready for your store.
I sell Clover
We’re lining up a small group of resellers and reps with delivery-heavy accounts to pilot the DDS before the App Market launch.
I work at another POS company
We won’t be exclusive to one POS brand, and a platform that supports us gets our full attention.
Clover and speed, answered
Is the DDS on the Clover App Market?
Version 1 was listed on the Clover App Market as an Android app, and we used it for testing. Version 2 is built for the Clover POS and planned for the App Market in March 2027.
What does the DDS need from Clover?
Read access to Clover's API, so delivery orders show up on the DDS, and write access, so the DDS can move orders along in the POS. For the DDS to work its best we need both.
Why are you focused on Clover?
Because Clover's platform is open to outside developers, and it is letting us make inroads: far enough in to run delivery from the first order to the last driver back. The hurdle for any delivery tool is getting into the POS back end.
How fast can a restaurant start?
On Toast, about 15 minutes with the restaurant's own credentials. On any system, a restaurant can type in addresses and the DDS builds the runs right away. On Clover, Version 2 is planned for March 2027, and early access is open now.
How is this different from a button that sends an order to DoorDash?
That kind of integration hands an order to an outside courier. The DDS builds the runs for the drivers a restaurant already employs: which orders go together, in what order, and the route, ending back at the restaurant.
Does the DDS replace DoorDash or Uber Eats?
No. Restaurants keep the apps for new customers and move their regulars in-house over time. BottomLine helps own-driver delivery pay.
What does a restaurant need to run it on Clover?
Clover, two Clover screens that can run the app (one at the packing station and one for drivers) and its own delivery drivers.
Is BottomLine affiliated with Clover?
No. Clover is a trademark of its owner, and BottomLine is not affiliated with or endorsed by Clover.
On Clover? Be first in line.
Tell us about your restaurant and we’ll let you know as soon as Version 2 is ready for your store.
Get early accessWork with usClover is a trademark of its owner. Toast and other product names are trademarks of their respective owners. BottomLine is not affiliated with or endorsed by them.