"Order modified: Items added in pack box is greater than quantity to be fulfilled now for SKU : [xxx] Remove 1 items from box before"

Or

Cancelled qty for subOrder : [xxx] order [xxx] is greater than received from channel while syncing 

Or

Insufficient quantity to pack from gsku: [xxx], batchId: null, subOrderId [yyy]

Can not create another shipment as no more qty left to be fulfilled for order:[xxx]

This error occurs when the operations team tries to pack more items than the ordered quantity.

Preventive Action: Ask the client not to add more items than the ordered quantity.

"Error from Channel : Manifests data is invalid" while closing manifest

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.

"Insufficient inventory to remove, already allocated to some order" on Bin Offline or Cycle Count screen

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. Please move the items to COMMON pool first before doing Bin Offline or Cycle Count.

"Order is in <order status> status, Required status : <order status>" on packing screen

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). 

"Status change from DISPATCHED to DISPATCHED for shipment <shipment id> is not allowed" on Bulk Handover screen while handover

Invalid BulkBox status change, DISPATCHED to DISPATCHED not allowed

The system has been designed in such a way that the user can not do the handover again if the handover is already done. The error shows the same. Whenever the user gets this message on the Bulk Handover screen, it means the order has already been processed through this screen. Only manifested shipments can be handed over.

Suppose you want to reprint handover document, there is an option to get the handover document printed later on from the Outward - Search Handover screen.

"ChannelSerialNo./ChannelSKU Not Found" in Order Entry - Return Order Upload 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.

"internal error" on GRN screen while scanning barcode

Omni got designed in a way that, GRN can be done only those SKU 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 this erro is encountered, do the following checks: 

Get the corresponding Global SKU id for 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)

"Internal error in OMS" on GRN screen while creating a new GRN

This error occurs when the warehouse operations team enters remarks consisting of more than 250 words.

Whenever this error occurs ask the warehouse ops team not to exceed more than 250 words in the remarks section.

"Some shipments not of client" while closing the manifest on manifest screen

While creating the Manifest, we have to make sure we have selected the CLIENT correctly. We should attach those AWB that belongs to the channel for which we created the manifest. 

In case if the user has created a manifest and attached AWB that does not belong to the channel, then remove those AWB using REMOVE button and create a new manifest id for removed ones.

"Processing/Allocated quantity is not sufficient for SKU :<Global SKU id>" on create bulk invoice screen

Rarely, due to some technical reasons omni demands to de-allocate items from the order to satisfy system logic. This error shows asks user to de-allocate 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.

"AWB not found" OR “Cannot find AWB” error on Manifests 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.

"Close the manifest with the External Manifest: <manifest id> or add these Orders that belongs to this manifest : <order id>" while closing manifest on Manifest screen

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.

"All orders must be in same state, orders in incorrect state:<order id>" on manifest screen

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 omni support attaching those order ids in the error.

"Cannot Handover Order <channel order id> as it is not packed" on handover screen

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 omni support for further assistance.  

Error in closing shipment: Error From Channel : Error from Channel: Could not pack order item as dispatch after date is greater than current time

Or

Error in closing shipment: INCREFF_FK004: Error from Channel: Could not pack order item as dispatch after date is greater than current time

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.

"AWB Number not created for Order Id : <order id>" on piece packing screen

While piece packing, Omni 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

"This is a return order, not yet approved from channel" on Piece Packing screen

This happens for the replacement order. Channel keeps a replacement order on hold till an expected status. Rarely, omni release pick list for on hold orders. Once item picked and comes to packing stage, Omni 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.

"No line present in order <channel order id> for subOrderId : <suborder id>" on Piece Packing screen

This happens when a mismatch in line items of order in omni vs channel due to manual interventions from the panel. While packing, Omni 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.

"Item unavailable to remove from the current bin" on Sundry-Remove Item screen

Omni 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.

“Invalid shipment status” on Outward Handover screen

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 AWB 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.

”Invalid bin status change, OPEN to OPEN not allowed” on GRN screen

Omni 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.

"INVALID Order state: <order status> Order : <order no>" while closing manifest

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.

