Rozina Begum's Work | ContraWork by Rozina BegumRozina Begum
I will do data analysis and create an interactive dashboard
Customer Shopping Insights Dashboard
A fast, user-friendly Streamlit web app designed to turn raw retail data into actionable business insights without any clutter or complexity.
What This Dashboard Does:
Smart File Check: Simply upload your sales CSV file. The app
automatically checks if the file structure, columns, and data types are
correct before processing—ensuring error-free reports.
Instant Executive KPIs: Get a clear overview of Total Revenue, Average
Order Value, Total Customer Count, and Average Review Ratings at
a glance.
Interactive Filtering: Easily filter your data by age, product categories,
shipping methods, or locations using simple sliders and dropdowns.
Table Reports & Visuals: Switch between organized summary tables and
clear interactive charts to see top-performing products, customer age
demographics, location trends, and payment preferences.
Tested & Ready: Pre-tested with Kaggle’s Customer Shopping Preferences
dataset (3,900+ customer records) to ensure seamless handling of real-
world shopping data.
Why It Feels So Fast:
Powered by Polars (an ultra-fast data processing engine built in Rust) instead of standard Python tools, this dashboard handles filtering, sorting, and reporting instantaneously—giving you a smooth, lag-free experience.
Note: Check out the attached screen recording video above to see the interactive upload flow, real-time filtering, and visual reports in action! Donut Shop Interactive Dashboard: Multi-Page Streamlit App
What this is
A multi-page business dashboard that shows a donut shop's sales, inventory and staff data in one place, with clear numbers, tables and charts. The data comes live from a PostgreSQL database, so the owner always sees current information without touching spreadsheets or the database.
4 pages, one simple layout
User Guide: explains how to use the dashboard.
Sale & Revenue: top-selling donuts, sales trends, sales by category, and
profit.
Inventory: purchases, stock, and food waste.
Employees Status: staff by shift, age group and role, plus salary figures.
Every page has the same structure. Key numbers (KPIs) sit at the top, with a Tables tab and a Charts tab below, so new users learn the layout once and can use the whole dashboard.
Refresh button for performance
Instead of reloading constantly in the background, each page has a Refresh button. Users load the latest data only when they need it, which keeps the server and the database light and the dashboard fast.
Filters with select boxes
Tables can be filtered with simple select boxes, for example by month or by employee role. Users get just the rows they want without writing any queries.
Export and share
Charts can be saved as an image with one click.
Tables can be downloaded as a CSV file for Excel or reports.
Fast and interactive
Data is loaded from PostgreSQL with ConnectorX and processed with Polars, which stays fast as the data grows. Results are cached, so repeated views load quickly. Charts are made with Plotly, so you can hover over any point to see its exact values.
Tools: Streamlit, Polars, ConnectorX, Plotly, PostgreSQL, Python Donut Shop Sales & Operations Analysis: Polars, Plotly and PostgreSQL
What this is
A data analysis project that turns a donut shop's database into clear, interactive insights about sales, inventory and staff. It reads live data straight from a PostgreSQL database, so the results always match what is happening in the business. There are no manual exports and no copy-pasted spreadsheets.
Why Polars, not the usual pandas
Most data analysis today is done with pandas. For this project I used Polars, a modern, high-performance data library written in Rust. I built the shop's database to scale, and the analysis needed to scale with it.
Fast on big data: Polars uses all of your computer's CPU cores, so it stays fast as the data grows from thousands of rows to millions.
Memory-efficient: it handles large datasets without slowing down or running out of memory.
Built for growth: when the business adds more sales, customers and locations, the analysis keeps working without being rewritten.
Live connection with ConnectorX
The analysis connects to PostgreSQL through ConnectorX, a database connector built for fast loading, and it loads data directly into Polars. Each run pulls the latest data, so a client can refresh the analysis at any time and see current numbers.
Interactive charts with Plotly
All charts are made with Plotly, so they are interactive and not just pictures. Hover over any bar, line or data point to see the exact values, and zoom in or turn data series on and off to explore the details yourself.
What the analysis covers
Sales & revenue: top-selling donuts, sales trends by month, sales by
category, and total profit.
Inventory & waste: ingredient purchases, wasted donuts, and the money
lost to waste.
Staff & operations: employees by shift and age group, and
salary summaries.
Tools: Python, Polars, ConnectorX, Plotly, PostgreSQL Donut Shop Database: PostgreSQL Design for a Growing Business
What this is
A complete PostgreSQL database that runs a donut shop's daily work: stock, suppliers, staff, customers, orders and payments. It has 3 schemas, 25 tables, 32 procedures and 9 triggers.
Why PostgreSQL
I chose PostgreSQL because it is reliable and scalable. If the business gets bigger, with more customers, orders and staff, the database keeps working smoothly and doesn't need to be rebuilt.
How it is organized
The database is split into 3 sections (schemas), so everything has a clear place:
Inventory: donuts, ingredients, suppliers, purchases, stock levels, discounts, waste, and price history.
HR: employee roles, shifts, salaries, and payment history.
Sales: customers, orders, payments, and canceled items.
All the tables are connected, so the data stays consistent. There are also 4 ready-made reports (views), such as daily sales, sales by donut, and canceled items.
Procedures: ready-made, safe operations
Every change to the data goes through one of 32 stored procedures, such as record_items, record_payment and cancel_sale. Each procedure checks the data first and gives a clear error message if something is wrong, for example a negative price, a donut that doesn't exist, or an order bigger than the stock.
I built it this way for speed and safety. Running operations directly from Python is slower, so my Python functions call these procedures instead. The work then runs inside the database in a single call, and the application never writes to the tables directly. In my testing, this was really fast.
Triggers: the automatic watchmen
9 triggers react the moment data changes, with no extra code needed:
A new order item is added: the donut stock goes down automatically and the change is logged.
A donut or ingredient price changes: the old and new prices are saved in a history table.
An employee's salary or shift changes: the change is saved in a history table.
Stock gets low: a warning is created for donuts at 10 or fewer and for ingredients below their minimum level.
New ingredients are purchased: the stock level is updated automatically.
Built with data analysis in mind
Customers and employees are never deleted, only marked inactive, so history is kept. Together with the price, salary, waste and inventory logs, this gives clean data for reports, forecasting and dashboards.
Tools: PostgreSQL, PL/pgSQL, Python