This happens for paytm orders. These orders will be in 'Download Packing Slip' on the seller panel. When you download the packing slip, the order will move to 'Request Pickup'.
After this, the user will be able to close the manifest.
This error comes because the bin contains items which are not in COMMON pool but in some RESERVED pool. In order to perform Bin Offline or Cycle count , the items in the bin should be in COMMON pool. Pls move the items to COMMON pool first before doing Bin Offline or Cycle Count.
This error is being encountered when the system gets unexpected order status from the channel. Due to some manual interventions orders status gets changed and this leads to block the process flow in the system. Whenever the user gets a similar error, check the order status on the panel and confirm whether it is in expected status (expected channel status varies channel to channel).
System has been designed in such a way that, user can't do handover again if the handover is already done. The error shows the same. When ever the user gets this message on the Bulk Handover screen, it means the order has already processed through this screen.
Suppose if you couldn't get the document printed, there is an option to get the handover document printed later on from 'Outward - Search Handover' screen.
You may face this error while uploading return order file. While setting the return order template file, make sure you populate channel_sku_id against the header product id (Not EAN/Client SKU id). You could refer jasper reports, CIMS | Listings for Channel sku id against an SKU.
Assure got designed in a way that, GRN can be done only those SKUs which are there in the PO. The user faces this issue when he tries to GRN an SKU which is not there in the PO.
Whenever a user gets encountered by this error, do the check as follows.
Get the corresponding global sku id to the EAN code that you were trying to scan. Then go to OMS > Search Orders > Enter channel Order id/Increff Order Id and search > Click on Order id > Click on 'Order line items' > Find the global sku id (by Ctrl+f and paste global sku id)
While creating the Manifest, we have to make sure we have selected the CLIENT correctly. We should attach those AWBs that belongs to the channel for which we created the manifest.
In case if the user has created a manifest and attached AWBs that doesn't belong to the channel, then remove those AWBs using REMOVE button and create a new manifest id for removed ones.
Rarely, due to some technical reasons assure demands to de-allocate items from the order to satisfy system logic. This error shows asks user to deallocate item from the order. We have designed a screen to de-allocated items from the order, Sundry - Deallocate Packed Quantity screen.
WMS > click on Sundry - Deallocate Packed Quantity > Enter the Order id > Click on 'Sync Order' > Check the message that shows up on the screen > get the global sku id from the message and figure out from which box items to be removed > get the required number of items from the box and scan those item ids on the screen.
Please do the following checks when you get this error :
- Check whether scanned AWB no is correct or not. If correct, process that order through the packing screen again and retry manifest.
- Confirm you have selected correct transporter while creating the Manifest.
If you still continue to face the issue, contact Helpdesk.
As you know, there are 2 types of orders in Assure :
- Piece Order - Currently only fulfilment 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 SKUs 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 fulfilment types of every order : a) BLOCK_COMPLETE , b) PARTIAL . Inventory is allocated to BULK orders on manually triggering the retry action. Depending on the fulfilment 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 fulfilment 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.
The user might face this issue while doing manifest for Snapdeal Orders. Snapdeal allocates some orders to open external manifest from channel end. Hence channel restricts to close the manifest with the same set of orders that got clustered in the external manifest id.
To overcome this, User could either close the external manifest id which is shown in the error from the panel else attach the shown Order id(displayed at the right end of the error) in the manifest and get it closed.
While manifest all attached orders should have same status (expected status). If any order moves to unexpected status while manifest, it throws this error. As a go forward, remove those orders which are mentioned in the error and close the manifest. Please write to assure support attaching those order ids in the error.
While handover all attached orders should have same status (expected status: PACKED from channel). If any order moves to unexpected status while handover, it throws this error. As a go forward, remove those orders which are mentioned in the error and do the handover. Please contact assure support for further assistance.
This is an error often comes for Flipkart orders. From the channel they define an attribute, 'Dispatch after date' for each order which is intended to make restriction on order processing. Orders can only processed after this time. So keep those orders aside and continue processing rest orders. The order can be packed when the current date crosses the dispatch after date.
While piece packing, Assure requests the channel for a shipment details. Error occurs here, most likely cause of this error is that channel has not yet assigned a courier partner for the order or the shipment label generation is still under process.
This happens due to technical/process delays from the channel end. Either user could retry after some time (Usually it gets resolved after sometime in most of the cases) else raise the concern to helpdesk, email@example.com.
This happens for the replacement order. Channel keeps a replacement order on hold till an expected status. Rarely, assure release pick list for on hold orders. Once item picked and comes to packing stage, Assure checks the order status on the channel. If the order is in on hold status it will throw this error and restrict to process further. In such cases, you may keep those items aside and continue with rest of the orders. Those on hold orders can be processed once its approved from the channel.
This happens when a mismatch in line items of order in assure vs channel due to manual interventions from the panel. While packing, Assure checks the line items in the channel. Once it found the mismatch, the system will throw this error. In such cases, the client has to manually cancel that order and create a new order.
Note: manual interventions from the panel are not entertained.
Assure throws this error when a user tries to remove an item which is already allocated for an order. In such cases, system will restrict to make the bin offline or to remove item. Either you can get the order id from Recycle desk by scanning the item id and get it processed or reach out helpdesk for further assistance.
Order can be done only ones in the life cycle of any order. If a user tries to handover an order more than one time system will throw this error. Make sure all AWBs under a Manifest ID has not dispatched. If any one of them got dispatched already, user should uncheck that AWB no. from the list which got dispatched already do the handover for rest of the orders.
Assure throws this error when a user tries to open a bin which already opened. When you get this error, you proceed to next step of the process since the bin is already opened.
This happens when mentioned(in the error) order under gone partial cancellation.As a go forward, user can remove that order which is showing in the error and continue closing the Manifest.
Note: Share the Order Id that you have removed. Team will investigate on that Order.
This happens when the assure gets an unexpected response from Amazon channel. Whenever user faces this issue, feel free to get the assistance from the assure support team.
While packing an item, assure checks order status on the channel. If the user gets this error while packing, it means the order got canceled from the channel. Since the Order got canceled, the user can keep that order aside and continue with processing rest of the orders.
This happens due to some technical delays from the channel end. The courier partner is not assigned from the channel end. In most of the cases it gets resolved without any interventions. Retry processing the order after some time. Feel free to raise the concern if it goes critical.
This error comes while packing one of the item in a Combo order, but the other item is unfulfillable. This order cannot be processed as the PARTIAL fulfillment is not allowed for this client.
Please do following checks,
- First login to the Seller Panel.
- Find out the orders which are manifested using the channel manifest id : 46197560.
- Please remove those orders in the current manifest list.
- Try manifesting for the rest of the orders.
This happens because one of the item for the order is Cancelled. Please change the item which is in PICKED status to INVOICED status. Please process the item and change it to INVOICED.
The inward PO contains the SKUs and the corresponding quantities to be inwarded. If the 'Excess GRN' is enabled, the client can inward more quantity for the SKU than mentioned in the PO. In this particular case, 'Excess GRN' is disabled for the client but the operation team is trying to inward the items more than the quantity mentioned in the Inward PO.
Please verify the corresponding PO and SKU and confirm the quantity mentioned. And also find out the items which are already inwarded.
Error "Invalid item status change, NEW to LIVE not allowed" on Inward- Put Away screen
This error comes on 'Inward- Put Away screen' when the warehouse person is trying to Putaway the bin at a location. Ideally, the bin should contain items which are in GRN state. This error comes because one or many of the items are in NEW state instead of GRN state. Once the tech team changes those items to NEW state, the putaway can be done for the bin. Please contact the Support team to do the needful.