Store Networks
Part of Retail store networks
Preparing backup connectivity for critical store devices
Prioritise store tasks, check shared dependencies and rehearse failover and recovery for critical retail devices.
Prepare backup connectivity by identifying tasks that must continue, tracing each task's devices and services, and checking what happens when the primary connection fails. A second internet link helps only while the necessary local equipment, power and remote service also work.
Choose the minimum service
Ask the store manager, payments team and support team which tasks cannot wait. For each, record the connection path and the authorised response if the task fails.
| Task | Dependencies and decision to check |
|---|---|
| Card payment | Confirm the terminal's connection options and any offline permissions, limits and reconciliation steps with the acquirer. |
| Stock lookup | Check the handheld, store Wi-Fi, internet route and application; decide whether another approved lookup is available. |
| Collection handoff | Check the order view and parcel record; decide how staff verify current status before releasing goods. |
Check the backup path
Options can include another fixed connection, a cellular gateway or a terminal with its own supported mobile connection. Australian government outage guidance recommends considering different providers or connection types where practical and warns that no communications technology is completely resilient. Check signal at the installed location, expected capacity, data arrangements and provider support.
Trace shared dependencies: a cellular gateway still needs power and a path to the devices it serves. Two fixed links may share an entry point or upstream infrastructure.
Decide which tasks receive priority if the backup has less capacity, and which tasks should pause.
Do not assume offline card acceptance is available. CommBank's guidance, for example, describes floor limits for offline transactions on its terminals; transactions above a merchant's limit can be declined. That is a limit of the described service, not a rule for every Australian terminal. Ask the retailer's acquirer about the exact devices, permissions, limits, liability and reconciliation process before issuing payment instructions.
Check failover and recovery separately
Arrange a controlled exercise with the provider and store team. Confirm the backup path, interrupt the approved primary path and attempt a representative task on each critical device. Record whether a new task succeeds and what happens to an interrupted one. Restore the primary path, then check for missing or repeated work.
Gateway behaviour varies. Cisco Meraki documents uplink monitoring and tests used to determine uplink status, as well as switching back to the preferred primary uplink when it returns. Those details cannot predict another gateway or payment application's behaviour. Record the proposed equipment's settings and the observed result before relying on the backup path.
Give staff an outage procedure
Keep a short procedure available during an internet failure: who confirms the incident, which tasks may continue, how staff handle an uncertain transaction, how to reach support and what must be reconciled after restoration. Keep key contacts accessible through another route. Review the procedure after changes to devices, providers, payment arrangements or the store layout.
