The Perko platform
Start with one proven workflow.
Perko connects staff, orders, payments, stock, and owner reporting without pretending every workflow has the same launch status. Start with a managed pilot and expand only after readiness is checked.
- One-location managed pilot
- Visible capability status
- Human-approved protected changes
Venue · Today
One operating record Orders, work, stock, and review
Connected The operating day
One venue. One operating record.
Orders, preparation, stock, time, customers, and review stay connected. Each domain keeps its own rules without becoming a second source of truth.
The fragmented day
Tickets, spreadsheets, chats, and separate terminals hold parts of the day. At close, someone must reconstruct what happened.
- 01 Orders Every channel, one order record
- 02 Kitchen Station-owned live work
- 03 Workforce Shifts, attendance, and approved time
- 04 Inventory Stock, recipes, and cost evidence
- 05 Payments Recorded methods and linked invoices
- 06 Review Sales, labor, stock, and visible exceptions
How the platform fits together
Many workspaces. Shared business facts.
Customers, staff, kitchens, managers, and owners need different tools. Perko gives each role a focused channel while the source records stay connected.
A channel can show a business fact. It cannot silently create a second authority for that fact.
Linked source recordsOrders · fulfillment · stock · time · money · permissions
Authoritative OfferingsCommerceFulfillmentWorkforceInventoryReporting
Explore each operating loop.
Each module owns cohesive work, permissions, readiness, reports, and recovery behavior.
01
Pilot and validation
Explore module 02 Counter, Orders & Kitchen
Counter, orders, approved payment records, and invoices are in the pilot; kitchen handoff remains under validation.
Active validation
Explore module 03 Inventory & Cost
Purchasing, document extraction, stock, recipes, and valuation are under active validation.
Product direction
Explore module 04 Direct Ordering & Repeat Business
Customer ordering and merchant rewards remain product direction, not a current launch promise.
Managed pilot
Explore module 05 Workforce
Plan shifts, verify attendance, approve time, and give staff clear earnings information in the managed pilot.
Managed pilot
Explore module 06 Owner Control
Owners can see live operating and labor indicators while broader close and device workflows remain bounded.
Pilot and validation
Explore module Evidence & Reports
Sales and labor reporting operate in the pilot; stock and cross-module reporting expand with validated sources.
In development
Useful next, but not sold as finished.
These capabilities have implementation behind them, but they remain outside the current public launch promise until release and operating evidence is accepted.
In development
Perko Assistant
A permission-scoped assistant can explain deterministic sales, order, inventory, and workforce data and prepare reviewable proposals. It cannot approve protected changes.
In development
Operational Finance
Accounts, recorded balances, paid expenses, receipts, transfers, reversals, and exports are being built as operational control—not bank reconciliation or statutory accounting.
Platform principles
Connected does not mean collapsed.
Perko links complete operating loops while preserving authority, history, and clear boundaries.
One authority for each fact
Money, stock, orders, time, and permissions keep a defined source record.
Complete loops over feature count
A module includes normal work, review, correction, recovery, and evidence.
Configuration instead of forks
Locations and business types use reviewed defaults without separate product code.
People approve protected change
Automation can propose. Authorized people approve money, stock, access, and publication changes.
Start with one operating problem.
Tell us about your business and the workflow you want to make clear first.