"unknown response from amazon sf" on Piece packing screen for Amazon channel

This happens when the omni gets an unexpected response from Amazon channel. Whenever user faces this issue, feel free to get the assistance from the omni support team.

"Error from channel : ReleaseIds: [4027003428] are cancelled in platform" on piece packing screen

While packing an item, omni 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.

"Error from channel : Order release with id 4026593609 does not have courier or tracking number assigned"

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.

"Order :<order id> is Unfulfillable" on Piece Packing Screen

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.

"Error from channel: Some Orders are already manifested., [null,"xxx"]"

Please do following checks,

First login to the Seller Panel.  

Find out the orders which are manifested using the channel manifest id : xxx. 

Please remove those orders in the current manifest list.

Try manifesting for the rest of the orders.      

"Invalid order state : PICKED order id : <order id>"

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.

"Excess GRN is not allowed for Global SKU Id : 1100228277 for quantity:14, Expected quantity13" on Inward - GRN screen

The inward PO contains the SKU 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.

"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.

"Error in closing shipment: Could not create shipment on Tatacliq, Error in closing shipment Internal Server Error 500"

This error comes on Piece-packing screen. This error happens for Tatacliq channel

"Incorrect Item Picked"

This error arises when the warehouse operation team tries to pack an item that is not associated with any order.

"Insufficient inventory to remove, already allocated to some order" while Bin consolidation.

As per the new Bin flow Bin consolidation can be done without making the Bin offline. This error comes when the user tries to move items from LIVE bin to OFFLINE bin where some SKU are already allocated for some Orders.

Error: "No shipment exists for awb: xxx and transporter: xxx" while scanning AWB number in manifest screen.

The error shows that the scanned AWB is not mapped with the transporter linked with the manifest Id created. So user has to check verify the transporter fo the manifest created.

Error: "These Orders are cancelled. please remove them :xxx" while closing the manifest    

Error message means, mentioned Order in the error message is in cancelled status. User has to remove those shipments from the manifest and check the order status on Seller panel and confirm the cancellation and recycle the item.

Error: "Unable to complete ReturnOrder: xxx since some of the items in return order expectation are not yet processed" while closing the return order completion

A return Order can be marked completed only if all its line items are processed or no pending items should be there. If a user gets this error, check the whether all line items are processed o rnot. If there is there any item pending, then those items have to be processed, else if the left item is not found, mark those items as MISSING' using missing button as shown in the screenshot.

Error: "Error From Channel: Manifest cannot be created for orderId: xxx, status: xxx" while closing the Manifest.

While closing the manifest, system checked the status of the Order on the Seller panel. If any order is processed offline (not via WMS) and dispatched or cancelled or returned to origin on the seller panel user will face such error while manifestation.

For such an error, the user has to remove the Order id from the manifest mentioned in the error message.

Error: "No shipment found for orderId:[xxx], externalInvoiceId: [xxx]"

This error occurs when the order is in Dispatched status. That is the reason you are not able to Handover the order. 

Error in closing shipment: Error creating order from rms, error message: Error From Channel: Error while creating order on Shiprocket, errors: [The billing phone must be 10 digits.][The shipping phone must be 10 digits.]

This error occurs when the phone number entered has a space in between the digits or if it is not in a valid format. We get this error from Shiprocket. 

Remove the space if it is present or enter the phone number in a valid format and proceed further.

Item is not associated with any order !!

This error occurs when the user is scanning an item ID which is still in recycle status or not yet picked or already dispatched from the warehouse.

Check the History of the Item Code in Audit Log screen in WMS to know the present status of the item.

Error in closing shipment: Error From Channel : Error in creating invoice pdf from rms, error message: Error From Channel: Error from Clear Tax Attempting IRN generation for seller <XXX (seller)> from GSTIN <xxx (header GSTIN)>. Please ensure that both the GSTINs in header and seller are same to generate IRN. Change the seller GSTIN to <header GSTIN> to generate for that GSTIN.,

