Analytics & logs

The dashboard

Every figure compares the last rolling 30 days against the 30 before it. This is deliberate: COD behaviour moves with festivals, salary cycles and weather, and a week-on-week read will have you chasing noise.

Daily roll-ups track total orders, the COD / prepaid / partial split, RTO count, OTPs sent and verified, messages sent, abandoned versus recovered checkouts, and address corrections.

Event log

An immutable audit trail with severity INFO, WARN or ERROR. The catalogue covers:

• OTP — OTP_SENT, OTP_VERIFIED, OTP_FAILED_WRONG_CODE, OTP_RATE_LIMITED, OTP_EXPIRED, OTP_SKIPPED_RETURNING
• Checkout — CHECKOUT_CREATED, PAYMENT_MODE_SELECTED, DISCOUNT_CODE_CREATED
• Partial — PARTIAL_ORDER_CREATED, PARTIAL_DEPOSIT_PAID, PARTIAL_ORDER_EDIT_DONE
• Orders — ORDER_RECEIVED_COD, ORDER_RECEIVED_PREPAID, ORDER_RECEIVED_PARTIAL, ORDER_RECEIVED_UNKNOWN
• Messaging — MESSAGE_SENT, MESSAGE_UNBILLED
• RTO — RTO_SCORE_COMPUTED, RTO_ORDER_FLAGGED, RTO_ORDER_AUTO_CANCELLED
• Lifecycle — APP_INSTALLED, APP_UNINSTALLED, SCOPES_UPDATED

Logging is fire-and-forget, so it never blocks the critical path of a checkout.

A weekly ten-minute read

OTP send-to-verify ratio. A drop of more than ten points week-on-week is a delivery problem, not a customer problem, until proven otherwise.

Failed verifications by pincode. Repeated failures from one area mean poor coverage, one bad actor, or a delivery-hostile zone about to show up in your RTO numbers.

Unverified checkouts trending up. Three consecutive weeks of increase means something in the flow got harder — a modal change, a theme update, or copy that stopped making sense.

Message delivery status, not send status. A message that leaves and never arrives costs the same and buys nothing.

Each of these leads your RTO rate by roughly one shipping cycle. That is the whole reason to look weekly rather than monthly.