Laundry networks: standardize decisions as well as screens

A network becomes less dependent on each manager’s memory when operating decisions are recorded and verifiable. Standardization does not require identical locations: equipment, hours and capacity may differ. Define what must be shared, what may vary locally and who approves each change. This makes expansion more predictable and support easier to coordinate.

Create a reference configuration

Record the service catalog, equipment identifiers, payment methods, support messages and maintenance procedures. Mark the differences permitted at each location, such as pricing or opening hours, and explain their source. Every change needs a version and an owner. Without this reference, a difference between stores can look like a software failure when the configuration is simply different.

Align access with responsibility

Distinguish people who view results, change prices, handle incidents and modify integrations. Grant access only to the locations required for their role, using individual accounts. A shared password prevents attribution and makes access removal harder when someone changes roles. Review permissions when staff join or leave, and keep a history of consequential changes.

Give support the location context

Use consistent identifiers for sites, equipment and transactions. “The machine does not work” needs a description of the interrupted stage, time and customer impact. Decide which problems local staff can resolve and which require a central team or specialist. Record checks already completed when handing over an incident so that customers do not repeatedly answer the same questions.

Example: a price update

Before changing several stores, validate the rule at one location and check the app, kiosk and reporting. Record the approver, affected sites and method for restoring the previous configuration. Then compare support and operating behavior across comparable locations. Distribute a validated version rather than recreating a manual change at every store and relying on informal confirmations.

Implementation checklist

• Document the standard and permitted exceptions.
• Use individual accounts and site-specific permissions.
• Record the author, version and scope of changes.
• Validate a change at one site before distributing it.