Full-Stack Developer – Multi-Tenant KPI Dashboard & Data Pipeline (Audit First)

We are building a portal and dashboard for salon franchises, several locations each. Owners log in and see their own numbers, per location and consolidated, synced nightly from the franchise system’s REST API. The numbers have to be defensible, not just presentable. If the dashboard says a location did $8,400 Tuesday, that’s what lands in the books. So the hard parts are the pipeline, not the charts. Failed syncs, days that never arrive, and a salon correcting Tuesday’s numbers on Thursday without duplicating or silently overwriting the original. Multi-tenant with 2FA. Owners see only their locations, firm staff see everything, managers limited to specific locations. Enforced in the backend and database, not the UI. KPIs: sales trends, customer count, average ticket, service vs product mix, labor hours, sales per labor hour, labor percentage, day of week and daypart. Date filters, period over period, year over year. Phase one is two or three pilot clients. QuickBooks posting comes later, so leave room for it. Send a multi-tenant dashboard you built (loom video or screenshots). Then tell me how you keep one client from seeing another’s data, layer by layer, and what happens when the API returns a corrected number for a day you already imported. Include rough cost and timeline. Start your reply with Salon.