Case Study · 01 / 10 Logistics & 3PL Save as PDF ↓
Document intelligence · 7-week build

The invoice that stopped touching 7 people.

How a Dubai 3PL cut document processing from 4 days to 18 minutes — without firing anyone.

ClientMeridian Cargo LocationJebel Ali, UAE PublishedMay 2026
Industry
3PL · Customs · Last-mile
Scale
8,400 shipments / month
Team
142 employees · $14M ARR
Engagement
7 weeks to production
Outcomes · 90 days post-launch
4.2d → 18m
Avg document processing time, from 4.2 days to 18 minutes
−87%
Error rate collapsed from 11.3% to 1.4%
6.6×
Documents per ops FTE per day — 47 → 312
§ 01 · The company

A Jebel Ali operator running on Sunday-night WhatsApp.

Meridian Cargo Solutions moves 8,400 shipments a month across the UAE, Saudi, and Oman. 142 employees, roughly $14M ARR, mostly mid-market e-commerce and FMCG. Customs clearance, last-mile, reverse logistics — the full chain.

Our protagonist is Karim Haddad, Head of Operations. What kept him up: every Sunday night he'd open WhatsApp to 30+ messages from clients asking where their proof-of-delivery was, why an invoice was wrong, or why customs got delayed because the commercial invoice didn't match the bill of lading.

Operating regionGCC · 3 markets
JEBEL ALI UAE · HQ DAMMAM SAUDI MUSCAT OMAN 8,400 SHIPMENTS / MO 3 CUSTOMS REGIMES
Primary hub
Secondary
— — —  Trade lane
§ 02 · The problem

2,800 documents a day. Each one touched by seven hands.

Daily flow

Every shipment generated 6 to 9 documents: commercial invoice, packing list, bill of lading, certificate of origin, customs declaration, delivery note, POD. Each one passed through 7 hands on average — shipper rep → ops coordinator → customs clerk → finance → account manager → client → finance again for reconciliation.

01SHIPPER 02OPS COORD 03CUSTOMS 04FINANCE 05AM 06CLIENT 07FINANCE↻ EACH DOCUMENT, 7 TOUCHES, 38 – 96 HOURS 11.3% ERROR RATE

The errors weren't exotic: typos in HS codes, mismatched weights between BoL and invoice, wrong currency conversions. Each one meant a customs hold, an angry client email, or a 3-week payment delay. Finance was carrying $1.8M in stuck receivables at any given time because of doc mismatches.

Breaking pointMarch

A single HS code typo on a 22-container shipment for Meridian's biggest FMCG client triggered a 9-day customs hold in Dammam. The client invoked the SLA penalty clause. Karim spent that weekend on calls instead of at his daughter's birthday.

$47,000 + the relationship

Ripple effects: ops team on 11-hour days, two coordinators quit in Q1, finance close slipped from day 5 to day 12 every month.

§ 03 · The solution

One document-intelligence pipe between intake and CargoWise.

Architecture

Vynara built a document intelligence layer that sits between Meridian's email / WhatsApp intake and their TMS. Documents land, get classified, extracted, cross-validated against the shipment record, and either auto-posted or flagged with a specific reason.

Seven weeks from kickoff to production. Humans stayed in the loop for exactly two things — everything else moved without a coordinator touching it. Customs clerks shifted from data entry to handling the 8% of edge cases that actually needed a brain.

Humans stay in the loop only when
confidence < 92% OR value > $5,000
§ 04 · How it works

The same chain, redrawn. From 7 touches to 1.

Before · Manual chain 7 touches
  1. Client email / WhatsApp lands in shared inbox
  2. Ops coord downloads + renames file
  3. Manually keys data into CargoWise15–20 min / doc
  4. Customs clerk re-verifies against BoL
  5. Finance pulls for invoicing — re-keys again
  6. Account manager reviews, sends to client
  7. Finance reconciles on payment↻ error loop risk
After · Vynara pipeline 1 touch (exceptions only)
  1. Auto-ingest from email / WhatsApp + classify across 8 doc types
  2. Extract fields with vision LLM + structured parser
  3. Cross-validate BoL weight ↔ invoice ↔ packing list
  4. Confidence > 92% AND value < $5K → auto-post to CargoWise92% of volume
  5. Else → route to specific human with pre-filled exception card
  6. Slack alert to AM only if client-facing issue
§ 05 · The numbers

Six metrics. Same engagement. 90 days.

Avg document processing time−99.7%
Before4.2 days
After18 min
Error rate−87.6%
Before11.3%
After1.4%
Documents per ops FTE / day+6.6×
Before47
After312
Stuck receivables−82.8%
Before$1.8M
After$310K
Monthly finance close−8 days
BeforeDay 12
AfterDay 4
Customs hold incidents−87.0%
Before23 / mo
After3 / mo
§ 06 · The timeline

Seven weeks. No mystery middle.

Phase
W1
W2
W3
W4
W5
W6
W7
Week 1Doc audit · 1,400 samples · 19 invoice variants
AUDIT
Week 2Classify + extract prototypes · model bake-off
PROTOTYPE
Week 3Cross-validation · 34 business rules mapped
VALIDATE
Week 4CargoWise REST integration · exception UI
INTEGRATE
Week 5Parallel run · shadow mode · 6 regressions caught
SHADOW
Week 6Soft cutover · 2 clients · 94.1% straight-through
CUTOVER
Week 7Full rollout · team → "exception specialists"
LIVE
§ 07 · What they said

The metric nobody puts in a case study.

"

I stopped checking WhatsApp on Sundays. That's the metric nobody puts in a case study but that's the one that matters to me.

KH
Karim Haddad
Head of Operations · Meridian Cargo
"

I was worried we'd have to let people go. We didn't. We doubled volume per person and finally took on the Saudi expansion we'd been pushing back for two years.

RS
Reema Saleh
CFO · Meridian Cargo
§ 08 · The takeaway

The pattern is portable.

Most companies don't need an AI strategy. They need one specific pipe rebuilt.

If your ops team is keying data from PDFs into another system, you have this problem — regardless of whether you call yourself logistics, manufacturing, or a law firm. Classify, extract, validate against a source of truth, route exceptions.

One-liner Your invoices touch 7 people before getting paid. We cut that to 1, in 7 weeks.
Send us your messiest inbox →