Skip to content
ConnectMyFile
Platform

Three products that actually know about each other.

CMF is one platform with one identity, one org tree, one permission model and one design system. The products are modules on it, not integrations bolted together after the fact. That is the difference between buying CMF and buying three tools.

Book a demoSee the connected journey →
The architecture

One shell, three modules, one platform underneath.

app.connectmyfile.comOne shellone navigation, one visual languagethe rail switches module, not accountone session, three modulesCMF POSmoduleKitchenHubmoduleCMF Auditmodulesame org treeCMF PlatformIdentity & SSOOrg tree & master dataRoles & permissionsCross-module analyticsOne database. One audit log. One place your data lives.
The connected journey

One Sunday, read across the three lanes.

The arrows are the hand-offs. Nothing is exported, re-keyed or reconciled between them.

09:3013:1213:4118:0018:0221:1522:00Mon 08:00CMF POSlaneKitchenHublaneCMF AuditlaneShift openedfloat countedKOT firedtable 6 · tandoorBill settledUPI + cashPurchase raisedfrom inside the POSCustomer orderoutlet prices appliedDispatcheddelivery challanGoods receivedinto StorageSelf-auditclosing walk-throughFinding assignedowner + deadlinepurchase → customer orderdispatch → goods receivedsite → scheduled auditOne outlet. One user directory. One dashboard the next morning.
What that buys you

Four things three separate tools cannot do.

Buy from your own kitchen without a second login
CMF POSOrdering portalSSO
SSO from the POS into the ordering portal, as that outlet.
That outlet's price list is already applied.
The order lands in the same pipeline as every other buyer.
One outlet, one identity, everywhere
OutletCustomer · Siteone record
The outlet in the POS is the customer in KitchenHub.
That same record is the site in CMF Audit.
One record, three views, no reconciliation.
One user, one password, one role
One roleThree modulespermissions
A store manager gets the right access in every module.
It comes from a single role on the org tree.
Revoke it in one place and it is gone everywhere.
One dashboard across all of it
Three modulesOne dashboardanalytics
Sales, stock and compliance for the same site.
Side by side, not in three exports.
Drill from org to region to a single outlet.
Adoption

Start with one, add the rest.

01
Start with CMF POS

Bill, print and close the day in your first outlet. Your outlets and users become the org tree.

02
Add CMF Audit

Those same outlets are already sites. Schedule formats against them on day one, no setup twice.

03
Add KitchenHub

Outlets become customers of your kitchen and order from inside the POS they already use.

Modules are priced separately and switch on without a migration.

Deployment & reliability

The cloud is where it reports, not where it depends.

Billing keeps working when the connection drops. The in-store box holds the day and syncs when it returns.

Audits are filled offline on a phone and upload later, photos and all.

Centrally monitored: every outlet's health visible to your team.

Every box reports its health, sync lag and printer state, so your team sees a problem at an outlet before the outlet calls.

ANDHERI WEST · OUTLETIn-store boxholds the day · 2 terminalsbilling · KOT · day-closeCMF CLOUDOne org tree212 sites · monitoredsync when onlineAUDIT PHONEuploads later, photos tooevery outlet's health visible to your team
Security

One permission model, and a log of everything that happened under it.

Role-based permissions to the action level
Session control & revocation
Full audit log across every module
Multi-country, multi-currency
200+ sites in one org tree
Data isolated per brand
Encrypted in transit and at rest

See CMF running on your own menu.

A 30-minute walkthrough on your data. No commitment.

Book a demoTalk to sales