The GSTIN of the seller got updated in Omni. That is why the error is coming. The cleartax credentials are on GSTIN level on cleartax (for each gstin there are separate credentials). So either they revert it to the older gstin or we would have to configure the newer cleartax credentials.

The seller has to update the GSTIN

Error in handing over the following Shipments: ["xxx"]. Please remove these shipments and try again

If an order was handed over to Amazon ops poc along with other manifested orders without marking the handover in our system we get this error. Hence as per amazon LP, the order is picked up and the status is marked as Shipped on the seller panel. Mark this orders as completed by using Manual Order Completion

Error: Pigeonhole consolidation still pending for item(s), allocated aisle ID: [xxx]

This error can occur when pigeonhole putaway is not done after sorting for all the line items and the user tries packing a line item. 

Or

This error can occur when pigeonhole putaway is not done after sorting for any line items and the user directly tries packing a line item. 

Some orders are already manifested ,for manifest Id: [xxx] shipments: [xxx],[xxx],[xxx]

This error occurs when there is any API call failure from Tatacliq API, but Tatacliq considers the call API call as close manifest. To resolve this remove the shipment that is present in the error message and make a new manifest for them and close the new manifest. The orders which are not present in the error message can be closed inside the same manifests.

Error: Error in closing shipment: Error creating shipping label from rms, error message: Error From Channel: Error from Shiprocket while generating AWB, error message: Please recharge your ShipRocket wallet. The minimum required balance is Rs 100

Or

Error in closing shipment: Error from Channel: Error creating shipping label from rms, error message: Error From Channel: Error from Shiprocket, message: {"message":"Insufficient amount to label this shipment","status_code":500}

The Shiprocket wallet balance of the client has gone below the minimum balance (Rs 100)

Solution: Recharge the Shiprocket wallet and try processing again.

All items created in gate entry not GRNed

This error occurs when the GRN process is not completed and trying to close Gate entry. To resolve this issue, please check if any items are in New Status and complete QC for the same. 

1. Go to GRN at Item Level Report - WMS or Storage : Non Live Items Report - WMS in Omni Reporting. 

2. Search if any items are in New Status for the respective Gate Entry ID.

3.  Turn on GRN of NEW status items by clicking on Configurations on the top right corner of the screen and then Complete the QC for those items to close the Gate Entry

Could not fetch Batch details for the scanned Perishable SKU !!

This error occurs when External batch ID is not mapped with the Perishable SKU while creating the gate entry. To resolve this issue, go to Gate entry screen and select the Gate entry ID for which the GRN is being done. Click on the Add New Entry to Existing PO and then go to Map External Batch section and upload the CSV file with necessary details.

Error in closing shipment: Error From Channel : Error creating order from rms, error message: Error From Channel: Error while creating order on Shiprocket, errors: [The billing address may not be greater than 190 characters.][The shipping address may not be greater than 190 characters.]

Or

Error in closing shipment: Error From Channel : Error creating order from rms, error message: Error From Channel: Error while creating order on Shiprocket, errors: Address 1 and Address 2 combined cannot be greater than 190 characters

Shiprocket has certain validations on details like Order ID, phone number, Address, pincode etc. As Increff proxy creates orders on Shiprocket panel, shiprocket throws an error if the validation is not met. If this is for Shopify channel and if the update webhook is configured, the data has to be updated on shopify as per the shiprocket validation that is the shipping address 1 and shipping address 2 together may not be greater than 190 characters. The same will flow to Increff.

Or

Error in closing shipment: Error from Channel: Error creating order from rms, error message: Error From Channel: Error from Shiprocket, message: {"message":"Oops! Invalid Data.","errors":{"shipping_city":["The shipping city may not be greater than 30 characters."]},"status_code":422}

Shiprocket has certain validations on details like Order ID, phone number, Address, pincode etc. As Increff proxy creates orders on Shiprocket panel, shiprocket throws an error if the validation is not met. If this is for Shopify channel and if the update webhook is configured, the data has to be updated on shopify as per the shiprocket validation that is the shipping city may not be greater than 30 characters. The same will flow to Increff.

Error From Channel: Error while creating order on Shiprocket, errors: [The order id may not be greater than 50 characters.]

