Purchase requests, approvals, purchase orders and vendor bills matched before anything is paid, with customs, freight and SABER costs landed on every imported product.
In many Saudi trading, F&B and manufacturing companies, orders go to suppliers over WhatsApp, vendor bills are posted as they arrive without checking the receipt, and import duty and freight never reach the product cost, so margins on goods landed through Jeddah or Dammam are guessed and input VAT is claimed on invoices that would fail a ZATCA review. Odoo Purchase runs requests, RFQs, purchase orders and receipts in one flow tied to stock and accounting, with approval rules, vendor pricelists and three-way matching, configured by Naqlah, Odoo Gold Partner in Saudi Arabia.
Vendor bills are checked for the supplier VAT number and e-invoice fields before posting, so input VAT at 15% is deductible and the purchase VAT report reconciles whether you file monthly or quarterly. Purchase taxes cover standard VAT, reverse charge on imported services and withholding tax on non-resident vendors, and purchase orders print in Arabic for local suppliers and English for foreign ones. Imports carry FASAH customs duty, freight and SABER conformity costs into product value through landed costs, so the margin on a container of green beans is real, and demand from Salla or Zid through the Naqlah Salla app and consumption from Foodics feed the reordering rules that raise the next purchase order in Odoo Inventory.
Clean input VAT
A vendor bill without a valid VAT number or QR is flagged before it is posted, reverse charge is applied to foreign service invoices and withholding is calculated on non-resident payments. The VAT return is built from bills that pass review.
Import costing that reaches the product
Customs duty, port handling, freight, insurance and SABER fees are added as landed costs on the receipt and allocated by value, weight or quantity. Product cost and margin reflect what the container actually cost.
Approval matrix by amount, category and branch
A branch manager approves consumables up to a limit, capital items go to finance, and every approval is recorded on the request. Nobody buys on a phone call.
1. Request raised and approved
A branch, site or department raises the request, and approval rules route it by amount and category, with the requester hierarchy synced from Jisr or ZenHR through the integrations Naqlah connects.
2. RFQ sent, vendor chosen, PO confirmed
Quotations are requested from approved vendors, compared on price and lead time, and the winning one becomes a confirmed purchase order in the vendor's language.
3. Goods received and checked
The receipt is scanned against the PO, quantities and quality are confirmed, and import costs are landed on the received products.
4. Bill matched, paid and VAT reported
The vendor bill is matched to the PO and receipt, posted with the correct purchase tax, paid by bank file or cheque, and included in the purchase VAT report.
Timelines depend on scope and the number of vendors and warehouses, and Naqlah gives you a clear roadmap in the first consultation.
| Area | Before | With Odoo via Naqlah |
|---|---|---|
| Ordering | WhatsApp or phone call to the supplier | Approved purchase order in the vendor's language |
| Approvals | Verbal, nobody remembers who agreed | Limits by amount, category and branch, recorded on the request |
| Receiving | Goods accepted unchecked | Receipt scanned and matched to the PO |
| Vendor bills | Posted as received, VAT fields unverified | Three-way matched and checked for e-invoice validity |
| Import costs | Duty and freight ignored in product cost | Landed on the product at receipt |
| Vendor selection | Habit and relationships | RFQ comparison and performance reports |
Everything else, we cover in a free 30-minute consultation.
Free consultation. Meet the team and get a clear roadmap in one call.
.svg)
.svg)