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

San Francisco, CA —

OSHA Injury Report: CHEFSTORE San Francisco 586

Injury · Job transfer or restriction

At a glance

On , an injury at CHEFSTORE San Francisco 586 in 170 S Van Ness Avenue, San Francisco, CA 94103 resulted in job transfer or restriction. Employee was sales Associate in grocery.

Watch Chefstore San Francisco 586 — free Get an email when a new federal OSHA severe-injury report for Chefstore San Francisco 586 is published. One employer, no account, unsubscribe in one click.

Where did this happen?

Establishment
CHEFSTORE San Francisco 586
Parent company
US Foods
Street
170 S Van Ness Avenue
City
San Francisco
State
CA
ZIP
94103
On-site location
sales floor paper craft department

What was the outcome?

Outcome
Job transfer or restriction (code 3)
Type
Injury (code 1)
Days restricted or transferred
2

Before the incident

working

What happened

cut open knuckle on the shelf

Injury or illness

Nature of InjuryIllness Laceration Avulsion Body Parts Finger

Object or substance involved

metal shelf

Summary line

Nature of InjuryIllness Laceration Avulsion Cause of InjuryIllnessSharp Object Body Parts Finger Object Substance metal shelf

Employee and industry

Job description
Sales Associate
SOC code
41-2011 — Cashiers
NAICS code
424410 — Grocery
NAICS vintage
2022
Avg employees
11
Total hours worked
27208
Establishment ID
1098416
Employer case #
US-586 SAN

When (timing detail)

Date of incident
Shift started
6:00:00.000
Time of incident
7:00:00.000
Filing year
2023
Submitted
02FEB24:22:09:00

More injuries at CHEFSTORE San Francisco 586

View CHEFSTORE San Francisco 586's full OSHA safety record →

More injuries in this industry (NAICS 424410)

More injuries in CA

Rancho Cucamonga, CA—

087-RCDC

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.