Bottle Shop End of Trade Web Application

What is Bottle Shop End of Trade Web Application?

A web-based application for Australian bottle shops to manage end-of-trade processes, cash handling, and financial reconciliation. It features a calendar interface, Australian currency support, safe and till float management, and automated variance calculation.

How to use Bottle Shop End of Trade Web Application?

Clone the repository, create a Python 3.13 virtual environment, install dependencies, initialize the SQLite database with Flask-Migrate, then run flask run. Navigate to http://localhost:5000 to access the current day's takings. Use the calendar to select dates, enter float denomination counts, record payment totals, and settle daily takings once reconciliation is complete.

Key features of Bottle Shop End of Trade Web Application?

• Calendar interface for date navigation
• Support for all Australian coin and banknote denominations
• Safe float management with $1,500 target
• Till float management with $500 target and optimal denomination breakdown
• End-of-trade reconciliation with automatic variance calculation
• Knowledge Graph integration for system architecture mapping

Use cases of Bottle Shop End of Trade Web Application?

• Daily reconciliation of sales, cash, and payment methods for a bottle shop
• Tracking and maintaining safe and till float denominations
• Calculating variance between POS readings and recorded payments
• Marking daily takings as settled after verification
• Onboarding developers via Knowledge Graph visualization of code structure

FAQ from Bottle Shop End of Trade Web Application

What runtime does this application require?

Python 3.13, Flask 2.3.3, SQLite (via SQLAlchemy 2.0.36), and standard web frontend assets (HTML5, CSS3, JavaScript with Bootstrap 5).

Are there known compatibility issues?

Yes, SQLAlchemy 2.0.x has a type annotation issue with Python 3.13. Suggested workarounds include downgrading to Python 3.11 or 3.12, waiting for a compatible SQLAlchemy release, or manually patching the code.

What data is stored, and where?

Financial records are stored in a local SQLite database under the schema daily_takings, which includes fields for date, till read, EFTPOS totals, cash, customer count, float denominations, variance, and settlement status.

How are floats managed?

The safe float has a target of $1,500 and the till float a target of $500. The application tracks opening and closing denominations and calculates the optimal till float makeup using smaller denominations where possible.

Is authentication supported?

No user authentication is implemented yet; it is listed as a future enhancement (manager access). The application currently runs without login.