Quality checks at receiving, production and delivery, with every failed check becoming a tracked alert, in Arabic and English.
Saudi factories and distributors are asked for inspection records by SFDA, SASO, auditors and customers, yet most checks still live on paper sheets and WhatsApp photos. Odoo Quality adds control points to the receipts and work orders already running in Odoo Inventory and Odoo Manufacturing, so each inspection is done inside the operation and each failure becomes an alert with a root cause, a corrective action and an owner.
Worksheets and instructions run in Arabic and English, so a mixed-nationality floor team and an Arabic-speaking quality manager read the same check. Lot and serial records give the traceability that SFDA inspections, SASO Quality Mark surveillance and HACCP audits ask for, with evidence photos and completed worksheets attached to the receipt or work order itself. As an Odoo Gold Partner in Saudi Arabia, Naqlah configures the control points around the certifications your factory actually holds.
Audit evidence on the record
Every check, photo and alert sits on the receipt or work order where it happened. When an ISO 9001 or HACCP auditor asks for the history of a lot, you filter the record instead of collecting paper.
Lot traceability for SFDA and recalls
A failed lot is blocked at receiving or after production and traced from supplier to customer in minutes. Expiry and lot data stay on the same stock moves that Inventory already tracks.
Vendor quality that feeds purchasing
Failure rate per vendor is reported from real inspection results, not memory. Purchasing sees which supplier keeps failing at receiving before the next order is placed.
1. The receipt triggers the check
When the shipment is received in Inventory, the control point opens the worksheet on the operator's tablet, in Arabic or English, with the measurement or photo required.
2. A failure creates an alert
A measurement outside tolerance or a rejected photo check creates a quality alert tagged with the product, lot and vendor, and the lot is moved to quarantine instead of stock.
3. The quality team acts
The team assigns a root cause and a corrective action on the alert, decides whether to return, rework or scrap, and the lot stays blocked until the alert is resolved.
4. The record closes and reports update
The alert closes, the vendor record shows the event, and the failure rate reports used by Purchase and management update on the same Odoo, with returns from Salla orders linked back when they are the trigger.
Timelines depend on the number of products, sites and certifications in scope, and Naqlah gives you a clear roadmap in the first consultation.
| Area | Before | With Odoo via Naqlah |
|---|---|---|
| Incoming inspection | Paper sheets filled after the goods are already on the shelf | Check on the receipt, lot blocked automatically on failure |
| Evidence | WhatsApp photos scattered across phones | Photo attached to the operation and the lot |
| Corrective action | Verbal instruction, nobody tracks closure | Alert with owner, root cause and stage |
| Vendor performance | Unknown until a customer complains | Failure rate per vendor, visible to Purchase |
| Audit preparation | Weeks of collecting documents before SFDA or ISO visits | History already on each receipt and work order |
| Language | English forms the floor team struggles with | Arabic and English worksheets on the tablet |
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)
