The first problem is that existing restaurants have POS systems that are (1) expensive, and (2) essential for operations. If you want to build an order-at-the-table system that reduces workload, you have to integrate with the POS system or replace it. Replacement is hard because these systems are actually somewhat complicated, and restaurants are scared of replacing their proven system with your unproven one.
Integration isn't hard from a technology standpoint, but you have to get the cooperation of the POS vendor. 80%+ of casual dining restaurants use either MICROS or Aloha (now owned by Radiant Systems). Neither have open APIs or are friendly to potential competitors. Radiant Systems has a kiosk-based front end used by gas stations for sandwich services (Sheetz if you're in the Midwest).
Permission is hard to obtain unless you have a large restaurant chain putting pressure on their vendor. Integration without permission is problematic because the POS system becomes unsupported (the answer to all problems will be "remove the tablet system").
So, the apparent solution is "Find a large restaurant to partner with." More about why that's hard in a minute.
Integration isn't hard from a technology standpoint, but you have to get the cooperation of the POS vendor. 80%+ of casual dining restaurants use either MICROS or Aloha (now owned by Radiant Systems). Neither have open APIs or are friendly to potential competitors. Radiant Systems has a kiosk-based front end used by gas stations for sandwich services (Sheetz if you're in the Midwest).
Permission is hard to obtain unless you have a large restaurant chain putting pressure on their vendor. Integration without permission is problematic because the POS system becomes unsupported (the answer to all problems will be "remove the tablet system").
So, the apparent solution is "Find a large restaurant to partner with." More about why that's hard in a minute.