Every operator 'knows' tomato prices went mad last quarter; almost none can say what they paid, when, and how fast it moved, which is the difference between renegotiating with data and grumbling at the vendor. This tracker logs your actual purchase prices per staple and builds your own trend line, stored privately in your browser, from the only market data that matters: your invoices.
Track commodity costs by logging your own paid price per staple at each purchase: the latest price, the logged range, and the percentage change over time tell you when to renegotiate, switch vendors, or re-cost menu items. Public wholesale reference prices are published daily on the government's Agmarknet portal.
No prices logged yet. Add your purchase price each time you buy a staple, within a few weeks you'll have your own trend line per item, from your own invoices, for your own market.
Data stays in your browser only, nothing is uploaded. For mandi-level reference prices, the government's Agmarknet portal publishes daily wholesale rates by market.
Because you don't buy at the market index, you buy at your vendor's rate, with your quality spec, in your city. Mandi data (Agmarknet publishes it daily) is a useful reference for negotiation, but the number that hits your P&L is the one on your challan, and that's what this tracks.
A single spike means nothing, produce breathes. A 15-20% sustained rise across 3-4 purchases is the signal: check the mandi reference to see if it's market-wide or vendor-specific, requote (Vendor Price Comparison tool), and re-cost the dishes where that item is primary (Seasonal Menu Costing).
The log is stored in this browser's local storage, deliberately: your purchase prices are commercially sensitive, and this tool never uploads them. The trade-off is no sync. For multi-device, multi-outlet purchase tracking with history, that's platform territory, talk to us.