What it plugs into.
DineHopper is meant to replace the pile of systems, not add to it — but a venue always has a few things it is keeping. These are the ones we connect to, each with a plain label: Live (venues use it today), Ready to switch on (built; you turn it on yourself), Waiting on partner (waiting on the other company), Coming (not available yet).
Taking payment
Booking deposits, gift cards, event tickets and paying the bill from the table QR code settle into your own Stripe account. We never hold your money.
Shown on the Stripe payment page to guests whose phone has them.
A Pay with PayPal button next to card for gift cards, event tickets and paying at the table. Paste your own PayPal app keys; the money goes to your PayPal account.
Through your Stripe account, for visitors who pay that way.
Pair a Revolut card reader with the till using your own Revolut Business account.
The till sends the amount to the card machine instead of it being keyed in twice. Waiting on the payments partner to sign off.
Take cards on the tablet itself, with no separate card machine.
Switching from another till
Upload the CSV export and bring across your menu, guests and gift cards. Past sales stay in the old system.
Standard USB and network hardware. The scanner types into the retail till like a keyboard: no driver, no bridge app.
Getting orders in
Pickup, delivery and QR at the table, on your own domain, with no commission on any of it. Guests pay at the counter.
Orders drop into the same kitchen queue as everything else, and you can pause the store from the till. Working on Uber’s test store; waiting on Uber to approve going live.
Waiting on DoorDash to give access to its ordering connection.
DoorDash drivers deliver the delivery orders from your own ordering page. Uses your own DoorDash Drive account.
Pulls the day’s parent pre-orders into the kitchen, for venues running a school contract.
Bookings and being found
A step-by-step guide to put your booking link on your Google profile, with a count of the bookings it brings.
A Book button on your Instagram and Facebook pages, with a count of the bookings each brings.
Keeps your hours, special days, Reserve and Order buttons in step with Google and shows your Google reviews. Waiting on Google to approve DineHopper for its business profile connection.
Guests and marketing
Guests who said yes to marketing are added to your Klaviyo list, and new orders and bookings arrive as events your flows can use.
Guests who said yes to marketing are added to your audience. People who unsubscribe in Mailchimp are switched to no marketing here.
Guests who said yes to marketing become HubSpot contacts, matched on email, and trade customers become companies.
Guests who said yes to marketing become Salesforce contacts, and trade customers become accounts.
Send guests who said yes as a custom audience, to build lookalike audiences for your ads.
Member cards and stamp cards that live in the guest’s phone wallet.
Your team and your tools
The alerts your phone gets, posted in a Slack channel, and /dinehopper for today’s bookings and sales.
New bookings, orders and register close-outs as Zapier triggers; create bookings, add guests and mark items sold out as actions.
Your own keys with set permissions, a public API for bookings, menu, orders and guests, and signed webhooks.
Sign in with Microsoft Entra, Okta, Google Workspace or ADFS (OpenID Connect or SAML).
The kitchen
Any Epson ePOS-Print compatible network printer. One per station if you want the grill, the bar and the dessert bench each printing their own.
Any tablet you already own, one link per station, no extra hardware and no per-screen fee.
The back office
Daily sales and supplier bills sent to your accounting package instead of being retyped.
Point a domain you already own at your DineHopper site.
The step-by-step guides live inside your account.
Every connection above is something you switch on yourself, and each one has a guide that tells you exactly where to click. Those sit behind your login rather than out here, because they are written against your own console and half of them name screens only an owner can open.
Sign in to read them, or ask us whether something you run today is covered before you commit.
Running something not on this list?
Tell us what it is. If it is common enough we will say so honestly, and if it is not, we will say that too.