Common Marketplace Errors

Modified on Tue, 02 Aug 2022 at 12:55 PM

The aim of this article is to help you understand common error messages you face during Marketplace order processing aka "Piece Order" processing.

Note: Channel and Marketplace are sometimes used interchangeably.


Error: "Error from channel: Shipping details not available for order id: <order id>" on piece packing screen.

While piece packing, Increff WMS requests the channel for a shipment label of an order. we may encounter this error here. The most likely cause of this error is that Marketplace has not yet assigned a courier partner for this order or the shipment label generation is still under process. 


This happens because of technical/process delays from the channel end. Either user could retry after some time (Usually it gets resolved after some time in most cases) else raise the concern to the helpdesk, assure.support@increff.com


Paytm Specific Errors


Error: "Error from Channel: Courier partner not assigned yet by the channel" on the packing screen

During piece packing, when Increff WMS requests Paytm for a shipment label of an order, we may encounter this error. The most probable cause of this error is that Paytm has not yet assigned a courier partner for this order. Hence, the shipment label cannot be generated. 


This happens because of technical/process delays from the channel end. Either user could retry after some time (Usually it gets resolved after some time in most cases) else raise the concern to the helpdesk, assure.support@increff.com


Error: "This is a return order, not yet approved from channel" on the packing screen

Paytm expects the processing of replacement orders to be on hold till the time return is picked up for the actual order placed by the customer. Increff WMS has the intelligence to block these orders from getting released for processing while making sure that the inventory is blocked for such an order. The order is automatically released for processing when the returned item is picked up from the customer's place (when it confirms from the channel)


Rarely, do some orders get into processing state before return picks up, thereby pick list releases and goes for packing. When such an order reaches the packing desk, this error is encountered. Please sideline those orders and continue processing the rest of the orders. Once the orders get approved from the channel user can retry processing those orders.


However, if you feel the behavior is different from what is mentioned, contact Increff WMS Helpdesk, assure.support@increff.com



Error: "417 Expectation Failed" on packing screen

This error occurs when Paytm fails to generate invoices and shipping labels at their end while packing. The system will throw out this error as this was not an expected response from the channel.


Feel free to write to Increff WMS support once you encounter this error so that the support team could follow up with the Paytm team to fix it. 

Note: The user can retry processing the Order intermittently.


Flipkart Specific Errors


Error: "Dimension not present for Shipment: 22193XXXX." on the packing screen

This happens when you are trying to fetch shipment labels (on Piece Packing Screen) in the case of commodities such as books or products where one of the dimensions is very small ~ < 1 cm. For such cases, it has been observed that Flipkart throws an error while trying to fetch the shipment label for those orders.


We have tried handling this issue as part of Increff WMS packing flow. However, if you end up encountering this error, please create a SUPPORT Ticket.



Error: "Error from Channel. Packing in Progress" on packing screen. 

This error is encountered on Piece Packing Screen when Flipkart is not able to a assign Logistic Partner for the respective order.
Operators can retry processing those items after some interval as it gets resolved after some time without any interventions in most cases. Feel free to raise a support ticket so that the team could escalate the concern to the Flipkart team.



Error: "Manifest cannot be created for orderId : OD12XXXXXXXXX" on manifest screen.

Usually, user gets this error while trying to close a manifest. Assure checks the channel order status of all orders which are attached to the manifest. If the order status differs other than the expected status, the system throws the error.


As a basic check, you could check the orders status on the panel. If the status on the channel is ready to dispatch/dispatched/canceled you can mark the order accordingly on OMS.

Note: All orders are expected to be processed via Assure.


Snapdeal Specific Errors


Error: "Error while getting credential from channel for channel" on manifest screen.

This is an error thrown by Snapdeal and you might encounter this in Piece Packing, Manifests or Order Search Screen. This happens when the credentials get expired from the channel end. In most of the cases, it works once retry later. Feel free to raise the concern if you feel the issue goes critical.


Error: "401 Unauthorized" on piece packing screen.

This is an error thrown by Snapdeal and you might encounter this in Piece Packing, Manifests or Order Search Screen. We have yet not been able to decipher this error message from Snapdeal. Please feel free to contact assure support for further assistance.



Error: "403 Forbidden" on manifest screen

This is an error thrown by Snapdeal and you might encounter this in Manifests Screen. We have yet not been able to decipher this error message from Snapdeal. Generally, this error gets resolved without any intervention. You can retry manifest after some time. Create a support ticket if the issue persists.  


Tatacliq Specific Errors

Error: "AWB No not generated on Tatacliq for Shipping Label Id :5304497 Message : ## AWBGenerationFailure : APEX COD Service not available" on piece packing screen

During piece packing, when Assure requests Tatacliq for a shipment label of an order, we may encounter this error ( on Piece Packing Screen ). The most likely cause of this error is that Tatacliq has not yet assigned a courier partner for this order. Hence, the shipment label cannot be generated. Please retry after sometime ( ~ 1hr ) to get a Shipment label(in most of the cases it gets resolved without any interventions). If the issue persists, 

please raise the Order Ids to Tatacliq team and contact your Tatacliq Account Manager.


Error in closing shipment: Could not create shipment on Tatacliq. Failed TransactionID : (TransactionId), Message : Transaction not in possible status to Generate AWB

During piece packing, when Assure requests Tatacliq for the status of an order, we may encounter this error (on Piece Packing Screen ). The most likely cause of this error is that Tatacliq has not yet assigned a courier partner for this order or that the order is canceled. Hence, the shipment label/invoice cannot be generated. Please raise the Order Ids to your Tatacliq Account Manager.


Error in closing shipment: Could not create shipment on Tatacliq. Failed TransactionID : (TransactionId), Message : PinCode is not Serviceable 

During piece packing, when Assure requests Tatacliq for the status of an order, we may encounter this error (on Piece Packing Screen ). The most likely cause of this error is that the pin code mentioned for this order might be restricted at Tatacliq. Hence, the shipment label/invoice cannot be generated. Please raise the Order Ids to your Tatacliq Account Manager. 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article