Supply chain resilience becomes real when an operator must decide what to isolate, who can authorize a replacement and how quickly goods can move through another channel. Two recent examples illustrate the distinction. Chipotle removed some jalapeños as a precaution in response to salmonella concerns, demonstrating a product-risk response. Separately, the Port of Virginia added a CSX rail service to Indianapolis, expanding transportation options between the port and an inland market.

These events involve different hazards, but they point to one operating principle: resilience requires pre-approved alternatives connected to clear activation triggers. A spreadsheet listing suppliers or routes is not enough. Teams need traceability, decision rights, tested procedures and measurements that show whether recovery is improving.

Separate product risk from transportation risk

Product incidents and transportation disruptions should not share one generic playbook. Product risk can require immediate isolation because continued use or distribution may widen exposure. Transportation risk usually concerns delay, capacity, cost or loss of service, so the response may be to reroute future freight while monitoring cargo already in transit.

For product risk, operators need to answer: Which lots are potentially affected? Where are they now? Which finished products or sites received them? Can inventory be electronically blocked before physical segregation is complete? Who decides whether stock stays quarantined, is returned or is otherwise dispositioned?

For transportation risk, the key questions differ: Which shipments and customer commitments are exposed? Is the disruption local, corridor-wide or carrier-specific? What capacity is available through another route or mode? How will a change affect transit time, handling, inventory and total landed cost?

Keep separate triggers and response trees, then connect them through a common incident-management structure. Both need an incident owner, a timestamped decision log, defined escalation authority and criteria for returning to normal operations.

Build lot-level traceability and rapid isolation

Chipotle’s precautionary removal of some jalapeños shows why operators must be able to act on a defined product scope rather than treating all inventory as interchangeable. The source reports the removal in connection with salmonella concerns; it should not be interpreted as proof that every jalapeño, supplier or location was affected.

Lot-level records should connect each receipt to the supplier, production or harvest identifier when available, purchase order, receipt date, storage location and subsequent transfers. If an ingredient enters a finished product, the relationship between input lots and output batches should also be searchable. Barcode scanning helps, but disciplined transaction records matter more than the label technology itself.

Create an isolation sequence that operators can execute without waiting for an improvised meeting:

1. Record the alert, its source and the product identifiers provided.
2. Place a system hold on matching or potentially matching inventory.
3. Identify every site, transfer and downstream use associated with those lots.
4. Physically segregate stock and verify quantities against system records.
5. Escalate gaps, including missing codes or inventory that cannot be located.
6. Document the authorized disposition and the evidence supporting release or removal.

The principal metric is time to identify affected lots, measured from receipt of an actionable alert to a verified location list. Also track time to system hold, percentage of units accounted for and reconciliation variance. A fast search with poor inventory accuracy is not a resilient outcome.

Pre-approve alternate suppliers before an incident

A backup supplier is useful only if the company can order an acceptable product from it under pressure. Approval should cover specifications, quality requirements, traceability fields, capacity, lead time, commercial terms and onboarding into purchasing and payment systems. For regulated or safety-sensitive products, the relevant internal specialists must define the required validation rather than allowing urgency to bypass controls.

Set activation triggers in advance. Examples include a formal supplier notification, inability to identify affected lots within the internal deadline, a projected stockout before replacement arrives, or failure of the incumbent supplier to provide required documentation. Assign authority by impact: a site manager might transfer approved stock between locations, while procurement or a designated incident leader activates another supplier.

Measure supplier concentration as the share of spend or critical volume supplied by the largest source, and examine it by item rather than only by supplier. Track replacement lead time from activation to usable receipt, alternate-supplier capacity confirmed within a defined window and the percentage of critical items with a currently approved second source. Review these measures alongside inventory coverage, because an alternate with a long lead time may not protect a low-stock operation.

Diversify routes as deliberately as suppliers

The new Virginia-to-Indianapolis rail service illustrates how an additional transport connection can broaden the set of available paths between a port and an inland destination. Operators should treat such services as potential options, not automatic solutions. Suitability depends on origin and destination, schedules, available capacity, drayage, terminal cutoffs, handling requirements, transit variability and cost.

Map each critical lane from origin through ports, terminals, carriers and inland nodes. Identify shared dependencies: two nominally different routes may still use the same port, rail ramp, bridge or final-mile provider. Route concentration should therefore measure not just carrier share, but the proportion of volume dependent on a corridor or node.

Define rerouting triggers such as a closure, repeated missed departures, capacity withdrawal or projected arrival beyond the customer’s tolerance. The transport response should specify which open bookings can be changed, how in-transit freight will be handled and who may approve cost premiums. Track reroute decision time, replacement capacity secured, on-time delivery during the incident and recovery time from disruption recognition to stable service.

What most people miss

Alternatives can exist on paper while remaining unusable. Supplier records expire, packaging differs, purchase orders are not configured, rail schedules do not match order cycles, and decision-makers hesitate because nobody owns the cost trade-off. Resilience therefore needs rehearsals. Run a traceability drill using a real lot, request a current capacity confirmation from an alternate supplier, and price a representative shipment over an alternate route. Record every manual workaround uncovered.

Incident documentation should capture alert time, facts known, assumptions, affected lots or shipments, decisions, approvers, communications, costs and closure criteria. After recovery, compare actual performance with thresholds and assign corrective actions. This turns disruption history into operating knowledge rather than a collection of emails.

Practical resilience checklist

• Map critical products to lots, suppliers, locations and downstream uses.
• Test how quickly teams can identify, block and physically isolate affected inventory.
• Keep product-risk triggers separate from transportation-risk triggers.
• Approve alternate suppliers before they are needed, including specifications and ordering setup.
• Measure replacement lead time and supplier concentration for each critical item.
• Map route dependencies across carriers, ports, terminals, corridors and final-mile providers.
• Measure route concentration and maintain at least one evaluated alternative for critical lanes.
• Define who may quarantine inventory, activate suppliers, reroute freight and approve premiums.
• Track time to identify affected lots, reroute decision time and total recovery time.
• Maintain a timestamped incident log with evidence, approvals, communications and closure criteria.
• Run periodic drills and close the gaps they reveal.