Safety Incidents OSHA Severe Injury Reports · 2015–2025
2,098,129Injury reports 132,232Establishments Most recent incident 2025-12-31

Rochester Hills, MI —

OSHA Injury Report: Trader Joe's 0668 Rochester Hills

Injury · Days away from work

At a glance

On , an injury at Trader Joe's 0668 Rochester Hills in 3044 Walton Blvd., Rochester Hills, MI 48309 resulted in days away from work. Employee was crew in grocery Store.

Watch Trader Joe's 0668 Rochester Hills — free Get an email when a new federal OSHA severe-injury report for Trader Joe's 0668 Rochester Hills is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
Trader Joe's 0668 Rochester Hills
Parent company
Trader Joe's
Street
3044 Walton Blvd.
City
Rochester Hills
State
MI
ZIP
48309
On-site location
Sales Floor

What was the outcome?

Outcome
Days away from work (code 2)
Type
Injury (code 1)
Days away from work
3

Before the incident

Removing flowers from boxes.

What happened

Pain in rotator cuff that has started to cause numbness tingling and restricted motion in fingers.

Injury or illness

Inflammation Shoulder

Object or substance involved

Overexertion

Summary line

Rotator cuff injury pain due to repetitive motions.

Employee and industry

Job description
Crew
SOC code
35-3023 — Fast Food and Counter Workers
NAICS code
445110 — Grocery Store
NAICS vintage
2022
Avg employees
104
Total hours worked
142998
EIN
43294200
Establishment ID
220551
Employer case #
11

When (timing detail)

Date of incident
Shift started
5:00:00.000
Time of incident
7:00:00.000
Filing year
2023
Submitted
02MAR24:01:57:00

More injuries at Trader Joe's 0668 Rochester Hills

View Trader Joe's 0668 Rochester Hills's full OSHA safety record →

More injuries in this industry (NAICS 445110)

AMARILLO, TX—

WM 4464

ALBUQUERQUE, NM—

WM 3385

More injuries in MI

Source

Data from OSHA ITA Form 300/301 electronic submissions, filing year 2023. ITA Case Detail records are establishment-reported submissions, not OSHA inspections — no per-record IMIS deep link exists.