An independent supermarket where the cashiers are local and the owner is not. Two languages, two very different needs, and a fresh category that was quietly losing money every week.
The shop was busy. The owner could not tell whether the fresh section was making money or losing it, because nobody was recording the waste.
Cashiers needed an English interface; training them on a Chinese system was not realistic. The owner needed Chinese reporting. And the fresh category — produce, bakery, chilled — was generating a daily loss that only showed up as a vague feeling at month end.
The language split was the easy part — it is a per-user setting. The real work was making waste visible.
Local staff work entirely in English. I read the stock and margin reports in Chinese. Two people, two languages, one set of numbers.
Not the software. The behaviour it made possible: recording waste at the moment it happens, and having a report that made the fresh section's contribution impossible to ignore.
Within a quarter the owner had changed the ordering pattern on two produce lines and moved the bakery markdown earlier in the day. Neither of those was a system feature. The system just stopped hiding the information.
Note on scope: this deployment is single-store and runs locally with an offline queue, because connectivity at the site is not reliable enough for a cloud-only counter. That is a deliberate trade-off, not a limitation of the product.
Waste control is usually the fastest win. Tell us which categories hurt and we will focus the demo there.
Request a free trial WhatsApp us sales@gdyun.online · Reply within one business day · Support 09:00–21:00 GMT+8