About this tool
A standalone, pilot-stage prototype for independent Atlanta kitchens.
Who it's for
Chef-owners and operators of 1–3 location independent restaurants in metro Atlanta. Not for chains, franchises, or multi-market groups.
Why supply chain is on the front page
A spreadsheet shows you a number. It doesn't show you where the pressure comes from. The supply-chain map on every result connects the dish to its ingredients, suppliers, and regions — so you can see at a glance which line is spiking and where the swap goes.
Designed for the line
- Big text and big buttons. Readable at arm's length on a phone.
- Color, icon, and word together — so it works on a printed sheet, in direct sun, and for colorblind viewers.
- No sound. No autoplay. No animations you have to wait through.
- Walk away mid-shift. Selection and results persist on your device.
- One-tap print formatted for a clipboard on the pass.
Privacy
No accounts. No email. Your dish selection lives in your browser. We do not store menus or recipes server-side during the pilot.
Data sources
Cost, allergen, nutrient, and sustainability data from the JourneyFoods API (/products/search, /products/{id}/cost, /allergens/{id}, /nutrients/{id}, /products/{id}/sustainability). The pilot prototype runs on mock data shaped like these endpoints.