INDIA POST

INTEGRATION DOCUMENT


About India Post

For more than 150 years, India Post has served as the backbone of the country’s communication, while playing a crucial role in reaching out to millions across the country. With more than 1,55,000 post offices, India Post has the most widely distributed postal network in the world. India Post endeavours to provide mail parcel, money transfer, banking, insurance and retail services with speed and reliability.

Services Integrated

Below are the services of India Post which are integrated with e-Retail:

  • Shipment Tracking
  • Forward Manifest

Prerequisite

Before configuring the transporter on Vin e-Retail, the following needs to be obtained from India Post:

  • Customer ID
  • Booking Office ID
  • Contract No
  • Service code
  • Customer File Ref Name

Configuring the logistics partner

Below are the steps to configure the transporter in eRetail:

1. Login on Vin e-Retail. Once logged in, navigate to left hand side of the screen towards the menu.


 

2. Hover over the Master Module and click on Transporter Master under Trading Partners.




3. In the Transporter Enquiry screen, click the Add New button that is located on the top right corner of the screen. Alternatively, use Alt+F as shortcut key to add a new transporter. This will bring up Transporter Create/Edit screen.



4. On the Transporter Create/Edit screen, select the Transporter Type as India Post from the drop-down list.


 

 

5. Fill the details as required in the below table:

Detail Transporter



S.No.

Section

Field (Free Text/Checkbox/

Dropdown)

Features

Details

1.

Detail Transporter

Transporter Type

Select the dropdown to choose the transporter. It is a mandatory field.

Select India Post. Once the transporter is selected, “Configure API Details” tab will appear.

1.a. 

Transporter Code*

Unique Code is generated by the user for each Transport. Once the Transporter Code is saved, it cannot be edited. It is a mandatory field.

It helps differentiating two or more records in case these records have same Transporter Name.

1.b.

Transporter Name*

Defined by the user. It is a mandatory field.

The user can use this field to give any name for the transporter.

1.c.

Company Name

Defined by the user.

This field is used to provide an optional alternative name to the transporter.

1.d.

GL Code

General Ledger Code and it is an optional free text field.

It is used for reference to locate the transporter in the books of accounts.

1.e.

Validate Service Loc

Checkbox that allows validation of Delivery location/pin code of the transporter

It is used to check whether the delivery location is serviceable or not (i.e., reachable by the transporter.)

1.f.

Send Ship Mail ID

Checkbox that allows to send ship mail ID to your customers.

When this option is enabled, the transporter will send order tracking information to the end customer via email.

1.g.

Reverse Validate Service Loc

Checkbox will allow validation for the delivery location/pin code in case of returns

It is used to check whether the pickup location is serviceable or not.

1.h.

Delivery Mode

Dropdown to select delivery mode as Air or Surface

It is not a mandatory field. The delivery via water bodies will be part of the surface only.

1.i.

Upload AWB series

Checkbox that allows to upload AWB series if manifest generation is offline otherwise leave it blank.

Check only if manifest generation is off line. Keep this option unchecked in case of real time manifest generation. Manifest (offline/real-time) can be selected in the Configure API Details tab.

1.j.

Is Active

Check this option to mark the transporter active. It is a mandatory field.

The transporter cannot be used if it is not marked active.

1.k.

Tracking hour

Free text field used for any number of hours less than 24 hours to check the shipment with the transporter.

6 hours is the ideal time and is also the default value.

1.l

Dimensional Factor

Optional free text field used to calculate the dimensional weight of the shipment.

The volume of the shipment is divided by Dimensional Factor to determine the shipment’s dimensional weight, which is then further used to calculate the shipment rates. It is an optional field.

1.m.

Trans Type*

Dropdown to be selected either as “Courier” or “Own Fleet”. It is a mandatory field.

In B2C cases, select “Courier” as the default Trans type.

In B2B cases, this field is more relevant.

2.

(a-d)

Contact Details

Mandatory fields

a. Address 1

b. Address 2

c. Country

d. State

a & b. Free text field to update the correct address 

 

c. & d. Dropdown boxes to select the correct City & State information

Address1, Address2, Country, and State are mandatory, and must be filled before further configuration.

2. (e-m)

Other fields like:

Address 3, Address 4, Phone, Alternate Phone, Fax, Email, Alternate Email, City & Pin code 

Optional fields to update the required information

These are optional fields to provide other contact information.

 

User Defined Fields

The user may also add up to 5 custom defined fields for their use in the User Defined Field tab. All these fields are optional.

