How to investigate low-activity stores using live Interaction signals

Investigate a low-activity store by checking the reporting setup, Device status where available, physical placement and trading context. Zero recorded Interactions are a signal to investigate, not proof of missing POS or a broken screen. Combine analytics with field evidence before assigning a cause or dispatching support.

Define what needs attention

“Dark store” is ambiguous, so use a precise operational label such as “no Device communication” or “no recorded QR-origin Sessions”. Agree the time window and compare locations with relevant trading conditions. A new, low-volume placement should not inherit an arbitrary threshold from an unrelated flagship bay.

Build the location register before installation: planned store, Touchpoint, Device where present, placement, expected activation date and responsible support team. Note whether identifiers are unique to a store or shared by a cohort.

Use a diagnostic matrix

| Observation | Possible explanations | Next check | | --- | --- | --- | | No recent Device communication | Connectivity loss, power loss or reporting issue | Check freshness rule, support logs and local playback | | Device communicating with no Interactions | Low traffic, unclear invitation, obstructed screen or Event issue | Review real Experience, placement photo and tracking test | | No QR or NFC activity | No use, mapping error, unreadable carrier or missing material | Test the physical Touchpoint and confirm its assigned route | | Sudden change after an update | Content, tracking or destination change | Compare version and publication time with the change | | Lower volume than peer stores | Different footfall, hours, stock or fixture position | Confirm comparability before assigning a fault |

These are hypotheses for investigation. Avoid turning a diagnostic suggestion into a claimed observation.

Separate connected hardware from printed Touchpoints

Managed hardware may provide operational status. Define what each status actually means and how recent it must be. Online is not the same as compliant, and Offline does not necessarily mean locally cached content is unavailable.

Printed QR and passive NFC material do not provide the same Device health signal. Recorded access can show that a route was used, but cannot continuously confirm material condition or location. Installation photos and periodic field checks remain useful alongside activity data.

Triage before sending a field visit

First check whether the location was expected to be live and whether Events are arriving against the correct identifier. Then review destination health, content version and any operational status available. Ask for a current fixture check when the cause remains physical or unclear.

Prioritise confirmed failures and higher-impact locations using the agreed service plan. Do not ask store colleagues to perform electrical or hardware work beyond their approved instructions. Escalate to the responsible installation or support Partner.

Keep a follow-up log

| Store and Touchpoint | Observed issue | Evidence checked | Assigned action and owner | Verification | | --- | --- | --- | --- | --- | | Enter location | State the precise signal | Status, test and current field evidence | Agree next action and due time | Record test result and closure time |

Keep the original observation and final diagnosis separate. After a fix, test the actual route or Device and confirm expected reporting. Closing a support ticket should not rely only on a return to non-zero counts.

Use findings to improve the rollout

Review repeated causes such as unclear prompts, mapping errors, difficult mounting or incomplete colleague briefing. Correct the system that created the issue, then update installation guidance and test a representative location before wider changes.

Store investigation checklist

• Planned live date and reporting scope confirmed
• Exact low-activity or communication observation recorded
• Tracking, destination and content version checked
• Physical and trading context reviewed
• Action assigned to the appropriate operational owner
• Fix verified and recurring causes fed into rollout improvements

Connect reporting with operational follow-up

MyPlayer can bring Interaction reporting into the Deployment discussion. Agree available Device signals, field responsibilities and escalation requirements for your actual store estate. Discuss your store monitoring plan.