New arrivals: 14 Scout case studies

Case study · FN Herstal

FN Herstal: offering purchase conditions reserved for employees

FN Herstal’s consumer store also had to welcome employees with their own purchase conditions. We built into Medusa a programme that ties an entitlement to an account, applies the benefit in the cart and tracks its yearly use. Employees see their usage; the team manages codes, caps and stacking rules.

Reserved conditionsProcesses

FN Herstal is a Belgian manufacturer whose online store sells to consumers in several markets. Some of its buyers also belong to the company and benefit from a reserved programme. The need was to run these conditions in the same store, with the same catalogue, while distinguishing authorised people and framing the use of their benefit. We therefore developed an employee journey and the management tools that go with it.

Tying the employee entitlement to a store account

A visitor must not obtain reserved conditions simply because they know a shared promo code. The programme relies on employee codes that the team imports and administers. Employees activate an available code on their account to attach their entitlement to their personal space.

This activation links the benefit to an identified account in the store. The person can then find their status and the tracking of their programme when they sign in. They use the common purchase journey, with conditions matching this entitlement.

The team keeps control of which codes can be used. This system organises the allocation of a commercial benefit; verifying the person’s identity and their membership of the company remains a matter for the procedures that govern this allocation.

Applying the benefit directly in the cart

Once the entitlement is active, the store takes the employee discount into account in the cart. The person sees the benefit while preparing their purchase. They do not have to ask after their order for an amount to be corrected to reflect their status.

We built this benefit into the way Medusa promotions work. The reduction enters the order calculation and remains identifiable in the information sent to Odoo. Operations can thus distinguish the employee discount from other commercial reductions.

The programme fits into the same purchase as for consumers: employees select their items in the store, review their cart and follow the checkout steps. The reserved conditions accompany this journey without requiring a separate employee catalogue to be managed.

Showing what is used, pending and remaining for the year

The benefit is capped by a configurable annual limit. Its use therefore has to be tracked across purchases, taking pending orders into account. Without this distinction, an employee might think an amount is still fully available when an order in progress already uses part of it.

We prepared a dashboard that separates recorded usage, pending amounts and what remains. Employees can check their situation from their account before preparing a new purchase. This information gives them a common reference with the team that administers the programme.

Tracking relies on the amount actually paid to measure usage. The catalogue price of a selection is therefore not enough to explain its effect on the cap: the reductions applied to the order count too. The programme provides for an annual reset of the tracking to start a new period.

Defining how the benefit coexists with promotions

Employees may come across a promotional campaign while they enjoy their benefit. We therefore handled the meeting of these two rules. The team must be able to decide whether a promotion can be combined or is exclusive.

Stacking is allowed by default in the documented behaviour. Exclusivity must be defined explicitly to prevent the benefits concerned from adding up. When an exclusive promotion conflicts with the employee benefit, the system keeps the better discount.

This distinction gives the team a way to prepare its commercial campaigns with the programme in mind. A promotion open to the public can thus be organised with an explicit rule for employees, instead of leaving its effect on the cart to an unplanned combination.

Giving the team the means to track and correct entitlements

The programme does not stop at the initial activation. The team can search for a code, invalidate it or detach it from an account. It thus has actions to change how entitlements are allocated without handling each change outside the store.

It can also adjust usage tracking when a correction is needed. This action leaves a trace. The balance shown to the employee can therefore be reconciled with a management history, rather than changed without explanation.

Codes, caps, usage and promotion rules are the different parts of one programme. Bringing them together lets the team handle an employee’s access as well as the questions that arise after several purchases.

Employees find their benefit, their usage and what remains in their account, within the consumer store. The team keeps the means to allocate entitlements, frame purchases and adjust their tracking. The programme thus turns a reserved commercial condition into a purchase and management journey both sides can follow.

All case studies →

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

See my discussion