Skip to main content

accessaudi Source: Dealer Order Feeds

accessaudi is the Audi US dealer ordering system, mirrored into BigQuery. Three raw assets read it, all through BQTableRawComponent with a service-account connection:

AssetBigQuery sourceStructure
raw/accessaudi_inventoryaccessaudi.inventory_* (one table per dealer)one row per dealer order, full order object in raw_blob
raw/accessaudi_modelsaccessaudi.product_modelsone row per product model
raw/accessaudi_featuresaccessaudi.product_modelssame table, read for options_blob, exterior_colors_blob and interior_colors_by_exterior_blob

The tables hold fetches from 2026-06-29 on.

AccessAudi writes snapshots irregularly, from zero to several a day. Every asset therefore sets latest_snapshot: true, which reads the latest fetch_date on or before the partition date, per shard for the wildcard read. snapshot_lookback_days (30) bounds how far back it reads. A dealer shard whose extension was uninstalled contributes its last snapshot for 30 days and then drops out, and the scan does not grow as the table ages. A downstream tier can still treat a snapshot younger than that as stale.

Dealer codes​

An AccessAudi dealer code is 4 followed by the dealer's five-character KVPS id. The dealer whose PSS kvps_id is 22A58 and whose mat_primary_code is USA22A58 has the AccessAudi code 422A58. Each inventory_* table name ends in that code.

The transformed inventory takes dealer_code from the name of the inventory_* table that holds the order. Consolidated dealers match on that column. The transformed inventory writes the order's owningDealerCode to owning_dealer_code. So far, the two codes have differed only on vehicles that AccessAudi labels MOBILITY. On those vehicles, the carline code and the model code also differ from the codes of the same model without the MOBILITY label.

AccessAudi puts the MOBILITY label in the model description, as in MOBILITY Q5 quattro. The carline codes of those vehicles start with MB. The owning_dealer_differs row check on the transformed inventory warns when the two dealer codes differ on a vehicle whose carline code does not start with MB.

What an accessaudi record holds​

A record has its model code, a model year, and a flat list of options as (option_code, label) pairs. It has no catalog id, trimline, model version or PR extensions. Those come from the public carline feed. Model Identity describes how the pipeline resolves a model's identity.

Each option in options_blob has portInstalledOptionIndicator, true for a port-installed accessory such as ALB, the cargo box, and false for a factory option such as WPS, the Premium Plus package. No other field of an option says what kind of feature it is.

The year is the sales model year, the year that the carline name and the VIN have. The year inside a catalog id can be one year earlier.

Order status between the factory and the lot​

AccessAudi gives an order's position between the factory and the dealer lot. inventoryStatusGroup is that status, written to vehicle_order_status. inventoryStatus and inventorySubStatus are its numeric form, written to inventory_status and inventory_sub_status. orderType is the sales order type, one of SHIP, HELD, SOLD, LHLD and AVBL, written to sale_order_type.

OneGraph has the same statuses as display text. Its source module maps them to AccessAudi's values while parsing, so both feeds reach the transformed tier with the same values:

status_codeAccessAudi inventoryStatusOneGraph orderStatusText
FACTORY10, 15none; the order has no VIN, so the public feed cannot list it
IN_TRANSIT_FROM_FACTORY20Intransit From Factory
PORT30Port Stock
IN_TRANSIT_TO_DEALER35Intransit Inland
DEALER_STOCK50Dealer Stock

Each feed has a status the other lacks:

  • FACTORY is AccessAudi's alone, because the order has no VIN yet.
  • Center Stock is OneGraph's alone. The mapping's ELSE branch keeps it as CENTER_STOCK, so status_code has six values.

orderType and sale_order_type need no mapping. Both feeds spell the values the same way, such as SHIP - Deliverable Inventory Order, and AccessAudi's five values are a subset of the public feed's nine.

Which feed wins​

AccessAudi is the system of record for a vehicle's current position. Where the two feeds disagree, they differ by one adjacent status, and AccessAudi is usually the further along.

Both AccessAudi feeds rank above OneGraph, so a vehicle an AccessAudi feed lists takes AccessAudi's status_code, dealer and option codes. Except for the fields below, OneGraph fills only the fields AccessAudi lacks.

The nationwide vehicle search is the accessaudi_search group, priority 1. It lists every dealer's vehicles every day it runs, so its dealer and status are the freshest AccessAudi has. The dealers' own accessaudi feed is priority 2: a dealer's snapshots are irregular, and a vehicle that leaves that feed for another dealer keeps its last snapshot's dealer in the feed's history. The accessaudi feed fills the columns the search lacks, such as order_reference. The two feeds merge on order_number.

merge.coalesce.prefer takes OneGraph's value first, then the search's, then the accessaudi feed's, for these fields:

  • feature_refs, because OneGraph lists more feature codes per vehicle. Featurization then describes a vehicle the same way whether or not its dealer has AccessAudi. OneGraph lists no port-installed accessories, so merge.coalesce.append adds the order's accessory_refs to OneGraph's feature_refs. No other code of the order is added.
  • ext_color and int_color, because OneGraph has the full color names.
  • msrp. The two feeds' prices differ for some vehicles both list, and the cause is not known.

