New arrivals: 14 Scout case studies

Case study · PALAS

PALAS: following each customer, from conversation to order

PALAS sells its jewellery to the public on Shopify and also works with a network of trade shops. Tracking of these customers was split between spreadsheets, email threads and meetings at trade fairs. To bring it together, we built a trade application with Medusa, connected to Shopify. The team finds there each company’s contacts, their access, orders and trade-fair meetings; a messaging feature keeps the exchanges made in the portal. The team can thus pick up a file without rebuilding it, and the shop can follow its relationship with the brand from a private space.

B2BProcesses

PALAS is a jewellery brand that sells directly to the public on its Shopify store. It also distributes its creations through a network of trade retailers. On the trade side, the relationship relied on Excel files, emails and meetings at trade fairs. Each tool held part of the story: a contact noted here, a request received there, an order entered elsewhere. To know whom to reach at a shop, where to deliver, what had been ordered and what remained to be done, these sources had to be cross-checked or the memory of the person handling the customer relied on. We sought to attach each piece of information to the right company as soon as it appears, so that a customer’s story can be read in one place, from conversation to order.

One record per company, not per contact

We started from a simple observation: PALAS works with shops, and a shop often has several people. The manager sometimes places an order, then a colleague asks a question about a delivery. Another contact may take over the relationship later. If the history is attached only to the person who ordered, it fragments as soon as the contact changes.

We therefore put the company at the centre of tracking. Its record brings together the company’s details, its delivery and billing addresses, its business model and the contacts attached to it. Orders and meetings are attached to the company, beyond the single contact who initiated them. When a new contact joins a shop, they step into a relationship whose history is already known.

The business model appears on the record because it shapes what follows. A shop may buy the jewellery to resell it, or receive it on consignment and pay only for what it sells. This information is visible as soon as the file is opened, and the team no longer has to remember it or look for it in an old exchange.

Access granted by PALAS, contact by contact

The trade network is not open to everyone. A shop that wants to work with the brand submits an access request and provides the information that lets PALAS qualify it. The team reviews each request and decides whether to accept it. Control stays with the brand, and each new shop arrives with a record already built.

Once the company is accepted, the team manages its contacts’ access to the private portal. Each person receives an email invitation with a link to activate their access. From the record, the team sees which contacts have been invited and which have access to the trade area. It can also invite a new person when the shop’s team changes.

This replaces informal access management with a clear rule: the brand grants access, the shop uses it. Joining the network itself becomes a step in the tracking, in the same place as everything else.

A request received becomes an order prepared by the team

A shop can order by itself from its private space. It can also keep writing an email or placing its request at a trade fair. The team must then be able to pick up this request in the application, for the right company and the right contact, without keeping parallel tracking in Excel.

For a buy-to-resell order received outside the portal, the team enters it in the application. It opens a draft order, chooses the company, contact and address concerned, then adds the items, quantities and agreed terms. The draft remains an internal working document. The team can complete and correct it before committing to it.

Before confirmation, the team checks amounts and availability. If an item in the draft is not available in sufficient quantity, the draft flags it so the team can adjust the order knowingly. It then confirms the draft, which becomes a full order.

At confirmation, the team can choose to notify the customer. The customer then receives an email with a secure link to their order. This message informs the customer without validating the order on their behalf: confirmation is the team’s responsibility. The shop, for its part, finds the order prepared for it in its history, just like those it places on its own.

Trade orders appear on the company record, whether they were placed in the portal or prepared by the team. To know what a customer has ordered, you consult a single history, without cross-checking emails and a spreadsheet.

Trade-fair meetings stay attached to the customer

Trade fairs are a chance to meet new shops and see those in the network again. To continue the relationship after the event, you need to find which contact was met and link that meeting to their company’s tracking.

We built trade fairs into the application. The team organises its events and the terms that apply there. Each meeting can be attached to a company and a contact. When PALAS gets a contact list from a trade fair, it can import it from a CSV file. The application then matches these contacts against those already known, to avoid creating a duplicate of a shop that is already part of the network.

An order can also be linked to the trade fair where it was placed. On a company record, the team can thus see at which fairs the shop was met and which orders relate to them. The origin of a relationship or an order can be found, instead of being rebuilt from memory.

Emails that accompany each step of the order

A shop needs to know where its order stands. Confirmation, payment, preparation and shipping are all pieces of information to pass on. Writing them one by one adds repetitive work to commercial follow-up.

