Case study · Scout
Scout: buying from several suppliers and tracking supplies to the right flat
Scout connects property organisations, which manage properties made up of flats, with product suppliers and service providers. A single need may involve several suppliers and several homes on a site. With Medusa and Mercur, we built an end-to-end purchasing journey. The basket is split between suppliers, each line can be allocated to the property’s units and accounts, and the order is then tracked through to receipt.
Scout is a B2B procurement platform for property organisations that manage properties made up of flats or units. It connects these organisations with product suppliers and service providers. For a property organisation, a purchase is not just a basket. It concerns a site, often a specific home, and must be attributable to the right accounts. It frequently involves several suppliers at once, each with its own shipping or collection locations. On arrival, what has been received still has to be recorded, along with any shortages or returns. We designed the journey that links these steps: preparing the request, the basket split by supplier, allocating the supplies, each vendor handling its share, receipt and, at the end of the chain, the invoice.
Each property with its units and its shared store
The journey rests first on a register of locations. A property manager finds the properties within their scope using a text search, in a list limited to the sites they have access to. Before displaying a property, Scout checks that it belongs to their organisation and their portfolio. In a large portfolio, each team thus works on its own sites without browsing those of others.
Each property groups its units, that is, the flats or homes that make it up, with their building, number and address. The manager can search for a unit, create one if it is missing or correct its details, without touching the property itself. The site’s contact details and context remain editable as they change.
Each property also has a special unit, created automatically: the site stock. It represents the shared store, alongside the actual homes. No one can modify or delete it. Each site thus keeps a storage point to receive supplies that do not yet have a specific destination.
Preparing the request in a shared list before buying
The need does not always arise with the person who places the order. A wish list attached to a property makes it possible to prepare it before purchase. For each need, it records the product, the desired variant, the quantity and an explanatory note. Each line can be edited or removed without losing the rest of the list. A property can have several lists, and two lists on the same site cannot have the same name, which avoids mixing them up.
Once preparation is complete, the list is marked as ready for review, provided it contains at least one need. Reviewers are alerted by a notification that the platform records, so that this handover is not lost. The list keeps its products and the history of its events, which makes it possible to understand how the need has evolved. If someone submits a version already superseded by a colleague’s change, the submission is rejected rather than overwriting that work.
The person authorised to buy for the organisation then imports the ready version into the basket of the same property. The request becomes a purchase without re-entering it line by line, and it remains attached to the site for which it was prepared.
A single basket, then one order per supplier
A site’s needs often mix items sold by different suppliers. Rather than forcing the buyer to place as many orders as there are vendors, Scout keeps a single basket. The basket is organised into groups by supplier and by the location the items ship from. The buyer can choose locations that offer collection when they prefer to pick up the supplies in person. Items that are not immediately available but can still be ordered follow a separate, clearly flagged path, instead of being mixed in with the rest.
Each line can carry a comment for the supplier, for example to specify a use or a delivery constraint. At checkout, the Mercur marketplace foundation, which we adapted, splits the basket into separate orders, one per supplier, grouped together in a single set. Payment amounts are allocated across these orders, so each share can be reconciled with the order it corresponds to. The buyer follows a single journey, while each supplier remains responsible for its share.
Allocating each supply to the right home and the right account at the time of purchase
For a property organisation, knowing what is being bought is not enough: it also needs to know which home the supply is intended for. On each basket line, the buyer can split the quantity between the property’s units and the organisation’s accounting codes. By way of illustration, part of a batch ordered for a residence can be allocated to two flats undergoing works, and the rest to the site’s shared store, each share being attached to the intended account.
If an allocation turns out to be wrong, the buyer clears it for the line concerned and redoes it. The allocation is thus decided at the time of purchase, by the person who knows where the supplies are going. It then accompanies the order.
Confirming the order within the framework set by the organisation
Several checks take place when the basket is confirmed. If an item’s availability has changed since the basket was put together, confirmation is suspended so that the buyer can review the quantities. When the organisation’s spending delegations require it, approval is requested before the orders are created. Payment on account is only accepted if the property is eligible for it with the supplier concerned.
A confirmation that has already been approved can be retried, for example after a connection drop: the retry returns the same result instead of creating a second purchase.
On the supplier side: handling its share of the order
Each supplier receives only the order that concerns it. Its team marks it as viewed, which distinguishes an order that has merely been transmitted from one that has actually been opened. It can also see which manager or location the order is assigned to. A supplier that uses its own management system can accept or reject the order and attach its internal reference to it, so that the two tracking records can be reconciled.
The order status then follows the actual processing. When a prepared order is waiting to be collected, the supplier marks it as ready for collection, and the buyer is notified before making the trip. If part of the order cannot be fulfilled, the supplier cancels only the remaining lines, without touching what has already been processed. An order that cannot be fulfilled can be cancelled with its reason, and an order’s payment can be refunded in the permitted cases.
Recording receipt and flagging discrepancies line by line
A shipment does not amount to receipt. On the organisation side, the buyer marks a delivery as received when it has actually arrived, and only for orders within their scope. When an order arrives in several deliveries, what has actually reached the site remains distinct from what is still expected.
When an item is missing or causes a problem on arrival, the buyer files a claim on the lines concerned. The supplier handles it line by line, taking into account the quantities involved. For a return, the buyer states the quantities and reasons. When the supplier confirms it has received the return, the amount still due on the purchase order is adjusted accordingly.
From the site store to the home that needs it
Not everything is bought for a specific flat. Supplies can be allocated to a property’s shared store, then find their destination later, when a home needs them. The manager then reallocates this stock to the unit concerned. This reallocation is limited to units on the same site. The supply thus keeps a trail all the way to the home where it is used, without leaving the property for which it was bought.
The invoice, the final link in the journey
The journey ends with the invoice. The supplier sets the tax applicable to its sale, then uploads its invoice as a PDF. The buyer compares the invoice with what was actually received, confirms the matches between lines and gives their approval. Scout records the identity of the person who made this decision. If the document is not suitable, the buyer can request a replacement invoice, where the supplier accepts this type of request.
When a purchase order is paid outside the platform, an authorised buyer can record the payment, except in organisations whose accounting is connected to RealPage. This declaration moves the payment tracking forward; it does not move any funds.
With Scout, a property organisation has a continuous journey, from the need identified in a property through to the supplier’s invoice. The single basket is split between suppliers, and lines can be allocated at the time of purchase to homes, to the site store and to the organisation’s accounts. Receipt is then recorded line by line. The organisation can thus track what was ordered, from which supplier, for which home and what actually arrived.