A supplier in another country, and a landed cost you know before you sell
Purchase orders in the supplier's currency, a receipt that raises the balance and updates the cost, and a match between the order, the receipt and the invoice — so no invoice is paid for goods that never arrived.
A complete purchasing cycle from RFQ to payment
Purchase orders
An order in the supplier's currency with an expected delivery date.
You know what was ordered and when it lands without searching a chat.
Three-way match
Order, receipt and invoice compared before payment.
No invoice is paid for goods that never arrived.
Key Features
Purchase orders in the supplier's currency — manually or automatically at the threshold
Order, receipt and invoice matched before payment
Landed cost allocated across the shipment's items
Supplier balances and due dates on a single screen
Purchasing from request to payment
From the request for quotation to settling the invoice, every station leaves a record — so no difference goes missing between four stations.
Request for quotation
Sent to several suppliers and compared on price and date.
Purchase order
Issued in the supplier's currency after comparison, with an expected delivery date.
Receipt
The quantity raises the location's balance and average cost is updated.
Invoice and match
The invoice is matched to order and receipt before payment, and creates its entry.
Every station leaves a record, so a difference surfaces before payment rather than in a stock count months later.
A complete purchasing cycle from RFQ to payment
Orders in the supplier's currency, a match before payment, and landed cost that reaches the item itself
Automatic purchasing
Instead of discovering a shortage too late, the purchase order reaches your supplier before the item runs out.
You set two numbers per item: a minimum level that means it has to be ordered, and a maximum level you want stock to reach after the purchase. Snad handles the rest — it watches stock daily, works out the difference, prepares a purchase order for the shortfall, and sends it to that item's supplier over WhatsApp and email as a PDF carrying your company logo.
Minimum level
The reorder point — once an item's balance drops to it, the item has to be ordered.
Maximum level
The balance you want stock to reach once the order arrives; the gap between the two numbers is the quantity ordered.
And both levels can differ from one warehouse to another.
"Suggest levels" button
Calculates both levels from your actual sales and each supplier's lead time.
Bulk assignment
Suppliers and levels for a group of items at once, with search and filters.
Two operating modes
Fully automatic sending, or a suggested order that waits for your approval.
Safety limits
An approval amount threshold, a daily spending cap, and the check hour and days in your own timezone.
WhatsApp and email together
Each channel's status is visible, and you are alerted if both fail.
A supplier reply page
They confirm the order, set the delivery date, and adjust quantities and prices — no account, no app, no training.
One-click invoice conversion
Using the figures the supplier confirmed, so stock rises and the entries are recorded.
A log that explains every decision
"Why wasn't this item ordered today?" — the answer is written out for you.
Preview before it runs
A button that shows what would have been ordered today, without creating an order or sending a message.
How the cycle works
Setup
Once: set the levels, make sure every item has a supplier and every supplier a contact channel, then choose the operating mode and safety limits.
Daily check
At the hour you chose, Snad compares each item's balance against its minimum level. Once a day.
Preparation
It works out the shortfall, deducts what is already on order but not yet received, and groups items from the same supplier into a single order.
Approval
If you chose suggested-order mode: review, adjust, then approve — or cancel.
Sending
The order goes to the supplier over WhatsApp and email with a PDF and a reply link.
Supplier reply
They confirm what they can supply, at what price and when — or decline. You get an instant notification and their figures appear next to yours.
Receipt and invoice
When the goods arrive you hit "convert to purchase invoice", so stock rises and the entries are recorded.
The cycle closes
The higher balance makes Snad skip that item tomorrow, and if it is still short only the remaining gap is ordered.
- A purchase order changes neither your stock nor your books — it is only a request to the supplier, and the accounting impact stays in the purchase invoice exactly as it is today.
- A supplier confirmation means "I will supply it", not "it has arrived" — which is why automatic conversion to an invoice is off by default.
When does buying without a system get expensive?
Five signs that cash is leaking from the purchase cycle, not from your selling margin
- 1
The supplier invoices in one currency and you pay in another
Between the order date and the settlement date the exchange rate moves, so the true cost becomes a number you learn after the moment you needed it for pricing. Recording the order in its own currency and posting it in your books' currency makes that difference visible instead of surprising.
- 2
Nobody matches the order to the receipt to the invoice
You ordered a hundred, received ninety, and were invoiced for a hundred. Without a three-way match the invoice is paid in full, and the gap only surfaces in a stock count months later — if it surfaces at all.
- 3
Landed cost never reaches the item cost
Freight, clearance and insurance are posted on their own, leaving the item carrying only its invoice price. The result is a margin that looks healthy on paper and never shows up in cash.
- 4
Purchase orders are sent and never tracked
An order in an email, a confirmation in a chat, and a delivery date in somebody's memory. When the supplier is late nobody finds out until the item runs out on the shelf.
- 5
Supplier balances are added up by hand
What you owe suppliers and when it falls due is the number that decides when you pay and when you negotiate. When it only appears by opening several files, some invoices are paid early and others slip late for no reason.
From ordering by message to a purchase cycle
The difference shows up at the fifth supplier, not the first
Buying by message
- The order is text in a chat
- Receipt is confirmed on trust
- Cost is the invoice figure and nothing else
- Follow-up depends on whoever sent the order
A controlled purchase cycle
- An order in the supplier's currency with an expected delivery date
- A receipt that raises the balance and matches the order
- Freight and clearance folded into the item cost
- Supplier balances and due dates on a single screen
A purchase cycle is not built because the team cannot be trusted. It is built because buying across a border passes through four stations — order, shipment, receipt, invoice — and every station without a record is a place where a difference goes missing that nobody is looking for.
The rest of the platform
The apps that run on the same database — switch on what you need today and add the rest when you need it
Available on every plan
The purchasing app is available on every plan, and the number of suppliers does not change the price — what differs is users and how many apps run at the same time.
And the Starter plan begins at zero riyals.
Compare plansFrequently asked questions about Purchases
Apps that run on one database
Questions before you subscribe
Not seeing your question? Write to us
Switch on what you need today
Open the account and start the same day — no setup fee and no implementation team.
Pricing