When Can the Business Run Again?

November 4, 2026

From OpenNova.

A system can be available while the business still cannot complete the customer transaction that depends on it.

Recent cybersecurity incidents affecting companies in our network have brought this issue closer to us. We’re not involved in their incident response efforts, but TAKKT’s public recovery update provides a concrete example.

What TAKKT disclosed

TAKKT, a German distributor of business equipment, identified a cyberattack on October 19. In its October 28 update it said the attack had been contained and secure recovery was underway. Most of its webshops and its communication channels remained available and were being used to take orders, while order processing, deliveries and invoicing were restricted.

On the earnings call the same day, the CEO said the ERP systems supporting the affected divisions were directly affected, that additional infrastructure had been taken offline as a precaution, and that some of the restrictions reflected the company’s own decision to restore cautiously. Teams used manual processes for selected orders, including some larger ones, while management prioritized the accumulated backlog by size, urgency and importance to customers, with particular attention to its largest and most profitable business.

Our reading

The detail that interests us is the relationship between system availability and what the business can actually complete. TAKKT described restrictions caused by the incident, additional infrastructure taken offline as a precaution, and manual processes that allowed selected orders to move.

Those conditions create different operating limits. A system taken offline for protection still affects the activities that depend on it. A manual workaround may allow an order to be fulfilled before the usual system is restored. Knowing which systems are available therefore needs to be connected to what each business activity requires and which alternatives are usable.

TAKKT’s manual processing illustrates why this is not simply a choice between operating and being shut down. Some orders could be fulfilled while normal processing remained constrained. Management described how it was prioritizing the backlog within those limits.

That is the question these incidents have brought closer to us: how clearly can leadership connect the condition of its technology to the commitments the business can still meet?

The question

If a critical system became unavailable tomorrow, would your leadership team know which business operations would stop, which would continue, and where workarounds could help?

If you are working through a decision other technology leaders could learn from, we’d like to hear it. A sentence or two is plenty: hello@opennova.com. We’ll ask before publishing anything you share.

The Pulse comes out every other Thursday, with the enterprise technology developments we think are worth your attention. Get The Pulse.