Demand Generation

Updated on February 4, 2026


Available soon in the following languages:



  • Pre-defined Beat No
  • Retailers
  • PO, SKUs and quantities

This page only captures demand intent.
It does not decide how or from where the demand will be fulfilled.



Why This Change Was Required

Problems in earlier flow:

  • Sales selecting dispatch warehouse (logistics task)
  • Incorrect warehouse selection
  • Manual follow-ups with Supply
  • Carry forward required cancellation & re-creation
  • Low flexibility for ad-hoc demand

With this change:

  • Sales work becomes simpler
  • Demand becomes flexible & editable
  • Capacity-driven planning becomes possible
  • Downstream re-adjustment is enabled

Who Can Use This Feature?

RoleAccess
Regional Managers & AboveFull Access
Warehouse / SupplyNo Access

Regional Managers cannot:

  • Adjust demand against capacity
  • Decide carry forward
  • Select dispatch warehouse

Before You Start (Pre-requisites)

Ensure:

  • You are logged in with Sales profile
  • Beats & retailers are correctly mapped to you and Purchase Orders are already punched
  • You understand:
    • Which beat you are servicing
    • Which retailers belong to that beat
  • You know the fulfillment date logic (Plus-2)

Key Concepts

Date Logic

  • Demand created today is fulfilled on Plus-2
  • Example:
    • Today: 1st Jan
    • Demand fulfillment/Delivery: 3rd Jan

Always check the Fulfillment Date before confirming.


What This Page Does vs Does Not Do

DoesDoes NOT
Create demandAdjust demand
Capture SKU quantitiesCheck capacity
Beat-wise planningAssign warehouse
Retailer-level ordersHandle carry forward

Step-by-Step: How to Create Demand Using Trip Management


Step 1: Login & Navigate

  1. Open https://oms.eggoz.in
  2. Login using Mobile No & OTP
  3. Navigate to Trip Management

Step 2: Select Beat

  1. Choose the Beat Num from dropdown you are creating demand for
  2. Beat determines:
    • Demand Classification
    • Retailer list
    • Route coverage

Select the correct beat number — demand classification and retailers are beat-locked.


Step 3: Select Area / Channel Classification

  • Select applicable:
    • GT / ON-MT / OF-MT (as per system)
  • This classification is later used for prioritization

Step 4: Select Retailer(s)

  1. Choose one or more retailers under the beat
  2. Retailer-wise demand will be recorded

Step 5: Book Order (SKU Entry)

  1. Click Book Order
  2. Select PO (if applicable)
  3. Enter SKU-wise quantities:
    • Select SKUs
    • Add Qty

Enter tentative/PO quantities — adjustment happens later, not here.


Step 6: Verify Fulfillment Date

  • Fulfillment date is auto-set to Plus-2
  • You may:
    • Keep default
    • Select a future date (if allowed)

Step 7: Confirm Demand

  1. Review:
    • Beat
    • Retailers
    • SKUs
    • Quantities
    • Fulfillment date
  2. Click Confirm

What Happens After Demand Is Created?

After confirmation:

  • Demand is recorded in the OMS
  • It moves to Trip Management (View Tab)
  • System checks:
    • Available Supply Capping
  • Possible next steps:
    • Auto move to Warehouse Allocation (if capacity is sufficient)
    • Appear in Sales Demand Adjust (if capacity is insufficient)

Regional Managers do not need to do anything else.


Common Mistakes

  • Selecting wrong beat number
  • Ignoring fulfillment date
  • Assuming warehouse selection is required
  • Creating duplicate demand

Process Impact (Sales Perspective)

EarlierNow
Sales chose dispatchSupply-owned
Manual coordinationSystem-driven
Rigid demand Flexible & Re-adjustable
Carry forward manualAutomated flow

Support & Escalation

Contact Tech-Support for:

  • Missing beats / Beats Mapping
  • Retailer visibility issues
  • Date selection issues
  • Demand not appearing in adjust page

📧 techsupport@eggoz.in


Next

Leave a Reply