Case study · Scout
Scout: applying negotiated prices to the properties they cover
On Scout, property organisations source from product suppliers and service providers. A given supplier offers a base price to all organisations, but also agrees specific terms with some of them or for certain sets of properties. We built targeted price lists on Medusa and Mercur. The supplier prepares them, dates them, populates them from a file while controlling what is taken in, then reserves them for the properties concerned.
Scout is a B2B procurement platform for organisations that manage property made up of flats or units. It connects these organisations, and the properties they operate, with the suppliers and service providers that serve them. It relies on Medusa for commerce and on Mercur for multi-vendor operation. For a supplier, prices pose a particular difficulty. Their catalogue has a base price that applies to everyone. Yet part of their business rests on agreements made with a specific client: an organisation that manages many buildings, or a set of properties grouped in the same portfolio. These terms must apply to the right orders, during the right period, without other clients seeing them and without the supplier having to maintain a second catalogue. We designed the management of these negotiated prices around this challenge.
A base price for everyone, terms reserved for certain clients
The base price remains the catalogue reference. It applies to any property that orders from a supplier without a specific agreement with them. A negotiated price only makes sense if it is attached to those who obtained it. Applied to everyone, it would cease to be a commercial term. Attached to the wrong party, it would make a property pay a price that does not match its agreement.
We therefore separated the two levels. The supplier keeps a single catalogue with their base prices. Alongside it, they create price lists that contain only the products covered by an agreement, with their agreed prices. Each price list designates the clients it is intended for. The catalogue is not duplicated: the price list contains the exceptions, and the rest of the catalogue continues to follow the base price.
Property groups to designate who benefits from an agreement
In property, an agreement does not always follow the boundaries of a single company. It may cover all the properties of an organisation, or only a selection of buildings forming a portfolio. To express these two situations, the supplier sets up groups. A group brings together properties designated one by one, entire client organisations, or both.
By way of illustration: a supplier of cleaning products agrees one price with an organisation for all of its residences, and another price for a few buildings managed under a separate contract. They can create a group for each case and reserve a separate price list for each.
The group is used to decide who benefits from the price. The price charged remains the one the supplier entered or imported into the price list: the group does not calculate a discount and does not deduct any margin.
Creating a price list, dating it and keeping it up to date
A wizard guides the creation of a price list. The supplier names it, chooses the target property groups, then adds the products and their prices. The name makes it possible to recognise the agreement among the supplier’s other commercial offers. The price list can be activated or deactivated without being deleted.
A commercial agreement often has a set duration. The supplier can set a start date and an end date of validity. A price agreed for a season or for the duration of a contract thus applies over the intended period, without anyone having to remember to open it and then withdraw it manually when the day comes.
The price list evolves with the commercial relationship. The supplier can add products to it to extend an agreement, change an agreed price or remove a line that is no longer part of it. These changes affect neither the rest of their catalogue nor their other price lists.
The price follows the property the order is placed for
On the client side, an order is always placed for a given property. It is this property that determines the applicable terms. When items are added to the basket or changed, or when the order is confirmed, the platform looks up the groups to which the property belongs, then the prices reserved for them. The people placing orders do not have to choose a price list or recall an agreement: the price displayed takes the property’s context into account.
When a property is covered both in its own right and through its organisation, the most specific attachment takes precedence. If groups designate the property directly, they are the ones used. Groups covering its organisation only apply if no group targets it directly. The supplier can thus define a general term for an organisation, then a specific term for some of its buildings.
A property that does not belong to any group stays at the catalogue base price: the mechanism prevents a reserved price from applying by default to every basket.
Importing a price file while seeing what will be taken in
When an agreement covers many products, entering each price one by one becomes time-consuming and error-prone. The supplier can therefore populate an existing price list from a CSV file that matches product references to prices.
Before importing, they can preview the file and its columns to check how they will be read. This step does not change anything yet. During processing, problematic lines are flagged: a missing reference, a reference unknown to their catalogue, a duplicate reference or an invalid amount. They can then view the import lines and their errors to understand what was not taken in and correct their file. A given price list can only receive one import at a time, which prevents two files from overlapping.
Each import is recorded, and the original file remains available for download. If a price is disputed later, the supplier can find the file it came from.
Prices entrusted to the supplier’s administrators
On Scout, a supplier can organise their team: administrators, store managers in charge of orders and stock, and account managers who look after a portfolio of clients. Prices commit the business. Creating and changing price lists is therefore reserved for the supplier’s administrators, as are changes to client groups and their pricing associations. Store managers and account managers do not have access to these settings.
The portfolio entrusted to an account manager answers a different question: which clients they look after. It does not give them the right to set prices. A one-off negotiation on a specific order goes, on their side, through a quote request, which is separate from price lists.
The supplier thus keeps a single catalogue with their base prices, to which they add price lists that reflect their agreements. They designate the properties or organisations concerned, set the validity period, update prices from a file while seeing the rejected lines, and keep a record of each import. Property organisations order for their properties and find the terms they have been granted, with no extra step at the time of purchase.