Shiprocket has certain validations on details like Order ID, phone number, Address, pincode etc. As Increff proxy creates orders on Shiprocket panel, shiprocket throws an error if the validation is not met. The order with this error have to be cancelled and replacement order for the same can be created. 

Error From Channel : Shipments more than 100 not allowed

This error occurs when more than 100 shipments are added in 1 manifest. Remove the extra shipments and try closing them in a different manifest.

Error in closing shipment: Error From Channel : PickList not yet released for order: [xxx]

The mentioned Channel order  ID in the error message  is still under upcoming orders on Flipkart seller panel dashboard. Hence the picklist has not been released yet. The dispatch details can be checked on the Flipkart seller panel. The orders can be processed only post that.

Error in closing shipment: Error From Channel : 500 Internal Server Error 

 The error occurs when the order is processed in Flipkart smart seller panel. Log in to seller panel using the credentials available at your end. Check the order status in seller panel by searching the parent order id and manually complete them on Increff panel.

Error in closing shipment: Error from Channel while creating Shipment: shipmentlength,shipmentbreadth,shipmentheight,shipmentweight values should not be empty. .Status Code: 601

Or

Error in closing shipment: INCREFF_FC003: SKU dimensions not configured in Firstcry Proxy

This error occurs when shipment length, shipment breadth, shipment height and shipment weight values are empty. 

Populate those values in VCOM Portal and then process the order.

Error in closing shipment: Error from Channel: Error creating shipping label from rms, error message: Error From Channel: Error from Shiprocket, message: {"message":"No courier service available between [pincode] and [pincode]","status_code":400}

Or

Error in closing shipment: INCREFF_SHOPIFY003: Error creating shipping label from rms, error message: Error From Channel: Error from Shiprocket, message: {"message":"Delivery postcode not serviceable.","status_code":400}

Or

Error in closing shipment: INCREFF_SHOPIFY003: Error creating shipping label from rms, error message: Error From Channel: Pincode not serviceable by clickpost/Shiprocket

Or

Error in closing shipment: Error from Channel: Error creating shipping label from rms, error message: Error From Channel: Error from Shiprocket, message: {"message":"No Courier serviceable for entered pincodes.","status_code":400}

Or

Error in closing shipment: INCREFF_SHOPIFY003: Error creating shipping label from rms, error message: Error From Channel: Error from Shiprocket, message: {"message":"Postcode not found in postcode_master : [xxx]","status_code":400}

If this error occurs it means the pincodes are not configured in shiprocket/clickpost, therfore raise the issue to seller and ask them to configure the pincodes. As a permanent fix To restrict the customer from placing the order on the Shopify panel if they have given non-configured pin codes.

"Internal Error in WMS" while uploading Handover receipt

This error occurs if the file size is too big. Please upload files within 10 MB size.

Error in handover :Error From Channel : Error from Channel while fetching orderDetails: API Hit Quota Exceeded

The following marketplaces Flipkart, Flipkart Smart , Nykaa , Nykaa Fashion and Trell have a maximum api usage quota of 429. This error occurs when the API count surpasses the same. This needs to be raised to the respective marketplace.

Error in closing shipment: Error From Channel : Could not create shipment on Tatacliq. Failed TransactionID : [xxx], Message : Transaction not in possible status to Generate AWB

Kindly check for the order status on seller panel. If the order is in cancelled status on seller panel, manually cancel the order in Increff by referring to the document Manual Order Cancellation.

Shipping Label with AWB number  XXXXX and transporter starlinks already exists : 

This error occurs because the shipping label with respective AWB Number and transporter starlinks already exists in the system.  This error is due to channel and it must be raised to the channel that one AWB Number cannot be associated with multiple orders, due to which shipping label and invoice are unable to be generated.

Error in closing shipment: Error From Channel : Error creating order from rms, error message: Error From Channel: Error while creating order on Shiprocket, errors: [The shipping email must be a valid email address.]

