Case study · Scout
Scout: getting a purchase approved and keeping requests moving
In a property organisation, a purchase often involves several levels of responsibility before it goes to a supplier. For Scout, a B2B procurement platform built with Medusa and Mercur, we designed a tiered approval workflow. This workflow shows in advance who needs to be involved and distinguishes an intermediate approval from the final decision. It also makes it possible to reject a request with a reason or to ask for a correction, and it keeps working while decision-makers are away.
Scout connects property organisations with product suppliers and service providers. These organisations manage properties made up of flats or units. Their teams order what the buildings need there: supplies, equipment, call-outs. Several people are involved, each working on the properties assigned to them. One prepares the purchase, another is accountable for it at a site, and a third holds broader authority. A purchase request therefore has to reach the right decision-maker, receive an answer that makes sense and not get stuck because someone is unavailable. We built an approval workflow on the platform that organises this journey, from preparing the basket to the decision that authorises the order.
Knowing before submitting who will need to authorise the purchase
A purchase request does not always follow the same path. The organisation defines its authority policy: amount thresholds that determine the level of approval required, and rules that apply when a purchase exceeds the planned budget. These criteria combine. A small order and a large expense therefore do not necessarily go up to the same level.
The person preparing the purchase does not have to guess these rules. Before submitting their basket, they can preview the expected approval level. They see who will need to be involved and why. They therefore know what to expect and can, if they wish, adjust their request before sending it. The workflow stops being a black box: the applicable rule can be read from the basket onwards.
This logic also applies to negotiated prices. When a quote accepted from a supplier is converted into an order, it enters the same approval workflow. A price obtained through negotiation does not bypass the organisation’s spending rules.
Tiers that separate intermediate approval from the final decision
When a request requires several levels, each approver decides on the tier that concerns them. Their approval is recorded, and the request moves on to the next level. This intermediate approval does not yet trigger the order. Only authorisation from the last required level allows the purchase to go through. The distinction matters: a site manager can validate the need without committing, on their own, to an expense that falls under a higher authority.
By way of illustration, unrelated to any client case: a manager confirms that a piece of equipment is needed for a building. The request then goes up to the person authorised for that level of spending, who makes the final decision. Each person acts at their own level, and every step remains traceable.
The workflow also takes the hierarchy into account. A higher-level approver can satisfy a lower tier, within the limits of their authority. If the request is accessible to them, it does not have to wait for an intermediate level to become available. The case moves forward without the rules being bypassed.
Rejecting with a reason, or asking for a revision rather than starting over
A decision is not limited to yes or no. When an approver rejects a request, they state their reason. The requester understands why the purchase is not going through: an unsuitable product, an excessive quantity, an expense to be postponed. They do not have to piece the reason together by chasing their line management.
Often, the request is almost right. The approver can then ask for a revision and add notes explaining what needs to be corrected. The requester prepares a new basket from their request. The lines of the request are carried over into it. They change what needs changing, then resubmit their request. They do not have to recreate their entire purchase file from memory over a detail.
During an absence, requests are flagged to a delegate
An approval workflow easily grinds to a halt when a decision-maker goes on leave: requests pile up with someone who will not see them. On Scout, an approver can declare their absence by entering their last day of unavailability and their time zone. The return date thus matches their local reality.
Before confirming, they can preview the planned delegates: they see who requests will be notified to during their absence. They leave knowing who will take over, without having to arrange it case by case.
Delegation does not only concern future requests. When the absence is declared or changed, requests already pending are rerouted as well. Cases opened before departure do not remain on hold until the approver returns.
A workflow that keeps pace with changes to the team and its scope
Approvers work within a specific scope. When a member is invited into the organisation, they are given a role and the properties they are responsible for. These properties can then be added or removed according to their responsibilities. Site managers manage the people who fall under their sites without having access to the whole portfolio. To keep track of their activity, an approver can view statistics on the requests that fall within their scope. They can gauge their own workload without seeing that of other sites.
Teams change, and the workflow has to take this into account. When a member’s role is changed, the platform checks whether they are still expected on unfinished approvals. This avoids removing from someone the authority they need while a case is awaiting their decision.
The approval workflow we built for Scout makes the applicable rule clear from the basket onwards. It separates a manager’s approval from the authorisation that commits the expense, and explains a rejection or a correction to the requester. During an absence, requests, including those already open, are flagged to the planned delegates. Property organisations can thus apply their spending rules without a decision-maker’s absence bringing cases to a standstill.