How a Recent Court Decision Put Supply Chain Managers on the Hook - The Case That Shifted the Risk

On February 20, 2026, a U.S. federal appeals court issued a decision that did not make front-page news outside legal and compliance circles. There were no dramatic headlines, no immediate market reaction. But inside procurement teams, compliance functions, and supply chain leadership groups, it landed differently.

The case involved Rubicon Resources, a U.S.-based seafood distributor. The facts went back more than a decade, to processing facilities in Thailand that relied on migrant workers from Cambodia. Workers had been recruited with promises of wages and housing. According to the lawsuit, what followed included withheld pay, confiscated passports, coercion, and punishment for those who tried to leave.

Rubicon did not own the factories. It did not employ the workers. It was not present on the production line. It was, in the language companies use every day, a commercial partner in a global supply chain.

That distance used to matter.

Signals that did not go away

Inside the company, there were signals. Employees had visited the facilities. A major retailer rejected shipments after raising concerns about labor conditions. A media report describing forced labor circulated internally among managers. For a short period, sales were paused. Then business resumed.

At the time, those decisions may have felt operational. Temporary disruption, commercial pressure, uncertainty about the facts. The kind of trade-offs that happen every day in supply chains.

Years later, they became evidence.

The plaintiffs brought the case under the U.S. Trafficking Victims Protection Reauthorization Act. A lower court dismissed it. The reasoning was straightforward. There was no proof that Rubicon had actually profited from forced labor. No completed gain, no liability.

The appeals court disagreed.

When “trying to benefit” becomes enough

In its February 2026 ruling, the Ninth Circuit made a point that is already being repeated in boardrooms and legal briefings. Under amendments to the law, it is enough that a company sought to benefit. Actual profit is no longer required. Attempt is sufficient.

The court went further. A company does not need to run a factory to be considered part of the violation. Continuing a business relationship after receiving credible information can qualify. Knowledge does not have to be absolute. It can be inferred from what was seen, what was reported, and what circulated inside the organization.

The visits. The rejected shipments. The internal emails sharing a news article. Together, they formed a picture of what the company knew, or should have known.

That phrase, “should have known,” carries weight. It does not require intent. It does not require a signed admission. It sits in the space where most operational decisions are made. Between uncertainty and action.

What counts as credible information? When does a concern become knowledge?

The quiet shift to personal exposure

For someone working in supply chain management, the details feel familiar. Supplier visits are routine. Risk reports arrive in inboxes. Articles get forwarded. Issues are flagged, discussed, sometimes downgraded. Decisions are made to continue, to monitor, to reassess later.

In this case, those ordinary moments did not disappear with time. They accumulated.

The court’s decision does not say that every manager is liable. It does not name individuals. But it redraws the line around responsibility. The distance between a decision made at a desk and conditions on a factory floor is no longer as wide as it once seemed.

What makes the ruling unsettling is not the severity of the allegations. It is the ordinariness of the decision points. Nothing in the record suggests a single dramatic moment where everything was clear. Instead, there were signals. Enough to raise questions. Not enough, perhaps, to force immediate action. Until, years later, they were enough for a court.

The timing matters. The decision does not stand alone. In Germany, supply chain due diligence laws impose obligations that reach into management responsibility. In Canada, reporting requirements come with personal exposure for directors and officers who approve or fail to prevent non-compliance. Across jurisdictions, the expectation is shifting from policy statements to demonstrable action.

Where the line now sits

For a supply chain manager reading the Rubicon decision, the question is not abstract. It is immediate. What counts as credible information? When does a concern become knowledge? At what point does continuing a relationship stop being a commercial choice and start becoming a legal risk?

There is no single answer in the ruling. That is part of what gives it force.

It leaves space. Space where judgment operates. Where decisions are made with incomplete information. Where pressure to deliver meets signals that are not yet definitive.

And in that space, the margin for error appears smaller than it did before.

The case now returns to the lower court. It is not yet a final judgment on liability. But the message is already clear enough to travel.

A visit, a report, a rejected shipment, an article shared internally. None of these, on their own, seem decisive. Together, they can become something else.

Something that does not stay inside the supply chain.