Skip to main content

Composite Inventory

For each market in the table below, the composite tier merges the market's public inventory sources into <oem>/<market>/composite/public_inventory. CompositeInventoryComponent describes the component and the meaning of a composite partition.

MarketSource groups, in configuration orderFirst partition
mercedes/mbusanafta, dealer_com, dealer_inspire, dealer_on, motive, tvm2026-09-03
stellantis/usinventory_api, dealer_com, dealer_inspire, dealer_on, motive, tvm2026-10-22
bmw/austolo2025-03-24

A source whose first partition is later than the market's adds, from that date, the vehicles only it lists. The market's daily vehicle count steps up on that date, and its daily sale count steps up over the following days.

bmw/au has one source, the Stolo feed. Its adapter writes:

  • dealer_id as dealer_code, zero-padded to five digits, the format of the BMW dealers entity's key;
  • manufacturer_code as model_code;
  • price as msrp.

Which value is kept​

The OEM feed has the highest priority in each market. It reports the OEM's own model codes and option lists, so for a descriptive column its value is kept wherever it has one. A column the OEM feed leaves null takes the next source's value. The dealer-website groups follow the OEM feed in alphabetical order of their names in every market.

Priority applies to the vehicle's descriptive columns: model, trim, colors, engine, drive and the like. These change rarely, so a source's latest row in its window is as good as a row from the partition date. msrp and mileage change while a vehicle is in stock, so they are listed in use_latest: their value comes from the source that listed the vehicle most recently with a value, and priority only breaks a tie.

The dealer-website sources each describe their own listing of the vehicle. The provider ids are renamed with the group's name, so each source's value is kept in its own column: <group>_site_id and <group>_dealer_id, for example tvm_site_id. The other listing columns are renamed with a shared dealer_ prefix and merged across the dealer-website groups in configuration order:

  • dealer_stock_number
  • dealer_price
  • dealer_date_in_stock
  • dealer_in_transit
  • dealer_vdp_url
  • dealer_in_stock, from the dealer_on, dealer_com and motive groups

dealer_date_in_stock is the stock date on a group's latest listing. dealer_arrival_date is the earliest stock date in the window, checked against the on-lot date; see Arrival dates.

dealer_code comes from the OEM feed and, in stellantis/us, from dealer_com, the only dealer-website source whose listings name the holding rooftop's OEM dealer code. The OEM feed's value is kept where it has one. The other dealer-website sources record the provider's own rooftop id instead; see Dealer-Website Inventory. A vehicle that only those sources listed has a null dealer_code.

Arrival dates​

mercedes/mbusa and stellantis/us use the default arrival_date_priority: the date the composite infers from an on-lot status first, then a date the OEM feed reports, then a dealer website's stock date. bmw/au puts the reported date first: [reported, inferred, dealer]. CompositeInventoryComponent defines the three dates.

MarketGroupOn-lot status (is_on_lot)Collection scope (collection_scope)Reported arrival (reported_arrival_date)Stock date (dealer_arrival_date)
mercedes/mbusanaftanonenonenonenone
mercedes/mbusadealer_comdealer_in_stockdealer_com_site_idnonedealer_date_in_stock
mercedes/mbusadealer_inspireNOT dealer_in_transitdealer_inspire_site_idnonedealer_date_in_stock
mercedes/mbusadealer_ondealer_in_stockdealer_on_site_idnonedealer_date_in_stock
mercedes/mbusamotivedealer_in_stockmotive_site_idnonedealer_date_in_stock
mercedes/mbusatvmnonenonenonedealer_date_in_stock
stellantis/usinventory_apistatus_code = 'KZX'dealer_codenonenone
stellantis/usdealer_comdealer_in_stockdealer_com_site_idnonedealer_date_in_stock
stellantis/usdealer_inspireNOT dealer_in_transitdealer_inspire_site_idnonedealer_date_in_stock
stellantis/usdealer_ondealer_in_stockdealer_on_site_idnonedealer_date_in_stock
stellantis/usmotivedealer_in_stockmotive_site_idnonedealer_date_in_stock
stellantis/ustvmNOT dealer_in_transittvm_site_idnonedealer_date_in_stock
bmw/austoloCASE WHEN stolo_arrival_date IS NOT NULL THEN TRUE ENDdealer_codestolo_arrival_datenone

Every group with an on-lot status sets collection_scope to the column that identifies its dealer website or dealer. When a site or dealer is added to collection, the vehicles already on its lot then get no inferred arrival on that day, instead of all appearing to arrive at once.

The NAFTA feed reports no status that separates a vehicle on the lot from one in transit. The mercedes/mbusa TVM sites never mark a vehicle in transit, so their listings do not show whether a vehicle is on the lot. DealerOn, Dealer.com and Motive mark a vehicle in stock, in transit or in production; only in_stock shows it on the lot. Neither the NAFTA feed nor the Stellantis inventory API reports an arrival date.

Stolo reports a vehicle's arrival at the dealer as distributionData.arrivalDate, written stolo_arrival_date in the composite. A vehicle is on the lot from the first partition whose row has a stolo_arrival_date. A row without one has a null on-lot status, not a false one: Stolo publishes the arrival date some days after the arrival, so the rows before it do not show the vehicle off the lot, and they do not null the reported date. bmw/au takes the reported date for arrival_date.

A dealer website's stock date is often weeks earlier than the vehicle's arrival on the lot, and a dealer can reset it later. It is used only for a vehicle with no inferred arrival.

Reported sales​

The Stolo feed reports a vehicle as sold through salesProcess.type, which the transformed tier writes as sold. In bmw/au, sources_reporting_sold is [stolo] on a partition whose Stolo row has sold true. The other markets have no source that reports a sale, so their sources_reporting_sold is empty and is_reported_sold is false.

Custom orders​

Stolo marks a custom order with a production priority of 1 or U while the vehicle is still before production. bmw/au sets custom_order: "priority_code IN ('1', 'U') AND TRY_CAST(event_id AS BIGINT) <= 150", where priority_code is productionData.productionPriority and event_id is productionData.orderStatus. A stock vehicle can also receive priority 1 when it is sold, after production, so the expression requires a pre-production status. is_custom_order stays true after production, because any row in the window that satisfies the expression marks the vehicle. The other markets have no source that marks a custom order, so their is_custom_order is false.

Column alignment​

Each source group reads only the columns listed in the composite's fields and in the group's extra_fields. fields lists the columns every source of the market writes.

The dealer-website sources name some columns differently from the OEM feed. Their adapters rename them to the OEM feed's names, so one column holds the value from every source:

MarketDealer-website columnComposite column
stellantis/usdrivetraindrive
stellantis/usexterior_colorexterior_color_desc
stellantis/usinterior_colorinterior_color_desc

One OEM-feed column is converted before the merge: inventory_api writes model_year as a string, and the dealer-website sources write an integer. The inventory_api group casts it to BIGINT; a value that is not a number becomes null.