Request a Call
Case Studies

FEWER FULFILMENT ERRORS WITH ORDER + APPROVAL AUTOMATION

Operations automation case study: this is what happens when operations stop running on “who remembers” and start running on clear workflows + alerts.
Service

Automation & CRM

Client

MetroMart Wholesale (Lagos)

Date

March, 2026

THE PROBLEM

Orders were coming in daily, but fulfilment was messy:

  • items were missed
  • approvals delayed dispatch
  • customers had to “chase” updates
  • management couldn’t see what was pending vs done

The business didn’t need more staff.
They needed an operations system.

BEFORE (BASELINE) — LAST 14 DAYS

  • Fulfilment errors (wrong/missed items): 27 incidents
  • Average approval time (manager sign-off): 4–8 hours
  • Orders delayed due to “waiting for confirmation”: ~18%
  • Manual time spent daily on updates/status checks: ~2 hours/day
  • Ops reporting: manual, inconsistent

What was BROKEN:

WHAT WAS BROKEN

  • No single source of truth for orders and statuses
  • Approvals happened in chats (easy to miss, no audit trail)
  • No automatic alerts for pending/overdue tasks
  • No daily summary/reporting to show bottlenecks
  • Too many handoffs with no ownership

What NEULEAD CHANGED

Built an operations tracker (Sheets/Airtable style pipeline)
Order ID, customer, items, payment status, fulfilment stage, owner, next step, due date.

Automated approvals
When an order hit “Awaiting Approval,” the approver got notified instantly and could approve/reject with a clear status update.

Added internal alerts + escalation
Alerts triggered when:

  • an order stayed too long in a stage
  • a high-value order was pending
  • a complaint/urgent issue appeared

Escalation went to a Telegram group for fast action.

Automated customer update triggers (optional)
When status changed (Processing → Dispatched), the system generated a ready-to-send update (or routed it to the team).

Daily ops reporting
A daily summary auto-generated:

  • orders received
  • orders pending approval
  • orders delayed
  • errors flagged
  • performance snapshot per staff

RESULT

WITHIN 30 DAYS

  • Fulfilment errors: 27 → 18 (down 33%)
  • Average approval time: 4–8 hours → 45 minutes
  • Delayed orders: 18% → 7%
  • Time saved: ~11 hours/week (less chasing, fewer manual updates)
  • Management visibility: daily dashboard + automated summary

WHY THIS WORKED

Errors don’t mean your team is bad. It usually means your system is missing.

When orders have owners, deadlines, approvals, and alerts, operations becomes predictable — and customers feel the difference.

No vanity metrics • Tracking-first • Mobile-first • Built for revenue