ID — Bahasa Indonesia

Muhamad Irga

Purwokerto, Central Java

Updated

WashUp — Laundry Pickup & Delivery

A laundry ordering system with pickup and delivery: customers order from a Flutter app, couriers accept and route pickups, admins approve orders and verify QRIS or bank-transfer payments in a Filament panel.

See the service: ERP for Village Enterprises & Small Business

Screenshots

WashUp admin dashboard with revenue cards and latest orders
Main application view · Open image for full resolution
Order list with service, service type, price, status, and payment method
Application view 2 · Open image for full resolution
Laundry services such as wash and iron, dry clean, shoes, and carpets
Application view 3 · Open image for full resolution
WashUp API returning a customer’s orders
Application view 4 · Open image for full resolution

Overview

What this system does.

WashUp lets a customer order laundry without leaving home. They choose a service and an express or regular type, set pickup and delivery addresses on the map, and pay by QRIS, bank transfer with proof upload, or cash.

Couriers see available orders, accept them, share their location, and update the status from pickup to delivery; the route endpoint orders their stops nearest-first using Haversine distance. Admins approve or reject orders, verify payments, confirm cash, and complete orders, and manage services, service types with their own durations, and clothing types. A clothing recognition endpoint is in place as a prototype for itemising pickups from photos.

I built the Laravel 12 API and Filament admin and the Flutter customer and courier app on my own.

Feature inventory

Highlights

13 capabilities verified against the project source.

  • Service and service-type selection
  • Pickup and delivery addresses with coordinates
  • QRIS, bank transfer with proof, and cash payments
  • Order confirmation and cancellation by the customer
  • Available orders and acceptance for couriers
  • Courier location updates
  • Nearest-first route ordering
  • Status history from pickup to delivery
  • Order approval, rejection, and completion by admin
  • Payment verification and cash confirmation
  • Services, service types, and clothing types
  • Clothing recognition endpoint (prototype)
  • Flutter app for customers and couriers

Tech stack

Built with 6 technologies.

  • Laravel 12
  • Filament 3
  • Laravel Sanctum
  • MySQL
  • Flutter
  • REST API

Common questions

What people usually ask.

How do couriers decide the order of pickups?

The route endpoint sorts their active orders by distance from the courier’s current location, so the nearest stop comes first.

Which payments are supported?

QRIS, bank transfer with an uploaded proof that admins verify, and cash confirmed on delivery.

Is the clothing recognition live?

Not yet. The endpoint and data model are in place, but recognition currently returns a stand-in result while a model is chosen.

Same field

Need something like this?

Send a short brief and I’ll come back with scope, approach, and an honest timeline.