1. Please note -
Only those cases which are blocked due to pod under lost status should be assigned to fops, any AWB having delivered status blocked under pod request should be assigned to lops respective agents.
2. PFA the rate list, share with client only on escalations, not every time.
3. Woocommerce simple steps to integrate -
To fetch orders and catalog in Shiprocket the user has to configure his WooCommerce API in Shiprocket Channel Configuration Page.
If the user already has a channel created on Shiprocket, he does not have to follow the following steps to integrate his Woocommerce Channel.
Step 1: Connect to your Shiprocket account and go to the Channels tab
Step 2: Click on the 'Add New Channel' button to add your Woocommerce channel
Step 3: Locate the Woocommerce channel and click on the 'Add' button
Step 4: Here, enter your Woocommerce store URL and click on 'Connect to Woocommerce'
Step 5: On clicking, you will be redirected to a page within WooCommerce. Please click on "Approve" to give Shiprocket the required permission to operate
Step 6: Once you approve the connection, it will redirect you to the previous "Channel" page with a consumer key and consumer secret
Step 7: Click on the "Update Channel & Test Credentials" to connect your channel with Shiprocket.
Please Note:
Please be ensured that your REST API is enabled in your WooCommerce plugin. To do this,
a. Within your Wordpress admin, go to the WooCommerce section.
b. Click on "Settings" and go to the API tab.
c. Check if your REST API is enabled or not. If you don't have an API tab, you need to upgrade your WooCommerce plugin to the latest version.
d. To show serviceability on your buyer panel, please update the weight in kgs and dimensions in cms for every product in your WooCommerce account.
4.NDR validation on more than a month old case from RTO delivered date:- This is very challenging on confirming RTO reason & NDR validation on more than a month old cases from RTD date. So accept queries where cases are less than a month old.
5.Multiple selection scenario:- Need to select multiple AWB selections or multiple AWB tags for raising a query against more than an AWB. & wherever AWB count is more than 50 AWB's, the team will select multiple AWB selections or multiple AWB tags along with putting only one AWB in AWB field. This will help us to pick all AWB;s instead of a few cases.
6.Adoption of NDR/ Expedite panel:- Have to push sellers for the adoption of NDR/Expedite panel instead of creating tickets.
7.Damage status on ICRM :- if the ICRM has status damage in intransit & product is neither perishable nor fragile, almost 90% of the orders are connected for origin due to poor packaging issue but Damage status can not be changed if AWB has been billed or in post bill status. (need to make seller understand where seller raises query for damage claim in intransit. example ( agent shares status as order is moving to origin but damage status can not be changed due to damage status)
8.CSAT to be pitched on every FCR call & chat wherein; the seller is satisfied with the solution.
9. Tickets should not be left open in case FCR tickets.
. The GST on seller's freight invoice will only reflect if the GST is added by following the below path -
Settings --> accounting details
Once the seller adds the GST in the SR panel then the same is reflected on his freight invoice from the next billing cycle. The agent should not guide for GSTIN process in such cases.
10.Now sellers can 'Escalate' from the Shiprocket panel if their weight disputes are rejected.
This will help sellers in raising their concerns over rejected weight discrepancies and save their efforts of going to Fresh-Desk to create tickets.
1- The escalation button will be active only when the seller's dispute has been rejected.
2- Both Escalation and Re-escalation buttons will be active for 2 working days.
3- If the seller is unable to take action within 2 working days, the Escalation button will be disabled.
4- Seller will have 2 working days to revert to any query asked by the Weight team.
5- Weight team will have time of 2 working days to revert on their queries.