Case study · Scout
Scout: scheduling recurring services and staying in control of upcoming work
Across a property portfolio, many services recur at regular intervals. For Scout, a B2B procurement platform for property organisations, we designed recurring series. A service that has already been prepared serves as a template, the platform generates the purchase orders at the chosen frequency, and authorised people can modify, pause, skip or stop upcoming visits.
Scout is aimed at property organisations that manage properties made up of flats or units. The platform connects them with product suppliers and service providers. It is built with Medusa and Mercur, which provide the commerce and marketplace foundation. Product purchases go through a catalogue and a basket. Service work follows another path: the service purchase order. Many of these jobs are not one-offs and recur every week, every month or every year. Redoing an almost identical file for each period takes time. It also creates a risk of omissions or discrepancies between two orders that ought to be the same. We therefore made it possible to turn a service into a recurring series, while leaving the decision on what will be ordered to the authorised people.
The service purchase order, the file for each visit
In Scout, a service visit is not added to a basket like a product. The person buying for the organisation creates a service purchase order. They can save it as a draft and come back to it later. They choose the provider from among those eligible for the property concerned and split the lines between the accounting codes and the homes in question. The order is only issued once its conditions have been checked, and it is then sent to the provider.
This order becomes the file for the visit. It holds its history, the appointments, the invoices and its progress status. For a regular service, this preparation work is often identical from one time to the next: same provider, same lines, same cost allocation. It is this observation that shaped the design of the series.
A series created from a service that has already been prepared
A series does not start from a blank form. It takes an existing service as a template, with its provider, its lines and their split between accounting codes and homes. The choices made for a first order are thus used for the following ones, without having to re-enter them.
The person who creates the series sets its frequency: weekly, monthly or yearly. They can also set when it ends, either with an end date or with a number of occurrences. By way of illustration, monthly cleaning of communal areas planned until a given date is described by a monthly frequency and an end date. An annual inspection planned for a set number of visits is instead described by a number of occurrences. Each due date gives rise to its own purchase order, with its own file. Appointments and invoices therefore remain attached to the visit they relate to.
From draft to automatic issuing, with explicit consent
Some series generate their orders as drafts: at each due date, the order is prepared, and a person reviews it before issuing it.
A series can also issue its orders automatically when they fall due, without each draft being reviewed. This issuing remains subject to the organisation’s approval rules: depending on these rules, an occurrence is issued or awaits approval. Switching a series from drafts to automatic issuing does, however, change the way the organisation commits itself. This switch therefore requires explicit consent, and the operating mode does not change unless an authorised person has decided so.
In both cases, the generation of due dates is designed so that a given occurrence produces only one order, so that the same visit is not ordered twice from the provider.
Changing what comes next without rewriting what has already been ordered
A service contract evolves. The frequency may change, a line may be added, a cost allocation may be corrected. Authorised people can modify the series rules and the template for the next repetitions.
These changes only apply to upcoming occurrences. Orders already generated remain as they were issued. They correspond to what the provider received and to the invoices linked to them, and rewriting the past would break that consistency. If an order that has already been issued needs correcting, the correction is made in its own file, within the limits allowed by its status.
Pausing, resuming, skipping a date or stopping
Not every interruption is permanent. A series can be paused during works, while homes are vacant or during a renegotiation, then resumed. When it is resumed, the series is assigned to a person authorised to modify it. It therefore no longer depends on a former manager who may no longer be available.
Sometimes a single visit is unnecessary, for example because it would fall at a time when it serves no purpose. It is possible to skip that future occurrence without touching the rest of the series, and the skipped date remains visible in its history.
When the commitment comes to an end, the series can be stopped permanently, and no further orders are generated. It is also possible to cancel the current order and all future occurrences in a single action. Cancelling an order requires a reason and checks that cancellation is still possible in light of what has already been committed or invoiced. The associated appointment is then cancelled, and the calendar does not keep a visit that will not take place.
A series paused when its conditions are no longer met
Automatic issuing commits the organisation without review. It therefore needs to know when to stop. If the conditions required to issue the order are no longer met at a due date, the series does not issue a commitment that has become incorrect. It pauses itself.
The person who issues the series receives a notification of this incident, separate from any purchase order. They are thus informed that the series is paused. They correct what needs correcting, then resume the series, without having to rebuild it.
Upcoming visits coordinated in a calendar
Each order generated by a series follows the usual service journey. The buyer and the provider can propose a time slot, accept the other party’s proposal or decline it, in which case the discussion stays open. The provider responds from an authorised link, without access to the organisation’s internal space. On the organisation’s side, only an authorised person can respond.
Service appointments for the properties each person can access are brought together in a calendar. Visits planned across several sites are thus visible in one place. A confirmed appointment can be exported to a file that common calendar applications can read, so that it can be found in one’s own calendar.
A regular service is thus prepared once in Scout, then repeated at the set frequency, under the organisation’s approval rules. Authorised people stay in control of what comes next: they adjust upcoming occurrences without rewriting what has already been ordered. Each visit keeps its own file and its own appointments.