Configure API Details


Configure the following as needed:



Field

Feature

Details

AWB Generation Type

It is a drop down list to select the type of AWB number generation.
NOTE: When selecting Off Line Manifest, the Upload AWB Series must be checked as well.

Enter the following accordingly:

1. Off Line Manifest - The AWB numbers are already acquired beforehand from India Post, and saved in Vin e-Retail database. These AWB numbers are then used to track order status of the shipment.

Create Return on RTO (WMS)

This option is used to create a return order for RTO (Return to Origin) made for any order created via the Warehouse Management System.

 

Create Return on RTO (SP)

This option is used to create a return order for RTO (Return to Origin) made for any order created via Seller Panel.

 

External Invoice

This option is used to generate the invoice provided by the B2B shipping partner.

This option is only relevant for B2B transporters. If left unchecked, then the system will generate the eRetail invoice.

External Shipping Label

This option is used to generate the shipping label provided by the B2B shipping partner.

This option is only relevant for B2B transporters. If left unchecked, then the system will generate the eRetail shipping label.

 

Below screen will appear once the AWB generation type is selected with two tabs:

  1. Tracking API Details
  2. Manifest API Details

Tracking API Details

Fill the details as per the information provided in the table.

S.No.

Field

Feature

Details

3.a.i.

Tracking API Details

It is a check box that enables Tracking API details

Tracking API is used to get the various statuses of an order, e.g. In Transit, Delivered, RTO, etc. 

Once this checkbox is clicked, the subsequent tabs will be enabled for allowing input.

3.a.ii

Customer ID

This field is used to enter the unique Customer ID is that provided by India Post.

 

3.a.iii.

Latest Event

This field is used to enter the 2 digit event code of the XML file that is sent to India Post.

Recommended value is “LE”. Possible values are:

1. “LE” – Latest Event.

2. “IB” – Booking.

3. “ID” – Delivery.

4. “RT” – Returned.

IB, ID, and RT files can be used for reconciliation of data on weekly or monthly basis.

3.a.iv.

Technical Aggregator

This field is used if the shipping partner being configured is a 3PL aggregator

This field is for internal use of Vinculum. It can be left blank if the transporter is not a 3PL aggregator. This field is not relevant for India Post.

3.a.v.

Ext Carrier Id

This field is used to store the Courier Partner ID of the client assigned by the 3PL aggregator.

This field is for internal use of Vinculum. It can be left blank if the transporter is not a 3PL aggregator. This field is not relevant for India Post.

3.a.vi.

Ext Carrier Name

This field is used to store the Account Code of the client assigned by the 3PL aggregator.

This field is for internal use of Vinculum. It can be left blank if the transporter is not a 3PL aggregator. This field is not relevant for India Post.

3.a.vii.

Ext Reverse Carrier Id

This field is used to store the Courier Partner ID of the client assigned by the 3PL aggregator.

This field is for internal use of Vinculum. It can be left blank if the transporter is not a 3PL aggregator. This field is not relevant for India Post.

3.a.viii.

Ext Reverse Carrier Name

This field is used to store the Account Code of the client assigned by the 3PL aggregator.

This field is for internal use of Vinculum. It can be left blank if the transporter is not a 3PL aggregator. This field is not relevant for India Post.

 

Manifest API Details

Fill the details as per the information provided in the table.

S.No.

Field

Feature

Details

3.b.i.

Manifest API Details

It is a check box that enables Manifest API details

Manifest API is mainly used to inform the transporter of the pickup location and the delivery location.

Once this checkbox is clicked, the subsequent tabs will be enabled for allowing input.

3.b.ii.

Booking Office ID

This field is used to enter the alphanumeric code provided by India Post.

 

3.b.iii.

Customer ID

This field is used to enter the unique Customer ID that is provided by India Post.

 

3.b.iv.

Contract No

This field is used to enter the unique Contract number that is provided by India Post.

 

3.b.v.

Service

This field is used to enter the two digit service code that is provided by India Post.

 

3.b.vi.

Customer File Ref Name

This field is used to enter a file reference name which is unique for any customer. This value is provided by India Post.

 

3.b.vii.

Unique Order Key [?]

This field is used to set the format of the outbound code / delivery number that is sent to the transporter.

Enter the following accordingly:

1. “EODR” – To pass external order number.

2. “OBC” – To pass the outbound code.

3. “EODRT” – To pass the external order number with time stamp.

4. “OBCT” – To pass the outbound code with time stamp.

The default value is “EODR”.