For dark stores and q-commerce fleets

The problems

• Deliveries stall because vehicles are down and it is discovered mid-shift.
• Batteries and chargers move between stores and stop being countable.
• Every store runs its own spreadsheet with its own definitions.
• Riders change per shift, so vehicle access is loose.
• Cost per delivery cannot be compared between stores.

How RideControl solves them

• Control Tower plus planned maintenance: down vehicles are known before the shift, not during it.
• Battery and asset inventory: packs, chargers and racks tracked per store with swap history.
• Zone Guard: a zone per dark store catchment, with alerts on every exit.
• Keyfobs: access issued and blocked per rider, per shift.
• BI dashboards: availability and cost per vehicle compared store by store on one definition.

Typical setup

1. Step 1

   Group tree

   Country node, city nodes, and one hub node per dark store.

2. Step 2

   Roles

   Store managers scoped to their store, a city operations lead above them, finance across the country.

3. Step 3

   Zones

   One zone per store catchment, plus a city zone for out-of-area drift.

4. Step 4

   Assets

   Batteries and chargers registered per store, with swaps recorded at handover.

5. Step 5

   Maintenance

   Planned intervals plus reported faults on the same kanban, so tomorrow's availability is known today.

Results operators see

• 97% fleet availability tracked on the dashboard.
• Zero-gap delivery slots per store.
• Cost per vehicle under control and comparable between stores.

Which plan fits