Case study · Scout
Scout: giving each supplier team member the right portfolio and the right access
Scout connects property organisations with product suppliers and service providers. A supplier does not sell alone there: it has stores, stock, sales representatives and a head office that keeps control over prices. In Scout’s supplier workspace, built with Medusa and Mercur, we organised these teams around distinct roles. Each team member is given stores, a territory or a portfolio of properties, and everyone finds the orders, quotes and alerts that concern them.
Scout is a B2B procurement platform. Its customers are property organisations that manage properties made up of apartments or units. For maintenance, equipment or call-outs, they find product suppliers and service providers there. The platform is built on Medusa and on Mercur, a marketplace foundation that can host multiple sellers. Yet the way a B2B supplier operates goes beyond that of a shop run by a single person. The same company may serve residences from several depots, assign accounts to different sales representatives by region or by customer, and reserve certain decisions for its head office. An account shared by the whole team would show everything to everyone. Nor would it say who should respond to an order or a price request. We therefore designed suppliers’ internal organisation: who does what, within which scope, and who is notified when a property places an order or requests a quote.
Three roles for a supplier’s team
The supplier workspace distinguishes three roles. The administrator manages all of their company’s activity on Scout: the team, the catalogue, orders, pricing and settings. The store manager works from one or more physical locations, with their orders, products, stock and delivery. The account manager, the equivalent of a sales representative, looks after customers. They view those customers’ orders, products, stock and statistics, and they work on the quote requests in their portfolio.
These roles reflect two ways of organising operations on the ground. The first follows the locations from which goods are shipped. The second follows the customers served. A supplier can thus entrust order preparation to its store teams, relationships with property organisations to its sales representatives, and keep at head office the decisions that commit the whole company.
These roles concern only the supplier’s team. Property organisations, for their part, have their own roles for buying, supervising or approving spending. A supplier store manager is not a manager on the customer side, and the organisation that buys is not to be confused with the team member who, within it, places the order.
The store manager works from their locations and their stock
For a supplier, a store or depot is first and foremost a real place, with an address from which products are shipped. Each location can carry specific conditions, flagged on the products that depend on it, for example an offer specific to that depot. It can also be given its own geographical service zones, that is, the areas it serves, as well as its own delivery options. In-store pickup can be enabled or disabled location by location, without affecting the other depots. A zero-cost delivery option must be confirmed explicitly: a forgotten rate does not accidentally become free delivery.
Stock follows the same logic. Quantities are held per item and per location. They can be adjusted manually or imported from a warehouse file, either added to existing levels or replacing them. The file format can be saved for reuse in the next import. An import launched by mistake can be cancelled while it can still be interrupted.
The store manager is attached to one or more locations. This attachment gives them access to their stores’ orders, not to all of the company’s orders. However, they have no access to general settings, pricing or quotes: commercial negotiation is not part of their role.
The account manager looks after a territory or a portfolio of properties
A sales representative is defined not by a depot but by the customers they look after. Scout offers two ways of drawing this scope. The first is geographical. The supplier creates territories and assigns them to its account managers, and the properties located within a territory fall within the scope of the sales representative responsible for it. When a territory is created at the time a sales representative is invited, the tool rejects any overlaps detected with the same supplier’s existing territories.
The second way is the portfolio. The supplier builds groups that bring together properties selected one by one, entire property organisations, or both. A group that includes an organisation covers all of its properties, and a property included both directly and through its organisation is counted only once. This approach suits accounts that do not respect the boundaries of a map: as an illustration, an organisation that manages residences in several regions can be looked after by a single point of contact. The list of groups shows, for each one, the accounts brought together and the available managers, which helps avoid mistakenly assigning a portfolio that has already been allocated.
The two approaches remain independent. Assigning a group of properties to a sales representative does not assign them any store, and attaching a manager to a depot does not give them a customer portfolio. The supplier can organise its sales force around its customers and its logistics around its locations, without one choice dictating the other.
Inviting a team member with their scope already defined
Each team member joins the supplier workspace by invitation, with their own access. The invitation specifies the email address, the role and the assignment. For a store manager, at least one location must be designated. For an account manager, an existing territory can be reused, a new one created, or a group of properties chosen.
These assignments are not merely a mention in the invitation message. They are recorded as soon as the invitation is sent, then applied to the team member’s account when they accept. The administrator tracks pending invitations and can already see which portfolio or store has been planned for a person who has not yet logged in.
Delegation remains controlled. A store manager can invite an account manager, but cannot invite an administrator or another store manager. Later on, a member’s role or scope can be changed, for example when a sales representative takes over a territory or a manager takes charge of a new depot.
Everyone finds the orders and quotes within their scope
For a team member to view an order, it must first belong to their company. The role then comes into play. The administrator sees their supplier’s orders. The store manager sees those relating to their locations. The account manager sees those of the properties they cover. The sales representative views these orders without modifying them: preparation remains the responsibility of the stores and the administration. The principle is therefore that everyone finds the files within their scope, without the sales representative becoming the person who fulfils the order.
Quote requests follow the same division. When a property requests a price for a specific order, the account manager whose territory or portfolio covers that property finds it in their list and can work on it. A sales representative who has not yet been assigned a scope sees no quotes. Some decisions nevertheless remain with head office: declining a quote request is reserved for the administrator. Pricing and the customer groups to which it applies can only be changed by the administration, not by sales representatives.
Notifying the right people at the right time
Receiving an order is not enough: the people concerned also need to know about it. For order-related events, Scout gathers the relevant recipients: the supplier’s administrators, the managers of the store from which the shipment leaves and the account managers who cover the property. A person concerned in more than one capacity receives only one message. If no one can be identified, the supplier’s general address is used as a last resort.
A quote request is sent to an account manager whose scope covers the property. Failing that, it goes to the supplier’s general address or to an administrator. This routing indicates who the matter falls to first. It does not lock the file or make it a matter reserved for a single person.
Finally, each team member sets their own notifications by category, by email or in the application feed. A store manager can thus keep the alerts that are useful to their work without being swamped by the rest, and this setting does not change their permissions.
With this organisation, a supplier on Scout brings its team on board without a shared account. Stores work on their locations and their stock, sales representatives look after a territory or a portfolio of properties, and the administration keeps control of pricing and of declining quotes. For property organisations, their orders and price requests are followed up by the people responsible for their account or for the stores that serve them.