New arrivals: 14 Scout case studies

Case study · Scout

Scout: a buying organisation, its properties and each team member’s permissions

A property organisation that buys for several properties does not give every team member the same scope or the same powers. Scout is a B2B procurement platform built with Medusa and Mercur. On it, we organised each buyer account around its properties, their units and a shared storeroom. Each member receives a role and a set of properties from the moment they are invited.

B2BOrganisations

Scout connects property organisations with product suppliers and service providers. These organisations manage properties made up of apartments or units. On the buyer side, Scout’s customer is therefore not a single person. It is an organisation, for example a management company operating several buildings, with managers, on-site teams and an accounting function. A purchase there always concerns a specific place: a unit to be refurbished, or the storeroom of a building where supplies are kept in advance. Several questions then arise. Who can view which property? Who brings a new colleague on board? Who keeps authority over the account? Medusa and Mercur provide the marketplace foundation. We built the buying organisation, its portfolio and its members’ permissions specifically for Scout.

The portfolio described before the first purchase

A new organisation starts by describing what it manages. The onboarding flow has it enter details of the organisation itself, its properties, the units that make them up and its accounting allocation accounts (GL accounts). This reference data is in place before the first purchase is made. An order can therefore be linked from the outset to an existing property and a known allocation, without being reclassified after the fact.

The portfolio can then evolve. A property’s details, such as its address or its operational context, can be updated. A unit can also be created within an existing property, for example after a lot is split or an apartment is added, without recreating the building. The building, number and address of each unit can be edited.

In an organisation that manages many sites, finding the right building must remain simple. Properties can be searched by text and are displayed page by page. The list contains only the properties the person has access to. Within a property, the relevant unit is searched for in the same way. This is how a purchase is assigned to the right unit rather than to the building in general.

A shared storeroom in every property

Not everything a property manager buys goes straight into an apartment. Light bulbs, filters or paint may be bought in advance and kept on site. If these purchases were assigned to a fictitious unit or to a unit chosen at random, each unit’s history would become misleading.

Each property therefore has a storeroom unit, created automatically and kept separate from the real units. It receives supplies bought for the site whose destination is not yet known. This storeroom cannot be edited or deleted like an ordinary unit. The shared storage point therefore always exists, whatever changes are made to the rest of the portfolio.

When an item from the storeroom is used in an apartment, it can be reassigned to that unit, within the same property. As an illustration (fictitious example), a batch of taps bought for a building can stay in the storeroom and then be assigned to the unit where one of them was fitted. The final destination of the purchase thus remains visible, without distorting the original purchase.

Inviting a team member with their role and properties

Access to an organisation is by invitation. The Master, who holds central authority over the account, invites a member by assigning them both a role and the properties they will be responsible for. The new colleague therefore arrives directly in their own scope, without going through a phase in which they would see the entire portfolio while waiting for a setting to be adjusted.

The member list shows the status of each invitation. It shows who has joined the team and who has not yet accepted. An invitation that has gone unanswered can be resent. Resending does not create a second account for the same person. A member’s details can also be edited, which keeps the organisation’s directory up to date.

Local responsibilities change over time: a residence is handed over to someone else, a team member takes on an additional site. The properties assigned to a member can be viewed, to check their actual scope, and then extended or reduced. This scope also determines what the person finds in the application: when viewing a property, they can only access the sites of their own organisation that have been entrusted to them.

Roles that say who decides

Scout distinguishes several roles within a buying organisation: Master, Manager, Supervisor, Buyer, Shopper and Accountant. These roles apply to people. The Buyer role, for example, refers to a team member who takes part in purchasing. It must not be confused with the buying organisation, which is the platform’s customer.

The Master role holds a special place. It cannot be assigned or changed directly like the others. Central authority over the account therefore cannot change hands through a simple edit to a profile. Creating a user with the Accountant role is subject to a dual condition: it is reserved for the Master, and only when the organisation operates in RealPage mode. This refers to a person responsible for accounting, not to an accounting allocation account.

Managers and Supervisors carry this administration out in the field, within precise limits. They see and manage only the members who report to them on the properties they are responsible for. A regional manager, for example, can therefore look after their team without the Master having to step in each time, yet without seeing all the sites or other managers’ teams. This delegation is specific to supervisory roles: the Buyer role does not grant the right to administer the organisation.

Changing a role without leaving a request without a decision-maker

In a property organisation, some purchases must be approved before they can go through. Changing a person’s role can therefore have an immediate consequence: if they were expected to approve a pending request, their change of role could leave that request with no one to approve it.

When a role is changed, Scout therefore checks whether the person is still expected on approvals that have not been completed. This check aims to avoid removing from a pending request the person who must decide on it: the organisation can deal with these requests before reorganising its team.

At Scout, a buying organisation describes its portfolio before it buys: properties, units and a shared storeroom. Each team member joins with a role and properties defined from the moment they are invited. The Master retains central authority, and Managers and Supervisors manage their team on their own sites. Everyone thus finds the buildings they are responsible for, and purchases remain linked to the right place.

All case studies →

Something to dig into? Add this article to your office hours discussion.

See my discussion