A Windows counter app links tA cashier needed to identify which table ordered eable orders, kitchen order tickets and final bills. Codex assisted development and troubleshooting; the restaurant can use the billing workflow without a runtime AI model.
A cashier needed to identify which table ordered each dish, communicate additions to the kitchen without resending the original order, and print a legible final bill on a narrow thermal roll. During installation, printer width and clipped amounts mattered more to staff than how the receipt looked on a desktop monitor.
Built a Flutter Windows counter with a local SQLite database, table selection, categorized dishes, kitchen order tickets (KOTs), settlement and receipt printing. The operator can configure receipt details and use sales reports to review bills and item quantities. Codex was used interactively to implement changes and investigate build, layout and printer issues. Field feedback and physical print samples informed revisions. Order totals, inventory and printing are conventional application logic, not model-generated decisions.
The builder reported installing the app on a customer Windows machine. Field print samples made concrete defects visible: names or totals could be clipped even when the screen layout looked correct. The workflow brings table ordering, kitchen tickets and customer billing into one counter application. No measured before/after service time, independently verified revenue, or customer satisfaction score is available.
One paying restaurant customer purchased the Windows counter product described in this submission. Across the broader Windows and Android billing portfolio, three distinct restaurant customers purchased the software as of 16 November 2026 (builder-reported). The Windows customer is included in the three. Customer revenue impact has not been measured.