DCS

Franchised automotive retail depends on a factory-owned B2B channel that sits outside the rooftop’s own software stack. Automakers provision that pipe so a store can order vehicles, pull genuine parts, file warranty, post factory financials, and receive recalls and incentive programs without mailing paper or re-keying every message.

Each OEM brands its own portal. BMW’s DCSnet still hosts warranty vehicle inquiry, retail delivery reporting, and campaign status. Honda and Acura route claims, parts orders, and VIN history through iN Plus. Hyundai’s WebDCS, often certified through an integration hub, is how dealers order and return parts, process warranties, submit financial statements, and file retail delivery reports. The category name is the same even when the login screen is not.

What the Factory Pipe Carries

The traffic is operational, not marketing. Typical payloads include:

• Vehicle orders: Allocation, specification, and status for units the store is building or stocking, plus the retail delivery report that starts in-service and warranty clocks.
• Parts: Stock orders, emergency orders, returns, and catalog lookups keyed to OEM part numbers and SKUs.
• Warranty and campaigns: Claim submission, labor operation codes, parts markup, credit notes, and VIN-level open-campaign flags that service advisors check before the repair order is written.
• Money and programs: Holdback, co-op, stair-step incentives, and the monthly factory financial statement the OEM requires in its chart of accounts.
• Notices: Safety recalls, technical campaigns, policy letters, and targeted messages to a dealer code.

Older hops used batch EDI. STAR (Standards for Technology in Automotive Retail) later published XML business-object documents covering parts, warranty, and retail deliveries so a certified DMS can speak a common dialect. Many OEMs now expose the same work over web portals and APIs, often as SaaS logins, while still requiring certified interfaces so the store’s system of record does not double-key.

How It Differs From a Dealer Management System

The in-store DMS is the rooftop’s system of record: deals, repair orders, accounting, payroll, and local inventory. An IMS tracks what sits on the lot or on the parts shelf. The factory pipe is the OEM’s network. Confusing the three is how groups buy the wrong stack or assume one vendor portal is an industry standard.

System	Owner	Job	Typical Records
DCS	Automaker (OEM)	Factory-dealer network	Vehicle orders, parts, warranty, retail delivery reports, incentives, recalls, factory financials
DMS	Dealership	In-store system of record	Deals, repair orders, accounting, payroll, local inventory
IMS	Dealership or group	Stock position	New and used units, parts on hand, aging, allocation

Certified DMS interfaces exist so warranty, parts, retail delivery reports, and financials can flow computer-to-computer. Without that certification, staff log into the OEM portal by hand, which is slower and error-prone. A dealer CRM or a generic ERP does not replace the factory channel. Franchise agreements still require the OEM path.

How Dealers Work the Channel

Day to day, the work is departmental:

• Service: VIN inquiry for coverage, campaigns, and history before the advisor writes the ticket. Warranty administrators attach repair-order documentation and watch credit notes come back.
• Parts: Counter people look up OEM catalogs, check warehouse locators, and push stock or emergency orders. Returns follow the same pipe.
• Sales and accounting: New-vehicle orders and retail delivery reports, incentive claims, and the factory financial that must match the OEM’s chart, not a generic P&L.
• Multi-franchise groups: Each brand still has its own dealer code, credentials, and certification program. A Honda iN Plus session does not file a BMW campaign.

STAR’s dealer-infrastructure work, and NADA’s long push for open standards, exist because multi-rooftop groups otherwise maintain a private circuit per OEM. The factory still owns the pipe. The store owns how cleanly its DMS, IMS, and people feed it.