At Return Gate Entry, why are packages are not distinguished based on channel and transporter?
At this stage, the system does not know which AWB are received from which channel or transporter. Hence, they are not distinguished.
If return orders are not found, why are they allowed at Return Gate Entry?
Return Gate Entry is done to only to confirm that the packages are received. AWB are not subjected to any test at this stage.
‘No Return Order found’ error while processing return order
This error is being thrown when the system couldn't find the return order details while scanning the return AWB which will be there on the packet. Usually, return order details either get pushed through APIs or manually uploaded via CIMS.
- Gate entry should be done for the scanning return AWB.
- Please make sure whether the return order details are present in the system or not. The user may refer to a report, Returns : Gate entry Report - OMS by filtering using tracking id.
If the AWB is not the present, either user has to upload the return data via CIMS (CIMS > Return Order upload > Select the Client-Channel-location > Download the template file and upload it after populating the data as per the template)
- Else please write to firstname.lastname@example.org to escalate to the respective channel to push the return order to our system through APIs.
Recently we have added more search parameters to search for the return order details by scanning Item Id, etc
What should be done to amazon return packages which throws ‘Order is Complete’ error?
What should be done to self-ship returns from customer with no SKU?
What should be done to returns received from customers through Courier?
What to be done if the AWB are covered (i.e. with other stickers)?
Please raise them to respective transporters with references.
Do all returns from AJIO needs to be scanned in AJIO JIT?
All AJIO returns need not be scanned in AJIO JIT. Only those which are not found in Assure and Self-Shipped returns are to be scanned in AJIO JIT.
What must be done if the AJIO Return Orders, already scanned in AJIO JIT, throws error in Assure?
What must be done if the product does not have any SKU Id and/or item Id and is received in different box and/or different product and/or duplicate product?
Please process it by marking QC Fail and marking it as ‘Product Mismatch’
What should be done if the image of a SKU not showing for QC?
- Check whether the image URL is uploaded in the product master or not ( OMS > Missing images > select the client > Click on 'Download CSV'). This will give you the complete list of SKU whose images are not yet updated.
If the URL is not updated, user can update the URL using 'Products' screen in OMS (OMS > Products > Update > Select the client > Download and upload the populated CSV file). In the 'ImageURL' column, image URL can be populated rest of the columns can be left blank. Link should not point to a site instead the URL should point to image directly.
- URL should be public, private URLs won't be able to access from the system. Suggested clouds are Google, Tinypic, Imgur, Dropbox, etc.
- The uploaded cloud domain should be whitelisted in the firewall.
What must be done if a new return order is scanned and it shows ‘Return is Complete’ and the product is mismatched too?
When every item in a bin is cleared, Why is the bin not made Offline automatically?
Many of our clients are using this as a feature. Alternatively, It is suggested to make the bin offline once the last item is picked.
Why Order is in UNFULFILLABLE status in WMS?
Allocated qty might be last item and it might have got marked as LOST. Since there is no more item to allocate for the Order, WMS marks the Order as UNFULFILLABLE.
Do following checks to make the order fulfillable.
• Check any Item kept in RECYCLE status. Make those items LIVE.
• Check whether inventory is available in some other inventory pool. If yes, move inventory to required pool. After sometime Order will be allocated.
• Get new stock for required SKU and do GRN.
Why the items are in ACK status and not moving to picking status?
There is a concept of Piece picking priority in Assure WMS, Suppose it is set to release 200 line items ( Wave size ) in 15 minutes ( Wave frequency ) and you have a pick pending of 215 orders. Once the number of order fall below 200, within a maximum of 15 minutes a wave be released with the difference.
Till then the items will be acknowledged state and will not move to picking.
Channel is not showing in drop-down in Pigeon Hole - Picking screen
Whenever a new channel got added, we have to make sure that the all required channel are added in Piece picking priority. User could add a channel as follows,
Please go to, Picking > Piece Picking Priority in WMS > click on + symbol and add the required channel.
Note: For Flipkart, You need to select FLIPKART or FLIPKARTV3 depending on the seller API version you are using.
Why only one line item present in 'return processing screen' while processing combo order items having same SKU ids?
If channel return is not integrated, we have to process returns through CIMS. We have to upload all return orders via CIMS. Expected return file template format, separate line for each return item with it's attributes. In the case of combo Orders with one SKU and same return order id, rows need to be duplicated according to the return item quantity.
Why the same GRN numbers appears for different dates in inward report?
We are not repeating the GRN number. Each GRN number corresponding to each gate entry. If you are using the same gate entry again for inwarding, then the same GRN appears.
WMS > Returns - Search Return Orders
Using return_shipment_id, Paste return_shipment_id in Channel Return ID and Search > Click on ‘Update AWB Packet’ > Enter AWB and Transporter.
Why can't I find order id in WMS but it is visible in OMS.
As you know, there are 2 types of orders in Assure :
Piece Order - Currently only fulfillment type BLOCK_COMPLETE is supported for piece orders. These are typically orders which are captured from Marketplaces. If sufficient inventory is not available in the sales channel pool for one of the SKU in an order, the order will get marked as UNFULFILLABLE and will not get released to WMS. Such orders will only get released to WMS once sufficient inventory is available and the order is not cancelled on the channel. In such a condition, the order can go into an UNFULFILLABLE state.
Bulk Order - There are 2 fulfillment types of every order : a) BLOCK_COMPLETE , b) PARTIAL . Inventory is allocated to BULK orders on manually triggering the retry action. Depending on the fulfillment type, the order will be sent to WMS for processing. If it is BLOCK_COMPLETE, the order will not be pushed to WMS until inventory is available for every SKU and Quantity specified in the order. In case the fulfillment type is specified as PARTIAL, It will get released to WMS even if there is inventory available for 1 SKU and 1 Quantity of that SKU.