Xpressbee Ecom MPS [B2C]

Xpressbees Logistics is a logistics company that provides end-to-end supply chain solutions, including first-mile, last-mile delivery, storage, and WMS.

Courier Partner ID: 338

Services Integrated:

Order Creation
Tracking via Polling

Steps to setup Xpressbees Ecom MPS on Clickpost

Firstly, complete the process of setting up a courier partner account by following the steps: https://docs.clickpost.ai/docs/create-an-courier-partner-account
This is the screen that you'll get :

Here, you can add the credentials as shared by the Xpressbees team. To give you a brief:

Name	value	description
`Business_account_name`	EnterpriseBusiness Name	Unique Business Name for each customer. It is a name allocated to a business in the XB systems This is required in the Order Creation API and has validation against it.
`username`	Enterprise ID	To generate the Tokens needed for Xpressbees APIs. You will get it from your Xpressbees relationship manager.
`password`	password	To generate the Tokens needed for Xpressbees APIs. You will get it from your Xpressbees relationship manager.
`secret key`	XB Key	XB Access Key ID of the service owner who will be granting anonymous access for a request that satisfies the set of constraints in the policy. You will get it from your Xpressbees relationship manager.
`service_type`	SD or NDD or SDD or IntraSDD or SFC (only in case of BFSI)	This field specifies the type of shipment delivery. SDD -> Same-day delivery NDD -> Next-day delivery SD -> InfraSDD -> SFC ->
`XB_manifesttion_key`	manifest XB Key	Required in the OC API. Mapped to ManifestID in the Xpressbees API payload. Will be shared by the XpressBees team.
`XB_tracking_key`	tracking XB Key	Required in the tracking API. Will be shared by the XpressBees team.
`category`	string value	This is a mandatory field that populates the Product Category field in the Xpressbees API payload. We’d always want the enterprise to send the shipment category in the cat field in the Clickpost items object but, if the customer is unable to do so, we can ask them to add their shipment category here and the same will be appended to the Xpressbees payload under Product Category Only 1 string is expected here.
`pickup vendor code`	string value	It is a mandatory field used to identify the pickup location vendor. XpressBees' API requires vendor codes to be sent against each unique pickup location for a customer. This is how it’s handled at our end: 1. We expect the customer to send in their own vendor_code in the Clickpost payloads. 2. If unable, they can also set them in the credentials here. 1 account_code per vendor_code 3. If both are not feasible (and not done) Clickpost will automatically generate these vendor codes and control the vendor_code generation logic and send them on behalf of the customer. These are unique ids generated per account.
`OTP based delivery`	YES or NO	It is a Mandatory field that signifies if an OTP verification is required at the receiver end for the shipment delivery then we use "YES" if not "NO". (By default it is "No")
`Load_type`	Ecom or BFSI

Once done, kindly press Submit and you have set up Xpressbees on Clickpost.

Note:

Pre-assigned AWBs: No need to configure pre-assigned AWBs, AWBs are generated by the carrier in real-time during the order creation API call and returned back in response.
Labels: Clickpost does generate a label for Xpreebees Ecom B2C MPS orders. Labels are generated by Clickpost and returned in API response to the customer.