Audience: Suppliers

The Rithum platform provides several Exceptions pages to help you isolate and handle any issues that arise with your retailer connections or fulfillment process. 

Here are the available types of exceptions:

  • Pipeline exceptions - All notifications that pertain to system changes or issues, including file failures and data issue exceptions. Pipeline rules include all the platform standard rules as well as any additional validation rules applied by your trading partner.
  • Order exceptions - All exceptions that relate to the fulfillment of orders, such as acknowledging, shipping, cancelling, invoicing. Order exceptions are measured based on your retailer's configured SLA rules. For more information, see Viewing and resolving order exceptions.
  • Inventory exceptions - All exceptions that relate to inventory, such as update frequency, etc. Inventory exceptions are measured based on your retailer's configured SLA rules. For more information, see Viewing and resolving inventory exceptions.
  • Catalog exceptions - All exceptions that relate to products with non-compliant attribute, if your trading partner uses advanced catalog services. For more information, see Viewing your catalog exceptions.

Interested in getting email alerts when exceptions occur? Learn more about configuring your notification preferences.

Viewing and resolving pipeline exceptions

Important: For Pipeline exceptions, the Exceptions page can only display errors with data that has been delivered and processed in your Rithum account. If there is an issue with your data feeds not making it to the platform in the first place, those will not appear as exceptions. Please reach out to the Software Support team for help in diagnosing missing data feeds.

 

Step 1: Click the navigation menu and select Automation & Reporting > Exceptions >  Pipeline Exceptions. The Pipeline Exceptions page is displayed with a list of your exceptions, with the most recent exceptions at the top.

In this example, Invoice 55172506 failed to create because it was submitted without a total amount.

Step 2: From here, you can:

  • Filter and view exceptions based on their severity. Click:
    • Error: The exception caused the update to reject completely. 
    • Warning: The update was still processed, but a warning was issued. These warnings are useful when your retailer may be planning to enforce a new requirement, but wants to give you time to adjust your data feed before actually rejecting those updates. 
    • Info: The update was processed but includes an informational message. This is the least impactful severity but may hold useful information about your data.
  • Resolve a pipeline exception. Click the exception you'd like to resolve, and it will expand to a detailed view.

Note: Some exceptions cannot be resolved using the Exceptions page and can be resolved outside of the page. For example, re-submitting an invoice with a valid total amount via an upload or other process will remove the exception from the page.

In the example below, the following options are displayed to (a) fix the invoice total and (b) provide a valid UPC code.

Step 3: Fill out the appropriate fields to resolve the exception and click Save.

 

Was this article helpful?
0 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.