One price list for the shop, WhatsApp and the website, with rules the owner sets
A shop with two boutiques keeps one price list, read by the till, the website and WhatsApp, with margin and rounding rules the owner approves from his phone.
Project overview
This scenario illustrates what we build; it is not a client reference.
This scenario shows how a shop with two boutiques, a WhatsApp catalogue and a small online shop can display the same price everywhere and move it with simple rules: minimum margin per category, rounding, dated promotions, recalculation when the purchase price changes. The owner approves every change from his phone.
Client challenges & requirements
A shop selling home appliances and phones runs two boutiques in Conakry, a WhatsApp catalogue and a small online shop, about 300 product references in all. Each channel has its own price list, kept by hand: a label in the boutique, a PDF sent on WhatsApp, a product page on the website. When the exchange rate moves or a supplier raises its price, the owner corrects the boutique the same day, the PDF later, and the website when someone remembers.
An iron shown at 180,000 GNF in the boutique, 165,000 GNF on last week's PDF, 150,000 GNF on the website.
The customer who compares asks for the lowest price, and nobody knows what margin is left on the sale.
Main objectives
Keep one price list, read by the till in both boutiques, the website and the WhatsApp catalogue
Write the pricing rules once: minimum margin per category, rounding, promotions with a start and end date
Recalculate selling prices when the purchase price or the exchange rate changes, without retyping 300 labels
Leave the final decision on every price change to the owner, from his phone
Project solution
-
We start with the price list
A Laravel back office on PostgreSQL becomes the single reference: each item has a purchase price, a category and a selling price. The till in both boutiques, the online shop and the WhatsApp catalogue read this price; the WhatsApp PDF is generated from the same list, nobody updates it by hand any more. The owner writes his rules once.
-
If the purchase price of an item changes, then the back office proposes a new selling price that respects the minimum margin of its category. If the calculated price is not round, then it is rounded to the chosen step, for example up to the next 5,000 GNF. If a promotion has an end date, then the normal price comes back on its own the next day. No price changes without the owner: he receives the proposal on his phone, with the old price, the new one and the margin, and he approves or rejects it.
-
Once approved, the price goes to the till, the website and the PDF at the same time. A Metabase dashboard shows the margin per category and per boutique, and the list of items sold below the minimum margin. No predictive model and no competitor price tracking: written rules, which the owner can read and change. The hosting provider is chosen with the client.
Indicators to track
- Price gap between the boutique, the website and the WhatsApp catalogue on the same item
- Time between a purchase price change and the selling price update
- Share of sales made below the minimum margin
- Number of price proposals approved or rejected by the owner
- Time spent each week updating prices
Tech stack
- Back-office et liste de prix
- Laravel Livewire PostgreSQL
- Canaux de vente
- Caisse de boutique Boutique en ligne Catalogue WhatsApp (PDF généré)
- Validation sur téléphone
- WhatsApp Business API Back-office adapté au mobile
- Tableau de bord
- Metabase
- Exploitation
- Sauvegardes quotidiennes Contrat de maintenance
Frequently asked questions
No. The back office proposes, the owner decides. Each proposal arrives on his phone with the old price, the new one and the margin. Until he approves, the displayed price does not move, on any channel. One exception, planned in advance: the end of a dated promotion, which restores the normal price on the written date.
The owner enters the rate he uses, as often as he wants. Items whose purchase price is in foreign currency are recalculated in GNF with that rate, and the back office proposes the new selling prices that respect the minimum margin. Nothing is read automatically from an exchange website: the rate used is the owner's.
It is possible, but it is a written rule, not a manual exception. The owner can set a gap per boutique or per category. The website and the WhatsApp catalogue show the reference price, and the dashboard shows both prices side by side.
A similar project?
Share your goals. After the scoping call, we propose a first scope and a timeline.
A question?
Call or write to us. We reply within one working day.
+224 627 293 377
hello@prisma-soft.comServices used
The Prisma Soft services this scenario draws on.
In the same industry
Client work and usage scenarios from the same industry.
