The store's day in numbers: walk-ins, bills, value, conversion and payment mix.
A daily sales report template is the one-page record of a store's trading day: how many people walked in, how many bought, what they spent and how they paid. The Store Manager fills it after closing, taking numbers from the POS and the footfall counter or door register, and attaches a photo of the day-end POS report as proof. The Area Manager reads it the same night or first thing next morning. It is a report, not an audit, so there is no score and no pass mark. What it gives the brand is a clean, comparable set of numbers from every store, every day, with a line of context on what drove the result.
Free. No form. The workbook has the same columns as the table below, with the score formula and a fatal-item check in place.
| # | Item | Audit question | Answer | Photo | What good looks like |
|---|---|---|---|---|---|
| 1 | Trading date | What trading date does this report cover? | Text | No | Date in day, month and year, matching the date printed on the POS report. |
| 2 | Walk-ins today | How many walk-ins did the footfall counter or door register record today? | Number | No | A single whole number from the counter or register, with staff movements excluded. |
| 3 | Bills raised | How many bills were raised today, excluding voided and returned bills? | Number | No | Bill count from the POS report, net of voids, matching the Z report exactly. |
| 4 | Conversion rate | What was today's conversion, bills divided by walk-ins, as a percentage? | Number | No | Percentage to one decimal place, worked out from the two numbers above. |
| # | Item | Audit question | Answer | Photo | What good looks like |
|---|---|---|---|---|---|
| 5 | Net sales value | What was today's net sales value in rupees, after returns and including GST? | Number | No | Rupee value from the POS report, net of returns, with GST included as the brand reports. |
| 6 | Average bill value | What was the average bill value in rupees, net sales divided by bills? | Number | No | Rupee value rounded to the nearest rupee, consistent with the two figures above. |
| 7 | Units per bill | How many units were sold per bill on average today? | Number | No | Units sold divided by bills, to one decimal place, taken from the POS report. |
| 8 | Top category | Which category, model or product line sold the most today by value? | Text | No | Names the category or model and its sales value in rupees for the day. |
| # | Item | Audit question | Answer | Photo | What good looks like |
|---|---|---|---|---|---|
| 9 | Payment mode split | How did today's sales split between cash, card and UPI, in rupees? | Text | No | Three rupee values for cash, card and UPI that add up to net sales. |
| 10 | Returns and exchanges | What was the value in rupees of returns and exchanges processed today? | Number | No | Rupee value of returns and exchanges, matching the returns line on the POS report. |
| 11 | Remarks on the day | What drove today's result, such as weather, an event, a stock gap or a staff shortage? | Text | No | One or two lines naming the main reason the day was above or below target. |
| 12 | Day-end POS report photo | Can you attach a clear photo of today's day-end POS report? | Photo | Required | Full report in frame, date, store code and totals readable, no glare. |
Loaded into BorentisOps, each required photo is live, GPS and time-stamped, so a photo from yesterday or another store does not pass. Where the brand has a docket or display standard, Drishti scores the photo against it and marks the misses. Every fail raises a ticket with an owner and a deadline, and the area manager sees the store on a heat map before the next visit.
The checklist runs offline and syncs when signal returns, in Hindi, English and Hinglish, and the operations score sits next to the store's selling score from Borentis Floor on one store card. Pricing is per store, so every store manager and staff member in the store is on the app.
Conversion tells you how many of the people who walked in bought something. Average bill value tells you how much each buyer spent. A store can hit its sales target with low conversion and a high bill value, or the other way round, and each points to a different fix. Low conversion usually means a selling or stock problem on the floor, while a low bill value points to weak add-on selling.
The photo is proof that the numbers typed into the report match the numbers the POS printed, which settles most disputes before they start. It also saves the Area Manager from asking each store for a copy. In BorentisOps the photo is taken live, with a GPS and time stamp, so it cannot be a picture of an older report.
No. It is a report, not an audit, so the pass mark is zero and no item is fatal. What matters is that every field is filled, the same way, by every store. In BorentisOps the numbers roll up into a daily view for the Area Manager and Regional Head, and the operations score from checklists sits next to them, so a sales dip can be read against how the store was run that day.
Yes. The Excel download keeps the same columns BorentisOps uses: section, item, question, answer type, photo rule, weight and fatal flag, so it imports as a checklist without retyping. A Borentis onboarding person maps the roles and stores, sets who fills it and who reviews it, and schedules it so it reaches the right phone at the right time. You can edit, add or remove items before or after the import.