What to export, field by field.
One page for your IT or MIS team, before the first call. Your column names do not have to match ours: we map your export to these fields in the first week and tell you what is missing. Send files exactly as your system produces them.
Fresh categories only: fruit and vegetables, dairy, bakery.
Format
CSV (UTF-8) or Excel, one file per table. Dates as YYYY-MM-DD; times as HH:MM, store local time. Quantities in the unit you sell in, with a unit column (kg or pieces). Money in rupees.
How much history
Twelve months if you have it. Six months is enough for where the money goes and a backtest on those months. A year is needed to compare festival seasons and measure seasonality from your own history; with less, those effects come from our calendar and are flagged as assumptions.
What not to send
No customer data of any kind. Remove staff names, employee IDs and phone numbers before export; if any arrive, we delete them on receipt.
How to send
Only after the NDA and data-sharing agreement are signed, through a secure link we provide. Data is held in an India cloud region and deleted at the end of the diagnostic unless you ask in writing to keep it.
Four files.
1. Daily sales and stock one row per store × item × day
| Field | Meaning | Example |
|---|---|---|
date | Trading date | 2026-09-28 |
store_id | Your store code | S08 |
item_id | Your item code (or PLU for loose produce) | FV07 |
unit | kg or pcs | kg |
sold | Quantity sold that day | 23.5 |
closing_stock | Stock on hand at close, as the system records it | 12.0 |
received | Quantity received that day (from DC, collection centre or supplier) | 30.0 |
wasted | Quantity written off that day (expiry, damage), if recorded | 1.5 |
2. Item master one row per item
| Field | Meaning | Example |
|---|---|---|
item_id, name | Code and description | FV07, Lemon |
category | Fruit & veg, dairy or bakery (your own hierarchy is fine) | Fruit & veg |
unit | kg or pcs | pcs |
shelf_life_days | Typical days the item can be sold after receipt | 7 |
case_pack | Units per crate, case or tray as ordered | 50 |
price, cost | Selling price and purchase cost per unit, in rupees | 5.00, 3.20 |
3. Store list one row per store
| Field | Meaning | Example |
|---|---|---|
store_id, name, city | Code, name and city | S08, Ameerpet, Hyderabad |
opened_on | Opening date, if under two years old | 2025-06-01 |
size_sqft, format | Selling area and format, if you keep them | 6500, Supermarket |
supplied_by | The DC or collection centre that supplies its fresh | DC1 |
4. Orders one row per store × item × order date
| Field | Meaning | Example |
|---|---|---|
order_date, store_id, item_id | When and what was ordered or allocated | 2026-09-27, S08, FV07 |
ordered_qty | Quantity ordered or allocated | 40 |
placed_by | Store or head office/DC (a role, never a person's name) | Store |
Each one sharpens a finding.
| File | Fields | What it adds |
|---|---|---|
| Sell-out times | date, store_id, item_id, last_sale_time on days the item ran out | Estimates demand you missed from when the shelf emptied, not just that it did |
| ERP reorder settings | store_id, item_id, min, max, reorder level, review cycle | The backtest against the rule your ERP actually uses |
| Promotion calendar | item_id, store_id (blank = all), start date, end date, type, discount % | Keeps promotion days out of normal demand |
| Write-off reasons | Reason code on each write-off | Splits waste into ordering, handling and damage |
| DC or collection-centre stock | date, node, item_id, usable stock at day end | Separates store ordering problems from supply shortfalls |
| Audited write-off line | "Inventory written off" for the last three years, and its valuation basis | Reconciles store-level waste to your accounts |
Questions about a field? Write to [email protected]. A food brand planning launches needs different data; it is listed on the launch review page.