Back to results

As of 2026-02-26, Burrito Arceliano, Inc. passed its most recent City of Chicago health inspection.

Burrito Arceliano, Inc.

PASS
3414 W Irving Park Rd, Chicago, IL 60618
North Center ยท Chicago Dept. of Public Health ยท Last inspected 2026-02-26

Violations at most recent inspection

OBSERVED EXCESSIVE AMOUNT OF ICE BUILD UP INSIDE FRONT CHEST FREEZER. MUST REMOVE ICE AND CLEAN INTERIOR SURFACES OF CHEST FREEZER AND MAINTAIN.
core violation
OBSERVED SEVERAL WATER DAMAGED CEILING TILES IN FRONT/REAR PREP AREAS ABOVE PREP TABLES AND HALLWAY. MUST REPAIR/REPLACE AND MAINTAIN AT ALL TIMES. OBSERVED PEELING WALLS IN THE UNISEX WASHROOM. MUST REPAINT WALL AND MAI
core violation
OBSERVED GREASE ACCUMULATED ON VENTILATION HOOD AND FILTERS ABOVE COOKING EQUIPMENT. MUST CLEAN AND MAINTAIN AT ALL TIMES.
core violation
OBSERVED CITY OF CHICAGO CERTIFIED FOOD SERVICE MANAGER WITHOUT ALLERGEN TRAINING CERTIFICATE. INSTRUCTED ABOVE THAT ALL CITY OF CHICAGO CERTIFIED FOOD FOO SERVICE MANAGERS MUST OBTAIN ALLERGEN TRAINING CERTIFICATES.
core violation
Advertisement

Inspection history โ€” tap to expand

Burrito Arceliano, Inc. health inspection FAQ

Has Burrito Arceliano, Inc. passed its most recent Chicago health inspection?

Burrito Arceliano, Inc. passed its most recent City of Chicago health inspection, conducted on 2026-02-26. This reflects the restaurant's current status as tracked by the Chicago Department of Public Health -- GutCheck rebuilds this page from the city's live data feed, so it updates automatically as new inspections are recorded.

What violations did Burrito Arceliano, Inc. have at its last health inspection?

Inspectors recorded 4 violations at Burrito Arceliano, Inc.'s most recent inspection on 2026-02-26. Full violation text is listed on this page below.

When was Burrito Arceliano, Inc. last inspected by the City of Chicago?

Burrito Arceliano, Inc. was last inspected on 2026-02-26. GutCheck's data is sourced directly from the City of Chicago's public Food Inspections feed and rebuilt on every deploy, so this date reflects the most recent inspection on file at the time you're viewing this page.