Creating & Assigning Orders to Vendors

Purpose: For Operations, CX, Vendor Ops & Business Development Teams


1. Purpose of This Module

To define:

  • How orders are created (customer-side & admin-side)

  • How vendors get assigned

  • When Ops/CX must intervene

  • Internal rules for assignment & reassignment

  • SLA standards for pickup timelines

  • BD/Vendor Ops support in ensuring availability

Goal:
✔ Faster pickups
✔ Accurate vendor assignment
✔ Higher order completion rate
✔ Better customer satisfaction
✔ Smooth operational flow


2. How Orders Are Created

Orders can be created through two methods:


A. Customer Self-Creation (Website / App)

The customer:

  1. Selects device

  2. Selects condition

  3. Views price

  4. Enters personal details

  5. Enters address/pincode

  6. Confirms Order

The order then appears in the Admin Panel under Orders → Pending Vendor Assignment.


B. Manual Order Creation (Admin Panel)

Used by Sales/CX when:

  • Customer calls for help

  • Customer cannot complete checkout

  • Customer needs manual assistance

  • Lead conversion requires admin support

Steps:

  1. Go to Orders → Create Order

  2. Enter customer details

  3. Select device/model

  4. Select condition

  5. Enter address & pincode

  6. Review price

  7. Confirm order

Once created → The order moves to Pending Vendor Assignment.


3. Vendor Assignment Process

Once an order is created, the system or Ops assigns a vendor.

Vendor assignment is done via:

A. Auto-Assignment (System Driven)

The system selects a vendor based on:

  • Pincode match

  • Device type support (phone/tablet/laptop/mac)

  • Vendor’s Wallet & Credits balance

  • Vendor SLA score

  • Distance & availability

  • Past performance

This is the default process.


B. Manual Assignment (Ops/Vendor Ops Required)

Used when:

  • No vendor available automatically

  • Vendor unresponsive

  • Vendor needs replacement

  • High-value or urgent order

  • Special request by customer

Steps:

  1. Go to Orders → Pending Assignment

  2. Click Assign Vendor

  3. View list of eligible vendors

  4. Check vendor SLA, credits & coverage

  5. Assign the best-suited vendor


4. Vendor Unlock Logic

Before accepting an order, the vendor must:

  1. Have Minimum Wallet Balance (to pay customer)

  2. Have Sufficient Credits (to unlock order)

  3. Cover the device type (phone, laptop, tablet, etc.)

  4. Be within serviceable area range

Only after satisfying all conditions →
Vendor can unlock the order.

Once unlocked →
Vendor is assigned officially and both customer & vendor get notifications.


5. Reassignment Rules

Reassignment is required when:

A. Vendor Not Responding

  • No call made to customer within SLA time (15 minutes)

  • Vendor unreachable or phone switched off

B. Vendor Declines Pickup

  • Not available

  • Not supporting device type

  • Delay issues

C. Customer Requests Different Time

Vendor not available → assign new vendor.

D. Vendor Violates Behaviour Rules

CX reports misbehaviour → Ops reassigns immediately.

E. Vendor Lacks Wallet/Credits

If vendor doesn’t have enough balance → reassign.


6. Reassignment Procedure (Ops/CX)

  1. Check current vendor status & reason for delay

  2. Add internal note explaining reason

  3. Click Reassign Vendor

  4. Select next best eligible vendor

  5. Notify customer about reassignment

  6. Monitor new vendor’s response


7. SLA for Vendor Assignment

Stage

SLA Time

Vendor acceptance after assignment

Within 15 minutes

Vendor calling customer

Within 20 minutes

Vendor reaching customer

Within scheduled time or < 60 min if ASAP

Reassignment if vendor fails

Within 10 minutes


8. CX Responsibilities

CX must:

  • Monitor order tracking

  • Ensure vendor calls customer within SLA

  • Contact vendor if no update

  • Communicate ETA to customer

  • Trigger reassignment if vendor unresponsive

  • Add internal notes for every action

  • Update customer on vendor details


9. Operations Responsibilities

Ops must:

  • Monitor all pending/assigned orders

  • Ensure timely vendor response

  • Approve reassignment

  • Support CX in escalated issues

  • Coordinate with Vendor Ops for vendor shortages


10. Vendor Operations Responsibilities

Vendor Ops must:

  • Ensure enough vendors in all areas

  • Monitor vendor availability per city/device type

  • Support reassignment when supply is low

  • Handle vendors who repeatedly miss orders


11. Business Development (BD) Responsibilities

BD Team ensures serviceability for all incoming orders.

They must:

  • Identify pincode gaps (orders created but no vendors available)

  • Coordinate with Vendor Ops to onboard vendors for uncovered areas

  • Track high-value areas that need more vendor supply

  • Share weekly coverage reports with Ops & Management

  • Support expansion of new cities to avoid "unassigned orders"


12. Customer Notifications During Assignment

Customer receives:

  1. Order Created

  2. Vendor Assigned (once vendor unlocks)

  3. Vendor En Route (when vendor taps Start Trip)

Clear communication = Trust + Higher conversion.


13. Vendor Notifications

Vendor receives:

  • New order available

  • Unlock requirements

  • Customer details after unlock

  • Route navigation

  • Payment process guidelines


14. One-Page Summary (Training Card)

Order Creation

  • Customer self-creates OR CX creates manually

  • Moves to Pending Vendor Assignment

Vendor Assignment

  • Auto or Manual

  • Vendor must have enough Wallet + Credits

  • Vendor unlocks order

Reassignment

Required if vendor is:

  • Unresponsive

  • Not available

  • Violating SLA

  • Out of coverage

  • Low on Wallet/Credits

Team Roles

  • CX → Tracking & communication

  • Ops → Assignment & escalation

  • Vendor Ops → Supply & quality

  • BD Team → Coverage & expansion


Was this article helpful?
© 2026 BigBold Technologies Pvt. Ltd.