Copy page

Hyperlocal

Client Features

The following features are enabled based on client configuration. Contact the Shadowfax team to enable them for your account.

OTP Verification

Drop OTP

Two options for drop validation:

1. Shadowfax-generated OTP — sent via SMS to the customer:

   Code
   SMS Format: 6179 is your delivery code. Please share this with Shadowfax rider on delivery. Order id: 9231754

2. Client-provided OTP — pass delivery_otp in the misc object at order creation. Shadowfax also sends this OTP to the customer via SMS.

Pickup OTP

1. COID validation — rider enters the last 4 digits of client_order_id
2. Custom pickup OTP — pass pickup_otp in the misc object and share with the delivery partner

Return OTP

When the RTS leg is configured, pass return_otp in the misc object at order creation. Share with the rider for marking RTS. By default, Shadowfax uses signature-based RTS delivery.

Pickup and Drop Geofence

Ensures the rider is within a configured radius before marking pickup or delivery. Pass delivery_geofence_radius (in meters) in order_details.

Geocode Drop Location

When enabled, the drop address is geocoded into latitude and longitude. Pass a complete Google-compatible address for accurate geocoding.

RTS (Return to Source)

If SKUs are not delivered and need to be returned to the store, RTS must be enabled. Confirmation options:

1. Signature Based — standard (default)
2. Return OTP Based — pass return_otp in misc at order creation

See Order Lifecycle for the RETURNED_TO_SELLER status and Callbacks for the RTS callback payload.

See the Place Order API for all optional fields.