Platform Overview

NextRoute organizes your business into a clear hierarchy:

Tenant (your business)
├── Service Zones (geographic areas)
│   └── Master Routes (recurring templates)
│       └── Template Stops (customers on the route)
├── Customers (billing entities)
│   └── Properties (service locations)
│       └── Service Plans (pricing + frequency)
├── Daily Routes (generated from templates)
│   └── Stops (individual service visits)
└── Invoices (auto-generated monthly)

Key Concepts

Customers vs Properties

A customer is a billing entity — name, email, phone, payment info. A customer can have multiple properties (service locations). Each property has its own:

• Address and coordinates
• Service plan (determines frequency and price)
• Service zone (determines which route template)
• Bin details (count, size, location)

This separation means you can bill one customer for multiple locations, or have a property management company with dozens of addresses.

Service Zones

A zone is a geographic boundary. Zones can be defined by:

• Polygon — draw on a map
• ZIP codes — list of ZIP codes
• Radius — center point + distance

Zones help organize your service area and are linked to master routes.

Master Routes → Daily Routes

A master route (template) defines a recurring route pattern:

• Which zone it covers
• What day of the week it runs
• Which driver is assigned
• Which customers/properties are on it

The system auto-generates daily routes from master routes. Each day, the cron job:

1. Checks which templates match today's day of the week
2. Filters stops by frequency (weekly, biweekly, monthly, quarterly)
3. Excludes blackout dates, vacation holds, and service skips
4. Creates draft routes ready for dispatch

Service Frequencies