Remix

Make your own version of Dairy Distribution Manager

Get an exact, working copy in your account, then change anything with chat.

Original by ghoste boy

Start free with 40 credits. No card needed.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.

Create a new, professional application for managing a milk and dairy products distribution business, similar to HANOTEK POS. It must be compatible with mobile phones and computers, feature an Arabic RTL interface, a modern white-and-blue design, light and dark modes, and use DZD as the currency.

### 1. Login
Create a login screen that requests the access code `0560`, stored and handled as a string to preserve the leading zero. The correct code must grant access, while incorrect codes must be rejected. Fix and actually test the authentication logic and navigation. Prevent users from bypassing the login screen.

### 2. Dashboard
Display today's sales, profits, expenses, collections, debts, number of sales, inventory levels, and recent activities, all calculated from real application data.

### 3. Products
Implement adding, editing, deleting, and searching products. Each product must include a name, image, barcode, category, purchase price, selling price, unit, quantity, minimum stock level, and expiration date.

### 4. Quantities and Inventory Updates
When adding a product, provide a functional field for its initial quantity. Add a separate **"Add Stock Quantity"** function that updates the existing stock balance and saves a stock movement record. Fix any errors that prevent quantity entry or product saving.

### 5. Barcode Scanner
Implement a real camera-based barcode scanner using the rear camera. It must be fast and reliable, similar to HANOTEK, and support EAN-13, EAN-8, UPC, and Code 128 formats. Include autofocus, zoom, and flashlight controls when supported by the device, and prevent duplicate scans. Make the scanner available in sales, products, debts, and inventory. Use a reliable scanning library, request camera permissions, and provide manual barcode entry when scanning is unavailable.

### 6. Sales
Allow users to scan products and add them to a cart, modify quantities, remove items, and calculate the total, discount, amount paid, and remaining balance. The amount paid must be optional. Deduct stock exactly once when a sale is confirmed. Maintain a sales history and prevent duplicate transactions.

### 7. Customers
Manage customer names, phone numbers, addresses, outstanding balances, account statements, and transaction histories.

### 8. Debts
Add a **"Register New Debt"** button that opens a form allowing the user to select a customer, add products and quantities using search or the camera scanner, calculate the total automatically, and optionally enter a partial payment before saving the debt and linking it to the customer.

Deduct inventory exactly once when the goods are delivered. Support full and partial repayments, customer account statements, a debt list, and remaining balance tracking. Repayments must not be counted as new sales.

### 9. Inventory and Delivery Truck
Maintain separate stock balances for the warehouse and delivery truck. Record loading, distribution, returns, damaged goods, stocktaking, and inventory alerts.

### 10. Suppliers and Purchases
Manage suppliers, purchase invoices, quantities, prices, payments, and outstanding supplier debts. Update inventory when purchased goods are received.

### 11. Expenses and Profits
Record fuel, maintenance, transportation, and other expenses. Calculate the cost of goods sold and net profit accurately, without double-counting expenses or debts.

### 12. Reports
Provide daily, weekly, and monthly reports covering sales, profits, expenses, inventory, debts, and repayments. Support CSV export where possible.

### 13. Settings
Include business name and details, backup and restore functionality, and PWA support if available.

### Mandatory Requirements
- Inspect the existing project structure before making any changes.
- Use a secure, persistent database. Do not rely on localStorage as the primary data store.
- Connect every button to a real, working function.
- Ensure data persists after closing and reopening the application.
- Prevent duplicate operations and maintain inventory and accounting accuracy.
- Preserve existing functionality wherever applicable.

### Required Tests Before Completion
Actually test the following scenarios:

1. Log in using the access code `0560`.
2. Add a product with an initial quantity.
3. Increase an existing product's stock quantity.
4. Scan a real barcode using a mobile phone.
5. Complete a sale.
6. Register a debt by selecting a customer.
7. Record a partial debt repayment.
8. Refresh the application and verify that all data remains saved.

Fix errors in the actual implementation rather than merely creating visual interfaces or using mock data.

At the end, clearly report which tests were successfully completed, which features remain incomplete, and any issues that could not be resolved. Do not claim that a feature or test works unless it has actually been verified.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.