Essendant's 310 Remote Workers Just Got a Warehouse Address

On Aug 20, 2026, TheStreet confirmed that Essendant's Lincolnshire, IL WARN filing bundles 200 on-site workers with 310 remote employees who report into that facility, for 510 job losses effective Oct 3. That single filing is the problem: if you're one of the 310 remote analysts, buyers, marketers, or IT staff, your next resume, LinkedIn, and every ATS-parsed application now inherits a warehouse-adjacent address at 200 Tri-State International Parkway unless you rewrite three specific lines first.

Why a WARN filing quietly rewrites your resume

A WARN notice is a public, employer-of-record document, and recruiters, layoff trackers, and background-check databases will treat every name on it as tied to the "facility" address, even if you've never set foot there. The Lincolnshire filing was structured as one event covering 510 people, so the framing that reaches recruiters is "warehouse closure," not "corporate HQ knowledge-work restructuring."

Two mechanics compound the damage:

• Layoff trackers propagate the framing. WARNTracker.com and Layoffs.fyi will list all 510 names under a single facility line item. A recruiter Googling "Essendant layoff" during outreach sees warehouse-closure headlines first.
• ATS parsers store the employer's address as structured data. When you paste "Essendant, Lincolnshire, IL" into the work experience field, an applicant tracking system (a database that extracts, indexes, and ranks resume content for recruiters) treats Lincolnshire as your employer geography and, downstream, as a proxy for your own.

The Essendant HQ at 200 Tri-State International Parkway is a suburban office park, not a warehouse. But WARN language calls it a "facility," and 60.8% of the Lincolnshire filing (310 of 510) is remote knowledge workers who will now share a postal code with distribution-center titles in every recruiter search that filters by employer plus location.

The numbers behind the mislabeling risk

Here's the population getting misclassified, drawn from Illinois WARN records, TheStreet's reporting, and Refolk's index of professional profiles.

The Refolk index number is the one to sit with. A keyword search for "Essendant remote" across US profiles returns effectively one clean match, because remote Essendant employees self-identify by function (Account Manager, Buyer, Category Analyst) rather than by work arrangement. That invisibility flips against them the moment recruiters filter by "Lincolnshire, IL" plus "Essendant" and pull warehouse-adjacent titles into the same result set.

The three lines you have to rewrite before Oct 3

Fix three specific fields: the header location, the employer line, and the LinkedIn location. Get all three right and you decouple yourself from the Lincolnshire facility address without lying about who signed your paycheck.

1. The header: your metro, not Essendant's

Put your actual metro in the resume header. Not "Remote." Not Lincolnshire. Your real city and state.

"Remote" is not a location an ATS can rank. Employers need your city, state, and country for tax, time zone, and legal reasons, and the parser stores that field for distance scoring. If you're a former Essendant analyst in Austin, your header should read "Austin, TX." If Charlotte, "Charlotte, NC." This is the field the ATS uses when a recruiter sets a radius filter, which 43.4% of them do.

If you list only "Remote" in the header, two things break at once:

1. You fail the distance ranking algorithm for any role tagged to a specific metro.
2. You lose the only signal that distinguishes you from a Lincolnshire warehouse worker with the same employer line.

2. The employer line: "Essendant (Lincolnshire, IL HQ) Remote"

In work experience, list the employer's city with "(Remote)" next to it, and explicitly mark Lincolnshire as HQ.

The wrong format is "Essendant, Lincolnshire, IL." That reads to a parser as your employer geography and, given the WARN filing, associates you with the facility closure. The right format is:

• Essendant (Lincolnshire, IL HQ), Remote
  Senior Category Analyst, Jan 2022 to Present
  Charlotte, NC

The "HQ" token matters. It tells the parser (and the recruiter skimming) that Lincolnshire is the corporate address, not your work location. Then "Remote" carries the work arrangement, and your header carries your actual metro. Three fields, three different jobs.

Rewriting this across five to eight past roles for every posting is tedious, which is exactly the work Refolk takes off you: paste the posting, get your own resume back rewritten for it, with the location fields tuned to that job's geography.

3. LinkedIn: change the location field this week

LinkedIn's location field feeds recruiter search filters directly, and it defaults to whatever you set years ago. If yours still reads "Greater Chicago Area" because you once commuted to Lincolnshire, change it to your real metro today.

LinkedIn Recruiter uses a location-plus-employer filter that will pull every ex-Essendant profile tagged to Chicago-area geography, warehouse and corporate alike, into the same result set. The ones who moved their location field to Austin, Charlotte, Denver, or wherever they actually live get sorted into knowledge-work searches instead.

Why "Remote" alone hurts you twice

Listing only "Remote" as your location fails ATS distance ranking and simultaneously removes the one signal that distinguishes you from displaced warehouse staff at the same employer. It is the worst of both worlds.

