Scrap Pickup Booking Web App with Material Rate Card and Pickup Scheduling

Selling household scrap still runs on phone calls and haggling: the kabadiwala quotes whatever rate suits him that day, households have no way to check whether ₹12/kg for newspaper is fair, and nobody keeps a record of what was sold. On the dealer's side, pickups are coordinated over voice calls, so routes are inefficient and disputes over weights are settled by whoever shouts louder. The result is a thin market where households get underpaid and dealers waste trips. This project builds a three-sided web app that brings the whole transaction into the open: a public per-kg rate card with minimum-quantity rules, slot-based pickup booking with address capture, live booking tracking from scheduled to paid, an agent screen where digital-scale weights are entered per material and the payout is computed automatically, and an admin console that manages rates, assigns agents and watches revenue. Because every number in the payout has an audit trail — rate card version, weighed quantities, applied rates — both sides can verify the transaction instead of arguing about it.

1. The customer opens the rate card page, checks today's per-kg rates and minimum quantities, and fills the booking form (name, 10-digit mobile, address, date, time slot, materials with approximate weights); the frontend validates the phone number and required fields before submitting.
2. The backend stores the booking as Scheduled with a generated ID (e.g. BK-1045), a creation timestamp and the estimated payout computed from the current rate card.
3. The admin console lists the new booking; the admin assigns a pickup agent from the agent roster, which moves the booking to Assigned and (in the deployed build) triggers an SMS to the customer with the agent's name.
4. The agent logs in and sees only their assigned pickups for the day with the customer's address, slot and declared materials; at the doorstep they weigh each material on a digital scale.
5. The agent enters the actual weights per material; the frontend multiplies each weight by the rate-card rate and shows the computed payout live; on confirmation the backend stores the actual weights, the applied rate version and the final payout, moving the booking to Picked up → Paid.
6. The customer can watch the booking's status stepper advance to Paid, and the admin's revenue dashboard reflects the completed payout.

Tech stack:

• Python 3 + Flask (backend REST API)
• PostgreSQL (bookings, users, rate-card versions, payout records)
• SQLAlchemy (ORM + schema migrations)
• HTML5, CSS3, vanilla JavaScript (frontend)
• Flask-Login (role-based sessions)
• Twilio / MSG91 (booking & assignment SMS — optional integration)
• Gunicorn + Nginx (deployment)

• [Public material rate card] Live per-kg rates for 12 scrap categories (paper, plastic, metals, e-waste, batteries) with minimum-pickup quantities and pickup rules, refreshable daily by the admin.
• [Slot-based pickup booking] Customer enters name, mobile, address, picks a date and a time slot (9–12 / 12–3 / 3–6), and lists materials with approximate weights; the form validates the phone format and required fields.
• [Booking tracking] Every booking moves through Scheduled → Assigned → Picked up → Paid with a visual stepper, so the customer always knows where their pickup stands.
• [Agent weighing screen] The assigned agent sees only their jobs, enters the actual digital-scale weight per material at the doorstep, and the payout is computed instantly from the active rate card.
• [Automatic payout computation] Payout = sum of (weighed kg × rate) per material, rounded to the nearest rupee; the receipt shows the line-item breakdown for the customer's confirmation.
• [Admin rate-card management] Rates are edited from the admin console and apply immediately to the customer card and the payout calculator; completed bookings keep the rate version that applied at weighing.
• [Agent assignment & revenue view] Admin assigns agents to new bookings from a dropdown, sees all bookings with statuses in one table, and tracks KPIs — total bookings, scrap value collected, pending pickups, active agents.
• [Three-role authentication] Separate customer, pickup-agent and admin logins with role-gated screens, so agents cannot edit rates and customers cannot see other bookings.

• Complete Flask web app source code (customer, agent and admin modules)
• PostgreSQL schema with migration scripts and seed rate-card data
• Role-based authentication (customer / agent / admin)
• Booking flow, weighing screen, payout calculator and admin console
• Deployment notes (Gunicorn + Nginx) with environment configuration
• Project report PDF (background, requirements, design, methodology, testing)
• PPT presentation for final review
• Viva Q&A preparation document (workflows, database design, security basics)