Shiprocket has certain validations on details like email ID, phone number, Address, pincode etc. As Increff proxy creates orders on Shiprocket panel, shiprocket throws an error if the validation is not met. The order with this error have to be cancelled and replacement order for the same can be created. 

Unable to fetch client-channel details for clientId: [xxx] and channelId:INTERNAL , Error : Channel Alias:INTERNAL doesn't exist for client:[xxx]

This means that the Item Code you are trying to process in Return Order Processing belongs to a B2B Outward Order with Channel as Internal. Such Item Code cannot be processed in B2C Return Order Processing. In order to inward the item, an Inward Order with Type as Return should be placed and then the item can be processed.

Note: To confirm whether the item belongs to a B2B Outward Order, you can search the Item Code in Audit Log screen in WMS where you can find the sub order id of the Outward Order.

Batch ID provided for non-perishable product

During GRN if the gate entry contains both perishable and non-perishable products, this error occurs since batch ID would not be present for non-perishable products. You will need to do the GRNfor non-perishable products on a different GRN.

Error in closing shipment: Error From Channel : Error creating order from rms, error message: Error From Channel: Error while creating order on Shiprocket, errors: Address 1 and Address 2 combined cannot be less than 3 characters

Shiprocket has certain validations on details like Order ID, phone number, Address, pincode etc. As Increff proxy creates orders on Shiprocket panel, shiprocket throws an error if the validation is not met. If this is for Shopify channel and if the update webhook is configured, the data has to be updated on shopify as per the shiprocket validation that is the shipping address 1 and shipping address 2 together may not be lesser than 3 characters. The same will flow to Increff.

Cannot complete Return Order as some of the items are still in NEW state : [xxx]

Kindly turn on GRN of 'NEW' status items toggle in Return Order Processing screen under Returns in WMS and then process the return order.

Invalid minExpiry/batch details provided for perishable SKUs: XXXX

The client entered the wrong batch details while creating the order, please ask client to check batch details while creating the order.

Error From Channel : Error marking order RTD: [xxx] 400 Bad Request

This error occurs if the order has been directly processed from seller panel. Kindly remove the order from the manifest and manually mark the order as completed by referring to Manual Order Completion.

Error in closing shipment: Error From Channel : Error from Channel while creating Shipment: Order is on Hold on Panel

This error occurs when the order is on hold on the marketplace for verification purposes. The order will be released by the marketplace for further processing after the verification.

No skus found for client Id and barcode combination 

This error occurs when the Client SKU Id and the barcode combination has been incorrectly uploaded in the Masters or wrong codes are being scanned while during GRN. 

Error in closing shipment: Error From Channel : Error creating shipping label from rms, error message: Error From Channel: Error from Shiprocket while generating AWB, error message: Invalid Customer Address

This error occurs when invalid customer address is given. Kindly check the customer address and update it in CSR Panel according to shiprocket validation.

Error From Channel : ERROR FROM CHANNEL: Packing in progress, Please retry packing after some time

This an error from the marketplace, kindly retry packing after sometime. 

Error in closing shipment: Error from Channel: 401 Unauthorized

This error occurs when the credentials have been updated on the seller panel. Kindly update the same in CIMS.

Error in closing shipment: Could not create shipment on Tatacliq. Failed TransactionID : [XXX], Message : Transaction not in possible status to Generate AWB

This error occurs when the order has been cancelled on the seller panel but the cancellation has not been synced to Increff. Kindly cancel the order manually by referring to Manual Order Cancellation.

 Error in closing shipment: Error from Channel: Error creating order from rms, error message: Error From Channel: Error from Shiprocket, message: {"message":"SKU cannot be repeated.","status_code":400}

Or

Error in closing shipment: Error from Channel: Error in computing tax and creating invoice pdf from rms, error message: Error From Channel: Quantity not matching for sku [xxx] ,stored quantity=2, requested quantity=1

This error occurs when the same SKU has been passed for different products while hitting the order creation API. Kindly cancel and create another order using the quantity field if there are many quantities for the same product.

This error happens when we attempt to process an item that is already live through returns. Please verify the item's status on the recycle screen and communicate it to the client.