Arrival date​

A vehicle's arrival_date is the earliest date at which any feed saw it reach DEALER_STOCK. For OneGraph, that date is the partition date. For AccessAudi, it is the fetch_date of the snapshot. For the vehicle search, it is the day of the search. Each source group has its own min window aggregation over its history, and arrival_date is the LEAST of them. AccessAudi lists a unit from the factory, and the public locator lists it only once it is for sale, so either feed alone would give a later date.

A feed contributes its date only when its first sighting of the vehicle comes before that status. When a feed first lists a vehicle already at DEALER_STOCK, the date is when the feed started listing the vehicle, not when the vehicle arrived. This condition matters most for AccessAudi, which often first lists a vehicle weeks after the public feed does, already at DEALER_STOCK. Without it, many arrival dates would be the start of a feed's coverage, and days_on_lot would use them. LEAST ignores nulls, so a vehicle with no date from any feed keeps a null arrival_date. days_to_lot/status_codes estimates those.

filter_window_boundary removes the same kind of false date at the edge of the 365-day window. It does not remove a feed's coverage start in the middle of the window. It is on for the OneGraph and accessaudi_search groups and off for the accessaudi group, because that feed's first sighting is the fetch_date of a real snapshot.

No feed has a retail date. inferred_sold_date is the date the vehicle disappeared from every feed that had it, after a four-day grace period. accessaudi_last_seen is the fetch_date of the latest AccessAudi snapshot that lists the vehicle. A dealer's snapshots are up to four days apart. days_on_lot is the span between the two dates.

days_to_lot/status_codes learns the delay from each status_code to arrival, per (model_id, status_code). It keys observations on vin, so FACTORY orders, which have no VIN in any feed until they ship, contribute nothing.

Refill allocation units​

Audi assigns some units to a dealer after production. Dealers call them filler. The dealer cannot change or refuse such a unit. Audi marks it in inventoryComments with a tag that names the month of the allocation, such as NOV_REFILL_ALLOC, OCTP2_REFILL_ALLOC or MAY_REFILL_ALLOCATION_II. Dealers often append their own notes to the tag, such as JUNE_REFILL_ALLOCATION / SOLD J 7/10. refill_allocation is true when the comment contains _REFILL_ALLOC, in any letter case.

A tagged order is past FACTORY when it first appears in AccessAudi, and its orderChangeable is false.

In the transformed tier, refill_allocation comes from one snapshot. A dealer can overwrite the comment and remove the tag. The consolidated inventory's refill_allocation is true when any AccessAudi snapshot in the window had the tag. The accessaudi_search feed has no comments, so a vehicle that only OneGraph or accessaudi_search lists has it null.

Audi chose a refill unit's configuration, so consolidated inventory's is_dealer_modifiable is false for it. attribute_stats has a dealer_modifiable statistic, with a half-life of 90 days, over the sold vehicles that are dealer-modifiable. sales_my_weighted and sales_hl90_my_weighted count a refill unit at the dealer-modifiable weight. The other sales statistics and the inventory statistics count it in full.

An AVBL - Available Inventory Order is not a refill unit. It is a unit that a dealer offers to other dealers. Every AVBL order has visibleToDealer true, and no other order has visibleToDealer true.

Reference document downloads​

JavaScript fills in the home page's Documents list. The initial HTML has Liferay.authToken but no document links. downLoadReferenceItems posts to /lr/group/audi-us/home with these query parameters:

ParameterValue
p_p_idomd_auus_WAR_vwgoaomdauusportlet
p_p_lifecycle2
p_p_statenormal
p_p_modeview
p_p_resource_idshowReferenceItem
p_p_cacheabilitycacheLevelPage

The request has an empty body and sends the authenticated session cookies, X-CSRF-TOKEN: <Liferay.authToken> and X-Requested-With: XMLHttpRequest. The JSON response contains referenceItems.Documents, beside Forms and Links. Each document has category, title (an HTML fragment) and location (a relative document URL). This request needs no status: success object and no ordering-page navigation parameters.

A location is fetched with an authenticated GET to /lr/documents/<group>/<uuid>. The URL has no .pdf suffix and can redirect within AccessAudi. Some reference items are not PDFs, and the content type these links report is unreliable.

ai_access_audi implements this. See its README.

Allocation periods​

firstRetrieveAllocationSummary returns the allocation summary of the session's dealer. ai_access_audi reads it with get_allocation_summary. The response's data has:

FieldContent
allocationPeriodBeansthe periods AccessAudi lists, current and past. Each has allocationPeriodCode, allocationPeriodDesc, startDate and endDate, in epoch milliseconds. startDate is midnight US Eastern of the first day, and endDate is midnight US Eastern of the order deadline day.
selectedPeriodLista list with the code of the period the summary describes
totalAllocations, totalAdjusted, totalSubmitted, totalPending, totalRemainingthe units of the session's dealer in the selected period
allocationBeansthe same counts per carline

