DEV Community

Layoff Atlas
Layoff Atlas

Posted on Originally published at layoffatlas.com

Starbucks' 18-Worker Philadelphia WARN Filing, Effective December 6, 2026, Explained

Starbucks' 18-Worker Philadelphia WARN Filing, Effective December 6, 2026, Explained

A newly imported record in the Layoff Atlas registry lists 18 Starbucks workers in Philadelphia, Pennsylvania, with an effective date of December 6, 2026. No notice date is published for the record, which arrived in the registry's recent undated imports. It is a small filing, but small filings are part of how the layoff picture gets built — and this one says as much about Pennsylvania's data as it does about one employer.

What the filing shows

The record is straightforward about what it contains and silent about the rest. It lists:

  • Employer: Starbucks
  • Location: Philadelphia, Pennsylvania
  • Workers: 18
  • Effective date: December 6, 2026
  • Notice date: unavailable

That last line matters. The registry's 90-day notice window only counts records with published notice dates, so undated records like this one appear separately, under recently imported notices. The filing is in the registry; what is missing is the paper trail that would normally accompany it — the date the notice was filed and the state publication that carried it.

Why an 18-worker record appears at all

Federal WARN thresholds are far above 18 workers at a single site: generally 100 or more full-time employees, or 50 to 499 where at least a third of the workforce is affected. A single 18-worker record does not, on its own, describe a federal WARN trigger. Records like this one reach the registry through attributed secondary sources rather than a direct official feed, and the registry preserves them because small records still carry information — about an employer's footprint, about a city, and about how layoff data accumulates outside the official pipeline.

Pennsylvania is a case in point. The state's page in the registry holds 1,901 notices covering 256,522 workers, but its official feed is not currently syncing new filings: the newest official notice date is March 18, 2025, and the archive contains zero eligible official filings from the last 365 days. Of the 1,901 Pennsylvania records, 245 are direct government records and 1,656 are attributed secondary records. In a state where the official pipeline has gone quiet, secondary records like the Starbucks Philadelphia filing are often the only fresh signal available.

The Pennsylvania picture

Pennsylvania's 2026 filings so far total 78 notices covering 12,181 workers. The state has 11 notices with future effective dates, and 80 notices in the archive carry no worker count at all. The Starbucks filing joins a December calendar in the state that already includes larger closures, such as the 96-worker Ask Foods closure in Palmyra effective December 1 and the 80-worker Pavilion at Bradford closure effective on or before December 1.

It is also worth separating this filing from the other Starbucks record in the registry. A separate 135-worker Starbucks closure filing in SeaTac, Washington, carries a notice date of October 23, 2026, and an effective date of December 31, 2026. Same employer, different site, different state, different scale — the registry treats them as distinct records, and readers should too.

The national picture

Nationally, the registry's 90-day window currently holds 679 notices covering 65,527 reported workers, with 33 counts unavailable. Washington leads the state ranking at 17,073 workers, followed by California at 14,001, Illinois at 4,626, Texas at 3,652, and Ohio at 3,180.

The upcoming calendar remains heavy. The registry's week-by-week effective-date totals are 5,503 workers for the week of October 26; 5,061 for November 2; 6,568 for November 9; 6,145 for November 16; 6,120 for November 23; and 5,592 for November 30. The Philadelphia filing's December 6 effective date falls just beyond that six-week stretch, in a December calendar that is still filling in.

How to read a record like this

Three cautions apply. First, these are reported plans, not confirmed job losses — a filing describes what an employer has reported, and plans can change, shrink, or be withdrawn. Second, worker totals exclude unavailable counts, so any total built from these records understates the full picture wherever counts are missing. Third, an undated record should be read as a lead, not a conclusion: without a notice date, the timing of the employer's decision and the notice period workers received cannot be verified from the registry alone.

For workers, the practical step is the same regardless of a filing's size: confirm whether a notice names your site, check the effective date, and contact the state's Rapid Response team for help with benefits, retraining, and job search. Small filings do not come with smaller consequences for the people named in them.

Data source: Layoff Atlas

Top comments (0)