The back office that runs a restaurant chain, rebuilt to feel calm: menu, staff, orders, promotions and reports for every site.
Context
Tabit is a hospitality platform: a mobile point of sale, online ordering, kiosks, loyalty and more. Tabit Office is the web app behind all of it, where operators set up and watch the business. It had grown feature by feature, and its structure followed the order things were built.
I redesigned it end to end, part-time at Tabit: structure, navigation, visual language and the key screens, plus the help center that supports it.
Decisions
A back office is only as good as the shape underneath it, so I fixed structure before colour. I audited every module as each kind of user would meet it, then regrouped fourteen modules into five jobs: run the day, people, grow, know and set up.
Two more choices held it together. One small kit of patterns used in every module, so an operator learns something once. And a top bar that always names the level you are editing, group, chain or site, because in a multi-site business the worst mistake is changing the wrong one.
Design
Login, home, sites, menu, item editor, online ordering, staff, roles, scheduling, tip out, promotions, gift cards, reports, BI, order search, site setup, third party, kiosk and what's new.
Every module follows the same pattern, and nothing goes live until you save.
Help center
The help center mirrors the same five groups, so docs and product share one map. Even the quiet moments are designed: loading, empty, errors and confirmations.
Takeaways
One language now runs from login to reports to the help center, and more than twenty screens sit on one system.
In a tool people use all day, structure matters more than style. Getting the grouping right made every later screen easier to design.
