Home/Fynd TMS

AI-Native · Quick-commerce OS · Live across JioMart · RBL (West Elm + Pottery Barn) · Netmeds

Fynd TMS.

The transport platform behind JioMart's 10–30 minute delivery promise. 1000+ JioMart locations live · 95% on-time · 100% system uptime since launch. Also runs the RBL in-house furniture fleet (West Elm + Pottery Barn · 4 cities) and the Netmeds in-house medicine fleet.

Live · JioMart 1000+ locations · RBL 4 cities · Netmeds in-house fleet Building · AI conversational analytics · email→TMS · live costing · offline rider

Live · operating numbers

JioMart locations

1000+

nationwide quick commerce

JioMart system uptime

100%

since platform launch

RBL shipment automation

85%

West Elm + Pottery Barn · 4 cities

01 · What's live for Reliance today

Five modules. Four layers. One transport spine.

Fynd TMS is the transport spine for three Reliance delivery models. JioMart proves it at quick-commerce scale (1000+ stores · 10–30 min). RBL proves it at high-touch furniture grain (4 cities · slot-based · in-home assembly). Netmeds runs an in-house medicine fleet on the same platform.

Bottom-up: where an order enters → how it's routed → who executes it → what it talks to on the Reliance side. The same four layers run for all three deployments.

Layer 01 · Order ingestionLive+ email-AI Building

Multi-channel intake · email-AI extraction. Pulls orders from any OMS, ERP, WMS or POS. Gen AI captures purchase orders arriving over email and creates trips automatically (Building — see §03).

Layer 02 · Routing brainLive

Precision polygons · AI route optimization · slot allocation. Custom polygon zones per store; AI route engine against real-time traffic; slot allocator matches windows to route capacity. Modules 04–05 below.

Layer 03 · Execution surfacesLive

Control Tower · Rider App · Customer Live Tracking. Dispatcher dashboard, rider mobile app with PoD/OTP/pay-on-delivery, white-labelled customer tracking with live ETA. Modules 01–03 below.

Layer 04 · Reliance integrationsLive

SAP POS · OMS · ERP · WMS · sales channels. Every JioMart sales channel feeds order events into TMS. SAP POS receives delivery confirmations. RBL ERP gets fleet utilisation back. Netmeds OMS triggers in-house dispatch.

The five live modules.

Each module sits in one of the four layers above. Status pill and who it's live for on every card; operating outcomes are in the §02 deep-dive cards below. Click any image to enlarge.

Control Tower dispatcher console · central dashboard with route map, ongoing trip cards, automated rider allocation

01 · Layer 03 · Execution

Live

Control Tower

Dispatcher console. Integrates with any OMS, ERP, WMS or POS. AI route optimization for fastest, most cost-effective deliveries. Multi-pickup multi-drop trip composition. Automated rider allocation by earliest possible delivery.

Live for · JioMart + RBL dispatch teams

02 · Layer 03 · Execution

Live

Rider App

Fleet execution. Task-wise approach handles pickup, delivery, installation and fixing in one flow. OTP + image proof of delivery. Pay-on-delivery via QR or payment links. Real-time map navigation.

Live for · JioMart + RBL + Netmeds in-house fleets

03 · Layer 03 · Execution

Live

Customer Live Tracking

End-customer surface. White-labelled to the brand. Live rider location on map. ETA in minutes. Direct rider communication.

Live for · JioMart + RBL customer surfaces

04 · Layer 02 · Routing

Live

Precision Delivery Zones

Polygon-based serviceability. Custom polygons per store replace broad pin-codes. Manual, time-based or distance-based polygon creation. Dynamic store allocation by exact lat/long.

Live for · JioMart 1000+ store catchments

AI Route Optimization · multi-stop route visualisation with traffic-aware path drawn between waypoints

05 · Layer 02 · Routing

Live

AI Route Optimization

