Skip to content

RIO Inventory

  1. Home
  2. RIO Inventory
  3. Release Notes
  4. 3.0


Retired the Basic (free) version

From this release, the Basic version is no longer available. Users who worked in the basic version who would like to upgrade to a paid version can contact WDCi by emailing and we can assist with steps to migrate any existing inventory records into the new version.



Terminology changes

We have changed the names of some of the terms and objects used in RIO inventory. Examples of the new terms are:

Inventory is assigned to a warehouse location (previously the term assigned and allocated were both used)

Inventory on an opportunity goes through 3 stages in the lifecycle of the opportunity.

  1. Assigned – this is the initial stage before the opportunity reaches the reserved threshold
  2. Reserved – reserved inventory does not impact quantity on hand, but it does reduce inventory available.
  3. Committed – committed inventory reduces the quantity on hand.


We have retired the term “stock” and standardised on the term inventory through the labels and error messages.


Low Inventory Threshold is a new term that is on the configuration page and the product page. This is the inventory count that indicates low stock. By default it is set on the Config page and applies to all products. You can override this number on the product screen if the override option is set on the configuration screen.




RIO Inventory no longer requires the use of a licence key, simplifying the trial and purchase process. You can now subscribe for a trial and purchase your licenses directly through the Appexchange.


The configuration page is simplified with the new terms making it easier to configure.


There is now a single click method for re-assigning inventory from multiple warehouses directly from the opportunity screen.


WDCi has developed an integration job to help RIO Inventory customers to import inventory information from Xero to Salesforce.  Data from other sources can be imported using CSV files, as long as the file uses the same format as those listed in the instructions below.



Changes to handle large numbers of Products:

  1. Changes have been made to the validation mechanism to address issues with validation exception when encountering very large data sets (over 100000)
  2. Changes have been made to the configuration mechanism to handle very large product counts in the instance (over 50000)


Changes to the OpportunityLineItem mechanism:

Previously, RIO Inventory did not handle existing OppLineItem so that when RIO Inventory saw the old OppLineItem,  it would only create 0 quantity assignments for it.  RIO Inventory now takes the existing OppLineItem quantity as the default assignment value instead of 0.


This means that for new users who install RIO Inventory, they no longer have to go to each of their existing OppLineItem and assign a quantity assignment for them, whatever quantity they have set for the OppLineItem is the default value.


Fix on the configuration when old version was not activated:

If RIO Inventory was not activated properly, a bug would occur when upgrading from old versions of RIO Inventory (v1.5) to newer versions of RIO Inventory (v1.6 upward).  This fix now allows upgrading without prior activation.


Was this article helpful to you? Yes No

How can we help?