New arrivals: 14 Scout case studies

Case study · PALAS

PALAS: card, bank transfer, deposit and balance for trade orders

The shops that resell PALAS jewellery do not all pay for their orders the same way. Some pay by card, others by bank transfer, and an order can be paid in two stages. We integrated these payments into the trade area built for the brand. Each wholesale order now shows what has been paid, what remains due and how to pay it.

B2BProcesses

PALAS creates jewellery. The brand sells it to consumers through its Shopify store and to a network of professional retailers. For a long time, this B2B business ran on Excel files, email exchanges and meetings at trade shows. We built a dedicated application for the brand with Medusa, connected to Shopify, along with a private portal where authorised shops place their orders. An order validated online then has to be paid. One shop may prefer card, another bank transfer, and an order can be paid with a deposit followed by a balance. These ways of paying had to coexist without the team having to reconstruct, for each order, who had paid what and what was still expected.

One amount, several ways to pay it

In a relationship between a brand and its resellers, payment varies from one order to the next. Habits differ from one shop to another. Some pay straight away, others prefer bank transfer. For a large order, a deposit makes it possible to commit to the purchase without paying everything on the same day. These variations are normal. They become hard to track when no tool brings them together.

When this information is scattered, someone has to reconcile a deposit announced in a message, a transfer reported by email and a balance kept in a spreadsheet. The need is to know, order by order, what has been received and what is still expected. The shop asks itself the same question: how much to pay now, how much later, and by what means.

This topic concerns wholesale orders: the shop buys the jewellery to resell it. Goods placed on consignment follow a different process: making them available is not a purchase to be paid for, and a deposit has nothing to do with stock placed on consignment.

Separating the payment method from the payment schedule

Our first choice was to distinguish two questions that are often confused. The first concerns the method: card or bank transfer. The second concerns the amount and the timing: paying everything at once, or paying a deposit and then the balance. By keeping them separate, a single order can accommodate different situations, and the team always understands which case it is dealing with.

The available flows distinguish card for the full amount, card for a deposit when it is offered, and bank transfer for the full amount. The shop sees the options actually open to its order. On the PALAS side, the team can also record partial payments received, including by bank transfer, and keep track of the outstanding balance.

The options displayed depend on what PALAS has enabled for the market concerned and on the terms set for the order. From the admin, the team can also adjust the payment terms offered on a given order. A shop therefore does not choose freely among every option: the portal presents those the brand has decided to make available.

When PALAS grants a business a commercial credit note, it can reduce the amount to be paid. It is neither financing nor an additional payment method. The credit note is taken into account once in the amount to be paid, instead of being mentioned in a message and then deducted from memory at the time of payment.

By card: pay in full, or pay a deposit knowing the balance

With card payment of the full amount, the shop pays the amount due for the order in one go. With a card deposit, the portal applies the share set for the deposit. It calculates and displays the amount to pay now and the balance that will remain due. Before validating, the shop therefore knows what it is committing to today and what it will have to pay later. Amounts are shown in the order currency.

A card payment may require authentication with the bank. A payment that has been initiated or authorised does not always correspond to money collected: the order relies on the amounts actually collected. Likewise, a recorded deposit does not mean the order has been paid. The balance remains identifiable, for both the shop and PALAS, until it is paid.

By bank transfer: details displayed, proof attached to the order

When the shop chooses bank transfer, the portal shows the bank details to use. The shop then makes the transfer from its bank, outside the portal.

If the conditions of the bank transfer flow require it, the shop attaches a proof of payment, as a PDF or an image, directly to the order. This document no longer gets lost in an inbox: it stays with the order it relates to, and the team finds it in the same place as everything else.

A proof of payment does not prove that the funds have arrived. It keeps the document sent by the shop with the order concerned. The team checks receipt of the funds before recording the payment: the attached document and the money received remain two separate pieces of information.

For the PALAS team: distinguishing what has been received from what remains

In the admin, the team finds on each order the payments linked to it and, where applicable, the proof of payment sent by the shop. A summary adds up the amounts actually collected and compares them with the order total. The team can thus see what has been paid and what is still to be received. A payment that has only been authorised is not counted as paid.

The team can also record on the order a partial payment already received, for example a bank transfer that arrived in several instalments. The tracking then keeps an amount outstanding for that same order. This means recording a sum received, without initiating a new transfer or charging a card.

For each order, the team thus distinguishes the amounts collected, the amount still expected and any proof of payment sent. Checking receipt of the transfer is still necessary; once the payment is recorded, the balance appears on the order without keeping a parallel calculation in a spreadsheet.

For the shop: finding its order and paying the balance

In its account, the shop views its order history, the payment status of each order and the amount still to be paid. When a sum remains due, it can initiate payment from its account.

The payment screens pick up the existing order. The shop does not recreate an order or redo its product selection. It pays what remains, with the methods available for that order. The amount to pay is shown in its area: the shop can resume payment without asking the team to piece its file back together.

Payment and order tracking emails accompany these steps. Above all, the portal lets everyone find what remains to be paid, and lets the shop resume payment where it left off.

Each PALAS trade order now carries its own payment status. The shop knows what it is paying now and what it will pay later. The team distinguishes a proof of payment received, a partial payment and a full payment. Any credit note is deducted once, in the right place. Ways of paying remain varied, within the limits the brand has set, without the deposit and balance of each order having to be reconstructed from messages and spreadsheets.

All case studies →

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

See my discussion