Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Definitions

  • Plan - A collection of orders that will be distributed as a batch (i.e. a shift for a given date)

  • Route - A collection of stops to be assigned to a driver

  • Stop - A location on a route where there are customers

  • Customer - An order/customer (customer name/phone presented to the driver) that has one/many deliveries

  • Delivery - An item (name presented to the driver) to be delivered to a customer (or picked up)

  • Driver - The courier that is performing the distribution - using the mobile app. Drivers are created within a company.

  • User - Personell that plans the distribution and assigns routes to drivers. Users might have access to multiple Companies. Two main-types os users:

    • Users connected to one/multiple distribution-companies

    • Users connected to one/multiple CustomerSystems. A supplier that has outsourced distribution to multiple distribution-companies, but still has insight and customer-service

Core Configuration

  • Company

    Status
    colourGreen
    titleRequired

    The local distribution-company that has drivers to dispatch.
    Input needed: CompanyName + Country (NO, SE)

    • DeliveryTime Rules

      Status
      titleOptional

      How long time does it take to service a customer in the given zip-interval? Can be rules for a Company or combination Company + CustomerSystem. Default is 3 minutes per customer.

  • CustomerSystem

    Status
    colourGreen
    titleRequired

    Each product-type can have a configuration. Normally a company has one CustomerSystem defined, but it can have multiple. And a CustomerSystem CAN be shared with multiple Companies.
    Input needed: CustomerSystemName + Country (NO, SE)
    Rules a CustomerSystem can have:

    • Acknowledgement Rules
      Defining what actions/policies you want for the drivers.

      • Quick-Actions

        Status
        colourGreen
        titleRequired

        This is the button(s) where the driver indicates a successful delivery/pickup for a customer.

        • Available types (choose at least one): CUSTOMER, DOOR, DELIVERED, PICKED_UP

        • Proof of Delivery (picture)

          • Choose (for each type) if driver has to take a picture when acknowledging. Will be visible in the dashboard

      • Deviations

        Status
        titleOptional

        • Available types: CANT_FIND(customer), MISSING, NOT_HOME, DAMAGED, NOT_ACCEPTING, OTHER

        • Choose context (for each type): Customer or Delivery/Product

        • Choose (for each type) if you want the driver to always add a comment when registering a deviation

    • Scanning (if items has PARCEL_NUMBER and a label with barcode/QR-code)

      Status
      titleOptional

      • Choose if you want the driver to Scan items when loading the truck

      • Choose if you want the driver to Scan items before delivering to customer

    • Notification Rules

      Status
      colourBlue
      titleAddon feature

      SMS can be triggered for certain events (with custom SMS-message). This feature needs additional setup/agreements. Available events:

      • “Soon there” - Driver on his/her way and is estimated to be there within X minutes.

      • “Successful delivery/pickup” - When driver selects a QuickAction (successful delivery/pickup)

Example Configuration

Suzy Shoes has activity in two cities and wants to use Plan & Go. Since operation in each city is very autonomous we create two companies, but they share the same CustomerSystem. See an example-setup below:

...