Skip to main content

Dealer Modifications

DealerModificationsComponent measures how often a dealer changes the build we ordered. The dealer acceptance rate is 1 minus modified_rate. The component classifies the deltas in placed_order_deltas, which compare our cured build with each capture of an order. See Build Deltas.

Which changes count​

A changed feature counts when it satisfies the OEM's counted_features_filter, a SQL condition on the columns of consolidated features. A replacement within a mutually exclusive group counts once.

A changed code that resolves to no consolidated feature has no feature_id. It is left out of counted_changes. The unresolved_changes check counts it. The check's metadata lists up to five orders that have an unresolved change.

Order filters and modification levels​

Each OEM configures named order filters and named modification levels. The component computes a rate for every pair of an order filter and a modification level.

  • An order filter selects the placed orders that a rate covers. Its where is a SQL condition on an order_modifications row.
  • A modification level defines when an order counts as modified. It has max_feature_changes and max_msrp_change_pct. An order reaches the level when its counted changes exceed max_feature_changes. An order also reaches the level when the absolute change in MSRP, as a percentage of the cured MSRP, exceeds max_msrp_change_pct.

Stellantis configures two order filters. settled selects locked orders, whose builds can no longer change. all selects every placed order. Orders placed in a recent month may not be locked yet. The all rate includes them. For a recent month, it counts the modifications made so far. Stellantis also configures two modification levels. An order reaches any when it has any counted change or any MSRP change. An order reaches significant when it has more than two counted changes or an MSRP change of more than 2%.

Assets​

Each asset is written to <oem>/<market>/reporting/, with one partition per day.

AssetRows
order_modificationsOne for each order that has a placed_order_deltas row in the day's partition or an earlier one
modification_rates_by_<key>One for each group, placement month, order filter and modification level
feature_modification_ratesOne for each dealer, model_id, placement month, order filter and feature

An order's row in order_modifications comes from its latest placed_order_deltas row. placed_order_deltas has no rows for an order after its first locked capture. So for a locked order, the row has the delta between our cured build and that capture. order_filter_names lists the order filters that select the order. modification_level_names lists the modification levels that the order reaches. placement_month is the month of placed_on. cured_features has the feature_id of each counted feature of our cured build, from the cured_features of the order's placed_order_deltas row. added_features has the feature_id of each counted feature that the dealer added. removed_features has the feature_id of each counted feature that the dealer removed. For a replacement, added_features has the new feature and removed_features has the replaced feature.

A day's partition of order_modifications reads every partition of placed_order_deltas and the day's partition of consolidated features. The asset's automation condition acts only on the latest day's partition. The condition requests a run of that partition once the day's partition of features exists and at least one partition of placed_order_deltas is materialized. The other partitions of placed_order_deltas may be missing. The condition requests the partition again each time a partition that it reads is materialized.

Each configured grouping has its own modification_rates_by_<key> asset. A grouping's group_by lists columns of order_modifications or of an asset in joins, such as business_center from consolidated dealers. A row of modification_rates_by_<key> has these columns:

  • placed_order_count is the number of orders that the order filter selects.
  • modified_order_count is the number of those orders that reach the modification level.
  • modified_rate is modified_order_count divided by placed_order_count.
  • feature_types has one entry for each feature_type that has a counted change in an order that reaches the row's modification level. An entry has these fields:
    • changed_order_count is the number of those orders that have a counted change of that type.
    • rate is changed_order_count divided by modified_order_count.

For each order filter and modification level, the totals_match_orders check sums placed_order_count over the rows of the asset. The check passes when the sum equals the number of order_modifications rows that the order filter selects. A join that matches an order to more than one row makes the check fail.

Per-feature rates​

feature_modification_rates has the rate at which a dealer removes each feature from the builds we order for one model. It also has the rate at which the dealer adds each feature to those builds. The component builds the asset only for an OEM whose configuration sets feature_rates.

The cured build is the order's cured_features in order_modifications. The current build is the cured build, plus the features in added_features, minus the features in removed_features.

A row has these columns:

  • placed_order_count is the number of orders of the dealer, model and placement month that the order filter selects.
  • cured_with_feature is the number of those orders whose cured build has the feature.
  • current_with_feature is the number of those orders whose current build has the feature.
  • removals is the number of orders whose dealer removed the feature from our cured build.
  • additions is the number of orders whose dealer added the feature to our cured build.
  • removal_rate is removals / cured_with_feature.
  • addition_rate is additions / (placed_order_count - cured_with_feature). The denominator is the number of orders whose cured build does not have the feature.
  • cured_take_rate is cured_with_feature / placed_order_count.
  • current_take_rate is current_with_feature / placed_order_count.

A rate whose denominator is 0 is null. A feature of a model has a row in every group of dealer, placement month and order filter that has orders of the model, when the cured or the current build of at least one order of the model has the feature. So every row has its group's placed_order_count, and the counts of rows can be summed across dealers and placement months. To compute a rate over several rows, sum their counts and divide the sums.