Multi-site Sunday counts without conflicting freezes

5 November 2025 · Helena Tam

Multi-site Sunday counts without conflicting freezes

Fashion and convenience groups often choose a Sunday so trading floors can close. The failure mode is familiar: each store freezes at a different hour while the stockroom keeps fulfilling internal transfers.

One freeze clock, local doors

Publish a single freeze timestamp in HKT for inventory ownership, then translate it into local door actions — when the shutter drops, when the last POS sale may complete, when the stockroom stops picking for stores.

Shared exception channel

Captains at Causeway Bay and Mong Kok should not invent separate WhatsApp groups. A shared log with site tags lets finance see cross-store transfers that crossed the freeze.

Stagger observer arrivals, not freeze times

Traffic and MTR works can delay a team; that is not a reason to move the freeze. Build travel buffer into observer call times instead.

Close with a cross-site memo

The coordination memo should list each site’s finish time and material exceptions in one document. Auditors dislike three unrelated PDFs for one group count.

Planning a similar Sunday? Walk through our count process and request dates before peak season fills.

← All field notes