Minimum Version Required: 26.07
Pre-Conditions
How to read this article: A table is where Encompass stores a set of records (for example, the Suggested Order History table). A field is a single piece of data on a record within a table (for example, the Suggested Order Quantity field). Table and field names appear in bold throughout, and each is labeled as a table or a field.
Before you begin, you will need:
The Customer, Product, and pre-sell date (or the downloaded Event) of the recommendation you are investigating.
Access to these tables: the Suggested Order History table, the orderIQ Model Data table, the Suggested Order Overrides table, the Suggested Order Configurations table, and the orderIQ Customer Product Combinations table.
Steps
How OrderIQ calculates the suggested quantity
The quantity a sales rep sees on the Invoice Edit page in Encompass Mobile is stored in the Suggested Order Quantity field on a record in the Suggested Order History table. OrderIQ calculates it with this formula:
Suggested Order Quantity = round( Num Units × Order Size )
The Num Units field (in the orderIQ Model Data table) is OrderIQ's forecast for that customer, product, and date. The Order Size field is the multiplier applied to that forecast. The result is rounded and saved as the Suggested Order Quantity field.
To trace a recommendation back to its source:
Open the Suggested Order History table and filter by the Customer, Product, and Date fields (the pre-sell date; on mobile this is tied to the downloaded Event). Read the Suggested Order Quantity field – this is the number the rep saw.
Open the orderIQ Model Data table and filter by the same Customer, Product, and Date fields. Read the Num Units field (the forecast), and for context the Lower Bound and Upper Bound fields.
Find the Order Size multiplier that was applied. First check the Suggested Order Overrides table for a record that matches this Product (or its brand, package, or supplier). If one applies, use its Order Size field. If no override applies, use the Order Size field on the account's record in the Suggested Order Configurations table.
Multiply and round: Num Units × Order Size, rounded, equals the Suggested Order Quantity field from step 1.
Fields And Definitions
Fields are grouped below by the table they belong to.
In the Suggested Order History table:
Suggested Order Quantity - The suggested number shown on the Invoice Edit page.
Date - The pre-sell date the suggestion is for.
Event - Links the suggestion to the route stop the salesperson downloaded.
Source - Indicates how the suggestion was generated.
In the orderIQ Model Data table:
Num Units - OrderIQ's forecast, in units, before the Order Size multiplier is applied.
Lower Bound / Upper Bound - The forecast confidence range around Num Units.
Is Used - Whether this record fed the suggestion.
In the Suggested Order Overrides table:
Order Size - The multiplier applied to Num Units when the override matches a product (or its brand, package, or supplier). Takes priority over the configuration value.
Round Threshold - Controls how the multiplied result is rounded.
Force To Case - Forces the result to whole-case quantities.
In the Suggested Order Configurations table:
Order Size - The account-level default multiplier, used when no override applies to the product.
In the orderIQ Customer Product Combinations table:
Sales Type - Classifies the product's sales pattern: Smooth, Intermittent, or Erratic. Only Smooth and Intermittent generate a record in the Suggested Order History table.
Best Practices
Use these troubleshooting paths when a suggestion looks wrong. Each one names the exact field and table to check.
If the suggested quantity is lower than what the rep usually orders, and the customer has two pre-sell stops in the week → Check the Order Size field in the Suggested Order Overrides table. For a two-stop customer, enter Order Size as a pair “xx;xx” – one value per stop. If you enter a single value, only the first stop uses the override; the second stop falls back to the smaller Order Size field in the Suggested Order Configurations table, so the second stop reads low.
Example A – product 18174, customer 4926, override Order Size 2: first stop (7/14) = Num Units 9 × 2 = 18 (rep ordered 14); second stop (7/16) = Num Units × 0.62 (configuration Order Size) = 5 (rep ordered 7). Entering “2;2” applies the override to both stops.
Example B – product 44074, customer 6182, override Order Size 4: second stop (7/16) = Num Units 1.940166 × 0.56 (configuration Order Size) ≈ 1 (rep ordered 3). The first stop used the override; the second fell back to the configuration.
If the forecast itself looks low → Check the Num Units, Lower Bound, and Upper Bound fields in the orderIQ Model Data table. Num Units accounts for holidays and promotions, so right after an event week (for example, the week of July 4th) with no upcoming event, the forecast drops toward the typical “no-event” level. Compare Num Units against its Lower Bound/Upper Bound range and the account's recent weekly sales before concluding it is wrong.
If no suggestion appears at all for a product → Check the Sales Type field in the orderIQ Customer Product Combinations table. Only products with Sales Type = Smooth or Intermittent generate a record in the Suggested Order History table. If the Sales Type is Erratic, OrderIQ creates no suggestion and nothing appears on Invoice Edit.
Remember the suggestion is a starting point → Reps can adjust the Suggested Order Quantity field on the invoice before submitting, so an occasional low or high suggestion can be corrected at the point of order.