New arrivals: 14 Scout case studies

Case study · PALAS

PALAS: from Excel to a private trade portal

PALAS sold its jewellery to the public on Shopify and tracked its trade customers in Excel, with every order re-entered by hand by the team. With Medusa, we built a management application and a private portal for shops, connected to the existing Shopify store, with no second catalogue to maintain.

B2BProcesses

PALAS is a jewellery brand. Its consumer sales go through its Shopify store, where the product pages, photos, collections and prices live. Its business with trade customers, shops and resellers, followed another path. Orders arrived by email or were taken at trade fairs. The team then re-entered them to prepare them, and both customer and order tracking were done in Excel. This way of working had served the business, but each order meant finding the customer, their details, the items and their terms, then entering everything. The brand wanted a dedicated application for its team and a space where the trade customers it welcomes could order directly. The project also had to preserve the existing Shopify store and spare the team from keeping a second catalogue up to date in parallel.

Keeping Shopify as the place where the catalogue is managed

Keeping Shopify shaped the connection between the public store and the trade area. The jewellery, its variants and its collections were already described in Shopify, and the team knew how to work there. Recreating these product pages in a new tool would have forced the team to update every new item, every photo and every price change in two places, with the risk of the two versions drifting apart.

We therefore connected the trade area, built with Medusa, to the Shopify store. The connection retrieves products with their variants, for example the same earring in several finishes or sizes, as well as the collections that group them. Product pages and public prices are still managed in Shopify, and the trade area picks up this information through automatic synchronisations. The catalogue is managed once, then presented to two different audiences.

A trade assortment selected from Shopify

Sharing the catalogue does not mean showing everything to trade customers. Not every item sold to the public is necessarily meant for resellers: one piece may be reserved for direct sales, another may be end of line. Automatically opening the whole public catalogue to shops would have taken away PALAS’s control over its trade offer.

The selection is therefore made in Shopify. The team marks there which products are offered to trade customers, and only those appear in the portal. Nothing is exposed by default. To add a piece to the trade offer or remove it, the team acts in the tool it already uses, and the next synchronisation updates the portal.

Reseller prices calculated according to PALAS’s rules

A shop does not buy at the price shown to the public. The trade area therefore had to present reseller prices without the team entering them one by one, which would have recreated the double work the brand wanted to avoid.

The synchronisation retrieves public prices from Shopify and derives standard reseller prices from them by applying PALAS’s commercial rules. When a public price changes in Shopify, the corresponding reseller price follows at the next synchronisation. Some situations fall outside the general rule, however, and specific adjustments decided by the brand are respected instead of being overwritten by the standard calculation.

Reseller price and public price side by side

In the portal, each item shows the reseller price and, when available, the reference public price. These two amounts serve different purposes.

The reseller price is what the shop pays PALAS for the piece. It is the one used for the items in its cart. The reference public price shows how the brand offers the piece to the public. It gives the buyer a benchmark to place the piece within its range, compare items with each other and prepare its in-store display. It is a point of information, not a retail price instruction. Having both amounts in view when choosing avoids having to check the public site or ask the team.

Availability that follows a shared stock

Jewellery sold to the public and jewellery ordered by shops come from the same stock network. A piece sold on the online store is no longer available to a reseller, and a quantity shipped to a shop is no longer available to the public. If each channel showed its quantities without taking the other into account, trade customers might order items that are already gone.

Availability is therefore synchronised automatically, at regular intervals, from Shopify to the trade area. The quantities offered to shops thus follow the state of the stock managed by the brand. Information also flows the other way: stock movements linked to trade orders are passed on to Shopify, which takes the items concerned into account. The aim is for the availability shown to trade customers to reflect what leaves through both channels, without asking the team to reconcile it again in a spreadsheet.

For the team: every customer and every order in one place

The first use concerns the PALAS team. The management application brings together customer companies, their contacts, their addresses and their orders. What was scattered across a spreadsheet, emails and trade-fair notes can now be found from the company record.

Not all orders go through the portal, and that is not the goal. When a shop sends its order by email or places it at a trade fair, the team finds the company and contact concerned, then prepares the order for them from data already present: contact details, addresses, trade catalogue items and reseller prices. It no longer has to rebuild the customer record or recalculate prices before starting. The gain lies in data entry and the administrative preparation of the order. Packing and shipping are still work to be done.

A portal reserved for the shops PALAS welcomes

Reseller prices and the trade assortment are not public. The portal is therefore closed by default, and PALAS decides who gets in. A shop can request access. The team reviews the request, accepts the company and invites the people who will order on its behalf.

Invited contacts sign in with a link received by email, with no extra password to remember. Once signed in, they see the trade catalogue, with the items selected by the brand, their reseller prices, reference public prices and availability.

Ordering, paying, tracking and restocking without waiting for the team

In the portal, the shop builds its cart from the trade catalogue, chooses its payment method among those PALAS offers and confirms its order. It then receives emails informing it of progress. It no longer needs the team to transcribe its selection to record its order.

A jewellery shop often reorders what already sells well for it. When it wants to restock, it can start from products it has already ordered rather than searching the whole catalogue. These items are picked up at current prices, not those of the original order. The restock thus reflects the terms in force, and the shop adjusts quantities before confirming.

Several people can buy for the same company, for example the manager and a sales assistant, or two store managers. They share their company’s order history. Each can check what has already been ordered and take over from a colleague.

Each order placed this way is entered by the customer themselves. For the team, items and quantities arrive already entered, and the order appears in the application alongside those received by email or at trade fairs. Orders from both journeys end up in the same tool.

PALAS thus has a tool to handle the orders that still go through its team, and a portal where shops prepare their own purchases and restocks. The gain comes from both sides: less data to rebuild for requests received, and data entry that disappears for self-service orders. The connection with Shopify keeps this trade business running without adding a second catalogue to maintain.

All case studies →

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

See my discussion