Dark Screens, Live Orders: Digital Continuity for Scotland’s Automated Warehouses

A Scottish warehouse can now process an order, route a tote, print a label, update a supplier portal and reconcile stock without a single manual keystroke. That is the promise of the modern distribution centre. It is also the source of a quieter, less visible vulnerability. When the conveyor stops because a control system has been locked, or the handheld scanners lose their session, the problem is no longer confined to the IT department. It becomes a goods-out problem, a customer-service problem and, before long, a contractual problem.

Cyber resilience in warehousing is often framed as a technical control set: firewalls, endpoint protection, patching. Those matter. But for an operator, the more useful frame is digital continuity: the ability to keep goods moving, even in degraded mode, while systems are restored. The following audit framework is designed for site leadership teams rather than security specialists. It treats cyber risk as an operational dependency to be understood, rehearsed and evidenced.

Start With the Dependency Map, Not the Firewall

Most sites know their WMS. Fewer have mapped everything the WMS touches. Begin with a physical walk-through and a simple question at each station: what happens here if the screen freezes for four hours? The list usually extends well beyond the warehouse management platform. Handheld scanners, label printers, conveyor PLCs, sortation controls, automated storage and retrieval units, weighbridges, temperature monitoring, yard management, access control, CCTV and building management systems all have a role in the flow of goods. So do supplier-linked inventory portals and electronic data interchange channels.

For each dependency, record three things: the process it supports, the maximum tolerable outage before customer promises are breached, and the manual workaround, if one exists. Rate each dependency red, amber or green. A red item is one where a two-hour outage halts despatch with no tested alternative. That map, not an asset register, should drive the resilience plan. It also gives the board a language it understands: not vulnerabilities, but hours of lost throughput.

The Third-Party Keyring

Automated warehouses are rarely self-contained. Integrators, software vendors, maintenance providers, managed service providers and group IT teams all hold some form of access. In multi-let Scottish industrial estates, shared network infrastructure and building services can add another layer of dependence. The audit should produce a current access register: who can connect, from where, using which credentials, and under what supervision.

Look for dormant accounts, shared passwords and remote maintenance links that bypass normal change control. Multi-factor authentication should be standard for remote access, and least-privilege principles should apply to vendor engineers as rigorously as to permanent staff. Contracts deserve scrutiny too. Does the supplier commit to notifying the site of a security incident within a defined window? Are data return and deletion obligations clear at exit? Can the operator audit the supplier's controls, or at least obtain independent assurance? A keyring with too many unlabelled keys is a continuity risk long before it becomes a breach.

Rehearse the Manual Warehouse

Many sites have a business continuity plan that assumes people will revert to paper. Very few have tested whether the paper process actually works at volume. Manual fallback is a skill, not a document. It requires pre-printed pick lists or a standalone template, label printing that does not depend on the WMS, agreed stock-count methods, radio or telephone communication protocols, and shift managers who know when to switch modes.

Run the exercise at a deliberately quiet period first. Time how long it takes to pick, pack and despatch a representative order set without system prompts. Identify where staff improvise and where improvisation creates reconciliation problems later. Then repeat the exercise with a supervisor who has not designed the fallback. The objective is not to prove that manual working is as good as automation. It is to establish a credible degraded mode, with defined cut-off points and a clear reconciliation routine for when systems return. Digital downtime should be a competency, not an emergency.

Reporting, Evidence and the Insurer’s Question

The UK regulatory backdrop is well established. The National Cyber Security Centre provides incident response guidance, and the Information Commissioner's Office expects personal data breaches to be reported within 72 hours where the threshold is met. Warehouse operators should also consider Cyber Essentials as a baseline assurance scheme for public-sector and larger commercial contracts. But the operational test is evidence. Can the site produce a timeline of system events, access logs and decisions taken during an incident? Forensic readiness is not only for investigators. It supports insurance claims, customer assurances and post-incident learning.

Insurance expectations deserve early review. Cyber cover and business interruption policies can carry notification conditions, waiting periods and exclusions that surprise operators after an event. The audit should confirm what the policy expects in terms of incident notification, whether physical damage from a cyber event is covered, and how lost throughput is calculated. Do not assume that a standard property policy responds to a ransomware-driven conveyor stoppage. Ask the broker a direct question and record the answer.

A Recovery Plan That Moves Goods

Recovery plans often focus on restoring servers. Warehouse operators need a plan that sequences the restart of physical flows. Define recovery time objectives for each critical system and recovery point objectives for stock data. Identify the minimum system set required to despatch safely, and the order in which conveyors, scanners and label printing should return. Build in a data reconciliation step before automated picking resumes, and a priority order list agreed with commercial teams.

Keep spare handhelds, label stock and offline licences available. Confirm whether the site can operate from an alternate location or a sister depot for a defined period. Then test the plan through a tabletop exercise at least twice a year, with shift managers, IT, suppliers and a representative from customer service. The output should be a list of corrections, not a certificate of completion.

The Board-Level Test

Digital continuity belongs on the same agenda as health and safety, labour planning and capacity utilisation. It needs a named owner, a budget line and a small set of metrics: dependency coverage, fallback test frequency, supplier assurance status, incident reporting times and open recovery actions. Automation does not remove operational risk. It relocates it to the places where goods, data and third parties meet. Scottish warehouses that map those places now will be the ones that keep despatching when the screens go dark.