COD to Prepaid Conversion for Self-Ship Orders 

Introduction


COD (Cash on Delivery) to Prepaid Conversion refers to a process where a customer initially places an order, choosing COD as the payment mode, but later decides to prepay for the order (before delivery). This conversion happens before the shipment is delivered.

 

In the context of Self-ship orders (i.e., where the brand or seller manages its own logistics instead of using marketplace logistics like Ekart or Delhivery), this feature becomes highly beneficial.

 

✅ Key Use Cases:

· Customer Experience Improvement:

  • Customers sometimes change their minds and prefer to pay online for convenience or to avoid handling cash.

· Operational Flexibility:

  • Enables sellers to collect payment digitally even for COD-tagged orders, minimizing RTO risk.

· RTO Reduction:

  • Prepaid orders are less likely to be rejected upon delivery, reducing return-to-origin instances.

How It Works (Typically):

  • The order is placed as COD.
  • Before dispatch, a payment link (PayU, Razorpay, etc.) is sent to the customer.
  • If the customer completes the payment:
    1. The order status is updated to Prepaid.
    2. Delivery is completed as a Prepaid order.
    3. COD collection process is bypassed.
        

Business Benefits:

  • Reduces cash handling at delivery
  • Minimizes fraud risk (no fake COD orders)
  • Decreases RTO and logistic cost
  • Boosts prepaid revenue share
  • Improves customer satisfaction with flexible payment options

 
User Journey

  • COD to Prepaid Conversion Flow – Self-ship Orders
  • The customer places a cash-on-delivery (COD) order on the brand's website.
  • The order is successfully created.
  • The seller receives the order within the Vin OMS system.
  • Business on Bot sends a payment link to the customer, enabling them to convert the COD order into a prepaid one.
  • The customer clicks on the link and initiates the payment.
  • Before processing the payment, Business on Bot checks the order status in Vin OMS:
  • If the order is already packed, the conversion to prepaid is not allowed.
  • If the order is not packed, the payment is processed, and the order status is updated.
  • Upon successful payment, the customer receives a confirmation message, and the COD collection at delivery is bypassed.

Notes: -

  • No Discount handling.
  • This workflow handles the prepack journey of the orders only, once order is packed, conversion won’t be allowed.

 

Steps to Integrate Business on Bot with Vin OMS for Order Updates

  1. Generate API Key and Assign API Owner
     
    The brand/customer needs to create an API Key and assign an API Owner from the Vinculum panel.
    Navigation:      Admin → Miscellaneous → Manage API → Add
     
  2. Assign Required API Access
     
    While generating the API Key, ensure that the following API access is granted:
    1. API Name: Order Update
    2. API Endpoint (for reference): /order/orderUpdate
        
  3. Share API Credentials with the Business on the Bot
     
    Once the API Key and API Owner details are created, they must be shared with the Business on Bot team for configuration on their end.

  4. Webhook Configuration (Business on Bot → Vinculum)
    The Business on Bot team will share a Webhook URL that must be registered in the Vinculum panel.

    Navigation:     Admin → Miscellaneous → Manage API → Register Webhook
    1. API Name: Get Order Status
    2. Webhook URL: [To be provided by Business on the Bot team]

 
 Sample API Curl

 

curl --location 'https://dynamic.vineretail.com/RestWS/api/eretail/v2/order/orderUpdate' \

--header 'Content-Type: application/Json' \

--header 'ApiKey: 6fc14a5aabc5477c9d745c4818ab69eb9f6eee4d9eef4a8bbda106e' \

--header 'ApiOwner: 84sa' \

--data '{

    "orders": [

        {

            "orderNo": "CHE146448",

            "paymentType": "Prepaid"

        }

    ]

}'