Routing brain. Maps fastest routes against real-time traffic. Auto-reroutes on disruption. Cuts fuel and dispatch cost by choosing the most efficient path. Supports multi-pickup multi-drop trip composition.

Live for · JioMart + RBL fleet routing

02 · Deep dive · three Reliance deployments

Same platform. Three delivery models.

JioMart uses TMS for ultra-short hops at quick-commerce scale. RBL uses TMS for slot-based, high-touch furniture deliveries with in-home assembly. Netmeds uses TMS for an in-house medicine fleet with dynamic routing. JioMart and RBL numbers come from published Fynd customer stories; Netmeds claims come from the Fynd TMS sales deck — citations inline.

Deployment 01

Live · 1000+ locations

JioMart · quick commerce · 10–30 min promise

Locations live

1000+

On-time rate

95%

System uptime

100%

Order capacity lift

3×

Precision mapping. Street-level polygons replace broad pin-code zones. Automatic optimal-store assignment based on customer coordinates. Zero coverage gaps.
New cities launched in weeks, not months. Store-onboarding flow ships new locations live within hours.

Deployment 02

Live · 4 cities

RBL · West Elm + Pottery Barn · in-house furniture fleet

DRIs · Divyendu Behera (RBL SCM) · Ravi Patere (RBL Furniture · Pan-India)

On-time rate

90%

Faster dispatch

40%

Pain-point drop

80%

Shipment automation

85%

Cities live. Delhi NCR · Mumbai · Hyderabad · Ahmedabad — all consistently meeting delivery timelines.
80% fewer clicks to process a shipment. Logistics team completes tasks in fewer steps; less decision fatigue.
Replaces WhatsApp + spreadsheets + paper PoD. Trip creation, rider assignment, proof of delivery, return pickups — all automated through the platform.
Slot-aware dispatch. Trips are created once support confirms customer availability, then assigned by region.
Manpower allocation for deliveries that need in-home assembly — paired with the Rider App task model.

Deployment 03

Live · in-house fleet

Netmeds · medicine quick-delivery

Netmeds is part of the Reliance Retail (Pharma) portfolio

Fleet model

In-house

replaces 3PL dependency

Routing

Dynamic + real-time

AI Route Optimization

Tracking

Live · per-rider

via Rider App + customer surface

Telemetry

Not yet shared

qualitative source only

Problem the source names. Inconsistent delivery times and limited control over ground operations were affecting timely delivery of essential medications and customer trust.
What TMS replaced. 3PL dependency for last-mile medicine delivery — moved to a dedicated in-house Netmeds fleet running on Fynd TMS.
Modules in production. AI Route Optimization (dynamic routing), Rider App (in-house fleet execution), Customer Live Tracking (per-order visibility).
Honesty note. Specific operating numbers (orders/day, on-time %, city count) are not in the deck source. The site does not back-fill numbers we cannot cite — telemetry pull is in flight from the Netmeds ops team.

03 · In flight · upcoming features

Six workstreams shipping next.

From the platform roadmap (deck slide 30 · "TMS of the Future"). Each adds AI-native depth to a layer that already runs in production.

01Building

AI Conversational Analytics

Natural-language queries against the dispatch graph. Personalised reports generated on demand instead of pre-built dashboards.

02Building

AI-driven order integration

Email purchase orders auto-converted into TMS trips via Gen AI extraction. Removes the manual order-entry layer that quick-commerce partners hit at peak.

03Building

Live costing & serviceability

Prioritise carriers using real-time delivery cost and service-performance signals. Replaces static carrier-tier configs.

04Building

Offline rider mode

Full Rider App functionality in zero-connectivity zones. Tasks queue locally and sync on reconnect — needed for tier-2/3 city expansion.

05Building

Invoicing & reconciliation

Auto-generates invoices and reconciles payments after delivery. Closes the cash loop without a separate finance pass.

06Building

Map-pinned task UI

Detailed task information surfaced through interactive map icons. Faster navigation for dispatchers managing 100s of concurrent trips.