POS + sales
Captures orders, item sales and payments.
Manager could show: Put sales beside scheduled labor and delivery orders.
A visual walkthrough · example restaurant
Your existing tools run each part of the restaurant. Manager reads their records, finds the problems that cost money and puts two or three concrete fixes next to each one, with the math. The owner approves; nothing runs on its own.
See the problems and the fixesSix short scenes · private pilot · example data · third-party names are not affiliated

Example sources · Square + 7shifts
Scheduled hours × hourly rate from the published schedule vs hourly POS sales, averaged over 4 Tuesdays. Leadership shifts are never suggested for cuts. Employee names are fictional.
Example sources · MarketMan + supplier invoices

Calculated from normalized invoice lines for the same vendor and item. Vendor names are fictional.
Example sources · DoorDash + Uber Eats
Marketplace payout reports (gross, fees, promotions). Price-change math assumes order volume stays flat. Manager does not change marketplace campaigns.
Example sources · Square + Toast
Comparison only. Manager does not claim why sales moved.
Example sources · Square + 7shifts + supplier invoices
Estimate. Food = invoice purchases over the trailing 4 weeks as a share of those weeks’ sales, applied to this week (purchases, not counted usage). Labor = payroll labor cost. Sales = POS net sales.
Manager analysis · Example data
Good morning. Six problems need a decision, each with options.
The delivery promotion and the ribeye credit: together up to $352.42 back this week, before touching schedules or menu prices.
$285.46 per week of extra promotion plus the $66.96 ribeye difference = $352.42. Tuesday 12 PM to 4 PM labor: $637.56 ÷ $1,357.20 = 47.0%. Prime cost: ($25,020.86 + $28,746.99) ÷ $81,422.44 = 66.0%, an estimate from purchases.
Reasoning follows the figures shown. Each suggestion waits for the owner’s approval.Manager organizes source records so the owner can review each problem, pick a fix and record why.
Example source ecosystem
Restaurant services handle different jobs; Manager brings available, restaurant-authorized records into one daily review.
Names and logos are trademarks of their respective owners. They appear only to show the kinds of services a restaurant may already use. Mycellium Lab is not affiliated with, endorsed by or sponsored by any of them, and this demo has no live connection to them.
Captures orders, item sales and payments.
Manager could show: Put sales beside scheduled labor and delivery orders.
Plans shifts and reports clock-ins, breaks, tips and labor.
Manager could show: Compare scheduled labor with sales and flag a gap to review.
Organizes invoices, inventory counts and vendors.
Manager could show: Flag supplier price changes on invoice lines for the owner to review.
Supports reservations, guest profiles, digital orders and channel activity.
Manager could show: Place guest and order activity beside the daily operating picture.
Carries marketplace order, fulfillment, subtotal, tax and tip details.
Manager could show: Compare order totals and fees to estimated payout, not profit.
Shows public listing context, hours, ratings and reviews.
Manager could show: Compare a lunch-menu hypothesis with public listings, not competitor sales.
Reports campaign spend and platform-attributed actions.
Manager could show: Read cost per attributed booking; attribution is not incrementality.
Organizes accounting records, expenses and financial reporting.
Manager could show: Add accounting context to the daily operating review.