1 Show
The guest opens the member code bright enough that the clerk does not fall back to a phone number.
The store side is not a reskin of the employee app or a management edition of the member app. Clerks at the register count in seconds. There are only two main paths: guest shows a code, redemption succeeds; stock is short, they order from a list. Put culture, HQ notices and heavy reports on clerk home and redemption falls out of habit. Where the member code comes from. See What belongs on a member mini program home. What happens after you connect HQ. See After the store app shares HQ stock and membership.
2 Scan
The store side opens ready to scan. On miss, allow the last four digits by hand—that is the fallback.
3 Confirm
See the coupon / punch card / order clearly so you do not scan the next table. The confirm key must be large.
4 Deduct
Punch card, stock and points change on the spot. Do not tick a box and backfill at night.
5 HQ can see it
The redemption record enters the same back office. Reconciliation does not collect manager screenshots.
Do not reorder on a group spreadsheet
The stockout list is generated from this store’s stock. The manager ticks quantities and submits. The number enters HQ purchasing or allocation. Status must be visible: submitted, shipped, arrived. If suppliers are also on the chain. See How supplier orders and settlement should run. Multi-end must share stock. See Why one back office keeps multi-end data from forking.
Redemption must be online. Two offline devices each redeem once and the punch card is pierced. Offline fits patrol photos, not deducting entitlements. See No network on site—do you need offline. On a weak network, prompt “please move closer to the register router.” Do not pretend it redeemed. Template redemption is often gray or only redeems platform coupons and will not match your punch-card rules. See A template mini program is almost as bad as none.
Isolate clerk accounts by store. Training only teaches scan and order
Seeing another store’s coupons kills trust immediately. Log in with a clerk code. Do not share one “store” password taped to the screen. Permissions, shifts and voided redemptions leave a trail. Phase one walks redemption and reorder. Notices and roster can wait for phase two. DaXi accepts on a real queue: open to success in a few seconds. To design the store side, go to the Apps & Mini Programs and say the format and whether you have punch cards. Main-entry choice is in Mini program or APP as the main entry. The path to launch is in From brief to launch: how a mobile build runs.
The reorder list should use this store’s safety stock and in-transit counts so managers do not fill by feel. After submit, HQ must be able to refuse or change the allocation warehouse, and status must return to the store side. If the store cannot see status they send another WeChat sheet and the system becomes furniture. The success page gives one sentence a guest understands: “3 visits left on the punch card,” which cuts an argument at the counter. The code shown on member home must be the entry to this same flow. Copy on both sides must match.
Voids, double-taps, dedicated devices and shifts belong in the redemption flow
Void and reverse-redeem need manager permission. Not everyone can tap them. If a wrong redeem can only be fixed by calling HQ, the store side will be abandoned. During peak jitter, submitting must show a clear state so they do not double-tap. The success page gives a number so when a guest asks “did it deduct?” the clerk can match it.
The device can be a dedicated unit. Switching WeChat on a personal phone slows redemption. A dedicated unit still needs lock screen and an account so a guest cannot open it. At shift handoff look at unfinished reorders and pending redeem exceptions. Do not only say “the goods are not here yet.” State in the system is what the next shift can catch.