Preview / not connected to live POS

One screen for the owner. One flow for the kitchen.

M&M can keep the register-to-kitchen flow they already use, then add a business layer for online orders, kitchen screens, inventory, alcohol, margins, and an owner agent in Slack.

Kitchen monitorLive tickets
12:08Owanbe Jollof x2Expo in 6 min
12:11Naija Beef SuyaGrill station
12:14Egusi + pounded yamReady for pickup
Slack / #operatorAsk the business

Ola: what is running low before dinner?

M&M Agent: Suya spice, goat meat, and Hennessy are below par. I drafted a reorder list and flagged two menu items with weak margins.

Food cost 31.4% Target: under 30%
Alcohol variance +$186 Check pours after 9pm

POS/KDS bridge

Inventory

Alcohol control

Slack agent

Integration path

First we identify Park Bistro. Then we choose the cleanest takeover path.

“Park Bistro” needs exact vendor confirmation. Until then, the safe preview shows three routes: direct API, non-invasive bridge, or full replacement of the order monitors.

A Direct into the current POS

If Park Bistro exposes orders, tickets, exports, or webhooks, Kanairo reads the flow instead of replacing it.

Best case: fastest adoption, least staff retraining.
B Bridge beside it

If the POS is closed, we import closeout reports, parse kitchen/receipt output, or mirror online orders into a parallel board.

Best for a demo while keeping the restaurant running.
C Take over the monitors

Ni Biashara provides cashier entry, kitchen display, expo, bar, and owner dashboards as one web app.

Best long-term if Ola wants all-in-one control.

What the platform manages

Not just POS. The whole operating loop.

01Order flow

Register, website, phone, catering, and Slack-requested orders enter the same ticket board.

02Inventory tracking

Recipe-level depletion for rice, goat, beef, pepper mix, plantain, spices, cups, and packaging.

03Alcohol tracking

Bottle/keg counts, pour variance, comps, voids, bartender shift notes, and reorder thresholds.

04Cost optimization

Menu margin alerts, vendor price drift, waste logs, prep forecasting, and high-profit item suggestions.

05Kitchen screens

Station views for grill, soups, fryer, expo, bar, ready orders, and 86-item status.

06Owner agent

Ola asks one Slack window: “What happened today?” “What should I buy?” “What is killing margin?”

Slack business agent

The business talks back, without mixing into personal life.

The agent lives inside a dedicated M&M Slack workspace/channel. It can summarize, flag, draft, and ask for approval — but it cannot spend, change prices, or commit to vendors without owner approval.

#operator #orders #kitchen #inventory #finance

Ola: what should I know before tonight?

M&M Agent: Three things: jollof is trending 22% above weekday baseline, goat is below par for Saturday, and two liquor bottles show variance after karaoke night.

Ola: draft the reorder list.

M&M Agent: Drafted. Waiting for your approval before sending anything to vendors.

Build plan

Start useful. Then become the system.

Week 1Discovery + mirror board

Confirm exact POS, inspect receipts/admin exports, build order board demo, connect Slack summaries.

Week 2Inventory + alcohol pilot

Load recipes, par levels, bottle counts, and closeout/import workflow.

Week 3Kitchen monitor mode

Run a browser-based KDS beside the current kitchen screen before replacing anything.

Week 4Payments + all-in-one decision

Choose Stripe Terminal/Square/Toast/ERPNext/Odoo/custom path after POS facts and owner appetite are known.