An allocation period is AccessAudi's record of an allocation window. Every dealer has the same selected period at the same time. allocationPeriodDesc names the kind of period. The letter at the end of the period code (AccessAudi Ordering) does not name it. The selected period alternates between two kinds:

  • A "Production" period has units allocated to dealers. One opens about once a month and lasts about a week.
  • A "DAP Production" period follows it. No dealer has allocated units in it.

The audi_us_accessaudi sensor reads the allocation summary at each tick during business hours (Allocation Windows). The window is open while the summary's totalAllocations is above zero and the current date in US Eastern time is on or before the period's order deadline. A "DAP Production" period never has units, so the sensor posts no message for it.

AccessAudi's Locate a Vehicle page searches the vehicles of every dealer, not only the session's own. Two portlet calls serve it:

p_p_resource_idDestinationFormReturns
renderAllSearchParametersshowLocateVehiclePageyears=<model year>, empty carlines, models and exteriorsdata.carlines: the carline keys offered for that model year, or null for a year not listed yet
getDynamicSearchResultshowSearchResultsrequest_params: JSON with searchParameterBean and dataTableParamModeldata.totalRecords, data.displayStart and data.dataList, one object per vehicle

A search with myPipeLine: "No" and no state, region, area or dealers field covers every dealer. The page refuses a search without a carline ("Please select at least one carline for your search.") and a search of more than one model year outside the dealer's pipeline ("Please select only one model year when searching outside of your dealership pipeline."). It does not offer order type 1 (SOLD), but getDynamicSearchResult accepts it and returns sold vehicles.

dataTableParamModel selects one page of the results:

  • iDisplayStart is the position of the page's first vehicle, counting from 1.
  • iDisplayLength is the page size.
  • iSortColumnName: comm_num sorts the results by commission number.

orderType is an object with key and value, such as {"key": "B", "value": "AVBL - Available Inventory Order"}. availableForTrade is a boolean. In the 200 vehicles of one 2027 search on 2026-10-28, holds was null and currentHolds false on every vehicle. Commission 151697 was one of them, and its retrievePipelineOrders order the day before listed a Dealer Hold.

raw/vehicle_search_latest collects the search with the first session AccessAudi accepts. When AccessAudi ends that session during the search, it starts over with the next accepted session. It fails when AccessAudi lists no carline for any of the model years. It searches:

  • every carline;
  • all five order types;
  • the model years from two calendar years back to next calendar year: 2024 to 2027 in 2026.

raw/vehicle_search_latest sends a search request again, up to three times, when AccessAudi answers it with an HTTP 5xx status or the request times out or loses its connection. It waits 1, 2 and 4 seconds before these retries. AccessAudi's WebSEAL proxy answers HTTP 500 with error DPWWA1235E when it cannot read a response from the server behind it. For an error status, the message of AccessAudiTransportError quotes the first 1,000 characters of the response body, with its whitespace collapsed.

raw/vehicle_search_latest holds one model year's pages in memory at a time, writing each year to a local file before searching the next. It writes one row per results page, with the RAW_ROW_SCHEMA columns:

  • _request_url is the request URL;

  • _request_params is request_params;

  • _response_body is the response without the vehicle fields that can hold personal data:

    • comments, customerInformation, driverInformation, onlnConfirmationId, onlnShoppingId, reservationId and carBean.comments;
    • the salesInformation fields for a salesperson, a manager or a contact: audiCareContact, finaceManager, financeManagerCandidateList, onlineLeaderId, salesManagerCandidateList, salesPerson, salesPersonCandidateList, salesPersonCode, salesPersonId, salesmanager, selectedFinanceManagerCandidate, selectedSalesManagerCandidate and selectedSalesPersonCandidate;
    • email, loginId and screenName of the dealer records billtoDealer, invoiceDealer, salesInformation.deliveringDealer and salesInformation.owningDealer.

    salesInformation.loyaltyVinNumber is "[REDACTED]" where AccessAudi sent a VIN and null where it sent null or an empty string;

  • _partition_date is the UTC date the asset wrote the search's pages.

The audi_us_accessaudi sensor requests it once a day, beside raw/order_guides_latest. For each of the two assets, the sensor tries a session at most once a day. raw/vehicle_search is its daily snapshot. It holds the pages whose _partition_date is the partition date, and is empty for a day whose search has not run.

Known gaps​

  • product_models has no package containment. options_blob is a flat list, and rules_blob has only option constraints. accessaudi features therefore always have a null parent_package_code, and package structure comes from the catalog source.
  • AccessAudi's commNum is a different identifier from the factory commission number. It maps to order_number, and the canonical commission_number stays null for this source.
  • portInstalledOptionIndicator sometimes disagrees with the order guides. On the 2026-10-05 snapshot, the guides listed 107 accessory codes. AccessAudi flagged 97 of them, did not list 5, and listed 5 with the flag false: QVM, QSS, ILU, ILX and ILY, all floor mats or illuminated rings, while the other codes for the same items are flagged. Nine further codes, such as SQK, are flagged in most model years and unflagged in one, with the same label. No flagged code is an option or a package in the guides. The guides outrank accessaudi in the consolidated tier (Model Identity), so the disagreement reaches a feature row only for a model year no guide covers.