1. Home
  2. AgVerdict Next
  3. Recommendation
  4. Feature Enhancement: Rec Based Shipping Papers

Feature Enhancement: Rec Based Shipping Papers

This is the second release phase of Shipping Papers. In this we are introducing the ability to create Recommendation based Shipping Papers.

This feature is by branch and will be available for Salinas’s branches with the first release.

You can find this new option under the recommendation reports, and selecting “Shipping papers”.

It will only be available for Recommendations that have priced products. You must make sure to have appropriate SKU associations in Pricing sections for all products you would like to see on the Shipping Paper. The same process is currently for App Scheduled-based Shipping Papers.

The overall process is no different than the process we have for App Scheduled-based Shipping Papers. After the Recommendation is Submitted, the user can navigate to the reports page, and select “Shipping Papers” and press ‘Create Papers’. Since we are utilizing JDE to generate the paper for us and send it back to us, it will take some time to get the papers back. Press ‘Refresh Status’ in order to see the latest Status of your papers. Once they are ready, you will be able to view them by pressing ‘View Selected’.

Modifications on Rec-Based Shipping Paper:

  1. In Rec-based Shipping Paper, Rec Number is going to be printed in ‘Order NO:’ field as shown in the screenshot.
  2. Ship Date will reflect Rec Proposed Date
  3. Loader Name field is always going to be empty

Create Shipping Papers on Submit


When submitting a recommendation we have added an option for “Create Individual Shipping Papers”. This was done in order to minimize the waiting time on the Shipping Papers page in Reports.

Addressed Issues:

We fixed an issue with Ship Date on the Scheduled-based Shipping Papers. We have updated the “Ship Date” information on the Shipping Papers to reflect the “Application Date”. Prior to this we were using the created on date which was deemed to be not in line with DOT requirements.

We addressed an issue with the “Duplicate recommendation” feature. The issue occurred when you duplicated a recommendation then added any new fields. This is now working as expected. 

Was this article helpful?

Related Articles

Leave a Comment