Branch
A physical store location.
- idPK
- name / slugUK
- regiontext
- lat / lngmap pin
- whatsappphone
→ has many staff, customers, products, invoices
HHMatrics · Multi-Branch Retail Platform
This is the blueprint of every piece of information the system stores and how it moves — from a customer browsing online to a follow-up message after they visit a store. Review it, and tell us anything you want added, renamed, or changed.
Each box is a table of records. Grouped by what it does. Every table tied to a branch is kept strictly separate per store — one branch can never see another branch's data. Only the Super Admin sees everything.
Branches & Staff Access
A physical store location.
→ has many staff, customers, products, invoices
Login for any staff member.
→ is one Manager or Salesman
Runs one branch.
→ belongs to one Branch
Serves customers on the floor.
→ handles many Interactions
Sessions & Super Admin one-time codes.
→ keeps logins safe & revocable
Customers & Sales
A shopper. Duplicates are auto-merged by name + mobile.
→ has interactions, invoices, reviews, messages
One visit — salesman meets customer.
→ yields one Review
Feedback via a private link.
→ rates a Product & a Salesman
Catalog & 3D
An item in a branch's inventory.
→ has photos & a 3D model
Each photo, plus its generated 3D avatar.
→ belongs to one Product
Billing, Messaging & Server Health
Pulled from your billing software's export files.
→ re-imports never double-count
Every WhatsApp/SMS Hermes sends.
→ transport can be swapped anytime
Snapshots of server health.
→ alerts IT if temp > 75°C
How a single shopper flows through the system — and where automated messages fire.
All of this runs on one in-house Ubuntu server — no monthly cloud fees. Messages go out through WhatsApp directly, without paying for the official business API.
What people use
↓ secured by Nginx (encrypted HTTPS)
The brains
↓ stores & queues work
Data & background work
Hermes → customer WhatsApp · billing export files → import · server heat → IT alert