New arrivals: 14 Scout case studies

Case study · FN Herstal

FN Herstal: connecting the store to stock, orders and content

FN Herstal’s international store had to work with Odoo for operations and Prismic for content. We connected these tools to Medusa so that products, availability, orders and tracking information flow between them. Teams keep their own working tool, and buyers find the information they need along their journey.

E-commerceIntegrations

FN Herstal is a Belgian manufacturer whose online store serves consumers in several countries. The project went beyond presenting products and taking payment for an order. Each sale also had to reach the teams that process it, availability known in Odoo had to be reflected, and content teams had to be able to prepare pages in Prismic. We organised these connections around the Medusa store, with a clear split of the information managed in each tool.

A commercial catalogue in Medusa, availability from Odoo

To avoid each team maintaining its own version of the same information, we defined the role of each tool. Medusa holds the commercial catalogue: the products offered for sale, their variants and their translations. This information is sent to Odoo so that operations can find the items sold online.

Stock follows the opposite path. Odoo supplies the available quantities to the store. A reference sold online thus stays linked to the one the teams use to manage goods. Customers see availability fed by operations, rather than stock kept separately for display on the site.

Stock updates are complemented by a periodic catch-up synchronisation. The team also has a diagnostic view to spot mapping mismatches. The point is to be able to find out why one reference is not updating, without treating every product as if it had the same problem.

Sending the order with its items, discounts and delivery

An order must stay recognisable when it moves from the store to the operations tool. We send Odoo the customer, the items and quantities ordered, and the information needed to process the sale. Teams can pick up the order without re-entering its contents from a confirmation email.

Discounts are part of this handover. A reduction changes the amount invoiced, so it must keep its meaning in Odoo. Commercial discounts and the employee benefit are identified separately in the information sent. The team sees the conditions applied to the sale instead of having to infer them from the total alone.

Delivery follows the same logic. During checkout, the store asks Odoo for the options matching the cart and the address. The buyer chooses among the options returned. The selected carrier then travels with the order, so the choice made online can be used when the order is processed.

Passing on payment changes and cancellations

A sale keeps evolving after it is recorded. Payment may be confirmed or fail; an order may be cancelled or refunded. We connected these events to Odoo so they are not known only to the store.

Payment is handled with Mollie. The connection passes relevant changes to the operations tool, along with refund events. Cancelling an order also triggers a corresponding request to Odoo. These exchanges give teams the information they need to continue their work based on the state of the sale.

Giving the customer shipment tracking and their invoice

Information must also flow back to the store. When Odoo reports a shipment or delivery, the online order is updated and the planned notifications can inform the buyer. The tracking number lets them follow their order after payment.

We also provided for the return of the PDF invoice produced in Odoo. It is attached to the order and can be downloaded from the customer journey. The invoice is still produced in the tool responsible for that operation; the store gives access to the document for the purchase.

Support follows the same continuity. The contact form captures, among other things, the subject of the request and, where applicable, the order concerned. The request is routed to Odoo according to its subject. Teams thus receive the context they need to handle it.

Preparing pages in Prismic and showing the right products there

Editorial teams have a different job: organising the site’s pages, navigation and articles in the languages offered. Prismic gives them the space to prepare this content. Medusa keeps the commercial information the purchase must rely on.

We connected Prismic content to the store’s products. A page can present a product and lead to its product page without creating a second commercial record to maintain in the editorial tool. Presentation copy and the sale each keep their role while taking part in the same journey.

This split lets teams work on a brand page or multilingual content without moving stock and order management into the publishing tool. Each team works on the information that belongs to its activity.

The journey now links a product’s presentation, its availability, the order and the documents that follow it. Medusa handles the sale, Odoo stock and operations, Prismic content. Our work makes these roles usable together: commercial data goes out to the teams, and processing information comes back to the buyer.

All case studies →

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

See my discussion