Par level management
Each site on a multi-location account keeps its own garment counts, sizes and pickup days, and changes are visible to the branch at once.
A customer self-service app lets a uniform rental customer change garment sizes, adjust a pickup window and check a delivery without calling the branch. SIZ Group designs and builds that app for uniform rental companies, starting with a free scoping call.
A uniform rental customer is rarely one person. A kitchen manager at a restaurant, a shop supervisor at an auto repair site and a plant safety coordinator at a factory all order from the same account, and each has a different idea of how many shirts and aprons the crew needs this week. A generic booking app assumes one buyer. Uniform rental needs an account that holds several sites, each with its own par levels and pickup days.
The timing pressure is also specific. A customer who runs out of clean chef coats on a Friday dinner service does not wait for the next scheduled route. If the app shows the next delivery window and lets that customer request an extra exchange in two taps, the branch avoids an emergency call-out and the kitchen keeps its line staffed.
Most uniform rental companies still take changes by phone, email, text and the note a route driver scribbles on a soiled-garment ticket. The branch then re-keys each change into the route system and the billing system, often the same afternoon. Each copy is a chance for a size to be wrong or a stop to be missed.
The breakdown points are predictable. A customer's request reaches the wrong branch, a driver never sees the revised par list, or a lost garment charge is disputed days after the truck has left. A self-service app removes the re-keying step, but only if the data it writes matches the route and invoice records exactly.
Before approving the build, the owner should be able to change a customer's size from the app and watch that change appear on the next route sheet and the next invoice draft without any manual step. That single path proves the app is worth having, and it is the first thing we would test together on a real account.
The customer experience lead should also see the app from the customer's side. We would walk through a dozen real requests, including a new hire outfitting, a seasonal crew swap and a request to pause service during a plant shutdown. Each one should end with the customer knowing what happens next and the branch knowing exactly what to pick up or deliver.
Each site on a multi-location account keeps its own garment counts, sizes and pickup days, and changes are visible to the branch at once.
Customers choose or move a window inside the route schedule, and the branch sees the change before the driver loads the truck.
Each stop shows whether the garments are scheduled, out for delivery, delivered or waiting on a soiled bag count.
A customer can review a flagged lost or damaged garment with a photo and approve or dispute the charge before the next invoice.
Monthly invoices, credits and replacement charges are available by site, so account managers answer questions without a phone search.
The walk-through starts with the kitchen manager of a busy restaurant logging in on a phone during a midweek lull. The account shows three sites, and she opens the one with the line cooks. She sees the current par for chef coats and aprons, along with the next scheduled delivery on Thursday morning.
She requests two extra coats in a larger size and adds a note that a new cook starts on Monday. The app confirms the change, flags it for the branch manager and shows the revised par list the route driver will see. Because the garment tags are already matched to the site, the driver knows which bags to load before leaving the yard.
When the delivery is done, the app shows the status as delivered and the soiled bag count picked up in return. The monthly rental invoice lists the new coats on the correct site line, so the manager never has to call the branch to ask why the total moved.
Most uniform rental companies run a route planning or rental management package alongside an accounting tool such as QuickBooks. We do not recommend replacing a system that already works for drivers. The customer app should read and write to the existing category of route software through an integration, so the branch keeps one source of truth for stops and garments.
We would also connect the app to a card processor such as Stripe for any payments and to the email tool your team already uses for receipts. Where a branch lacks an API, we describe the gap in the scoping document and propose a simple scheduled export instead of a fragile workaround.
Demand moves in waves for uniform rental. New hire outfitting peaks when a restaurant opens or a factory adds a shift. Seasonal crews for landscaping or event services arrive in spring and leave in autumn, and a manufacturing plant may close for two weeks of maintenance with no garments needed at all.
The app should handle those waves with date-based par changes and pause options that the customer sets in advance. A customer who knows the plant closes in August can schedule the pause in July, and the branch sees it on the route plan before the trucks are loaded.
Customers switch when the app is faster than a phone call for the tasks they do most, such as changing sizes or moving a pickup. We would test the top ten requests with a few real accounts before launch and keep the phone number visible for anything unusual.
The branch records the charge against a specific garment tag, and the customer receives a notice with the reason and a photo when one is available. The customer can approve or dispute the charge in the app, and the decision flows to the invoice.
Yes, if you want changes to reach drivers without retyping them. We map the stops, par lists and garment matches in the scoping call, then decide whether a live integration or a scheduled export is the safer route for your system.
The same features can work in a mobile browser through a secure link, so a plant supervisor on a shared tablet can still change a pickup. Native apps are useful when customers order often and want push notifications.
Payments run through a hosted card processor such as Stripe, so card numbers are not stored in our app. We confirm the processor, fees and refund rules with you in writing before the build starts.
Share your branches, route system and typical customer requests, and we will confirm scope and price in writing before any build begins.