System alerts can alert your team to issues with orders, channels, inventory, and more. Please monitor your System Alerts for issues with your account. The System Alerts viewer can be found in the upper right corner of RetailOps, next to your username.
Below, you'll find a general definition for each alert. If you are concerned about a specific alert or set of alerts, please contact RetailOps Support.
To learn more about resolving System Alerts, check out this article: Resolve System Alerts
Title |
Definition |
Action Item |
Applies to order returns only. Action items are notes manually entered by a user when returning an item through the Order Returns tool. |
Adjustment Processing Error |
The Perfect Pick inventory agent attempted to adjust inventory, but was unable to do so. |
Amazon Invpush Fail |
RetailOps attempted to push an inventory update to Amazon, but an error in Amazon caused this to fail. |
Attach Payment Failed |
Retailops has attempted to record a payment with the order, but an error has occured with the channel. Please review the order and update payment if necessary. |
CA Feed - CA Reported an error |
RetailOps has attempted to send catalog data to ChannelAdvisor. However, an error in the data has caused this to fail. |
CA Feed Api Remote General Error |
ChannelAdvisor is experiencing difficulty, please contact your ChannelAdvisor representative or CA Support. |
Capture Grand Total Failed |
For customers using pre-shipment payment capture, this indicates that the payment capture has failed, and you will need to record a new payment to proceed. |
Channel Cancel Fail |
RetailOps has attempted to notify the sales channel that the customer order has been canceled. However, the attempt has failed. |
Channel Catalog System Error |
RetailOps has attempted to send catalog data to the sales channel. However, an error in the sales channel has caused this to fail. |
Channel Catalog User Error |
RetailOps has attempted to send catalog data to the sales channel. However, the feed template has been misconfigured and thus, it is sending invalid data to the channel. |
Channel Complete Fail |
RetailOps has attempted to notify the sales channel that the customer order has been fulfilled/completed. However, the attempt has failed. |
Channel Fulfillment Fail |
RetailOps has sent fulfillment data to the channel, but the channel was unable to process the fulfillment data. |
Channel Order Import/update failure |
Typically on Amazon orders, this error indicates the SKUs on the order were changed after the order was created. |
Channel Orderpull Fail |
RetailOps attempted to pull orders from a channel, but encountered an error, preventing order import. Please check the order reference number to ensure it was imported before clearing the alert. |
Channel Refund Due |
The refund was unable to be processed through Channel Advisor and will need to be processed manually based on payment types. |
Channel Rejected Tracking |
Tracking information is different than what is currently selected (e.g. Fedex's shipping was used but uploaded into Channel Advisor as USPS) or mismatched quantities have been entered into Channel Advisor. |
Channel Shipment Fail |
RetailOps has sent shipment data to the channel, but the channel was unable to process the shipment data. |
Class Code Unmatched |
When using the Amazon "Buy Shipping" API and Channel Advisor, this indicates the shipping class code is not an expected value, and may be a new addition by Amazon. Please contact help@retailops.com with this error message. |
EDI 810 Invalid |
EDI 180 regards invoice specific errors. This may include invalid order shipment (OS) items, duplicate items, items linked to other orders through Dropship/JIT and incomplete orders with no OS items attached. |
EDI 850 Failed to Transmit |
EDI 850 regards PO-specific errors including missing quantities, shipping details, and payment terms. |
Insufficient in-store inventory |
Applies to POS orders only. There are not enough units of the requested item stored inside the retail store zone to fulfill the order. |
Inventory Sync Failed |
RetailOps has attempted to send data on inventory levels to the sales channel. However, the attempt has failed. |
Inventory Unavailable |
There are no longer enough units of this item available to fulfill the order. This often means either that inventory has been reserved by another order or that inventory has been moved into a non-pickable location. |
Magento Extension Catalog Push Fail |
RetailOps has attempted to send catalog data to the sales channel. However, an error in the sales channel has caused this to fail. |
Magento Extension Invpush Fail |
RetailOps has attempted to send inventory data to the sales channel. However, an error in the sales channel has caused this to fail. |
Magento Failed to Update Inventory |
RetailOps has attempted to send updates on inventory levels to Magento. However, the attempt has failed. |
Magento Feed - Magento Returned an error |
Legacy Magento Connector - RetailOps has attempted to send catalog data to the sales channel. However, an error in the sales channel has caused this to fail. |
Magento Feed - Template Warning |
Legacy Magento Connector - RetailOps has attempted to send catalog data to the sales channel. However, an error in the feed template has caused this to fail. |
Order Expired |
The customer order has reached or exceeded its Cancel Date without reaching Status: Fulfilled. However, the order has not been canceled yet. |
Order requires review |
The order is missing one or more items to allow processing, which may include: insufficient funds, incorrect payment type, invalid items, missing shipping service or no service selected, or contains items that are no longer available/in stock. |
Payment Settlement Failure |
An attempt to settle the payment or refund with the channel was not successful. |
Payment Settlement Nsf |
Upon payment settlement, the funds are not sufficient either because they are not available or they do not meet the order total. |
Pick Confirm Error |
RetailOps requested an inventory pick in Perfect Pick, but the pick was not completed sucessfully. Please review the error for more detail. |
Picking Move Fail |
RetailOps requested an inventory pick in Perfect Pick, but the pick was not completed sucessfully. Please review the error for more detail. |
PO Detach - PO No Longer Considered Viable |
Based on the vendor setting "Post Receipt Viable (days)", the PO is no longer considered "viable". Once a PO goes into a "Receiving" status, this countdown begins. |
PO Detach - Vendor Config |
A change was made to the vendor configuration, which caused the PO item(s) to detach. |
PO ready for review |
The PO has turned to Status: Review to be reviewed before manual submission to the vendor. This is intended for manual PO workflows that do not utilize the automatic PO transmission feature. |
PO Ship address changed after submission |
Applies to Dropship orders only. The Ship Address was changed after the PO went into Status: Submitted. |
Putaway Confirm Error |
When performing a putaway, Perfect Pick sent incorrect container details to RetailOps. Please contact your Perfect Pick support team for more information. |
Refund Due |
The refund was unable to be processed automatically, and will need to be processed manually. |
Return Submit Fail |
RetailOps has attempted to submit data on order returns processed through RetailOps. However, the attempt has failed. |
Ship Map Failed |
Ship mapping from a specified source (e.g. ChannelAdvisor, Buy.com, Amazon) was not setup in Shipping Setup to have a default shipping method. Orders will not ship until mapping has been setup. Please refer to the "Map Ship Services to Channels" section of this article: https://bit.ly/2FJIgBU |
Shopify Catpush Error |
RetailOps attempted to push catalog data to Shopify, but an error prevented this. This error is returned by Shopify, please contact Shopify Support for more information. |
Shopify Invpush Missing ID |
This alert indicates that your inventory sync with Shopify is experiencing trouble due to a missing Shopify ID. Please contact help@retailops.com for assistance. |
Comments
0 comments
Please sign in to leave a comment.