Location isn't just a filter field. It also functions as a keyword signal in ATS scoring. Including "New York" or "NYC" on a resume targeted at a New York role gives your overall score a slight boost because the system recognizes geographic alignment. Modern ATS platforms use weighted formulas that evaluate proximity to the job location alongside skill match, and candidates nearer to the job site rank higher even when their skill alignment is slightly weaker.

For a former Essendant remote worker in Austin who lists "Lincolnshire, IL" in the header, that mechanic double-punishes:

• Low distance score for Austin-based roles, because the parser thinks you're 1,100 miles away.
• Keyword contamination pulling you toward Chicago-metro warehouse postings, because "Lincolnshire" and "Illinois" match the employer geographies of every distribution-center opening in the region.

The Oct 3 deadline changes your resume math

Apply before Oct 3 and you can list "present" on your Essendant role, which avoids the employment-gap flag that ATS parsers weight negatively. Most of the disclosed terminations happen on or within two weeks after Oct 3, so the mechanical advantage of an unbroken employment line disappears the moment the WARN date hits.

Three tactics to run this week:

1. Front-load applications for roles you actually want while your resume still says "Present." A parser that sees a current role scores you higher on tenure continuity than one that sees a two-month gap.
2. Pre-write two versions of every experience bullet, one with "Present" and one with "Oct 2026." Swap them the day the WARN takes effect. Refolk's tailoring flow keeps both variants aligned to whichever posting you're applying to that day.
3. Skip the "Open to Work" green ring on LinkedIn until after Oct 3. It signals the layoff to recruiters, who will then pattern-match you to the WARN headline before reading your titles.

The sister-facility workers face the same problem

Every Essendant closure with remote reportees carries the same mislabeling risk. WARN records show actions affecting 192 employees in Georgia (Suwanee), 150 in Pennsylvania (Phoenixville), 136 in Texas (Irving), 53 in Arizona, and additional cuts at Carol Stream, IL (134 jobs), Sacramento, and Perris, CA. Any remote worker who reported into one of those facilities inherits the same warehouse-adjacent address unless they intervene.

If you were remote and reported into Suwanee, your employer line should read:

• Essendant (Suwanee, GA distribution center), Remote

The parenthetical is doing real work. It tells a recruiter the Georgia address is the reporting site, not your work location. Without it, an ATS in Atlanta will rank you against local warehouse titles.

What to change today: the checklist

1. Resume header: your real metro, not "Remote," not Lincolnshire.
2. Employer line: "Essendant (Lincolnshire, IL HQ), Remote" or the equivalent for your sister facility.
3. LinkedIn location: the metro you actually live in, updated this week.
4. LinkedIn About section: one sentence naming the function you did (Category Analyst, Buyer, Sales Ops) so keyword searches that skip "Essendant" still surface you.
5. Apply before Oct 3 to any role where you'd want to say "Present" in your current title.
6. Version-control your resume so the day the WARN hits, you can flip "Present" to "Oct 2026" across all copies at once.

The Essendant filing is going to shape how recruiters read every one of these 310 profiles for the next twelve months. The workers who rewrite three lines this week get sorted into the searches they want. The ones who don't get pulled into warehouse-adjacent result sets in every ATS that trusts the parsed employer address, which is roughly 75% of them.

FAQ

Should I list my Essendant role as "Remote" or with a city?

List both. The correct format is "Essendant (Lincolnshire, IL HQ), Remote" in the experience block, and your actual metro (Austin, Charlotte, Denver, wherever you live) in the resume header. Listing only "Remote" fails ATS distance ranking and removes the one signal that distinguishes you from Lincolnshire warehouse staff on the same WARN filing. Listing only "Lincolnshire, IL" geotags you to a metro you don't live in and pulls you into Chicago-area warehouse searches.

How do I keep recruiters from associating me with the warehouse closure headlines?

Change your LinkedIn location to your real metro this week, add the function (Analyst, Buyer, Category Manager, IT) to your headline, and use the "(HQ)" parenthetical on your Essendant employer line. A recruiter who filters by "Lincolnshire, IL" plus "Essendant" will still see you, but a recruiter searching for "Senior Category Analyst" in your actual metro will now surface your profile before the warehouse titles.

Does it matter that I apply before Oct 3, 2026?

Yes, mechanically. While you're still on payroll you can list "Present" on your Essendant role, which avoids the employment-gap flag ATS parsers weight negatively. Most terminations from the Lincolnshire filing hit on or within two weeks after Oct 3, so any application submitted before then benefits from an unbroken employment line. After Oct 3, you'll want to swap "Present" for "Oct 2026" across every version of your resume.

What if I reported into a sister facility like Suwanee, Irving, or Phoenixville?

Same fix, different address. Use "Essendant (Suwanee, GA distribution center), Remote" or "Essendant (Irving, TX facility), Remote." The parenthetical marks the reporting site as the employer's geography, not yours. Every one of the six-state closures (192 in Georgia, 150 in Pennsylvania, 136 in Texas, 53 in Arizona, plus California and Illinois) creates the same mislabeling risk for remote reportees, and the fix scales the same way.