WareHub

Build a responsive web app called WareHub for warehouse sparepart management in a factory, optimized for Android browsers and mobile-first usage, using Supabase as the backend.

Core requirements:
1. Authentication and role-based access control
Implement Supabase Auth and RLS. Roles: Admin, Supervisor, Operator, Viewer. Admin can manage users, reset passwords, assign roles, and delete users.

2. Master Data
Create an import flow for CSV and XLSX files. Required headers exactly: Kode, Nama, Uom, Gudang, Lot, Bin, Saldo. Validate headers and rows, show preview/errors, and allow bulk delete all master data. If duplicate rows are exactly the same, do not merge them; store them as separate rows with their own saldo values.

3. Good Receipt
Create a transaction module where transaction number is manually entered by the operator, not auto-generated. One GR transaction can contain multiple items. Each line supports item search by manual search and barcode scan. Auto-fill location and rack from master data. Show system balance and update saldo by adding incoming qty. Support delete by transaction number and delete all GR transactions.

4. Good Issue
Create a transaction module where GI number is manually entered. Each GI transaction can contain multiple items and items can be added later into an existing GI number. Provide a dropdown for division values: mekanik, elektrik, logistik, ga, office, produksi, hse, qa, qc, hrd, utility, civil, instrument, finance, purchasing. Support manual input and barcode scan. Auto-fill location and rack from master data. Show stock balance and deduct quantity. Support delete by transaction number and delete all GI transactions.

5. Stock Opname
Create stock opname with a manual transaction number, multiple items per transaction, and maximum 26 items per transaction. Fields: item, system balance, physical balance, and automatic status calculation. If physical > system, classify as GR. If physical < system, classify as GI. If equal, status is sesuai. Support adding items to an existing opname number, delete by transaction number, delete all, and export completed data to Excel.

6. Reports and Stock
Build report screens for inbound mutations, outbound mutations, and stock opname history. Add stock/saldo view with barcode labels in vertical format for each item and a print all barcodes action. Export reports to Excel.

7. UX/UI
Use a clean minimal design with attractive colors, high contrast, and no ugly logos. Make it fast, simple, and suitable for factory warehouse use on Android. Use large touch targets and clear tables.

Suggested stack:
Frontend: Next.js or React + TypeScript + Tailwind CSS + shadcn/ui
Backend: Supabase Postgres, Auth, Storage, RLS, and Edge Functions if needed
Forms/validation: React Hook Form + Zod
Tables/search: TanStack Table
Barcode: browser camera scanner support with manual fallback
Excel export: SheetJS or ExcelJS

Data model suggestions:
users, roles, user_roles, master_items, gr_headers, gr_lines, gi_headers, gi_lines, opname_headers, opname_lines, stock_movements, audit_logs, barcode_labels

Implementation notes:
Use server-side validation for all writes. Add indexes on item code, transaction number, date, division, lot, bin. Keep reports filterable by date range and transaction number. Include confirmation dialogs for bulk delete. Make all destructive actions admin-only and logged. Build polished empty states, validation messages, and loading states.