← Toate rapoartele

Livrat

Email confirmation switched on, plus a transparency tool that shows why a courier was chosen for a delivery

Operations / Trust

We turned on email confirmation for new partner and fleet sign-ups, so a new partner now receives a one-time secure link to confirm their address - tested end to end on our own mailbox. We also added a behind-the-scenes scoring tool that, for every delivery, records which courier our system would pick using a richer set of signals (reliability, fairness, distance, cash-handling limits and more) and compares it with the courier actually offered the job. Dispatchers can now see why a courier was chosen and why others were not. This runs in observe-only mode: it changes nothing about how deliveries are assigned today, it only makes the decision transparent and prepares a safer future upgrade.

  • email
  • dispatch
  • operations
  • couriers
  • quality

What changed

  • Email confirmation for partner and fleet sign-ups is now live; the secure link confirms once and cannot be reused.
  • A new dispatch transparency tool records, per delivery, the eligible couriers, the system's preferred pick, and the reasons any courier was excluded.
  • Dispatchers and administrators can open a 'why this courier' view for any delivery.
  • The smarter scoring runs in observe-only mode - real delivery assignment is unchanged.

Why it matters

Confirming a partner's email reduces wrong-address sign-ups and builds trust from the first step.

Delivery assignment used to be effectively closest-courier-first with no visibility. The new tool exposes the full picture - reliability, fairness, distance, cash limits - so the team can verify the system is fair before we ever let the richer scoring make live decisions.

Safety

  • Observe-only: the transparency tool can never change who gets a delivery, and is fully reversible with a single switch.
  • No personal courier data (names, phones) is used in scoring or shown - only operational metrics.
  • Reviewed by independent automated reviewers; the one improvement they suggested (bounding memory use) was applied the same run.

Commit: e7aff34