DeccanPro · Chennai restaurant guide
https://deccanpro.com/guides/restaurant-pos-midnight-checklist/
Updated
Record the dates your team actually uses
Write down the calendar date, the restaurant’s shift label and the clock used by the server. A shift called Monday dinner may continue into Tuesday morning. Do not assume the application groups those hours into one business day, or that every screen uses the same date filter.
Ask the demonstrator to identify how the intended deployment handles dates and time zones. Record the answer and the report filters you will use. Do not change the clock of a live restaurant computer to run this exercise; arrange an isolated demonstration or an agreed observation across the real boundary.
Keep one practice table open across the boundary
For a supervised test, enter two dosas on a practice table at 23:55 and keep the order open. Record its reference and what the kitchen sees. At 00:05 add one coffee through the supported workflow. These times and quantities are an illustrative test, not a claim about your restaurant’s service hours.
The expected complete order is two dosas and one coffee. Inspect the counter, captain view and actual kitchen instruction separately. An order remaining at the counter does not establish that the kitchen display still includes it. Keep the first ticket and the update together so nobody treats the original dishes as a fresh cooking request.
Check the kitchen display’s current-day boundary
The reviewed DeccanPro kitchen-display feed selects KOT orders created from the start of the server’s current calendar day and excludes paid or cancelled records. That current-day selection is important for an order created before midnight: do not assume it will remain in the kitchen feed after the day changes.
Demonstrate the behaviour in the version and configuration you intend to use. Record whether the old table remains visible, how a new addition is communicated and how the cook obtains the complete current instructions. If the required overnight workflow is not supported, treat it as an unresolved requirement. Agree a supported alternative or a verified correction before using the display as the sole kitchen reference.
Find the final bill without counting the order twice
Complete the practice bill after midnight using the supported lookup. Check that it still contains two dosas and one coffee and that each item is billed once. The order-entry date, bill-completion date and payment date may answer different reporting questions; ask the demonstrator to show which date each relevant report uses.
Review both calendar dates and your intended shift report with the same transaction reference. A bill missing from one date filter is not by itself evidence that it was lost. Conversely, finding an open order and a completed bill in different views does not mean there were two sales. Reconcile the saved transaction before recreating anything.
Give the next operator a usable handover
For every unfinished late-service table, record the reference, last confirmed kitchen instruction, payment state and responsible staff member. Include any order that is absent from the current kitchen view but still needs preparation or collection. Use the free shift-handover worksheet linked below with anonymised practice details.
Ask a replacement cashier or captain to locate the order without coaching. They should be able to explain what remains to be done and which date filters reveal the relevant records. Keep unresolved display or reporting behaviour on the demo scorecard, with a named person and a retest plan.
PUT IT INTO PRACTICE
Your checklist
- Server date and intended shift label recorded separately
- One 23:55 order kept open until a 00:05 addition
- Counter, captain and kitchen checked independently
- Current-day KDS selection tested explicitly
- Final bill reconciled across the relevant report dates
- Next operator can locate and explain unfinished orders
