Skip to content
    Operational Strategy

    How to plan around a factory shutdown at origin

    Oct 1, 20266 min read

    A factory shutdown at origin is the one disruption you can see coming a year out. Here is how to run the six weeks around it without losing the thread.

    Golden Week started this morning. For the next seven days a large share of the factories feeding North American and European production lines are closed, and the people who normally answer questions about order status are not at their desks. Every planner has that week blocked out. What is not blocked out is the state those orders were already in when the lights went off. Vessels have been waiting up to twelve days for a berth at Shanghai and Ningbo, and Typhoon Saudel suspended operations at Ningbo for a cumulative 78 hours in the week before the holiday, with more than 800 commercial vessels anchored offshore while it passed.

    So the shutdown is not starting from a clean baseline this year. It is starting on top of a backlog.

    A shutdown is four phases, not one date

    The mistake is treating a known closure as a single entry in a calendar. It is a cycle that runs for roughly six weeks: the rush before the gates close, the silence while they are shut, the restart that does not restore your schedule, and the arrival wave that lands weeks later in your own yard. Each phase breaks a different part of your operation, and each one needs a different thing from your data.

    Teams that lose a week to Golden Week or Lunar New Year almost never lose it during the holiday itself. They lose it in the handover between phases, when an assumption made in week one is still being quoted to a customer in week five.

    Phase one: the pre-close rush hides which orders actually made it

    In the fortnight before a shutdown, suppliers push to ship everything they can. Volume spikes, advance shipping notices arrive in batches, and booking confirmations pile up faster than anyone can check them. The same rush happens ahead of a weather closure, on a clock of hours rather than weeks: handling a port closure at origin covers what to hold back when the exit is what stops rather than production. The problem is that a booking is a statement of intent. It is not an event. A purchase order can be confirmed, invoiced, and listed as shipped while the cargo is still sitting at the supplier's dock waiting for a truck that was never going to come before the gates closed.

    This is the single highest-value question of the whole cycle, and it has a narrow window: which orders genuinely got gated in, and which ones are only shipped on paper? Answered in week one, it is a supplier conversation. Answered in week five, it is a stockout. The practical test is whether you can tie each open order to a physical event at origin rather than a document, which is the same discipline that makes tracking cargo before it leaves origin worth setting up in the first place.

    Phase two: the silence window is where visibility quietly breaks

    Once the factory closes, the usual way of finding things out stops working. There is nobody to email. The forwarder's origin desk is running a skeleton team. What most teams do is wait, and waiting is where the week goes.

    Cargo does not stop generating events just because the supplier is on holiday. Containers still gate in, vessels still berth, carriers still publish status changes, and customs still clears entries. The signal is there. It is scattered across carrier portals, forwarder emails, and terminal systems, in a dozen formats, with nobody normalizing it into something a planner can read. Across the industry, 62% of supply chain exceptions are detected only after they have already affected a customer, and a holiday week is exactly the condition that produces that number: the events kept arriving, and nobody was reading them.

    A command center like Orkestra is built for precisely this gap. It keeps pulling and normalizing carrier, forwarder, and terminal events across every connected system while your origin team is dark, so the week comes back with a current picture rather than a mailbox to work through. The work that matters during a shutdown is not chasing. It is noticing.

    Phase three: the restart does not restore your schedule

    The gates reopen and everyone assumes the plan resumes. It does not. Carriers spend the quiet period rebalancing their networks, which means blank sailings and port omissions on the services you were counting on. Maersk has already published Asia to Europe blank sailings covering a Ningbo departure on 8 October and a Shanghai departure on 10 October. Cargo booked on an omitted call does not fail loudly. It gets rolled to the next vessel, and the first anyone hears about it is often a revised ETA with no explanation attached.

    Restart week is also when ETA quality is at its worst, because carrier schedules are being rewritten faster than downstream systems absorb them. If your customer promises are built on an ETA that nobody has re-baselined since September, they are wrong and you do not know by how much. Two habits carry teams through it: treating a schedule change as an exception to be worked rather than a notification to be filed, which is the heart of catching blank sailings and port omissions early, and holding your carriers to a measured standard on ETA accuracy rather than a stated one.

    This is the phase where exception management earns its place. Orkestra detects the rollover as the event lands, prices the impact against the orders and customers actually behind that container, and routes it to someone with a decision to make. OIA Global cut exception resolution time by 60% in a single quarter working this way, and the gain is largest exactly when the volume of exceptions spikes.

    Phase four: the backlog lands all at once, inland

    Six to eight weeks after the gates reopen, everything that shipped in the rush arrives in a cluster. Transpacific pressure this year has been shifting away from ocean rates and toward inland costs, which is where that cluster does its damage. Drayage capacity, chassis availability, warehouse receiving labor, and free time on equipment all get consumed at once by a wave that was entirely predictable in September.

    The avoidable cost here is almost always concentrated in a small number of containers, and it is a clock problem rather than a visibility problem. Free time starts at a known moment. Appointment windows at the inland terminal are bookable in advance. Teams that track those as live countdowns tend to find that most of their demurrage and detention came from a handful of boxes that nobody was watching, not from a general failure. When the arrival wave does hit and several hundred shipments need attention in the same week, the constraint stops being information and becomes sequencing, which is a different skill: knowing how to prioritize exceptions when everything is late at once.

    What to set up before the next one

    Lunar New Year is the next closure, and the work to prepare for it is unglamorous and short.

    Pick the phase you handled worst this time and instrument it. Write down, now, which orders you believe shipped before the gates closed, and check that list against gate-in events in three weeks. Put a countdown on free time for every container arriving in the backlog window instead of reading it off an invoice afterwards. Agree internally on who owns a rolled booking so the decision does not wait for a meeting. And make sure one person can answer "what moved and what did not" from one screen, rather than from four portals and a forwarder call.

    A shutdown is the fairest test a supply chain gets, because nothing about it is a surprise. The dates are published a year ahead. The behavior of suppliers and carriers around those dates repeats every single cycle. What varies is whether your team spends the restart reconstructing what happened or acting on it, and that comes down to whether the events kept landing somewhere useful while the lights were off. That is the job Orkestra was built to do: one normalized view across carriers, forwarders, and your own systems, exceptions ranked by what they actually hold up, and a record that stays current through the weeks when nobody is there to maintain it.

    Get full visibility across your origin network

    Trusted by leading supply chain teams
    MatalcoOIA GlobalKingsdownDBWMatalcoOIA GlobalKingsdownDBW
    DLAIllyLevitt SafetySquareInstoreDLAIllyLevitt SafetySquareInstore
    TAKE THE NEXT STEP

    Action breaks down when operations are disconnected.

    Orkestra gives teams one place to see what matters, coordinate the response, and move operations forward.