docs.checkout.address_intelligence
Address Intelligence
Merchant-owned RTO intelligence built from source-collected DigiPin, structured address details, and delivery outcomes.
What QuantaRoute can promise
QuantaRoute should promise measurable reduction in address-discrepancy-led RTO, not blanket RTO reduction. COD refusal, impulse buying, fraud, pricing shock, and buyer unavailability are separate problems. Address Intelligence focuses on the portion of RTO where the delivery location or address details are likely the cause.
Scoring input
The checkout scorer accepts a compact record that combines DigiPin, address completeness, recurrence, payment mode, historical delivery outcomes, and micro-zone reliability.
{
"merchantId": "merchant-uuid",
"sessionId": "checkout-session-uuid",
"buyerId": "buyer-uuid",
"addressId": "address-uuid",
"digipin": "39J-438-TJC7",
"digipinVerified": true,
"digipinCell": "39J-438",
"pincode": "560034",
"pincodeMatchesLocation": true,
"flatNumber": "4B",
"floorNumber": "3",
"buildingName": "Sunshine Apartments",
"streetName": "MG Road",
"locality": "Koramangala",
"paymentMode": "cod",
"buyerOrderCount": 0,
"addressSuccessfulDeliveries": 0,
"addressRtoCount": 0,
"pincodeRtoRate": 0.18,
"microZoneRtoRate": 0.32,
"addressEditCount": 2,
"mapReconfirmCount": 0
}Scoring output
Scores are explainable by design. Each score returns a risk bucket, numeric score, confidence, reasons, and the checkout interventions that should run.
{
"riskLevel": "medium",
"riskScore": 48,
"confidence": 0.85,
"reasons": ["high_rto_micro_zone", "first_time_cod"],
"interventions": ["prepaid_nudge", "courier_delivery_note"],
"explanation": "Medium address-discrepancy risk (48/100) because of high rto micro zone, first time cod. Recommended intervention: prepaid nudge, courier delivery note."
}Intervention policy
| Risk | Default action | Why |
|---|---|---|
| Low | No intervention | Address has enough source and delivery confidence. |
| Medium | Prompt missing detail, map reconfirmation, or prepaid nudge | Resolve ambiguity without blocking good buyers. |
| High | Restrict COD, manual review, and courier delivery note | Prevent avoidable dispatch cost when address discrepancy signals stack up. |
Delivery outcome feedback
Merchants should import delivery and RTO outcomes from their OMS, Shiprocket, Delhivery, ClickPost, or internal support workflows. These outcomes power merchant-specific learning before QuantaRoute has any network-wide data.
{
"rows": [
{
"order_id": "ORD-1001",
"buyer_id": "buyer-uuid",
"address_id": "address-uuid",
"payment_mode": "cod",
"delivery_outcome": "address_rto",
"rto_reason": "house number missing",
"pincode": "560034",
"digipin": "39J-438-TJC7",
"digipin_cell": "39J-438",
"order_value_rupee": 1299,
"rto_at": "2026-06-28T10:00:00+05:30"
}
]
}Merchant dashboard
The checkout dashboard visualizes the module as an operating system for address quality.
Address RTO opportunity
Share of total RTO that appears address-discrepancy-led.
DigiPin coverage
Saved addresses and new checkouts with source-collected coordinates.
Risk distribution
Low, medium, and high address risk across scored sessions.
Intervention impact
How often reconfirmation, address prompts, prepaid nudges, COD gating, or review fired.
Delivery confidence map
Successful delivery and RTO density by DigiPin cell.
Claims to avoid
- Do not claim guaranteed total RTO reduction.
- Do not claim building-footprint existence prediction until QuantaRoute Search is ready.
- Do not claim carrier-grade routing parity with Delhivery Maps.
- Do not claim GoKwik or Razorpay-scale network risk intelligence on day one.