Back to results

As of 2026-02-18, Habanero received a Pass w/ Conditions on its most recent City of Chicago health inspection.

Habanero

CONDITIONAL
222 W Merchandise Mart Plz, Chicago, IL 60654
River North ยท Chicago Dept. of Public Health ยท Last inspected 2026-02-18

Violations at most recent inspection

OBSERVED NO THERMOMETER INSIDE REAR PREP COOLER. MANAGEMENT PROVIDED THERMOMETER DURING INSPECTION. INSTRUCTED TO MAINTAIN THERMOMETERS IN ALL COOLERS CONTAINING TCS ITEMS.
core violation
OBSERVED CONTAINERS OF BULK ITEMS SUCH AS RICE AND BEANS NOT LABELLED. INSTRUCTED TO LABEL WITH COMMON NAME.
core violation
OBSERVED THE FOLLOWING REPEAT CORE VIOLATIONS NOT CORRECTED FROM REPORT #2611931 DATED 2/7/2025: #57 "OBSERVED NO FOOD HANDLER TRAINING FOR TWO FOOD HANDLERS. INSTRUCTED TO PROVIDE PROOF OF FOOD HANDLER TRAINING FOR ALL
priority violation
OBSERVED NO SUMMARY POSTED FOR PUBLIC VIEW FROM PREVIOUS INSPECTION #2611931 DATED 2/7/2025. LEFT NEW SUMMARY AND INSTRUCTED TO POST FOR PUBLIC VIEW. PRIORITY FOUNDATION VIOLATION 7-42-010(B). CITATION ISSUED.
priority violation
Advertisement

Inspection history โ€” tap to expand

Habanero health inspection FAQ

Has Habanero passed its most recent Chicago health inspection?

Habanero received a Pass w/ Conditions on its most recent City of Chicago health inspection, conducted on 2026-02-18. 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 Habanero have at its last health inspection?

Inspectors recorded 4 violations at Habanero's most recent inspection on 2026-02-18, including 2 classified as Priority or Priority Foundation. Full violation text is listed on this page below.

When was Habanero last inspected by the City of Chicago?

Habanero was last inspected on 2026-02-18. 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.