TL;DR
Getting receipt OCR to 99%+ on real inputs — crumpled thermal prints, glare, Arabic-English mixed layouts, faded ink — is not a model problem; it is a pipeline problem. Pre-processing, layout understanding, dictionary-anchored post-correction, and a confidence-gated human-in-the-loop are what separates a demo from a loyalty programme that actually accrues points correctly.
Why generic OCR fails on receipts
Receipts are the worst-case OCR input:
- Thermal print fades within weeks; characters break.
- Phone cameras add glare, blur, perspective skew.
- Layouts vary by every retailer, every promo period.
- Arabic-English mixed lines and RTL totals confuse most parsers.
- Numbers — the part you actually care about — are the most fragile.
A general-purpose OCR model lands around 85–92% on this. You need 99%+ to run a loyalty programme.
The production pipeline, stage by stage
1. Capture & pre-process
- On-device guidance: edge detection, perspective lock, blur warning before capture.
- Server-side: deskew, denoise, adaptive thresholding, glare removal.
- Reject and re-prompt if quality score is below threshold.
2. Layout understanding
- Detect retailer template (logo + structural fingerprint).
- Segment: header, line items, totals, footer.
- Handle RTL totals and bilingual columns natively.
3. Text recognition
- Recogniser fine-tuned on receipt-style fonts (thermal, dot-matrix, condensed).
- Bilingual model — Arabic + English in a single pass.
- Per-character confidence scores retained downstream.
4. Post-correction
- Dictionary anchoring against the retailer's product catalogue.
- Numeric sanity checks: line totals sum to subtotal, VAT matches rate, total reconciles.
- Date/time validation against POS timezone.
5. Confidence-gated review
- Auto-accept above threshold.
- Route to human review for edge cases.
- Every human correction feeds the retraining loop.
What we measure
| Metric | Target | Why |
| Field-level accuracy (totals) | >99.5% | The number that pays |
| Field-level accuracy (line items) | >97% | Personalisation quality |
| Auto-accept rate | >85% | Cost per receipt |
| Median latency | <2 s | UX |
| Human-review SLA | <30 s | Member experience |
| Drift on new retailer | <1 wk to baseline | Time-to-onboard |
The three habits that get you to 99%
- Onboard retailers, not receipts. A small template library plus catalogue beats a giant generic model.
- Trust confidence, not averages. Route low-confidence fields, never low-confidence receipts in aggregate.
- Close the loop daily. Yesterday's corrections must influence today's model — or you stall at 95%.
The honest takeaway
Receipt OCR is solved — as a pipeline, not as a model. The teams winning at 99%+ are the ones who treat it like a logistics product with SLAs, drift monitoring and a retraining cadence — not a one-off ML deliverable.
Take the next step
Need receipt scanning that actually holds up in production? Valus runs receipt and document OCR pipelines for loyalty, fintech and tax-recovery use cases across MENA — Arabic-English native, retailer-onboarded, drift-monitored. Book a working session:
Get in touchFAQ
Why not just use a general OCR API?
They peak around 90% on real receipts. The gap to 99% is in pre-processing, layout, dictionary anchoring and review — not the recogniser.
How do you handle new retailers?
Fingerprint the layout, ingest the product catalogue, run a one-week baseline. Most new retailers reach SLA within 5–10 working days.
Does it work on Arabic receipts?
Yes — bilingual recogniser, RTL-aware layout, Arabic dictionary anchoring. This is a hard requirement in MENA.
What about faded thermal prints?
We use adaptive thresholding and a model fine-tuned on faded inputs. Some receipts are unrecoverable; the pipeline must reject gracefully and prompt the user.
What's the biggest mistake?
Measuring average accuracy instead of field-level confidence. Averages hide the 1% that breaks your loyalty maths.



