Multi-Restaurant Node Cloud Backend

I need a solid backend that lets several independent restaurants run from the same cloud platform while keeping a local MySQL database at each venue. The stack is already set: Node.js on the server side, Angular for the web console, and standard SQL.

Core features I must see working: order management that mirrors every ticket and status update in real time, a secure user-authentication layer (roles for cashiers, kitchen, managers, etc.), and inventory tracking that updates stock counts the moment an item is sold or a delivery is recorded.

Each restaurant keeps operating even if its connection blips, so a lightweight web service will sit on the local machine, watch the MySQL tables, and push changes to the cloud API the instant they happen; the cloud then replies with any new data to keep both sides in sync. Think of it as bidirectional, near-zero latency replication built specifically for this schema, not generic DB replication.

For visibility I want an Angular dashboard that shows live orders, inventory levels and basic user management. Clean, modular code, TypeScript throughout, Sequelize or TypeORM is fine for the data layer as long as migrations are included. Please package the project with a short README covering environment variables, build commands and how to seed a fresh database so I can spin up staging quickly.

Acceptance will be based on:
• A working REST/GraphQL API that passes Postman tests for orders, users and inventory
• Real-time sync demoed with two local cafés pushing data to one cloud instance without conflicts
• JWT-based auth with role checks on every protected route
• Angular UI compiling with ng build --prod and consuming the live API

If you have already tackled similar multi-branch or POS-style systems, let me know; otherwise, outline your approach to the sync layer so I can be confident it will scale beyond the first three restaurants.