We tied emails to the key steps of the order: creation or confirmation, payment, preparation and shipping. For an order prepared by PALAS, the team keeps the choice of notifying the customer at confirmation. The other messages accompany the relevant steps according to the order’s journey. The content is offered in French or English according to the customer’s language preference.

Some orders benefit from a discount valid for a limited time. Reminders let the customer know the deadline, and expiry is taken into account once the period has passed. The point is to follow the terms of this offer, without confusing them with a reminder for an overdue invoice.

The team no longer has to write these recurring updates. It keeps its own messages for what genuinely needs a conversation.

An ongoing conversation between the shop and the PALAS team

Not all exchanges with the brand concern an order. A shop may have a question about a product, a delivery or a restock. Being able to pick up the thread of a conversation matters as much as finding an order.

We built messaging between the shop and the PALAS team into the portal. The history of each conversation is kept. If a conversation has been closed and a new message arrives, it reopens by itself: the thread resumes where it stopped, and the message is not lost in an exchange considered finished.

Unread message counters appear on both sides. The team sees which conversations contain unread messages, and the shop sees that a message is waiting. Messaging covers exchanges made through the portal. Emails received elsewhere stay in their respective inboxes, and the team decides what it carries over into the application, for example as a draft order.

Seeing what needs action, where it arises

Following a customer also means knowing what remains to be done. We displayed the useful signals in the screens where the team already works, so it can act without rebuilding the state of the file.

These signals answer specific situations. On a draft, the insufficient-stock alert shows what must be reviewed before confirming. On the logistics side, statuses distinguish pending orders, preparations to do and shipments to make or completed. The team sees at a glance what remains to be handled. In messaging, unread counters flag conversations containing messages to read. For tracking consignment shops, the team has a dedicated space showing requests, sales, returns and stock counts with their status. It also shows who must act next and what action is expected.

We separated two kinds of indication. Some describe a state, for example the payment status of an order. Others call for an action, such as a draft to review or an order to prepare. Likewise, an email informing the shop does not play the same role as an alert meant for the team. Signals do not decide for the team: they show it where the next action lies.

Communication aligned with the commercial relationship, with Klaviyo

PALAS also communicates with its customers by email, beyond order tracking. So that these messages reflect the actual relationship with each shop, we built a connection between the trade application and Klaviyo.

The profiles of contacts attached to active companies are enriched there with elements from commercial tracking: order statistics, by currency, and trade-fair meetings. The trade language preference is kept independently of the Shopify customer’s preference. B2B communications can thus be offered in French or English, even if the person uses another language for their personal purchases.

The brand can thus build audiences and send messages consistent with what it knows about each customer, for example according to their ordering activity or their presence at a trade fair. This connection enriches profiles without changing subscription choices: each contact receives communications according to their own consent.

An overview of the network on a map

Records let the team follow each shop in detail. The team also needs an overview of its network. We therefore added a map that locates shops geographically, with order and activity indicators, as well as the opens and clicks available for tracked emails. These indicators are not a history of the team’s mailboxes.

This map lets the team read the network differently from a list: spot the shops in an area, then check the available indicators to understand their activity and prepare commercial follow-up.

What changes in the work of the team and the shops

The first change concerns where information lives. Contacts, addresses, access, orders, trade-fair meetings and conversations are attached to the same company. To pick up a file, the team opens a record instead of gathering pieces from spreadsheets and email inboxes. A colleague can find the recorded elements of the file to take over.

The second concerns continuity between conversation and order. For buy-to-resell, a request received by email or at a trade fair is entered as a draft, checked, then confirmed. It then joins the same history as orders placed online, and the shop can be notified with a link to its order. Orders placed in the portal and those prepared by the team end up in the same tracking.

The third concerns the shops. They find their history, follow their orders and exchange with the PALAS team from their private space. The emails sent at each step keep them informed without the team having to write these messages one by one.

Finally, the team knows better where to start. Drafts to review, orders to prepare, messages waiting, consignment actions: these signals appear where the work is done. They do not replace the team’s judgement, but spare it from searching for what needs its attention.

We organised PALAS’s commercial tracking around the customer company: its contacts, their access, its orders and the meetings that mark the relationship. The team can prepare an order from a conversation, follow its progress and see the actions to handle. Shops have their history and messaging, while emails accompany the steps of their orders. The gain comes from this continuity: less information to search for or re-enter, and more room for the exchanges that truly need the team’s attention.

All case studies →

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

See my discussion