Start with the lab-to-dentist process
Confirm how clinics submit teeth, restoration details, dates and files, and what they can see after submission. Arabic and English should work as genuine interfaces, including RTL where relevant, rather than being limited to translated labels on a few screens.
Check production depth
Ask whether the lab can configure stations and different restoration routes, manage technician permissions, record issues and perform QC. A Saudi-specific label does not compensate for a system that cannot represent the actual production floor.
Verify Saudi financial functionality precisely
Review SAR pricing, VAT settings, legal identity, national-address fields and bilingual invoice output. If ZATCA is mentioned, determine whether the feature is only a Phase 1 basic QR or includes Phase 2 integration. These are materially different capabilities.
- Default and configurable SAR pricing
- VAT number and Saudi tax-profile validation
- Arabic and English invoice presentation
- Explicit statement of any FATOORA connection or its absence
Plan data and team adoption
List the dentists, catalog, technicians, stations, materials and opening balances that must be prepared. Test a real case in Arabic and English from order through invoice. Choose a system whose claims can be demonstrated in that workflow.
Questions labs ask
Does a ZATCA QR mean Phase 2 integration?
No. A Phase 1 basic QR does not imply clearance, reporting, signing or FATOORA connectivity.
Why does Arabic RTL matter?
It makes navigation, forms and case review natural for Arabic-speaking lab and clinic users.