Skip to Content
MAFA Group · Odoo 17

Customer forms that read themselves, with a person signing off

A vision model extracts registration forms straight from incoming mail. It never writes to the database — an admin approves.

Led by Umar · ~4,350 LOC
Odoo 17 Groq Vision

The problem a client brought us

“Our sales team retypes every customer registration form into the ERP by hand — PDFs, scans, Excel sheets, sometimes a phone photo of a printout.”

Before and after

Retyped by hand

  • PDF
  • Scanned form
  • Excel sheet
  • Phone photo

Read by the model, approved by a person

One review queue

What we found and built

A pipeline that reads the forms instead: an incoming mail hook identifies which attachment is actually the registration form among the noise, a vision model extracts the fields — including Saudi VAT/CR compliance fields — and the result lands in an admin review queue for one-click approval.

Result

The model never writes to the database directly — it fills a form, a human approves it. That constraint is what made it safe to ship, and it's why the client trusted it in production from week one.

The pattern behind it

The model fills the form; a person approves it

AI earns its place where a person can check the output. Our models never write to the database directly: they draft, and someone signs off.

How we think about problems

Recognise any of this?

Most of our work starts with a message that sounds a lot like this one did.