Predictika · Vehicle fleet orders
An AI sales agent prepares a fleet order for 2026 Subaru Forester vehicles: trims, option packages, paint colors and the delivery state. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of Subaru's published trim, package and paint information and returns a verdict, every reason, a line-item quote and the figures it computed.
This validator models 2026 Forester orders built on the trims, prices, option packages and paint information Subaru has published, not just the scenarios shown below.
Any 2026 Forester fleet order that touches these rules is in scope — not only the scenarios pictured here. Not covered: other Subaru models, model years, dealer-installed accessories, taxes, registration and dealer fees, financing, and fleet incentive amounts (not published). Assumptions: color availability on trims other than Wilderness is not restricted in this model, and prices are MSRPs from the launch pricing announcement and may have changed.
8 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch
Proposing agent: AI sales agent (scripted)
Before sending, the agent must call Recorded run
What this means
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in typical CPQ products) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.
| What the validator caught | Typical rules-based CPQ | Predictika |
|---|---|---|
| Stated order totals that must equal the published prices | Only with care A stated figure is a free-entry field; a rule can compare it with a computed total, but the total depends on trims, packages, paint and the destination charge that have to be kept in step with the price list. | The stated total travels with the order and is compared with the computed total on every call. |
| Option packages that exist only on some trims | Easy A product rule can restrict a package to the trims that offer it. | The same rule is checked with the rest, on every line. |
| Colors that depend on the trim, such as Wilderness | Only with care A compatibility table of trims and colors. It works, but every added color or trim means editing the table, and a premium paint price rides on some of the colors. | Trim, color, paint charge and the order total are in one request and are checked together. |
| A multi-line order where each line has its own trim, package and color | Only with workarounds Rules usually run per line, so a total that must agree with every line, the delivery state and a fleet discount needs cross-line rules that interact with each other. | Every line, the delivery state and the total are checked at once. |
| Every problem returned in one answer | Only with workarounds Rules tend to fire as the quote is saved or a step is completed, so a rep often fixes one error and meets the next. | All findings come back together, whatever order the choices arrived in. |
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the order; approval findings need a person to sign off; everything else is computed. The same rules apply to each of the three order lines.
| 1 | Line 1 adds an option package, but the Base and Touring trims have no option package. |
| 2 | Line 1 asks for Geyser Blue, which is only available on Wilderness models. |
| 3 | Line 1 asks for a Wilderness in a color that is not among the six Wilderness colors (Autumn Green Metallic, Crystal Black Silica, Crystal White Pearl, Geyser Blue, Magnetite Gray Metallic, River Rock Pearl). |
| 4 | The order has 0 vehicles; at least 1 is needed. |
| 5 | Line 1 has a negative quantity of -2 vehicles. |
| 6 | The order states a total of $348,349; the published MSRPs and destination charges give $348,350. |
| 7 | A fleet incentive or volume discount is not published; a person should confirm it before the order is sent. |