How do you keep cleaners supplied so missing products don’t disrupt service?

Slate gives cleaners a supply-request workflow tied to the visit or property, then keeps the request visible through fulfillment and receipt. A cleaner selects from the catalog available for that client, enters quantities and context, and chooses normal or urgent handling. Operations receives the request and can follow the order timeline instead of relying on an untracked text message.

Start in the right location context

From /supplies, a cleaner can request supplies for an assigned visit or choose an assigned property. Slate validates that context before loading the catalog. It also filters the catalog to products that can be requested for that client. A request cannot be used to order arbitrary products for an unrelated property, and a visit and property cannot be supplied as conflicting contexts in the same request.

The cleaner selects one or more products, quantities, optional item notes, and an optional item photo. They can add a request-level note and mark the request urgent when the timing matters. The dialog can show an informational recent-order warning for a selected product at that property; that warning does not block a new request and does not claim the earlier order solved the current need.

Keep fulfillment visible after submit

Submitting creates a supply request with the cleaner, client, property, and—when applicable—visit context. Slate records a submitted event, notifies the operations team, and bridges the request into the admin task inbox. The cleaner can review their request history, open a request detail, and load its timeline at /supplies rather than wondering whether the office saw the request.

The timeline is the operational handoff: the office can move the request through its configured fulfillment process and the cleaner can see the resulting order states. Status visibility is not the same as a promised delivery time. Product availability, approval, purchasing, carrier performance, and account settings still determine what happens next.

Confirm what actually arrived

When the request is delivered, the cleaner can confirm receipt. Every non-declined item must be classified as received, missing, or damaged; the workflow does not let a partial confirmation quietly close the order. The cleaner can add a note and photo to the receipt and to individual item outcomes.

If an item is missing or damaged, Slate records a receipt exception and raises an operations alert tied to the supply request. That gives the team a specific follow-up record: the delivered order is closed as received, but the exception remains visible for resolution. It is more useful than marking the whole shipment “fine” because one box arrived.

What this means for a multi-location client

Your team can trace a supply need from an assigned location to a request, fulfillment timeline, delivery confirmation, and exception alert. Cleaners have a structured way to ask for products while they are working; operations has enough context to decide whether to approve, purchase, ship, or investigate.

The cleaner catalog and request permissions are assignment- and client-scoped. The current cleaner restock-alert submission endpoint is disabled and returns a clear error; this workflow should not be described as a cleaner-submitted restock-alert system. A cleaner who sees client-stocked stock running low should use the configured office or contact process instead. Slate also does not promise a product, delivery date, or uninterrupted service merely because a request was submitted.

See the supply workflow

Ask Slate to map your client-specific catalog, urgent-request rules, fulfillment statuses, receipt process, and missing-or-damaged escalation into a location-aware supply workflow.

Discuss your supply workflow