O2VEND Retail ERP
  • Getting Started
  • Ecommerce
  • Back Office
  • POS
  • Agent App
  • PIM
  • Communication
  • CMS
  • OMS
  • WMS
  • O2C
  • Accounting
  • Reports
  • Themes and Apps
Search Results for

    Show / Hide Table of Contents
    • Order Management System
    • Order Management Overview
    • Quotation Management
    • Request for Quotation
    • Work Order Management
    • Purchase Order Management
    • Subscription Orders
    • Active Carts Monitoring
    • Sales Beats Management
    • Sales Routes Management
    • Beat Runs Tracking
    • Route Run Tracking
    • Create Sales Order
    • Edit Sales Order
    • Goods Issue in Sales Order

    Beat Run Initiation in O2VEND – Step-by-Step Daily Delivery Planning

    Learn how to plan daily or multi-day deliveries in O2VEND using the Beat Run Initiate screen. Organize beats, orders, and shipping classes efficiently for on-time deliveries.

    The Beat Run – Initiate screen is used to plan daily or date-wise deliveries for a selected Beat.
    This page converts a delivery area into an actionable delivery run by mapping orders, shipping class, and dates.

    The Beat Run Initiate screen in O2VEND transforms delivery areas into structured delivery plans.
    It connects beats, dates, shipping rules, and orders into one controlled delivery workflow.

    This step is essential for accurate, scalable, and on-time deliveries.

    What Is a Beat Run?

    A Beat Run represents a delivery plan for a specific Beat and date range.

    In simple terms:

    Beat = Delivery Area
    Beat Run = Delivery execution plan for that area

    Beat Runs help control:

    • Which orders go out
    • On which date
    • Under which delivery type
    • For which area

    Beat Run – Initiate Screen

    The Beat Run – Initiate screen is used to convert a delivery area into a date-wise delivery plan.

    Navigation Path

    O2VEND Back Office → Beat Route → Beat Run → Initiate


    Beat Run – Initiate Screen Explained

    Start Date

    Defines the starting date of the delivery run.

    Example shown:
    24-12-2025

    Orders from this date onward are considered.


    End Date

    Defines the ending date of the delivery run.

    Example shown:
    25-12-2025

    Helps create multi-day delivery runs when needed.


    Code

    Optional reference code for the beat run.

    Used for:

    • Internal tracking
    • Reports
    • Audit references

    If left blank, the system can auto-generate one.


    Beat

    Selects the delivery area for which the run is created.

    Example shown:
    Anna Nagar East

    Only customers and orders under this beat are included.


    Shipping Class

    Defines the delivery type applied to this run.

    Example shown:
    Regular Delivery

    Ensures correct delivery rules, timelines, and charges.


    Orders & Shipment Tabs

    Orders Tab

    Displays:

    • Customer Name
    • Order Number
    • Order Date
    • Order Status

    Shipment Tab

    Used to:

    • Convert selected orders into shipments
    • Prepare orders for delivery execution
    • Move towards Route Run (actual delivery)

    Save Beat Run

    Click Save (top-right corner) to initiate the Beat Run.

    Once saved:

    • Orders are locked into the run
    • The Beat Run becomes available for shipment planning
    • Delivery execution can begin via Route Run

    What Happens After Beat Run?

    After initiating a Beat Run, it is used to:

    • Generate Shipments
    • Assign Routes
    • Track delivery status
    • Monitor delivery performance

    Why Beat Run Is Important

    • Prevents missed deliveries
    • Organizes date-wise delivery planning
    • Improves rider efficiency
    • Ensures accurate order-to-delivery flow

    In this article
    Back to top _includes/footer.html
    © 2019–2026 Jeyan Technologies Private Limited • www.o2vend.com • Create your own store