How SSP fits together
SSP is one system with several screens. A restaurant sets everything up once in SSP Manager. Guests, waiters and the kitchen then work on the same live order, each from their own screen, and every sale ends up back in SSP Manager. Nothing is copied between apps: when one screen changes the order, the others see it straight away.
The products
| Product | Who uses it | Where it runs | What it's for |
|---|---|---|---|
| SSP Manager | Owners and managers | Any browser, at manager.ssppos.com | The back office. Menus, tables, staff and permissions, kitchen stations, taxes, payments, website ordering and reports. Every other app reads its settings from here. |
| SSP Waiter Web | Servers, hosts, floor managers | Any browser, at waiter.ssppos.com: a POS terminal, tablet or desktop | Open tables, take orders, send them to the kitchen, take payments. |
| SSP Waiter Mobile | Servers on the floor | An app for iOS, Android and Windows | The same job as Waiter Web, from a phone or handheld. |
| SSP Kitchen | Cooks and the pass | A browser on the kitchen screen, at kitchen.ssppos.com | The kitchen display (KDS). Shows each station its dishes, runs courses and timers, accepts web orders, and lets the kitchen 86 a dish. |
| Scan. Splt. Pay. | Guests | The guest's own phone, at SPLT.ca. Nothing to install. | See the table's order, add to it if the restaurant allows, split the bill, tip and pay. |
| Website ordering | Guests ordering ahead | The restaurant's own website, or an ordering link or QR code | Pickup orders. Set up in SSP Manager; the orders go to the kitchen like any other. |
| Plugin SDK | Developers | Their own servers | Connect payment, delivery, inventory and other services to SSP. |
Follow one order
- Set up. In SSP Manager the restaurant builds its menu, lays out its tables, invites its staff and creates its kitchen stations. Routing decides which station cooks which dish.
- Order. The guest taps the tag or opens the link on their table, and Scan. Splt. Pay. opens on that table's order. A server can start or add to the same order from SSP Waiter. Both see every line as it's added.
- Send to the kitchen. When the order is sent, each dish appears on the SSP Kitchen screen of the station that cooks it. The pass (Expo screen) sees the whole ticket.
- Cook and serve. Each tap in the kitchen (Preparing, Ready, Served) shows on the waiter's screen and on the guest's phone at once.
- Pay. The guests split and pay on their phones, if the restaurant allows it, or the server takes the payment. It's one bill: whatever someone pays comes off what the rest of the table owes.
- Report. The order, its payments and tips appear in SSP Manager's Orders and Reports, including the End of Day and End of Shift reports.
A pickup order from the restaurant's website follows the same path from step 3. The kitchen accepts it with a ready time, and the guest follows it on their phone until it's picked up.
When something runs out
Every menu item has one Available switch, kept in SSP Manager for the whole location. Turning it off ("86-ing" the dish) takes the dish off every screen at once:
| Where | What happens |
|---|---|
| SSP Waiter | The dish can't be ordered: the waiter's screen shows it as unavailable instead of letting it be added. |
| Scan. Splt. Pay. | The dish disappears from the menu on the guest's phone. |
| Website ordering | The dish shows as sold out. |
| Orders already sent | Not affected: the kitchen cooks what's already on the board. |
Two places can flip the switch:
- The kitchen, from the dish's sheet on SSP Kitchen. This is the fastest during service. See 86 a dish.
- A manager, in SSP Manager's menu, for one item or many at once. See 86 an item during service.
Only SSP Manager can put a dish back. The kitchen screen can take it off but not bring it back.
One login, one set of permissions
Staff sign in to SSP Waiter and SSP Kitchen with their SSP Manager account; there are no separate passwords per app. What each person can do (take payments, apply discounts, 86 a dish, fire a course) comes from their role and permissions, set once in SSP Manager. See Roles & permissions.
Guests never need an account. Their phone is tied to the table, or to the order code, and nothing more.
Where to start
| You are… | Start here |
|---|---|
| Setting up a restaurant, or trying SSP out | Onboarding. For a trial you can skip the optional steps, such as payments and taxes, and come back to them later. |
| A server or host | Signing in and shared tablets |
| Working in the kitchen | SSP Kitchen |
| A guest at the table | Help with Scan. Splt. Pay. |
| A developer | Plugin SDK |