A four-app laundry marketplace for partnered residential buildings that runs subscriptions, routing, vendor matching, and Stripe settlements from one platform.
Skipwash's network spans residents, partnered buildings, vendors, and delivery teams, and coordination between them ran on spreadsheets, phone calls, and manual follow-ups. No one could trace an order from a building to its vendor and back. Skipwash needed one managed marketplace where residents book pickup and delivery from approved vendors, with each stakeholder confined to its own data.
Our team designed the multi-tenant platform around how orders move through the network. Four apps share one order record, while role-based permissions keep every tenant’s data separate.
The logistics core is a route lifecycle engine with templates, recurring instances, building stops, and overrides. Vendor assignment runs on an LRU-based engine that respects capacity, building mappings, and availability, with radius-based fallback when mapped vendors are unavailable. A subscription engine generates weekly and bi-weekly orders automatically and handles skips, plan changes, and two billing models.
Underneath, queue-based background processing runs recurring jobs, payments, routing, and notifications safely under concurrent load. Stripe handles payouts to vendors, buildings, and delivery partners, with automatic holds on disputed orders. Public holidays and staff leaves are managed in one calendar.
The marketplace flow was mapped before any build work, and it shaped every decision that followed. Separate applications and role-based tenancy came straight out of how the four stakeholder groups interact.
Priority-only assignment would have overloaded Skipwash's main vendor. An LRU engine bounded by capacity and building mappings keeps the network balanced, with a radius-based fallback for coverage gaps.
Order generation, payments, routing, and notifications all run as background jobs. That design lets concurrent workflows scale without dropped jobs or race conditions.
Holidays and leaves feed subscription generation, vendor matching, pickup scheduling, and billing anchors from a single source. Schedules no longer need manual adjustment.
Settlement snapshots, payout tracking, and dispute holds were built into the payment layer from the start. Contested orders stay unsettled until review is complete.
What Makes Us The Buzz of Tech Town?
Contact Us
Have Questions? Let's Talk!
Fill out this form to drop us an email, and we will reach out to shape something extraordinary.