The Perko platform
One foundation, composed for your business.
Perko connects customers, sales, offerings, fulfillment, staff, payments, and reporting through linked source records. Start with the operating loop your business needs.
- Shared source records
- Modules with clear ownership
- Channels for each role
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.
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 Customers Direct ordering and merchant rewards
- 06 Review Exceptions and close-ready records
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.
Explore each operating loop.
Each module owns cohesive work, permissions, readiness, reports, and recovery behavior.
Counter, Orders & Kitchen
Counter, table QR, and pickup in one live flow, from payment to station and handoff.
Inventory & Margin
Supplier receipt to plate cost. Stock, recipes, counts, and margin stay linked.
Direct Ordering & Repeat Business
Discovery, attributed orders, status, and merchant rewards in one customer loop.
Workforce
Plan shifts, verify attendance, review exceptions, and give staff a clear time record.
Owner Control
Today’s work, module state, access, devices, and the path to close in one place.
Evidence & Reports
Sales, labor, stock, and exceptions become traceable owner evidence.
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.