Skip to content
JehBuilds
Writing
By MD Jehad H.··4 min read·Field note

Plan for an order processing outage before it happens

Drafted through my n8n + AI pipeline, edited by me.

Boston Scientific spent this week unable to process or ship customer orders after a cyberattack cut off access to core business systems. The company has not said whether data was stolen or whether ransomware was involved, only that shares fell more than 5 percent while it worked with outside investigators and gave no timeline for restoring full operations. If a global medical device maker can lose its order pipeline overnight, a small operations team running the same functions through one platform can lose it just as fast.

What happened

On August 25, Boston Scientific disclosed a cyberattack that disrupted its IT network and blocked access to the systems it uses to process and ship customer orders. The company activated its incident response plan and brought in outside cybersecurity firms, but as of this week it still could not say how long full restoration would take or whether the incident would materially affect the business. That is the detail worth sitting with: a company with dedicated security staff and enterprise tooling did not have a fast answer ready.

Why an order processing outage matters for a five-person shop too

Most small service and product businesses run order intake, invoicing, and fulfillment through one connected stack: a form, a CRM, a payment processor, maybe an automation tool stitching them together. That setup runs fine until the platform goes down, gets suspended, or gets hit the way Boston Scientific was this week. What actually protects you at that point is whether anyone on the team knows the manual workaround, not how good the automation was beforehand.

Build the fallback before you need it

  1. 1

    Write down the manual path

    For each system that touches an order, from intake to payment to fulfillment, write one paragraph on how to do that step by hand: a phone number, a paper form, a manual invoice template.

  2. 2

    Pick the messenger in advance

    Decide now who tells customers there is a delay and what that message says. A template saved in a shared doc beats composing one while the phone is ringing.

  3. 3

    Name one person who can call it

    Someone needs the authority to say the team is switching to manual mode without waiting for a meeting. Put their name on the plan.

  4. 4

    Test it once a year

    Run a fifteen-minute drill: pretend the main system is down and walk through the paper version. Most gaps show up on the first attempt, not the fifth.

Comparison of an order pipeline with no fallback plan against one with a written fallback plan

  • One system runs intake, invoicing, and shipping
  • No written manual workaround
  • Customers hear nothing until someone remembers to reach out
Boston Scientific's outage began August 25 with no restoration timeline given days later. A written fallback plan is what closes that same gap for a small team.

Bookmark the status page

If your automation platform or payment processor publishes a status page, save the link somewhere your team can find it fast. Knowing within minutes whether the outage is on your end or theirs stops you from troubleshooting the wrong thing.

Does this apply if I only use one tool, like just Shopify or just QuickBooks?

Yes. A single-tool outage is the same failure, just with fewer moving parts to explain to a customer.

How long should a manual fallback plan take to write?

Under an hour for most small operations. The value comes from having something written down before the day you need it, not from how polished it reads.

None of this requires new software, just an hour spent asking where your order pipeline has a single point of failure. If you want a second set of eyes on that question for your own workflow, that is a conversation worth having before an outage forces it.

Building something this should run inside?

Book a systems call

Keep reading