Error in closing shipment: Error from Channel: Error From Channel: Error from Clear Tax EInvoice.ItemList[0].HsnCd : HSN code provided for line item is 00000000.0 which is of invalid length. Please send valid HSN/SAC codes via https://einvoice1.gst.gov.in/Others/MasterCodes,EInvoice.ItemList[0].HsnCd : HSN code 00000000.0 in line item 1 is invalid. Please check the HSN/SAC codes via https://einvoice1.gst.gov.in/Others/MasterCodes,

Please update the correct HSN in OMS--> Products screen and then process the order.

Error in closing shipment: Error from Channel: Error creating order from rms, error message: Error From Channel: Error from Shiprocket, message: {"message":"Oops! Invalid Data.","errors":{"breadth":["The breadth must be greater than or equal to 0.5."]},"s

This error occurs when shiprocket's validation is violated. Please update the length, breadth, height and weight in OMS--> Products screen according to the value mentioned in the error message and then process the order.

Error: Error in closing shipment: INCREFF_SHOPIFY003: Error creating shipping label from rms, error message: Error From Channel: Error from Shiprocket, message: {"message":"[\"Customer city is empty\"]","status_code":400}

This error occurs when shiprocket's validation is violated. Please update the customer city on the seller panel or the CSR panel and then process the order.

Error in closing shipment: INCREFF_SHOPIFY003: Error creating shipping label from rms, error message: Error From Channel: Error from Shiprocket, message: {"message":"[\"Customer name contain numbers or special characters\"]","status_code":400}

This error occurs when shiprocket's validation is violated. Please update the customer name on the seller panel or the CSR panel and then process the order.

Error in closing shipment: INCREFF_SHOPIFY003: Error creating shipping label from rms, error message: Error From Channel: Error from Shipway: ecom (carrier_id 5) <br/>Order Id: XXXXXX-sXXXXXXXX : Delivery is not operational on pincode XXXXXX at this moment !.

Or

Error in closing shipment: INCREFF_SHOPIFY003: Error creating shipping label from rms, error message: Error From Channel: Error from Shipway: ecom (carrier_id 5) <br/>Order Id: xxxxx-sYYYYY : CONSIGNEE PINCODE NOT SERVICED.

This error occurs when the given pincode is not serviceable by Shipway. 

Error in closing shipment: INCREFF_SHOPIFY003: Error creating shipping label from rms, error message: Error From Channel: Error from Shiprocket, message: {"message":"[\"Customer city is invalid, Language other than english is not supported.\",\"Customer Address is invalid, Language other than english is not supported.\"]","status_code":400}

This error occurs when the customer's city and address have been given in any language other than English. Please update this in the CSR panel or the seller panel, and then try packing the order.

Error in closing shipment: Error from Channel: Error from Channel: Serial/IMEI number is missing. Please enter Serial/IMEI number and retry.

This error occurs if the IMEI number is not mapped with the Item ID for electronic devices. Please follow the below steps to resolve the error.

1. Go to WMS--> External Serial Code Mapping screen.

2. Scan the Item ID and in the External Serial Code field, scan the IMEI number.

3. Try packing the order again after the mapping is done.

Error in closing shipment: Error from Channel: Error creating order from rms, error message: Error From Channel: Error from Shiprocket, message: {"message":"Oops! Invalid Data.","errors":{"billing_pincode":["The billing pincode must be 6 digits."],"shipping_pincode":["The shipping pincode must be 6 digits."]},"status_code":422}

This error occurs when the given pincode is less than or more than 6 digits. Please update this in the CSR panel or the seller panel, and then try packing the order.

No Return Gate Entry Items found in RECEIVED/PROCESSING status !!

This error occurs if the AWB is not associated with any of the return gate entries. Please create the return gate entry and map the AWB to it before processing the return order.

Error in closing shipment: INCREFF_SHOPIFY003: Error creating shipping label from rms, error message: Error From Channel: Max Length of 100 Exceeded for Address-1

This error occurs when the given customer address has exceeded 100 characters in Address-1 field. Please update this in the CSR panel or the seller panel, and then try packing the order.