01
Local-first POS
The tap lands before the network answers.
Orders, notes and checkout intents are accepted on the device first, then synchronized and reconciled in the background.
Restaurant operations, built for the rush
From first tap to last count, one restaurant system.
WizyFNB joins a local-first iPad POS, live table and kitchen flow, detailed inventory and owner controls inside one secure Wizy workspace.
Dine-in focusedTablet-readyWorkspace-secured
Sample shift preview
Local + syncedOpen
Ordering
Kitchen
Ready
Checkout
Available
One check · every station
Table service flow
Order accepted locallySaved
Kitchen ticketPreparing
Inventory componentsLinked
Checkout intentDurable
Inventory signal
Low stock and expiry stay visible to operators.
Local-first order flow
Kitchen station states
Inventory management
Secure MCP roadmap
Why WizyFNB
Built around restaurant failure points—not generic software checklists.
The strongest parts of WizyFNB live where service usually breaks: network delay, station handoff and the gap between what was sold and what remains in stock.
02
One live check
Floor, kitchen and checkout share the same story.
A table order moves through kitchen states, payment and release without staff rebuilding context at each station.
03
Inventory-aware
Stock decisions stay close to what you sell.
Track ingredients, supplies and retail products, then connect menu variants to the inventory components they consume.
Inventory management
Know what is on hand—and what each menu choice consumes.
Inventory is an operator workflow, not a hidden accounting table. WizyFNB combines reference data, stock movement, alerts and menu component mapping in the same Back Office.
- Ingredients, supplies and retail products
- Units, groups, vendors and storage locations
- Quick adjustments with movement history
- Low-stock, out-of-stock and expiry signals
- Menu-variant component recipes
Sample inventory workspace
Operational stock overview
Ingredient
Tracked by base unit
Healthy
Fresh stock
Expiry window visible
Review
Supply
Movement history ready
Tracked
Movement ledger
Purchase, adjustment and waste history
Menu components
Variant-level ingredient mapping
AI operations through MCP
PlannedLet AI help operate the restaurant—inside a permission boundary.
The WizyFNB MCP roadmap gives approved AI clients narrow tools to read restaurant context and prepare menu, inventory and dine-in order actions for one authorized workspace.
One workspace per consent
Role and scope checked
Business-named AI tools
Preview before sensitive commit
AI operation preview
“Prepare a dine-in order for the selected table using available menu variants.”
Authorized flow
1Resolve workspace, table and menuRead
2Build an authoritative order previewPrepare
3Ask a human to confirm kitchen impactApprove
4Commit once with an idempotency keyWrite
Connected operations
Every screen has a job. Every job shares restaurant context.
WizyFNB separates fast staff interaction from compact operator control, while keeping both attached to the same workspace and platform APIs.
01
Floor
Tables and service areas
Live occupancy overlays local check activity, keeping the floor usable even while background work is still syncing.
02
Kitchen
Tickets by station
Move items from sent to preparing, ready and served while preserving notes, variants and modifiers.
03
Checkout
Cash and card-terminal recovery
Durable payment intent, exact terminal recovery and idempotent completion protect the cashier from duplicate actions.
04
Menu
Variants built into the catalog
Each sellable size or format keeps its own price, availability and historical order identity.
05
Back Office
Compact control for operators
Menu, tables, orders, inventory, guests, staff and settings live in a scan-friendly owner workspace.
06
Wizy foundation
One secure workspace boundary
Roles, staff context, modules, location, currency and language travel with the authenticated workspace.
Two purpose-built surfaces
Touch-first for staff. Scan-first for operators.
A single compromise layout cannot serve a busy cashier and an owner reviewing twenty inventory rows. WizyFNB gives each context its own interface.
Staff POS
Large controls. Minimal typing. Immediate feedback.
Table cards, menu tiles, quantity controls and payment choices are sized for a landscape iPad during service.
Select table
Tap items
Send kitchen
Back Office
Compact tools for setup, review and control.
Owners and managers scan menus, orders, inventory, customers, staff and settings without oversized POS chrome.
Inventory alerts and item rows
Menu variants and availability
Workspace roles and modules
Operator questions
Clear answers before the first shift.
WizyFNB is intentionally focused on dine-in restaurant operations in its current product phase.
Is WizyFNB just another POS?
No. POS is the service surface. WizyFNB connects it to table state, kitchen fulfillment, menu control, inventory, payments and the owner Back Office.
What happens when restaurant Wi-Fi is unstable?
The POS is designed local-first. Staff actions are recorded on the device before related network work, then a background worker syncs and reconciles them when connectivity allows.
Can inventory follow menu consumption?
Yes. Menu variants can be linked to inventory components, while operators manage quantities, units, categories, vendors, movements and alerts from Back Office.
Is the MCP integration available today?
MCP is a planned, security-gated capability. The design uses explicit workspace consent, narrow permissions and preview-before-commit for sensitive AI actions. It is not presented as generally available yet.
Your service flow, mapped
See how WizyFNB fits your floor, menu and stock room.
Bring the way your team takes orders today. We will map the first rollout around the workflows that matter during service.