S/005

Mağaza OPS

Shift handovers, cash counts, target tracking, expenses, labels, training and onboarding — the actual day of a store floor, installed as an app on the staff's own phones.

StatusOngoing
Active2025 —
CategoriesSystems, Automation, Commerce
StackPHP · MySQL · PWA · Service Worker · Web Manifest · Offline cache
01

Context

A store does not run on a strategy. It runs on a sequence of small, repeated, unglamorous acts: opening, counting, checking, labelling, handing over.

Head office sees the month. The floor lives the shift.

02

Friction

The shift record was paper, and paper reached the office days later — by which time it could only be filed, not used.

New staff learned the routine by standing next to someone who already knew it, which made quality a function of who was on that day.

The shift isthe smallest unitof a business.

03

System

The shift is the object. Opening one starts a record; cash counts, expenses, target readings and documents attach to it; closing it produces the store's report without anyone writing a report.

Training and onboarding live in the same application, next to the task they describe, rather than in a binder.

Architecture
Shift openFloor activityCash countTarget trackingExpense / DocumentShift closeStore report
04

Interface

Installed from the browser onto the staff phone, with an offline page and a cached shell, because a store's network is not a promise.

Every routine is a short, ordered list. If a step cannot be completed on a phone in one hand, it is the wrong step.

05

Automation

Nobody types a daily report any more. Target tracking, cash position and expenses are byproducts of the shift being worked, not a second task performed after it.

The label, the document and the handover note are generated from the same record that authorised them.

06

Data

Every store writes into the same schema, so comparison between stores is arithmetic rather than interpretation.

The floor's numbers reach the financial core as movements, not as a summary someone retyped.

Panels
Operations · 13
ShiftsStore auditLabel designExpense vouchersStatus label editorOnboarding documentsDevice listsCompatibility searchLost sales entryTechnical serviceCorporate mailAdvertisement builderIn-store music
Finance · 8
Requests and correctionsCard commissionTransfer and online POS controlDaily margin trackingTill reportingTarget trackingManagement reportingInvoice control
Training · 2
Staff trainingOrientation
Dealer · 2
Dealer accessPhone dealers

Counted from the published panel archive, August 2026.

07

Impact

The system is now twenty-five panels wide, and the shape of that list is the argument: thirteen of them are operations, eight are finance, four are training and dealer access. It grew where the day was heaviest, not where a roadmap said it should.

Counts come from the archive the business publishes itself. Nothing here is estimated.

Panels25
Operations13
Finance8
Training / dealer4
08

Evolution

The open direction is anomaly rather than accumulation: the system should be the first to notice that a count, a margin or a shift does not look like the others.