The challenge
Laundry pickup and delivery software has a pricing problem built in: nobody knows a load's true weight until it has been collected. This Australian laundry and dry-cleaning service wanted customers to book pickups and pay online anyway, and to settle any difference later without a phone call.
The service also covers set areas. Bookings from other postcodes had to stop at the order form, before they turned into a pickup nobody could make. Staff needed a clear plan for each day's pickups and deliveries.
And the business wanted to keep control of its own website. Prices and page copy change through the year, and the team wanted to edit them in-house rather than book programming time for each change.
What we built: laundry pickup and delivery software
We used two tools for two jobs. A content management system runs the public pages: home, about, pricing and contact. Staff edit prices there themselves. The contact page carries a map of the serviceable areas, click-to-call, a WhatsApp link, a contact form and opening hours.
A React and Node.js system, hosted on DigitalOcean, handles the orders. It has three parts:
Customer ordering. Registration, a choice of service such as wash and fold or dry cleaning, garments or an estimated weight, and pickup and drop-off times.
Online payment. Customers pay when they book, then see a confirmation screen and receive a confirmation email.
Admin panel. Orders, customers, pricing and service areas, plus weight adjustments and a printable daily summary.
The order form checks the postcode against the service areas while the customer types. Staff keep that list current in the admin panel, so a new suburb can be switched on without code changes.
How it works day to day
Picture a customer with a week's worth of washing. They open the order form, enter their postcode and find out straight away whether the service reaches them. They choose wash and fold, give an estimated weight, pick a pickup time and a drop-off time, and pay.
On collection day, staff print the daily summary listing every pickup and delivery. After the load is collected, staff confirm its weight. If it differs from the estimate, they update the order and the system sends the customer a payment link for the difference.
From their dashboard, the customer follows the order from placed to picked up, in progress and delivered. Next time, they can repeat a past order in one step instead of filling in the form again.
The result
Customers book and pay for laundry online and follow each order through to delivery. Bookings from outside the service area stop at the form. Weight differences are settled with a payment link rather than a phone call, and staff start each day with a printed run sheet of pickups and deliveries.
Pricing and page content stay in the business's own hands, while the ordering system handles the logic a standard website can't: postcode checks, payments and weight adjustments.
What the research says
Ordering online is routine. A record 9.8 million Australian households, 82% of the total, shopped online in 2025, and 41% of them did so at least fortnightly (Australia Post eCommerce Report 2026). Booking a pickup fits a habit customers already have.
Long checkouts lose orders. Baymard Institute puts the average online cart abandonment rate at 70.22%, across 50 studies. Among US shoppers who left, 17% blamed a checkout that was too long or complicated (Baymard Institute). Checking the postcode as the customer types tells them early whether they are covered, before they fill in the rest.
Cash is a small slice of payments. Around 15% of consumer payments by number were made in cash in 2025, and about 8% by value, according to the Reserve Bank's latest Consumer Payments Survey (RBA Bulletin, April 2026). Online payment at booking, plus a payment link for any weight difference, matches how most purchases are already paid for.
Where AI fits next
Nothing below is part of the current system; these are ideas for a later phase. A model could suggest a likely weight from the garments a customer lists, so the first price lands closer to the final one.
It could also group each day's pickups into sensible runs by area, and a chat assistant could answer questions about services, prices and coverage from the site's own pages.
Planning something similar?
Before you build a laundry booking system, answer these four questions:
Which postcodes or suburbs do you serve, and who keeps that list up to date?
How will you price a load whose weight is only known after pickup?
Which payment provider suits your fees, refunds and payment links?
What does your team need in hand at the start of each day's run?
See how we approach web application development and workflow automation, read about when you need a web application rather than a website, or browse more of our projects.
Other projects like this one are collected on our operations and logistics page.
