OEM dealer portals · 20 systems
User access for every OEM portal across your dealer group.
StitchOps sets up new hires in GM GlobalConnect, Ford FMCDealer, DealerCONNECT and the other OEM portals your stores use, and removes them the moment they leave. It also pulls OEM reports on a schedule and keeps a record of every step.
See all 20 below ↓Every franchise means another portal.
A group with Ford, Chevrolet and Jeep stores has three OEM portals, each with its own users at each rooftop. The OEM expects you to keep those users current. Most groups only find the stale ones when someone else points them out.
The manual way is one portal at a time.
When someone starts, the office manager or the store admin sets them up in the OEM portal by hand. When someone leaves, removing them is one more item on a long list. Role changes, like a salesperson moving into the service lane, often never get updated at all.
What StitchOps does across your OEM portals.
When HR adds someone, StitchOps sets them up in the OEM portal for each store they work at. When someone changes jobs, it updates their role. When someone leaves, it removes them everywhere, and each month it checks every portal's users against who actually works at each store.
OEM reports, pulled for your controller.
Sales, warranty and incentive reports sit in a different portal for every brand. StitchOps logs in on a schedule, downloads them, and puts them where your controller expects them, so nobody spends the start of the month clicking through portals.
Every OEM dealer portals system we support.
If yours is not here and it has a login, we can still run it.
GM GlobalConnect
US · CanadaGeneral Motors
GM's dealer portal for sales, service, parts and reports.
How StitchOps runs it →Ford FMCDealer
US · CanadaFord
Ford's dealer portal for sales, warranty and reports.
How StitchOps runs it →Ford OASIS
US · CanadaFord
Ford's vehicle service history and warranty lookup.
Toyota Dealer Daily
USToyota
Toyota's dealer portal.
Lexus Dealer Daily
USToyota
Lexus' dealer portal.
Honda/Acura iN
USHonda
Honda and Acura's dealer portal.
Stellantis DealerCONNECT
US · CanadaStellantis
Stellantis' dealer portal for Chrysler, Dodge, Jeep, Ram and FIAT stores.
How StitchOps runs it →Nissan DBS
USNissan
Nissan's dealer business system.
Hyundai WebDCS
USHyundai
Hyundai's dealer portal.
How StitchOps runs it →Kia KDealer
USKia
Kia's dealer portal.
How StitchOps runs it →Mercedes-Benz NetStar
USMercedes-Benz
Mercedes-Benz's dealer portal.
BMW CenterNet
USBMW
BMW's dealer portal.
VW/Audi OneHub
USVolkswagen Group
The Volkswagen and Audi dealer portal.
SubaruNet
USSubaru
Subaru's dealer portal.
Mazda eMDCS
USMazda
Mazda's dealer portal.
JLR Retailer Portal
USJLR
Jaguar Land Rover's retailer portal.
Volvo VISTA
USVolvo Cars
Volvo's dealer portal for service and parts.
Genesis retailer portal
USGenesis
Genesis' retailer portal.
Mitsubishi dealer portal
USMitsubishi Motors
Mitsubishi's dealer portal.
Lincoln Pickup and Delivery
USFord Motor Company
Lincoln's service valet program, run through Ford and Lincoln dealer portals.
Common questions.
Can StitchOps work in OEM portals that have no way for other software to connect?
Yes. That is what it is built for. StitchOps logs in to each OEM portal the way your staff would, does the task, and keeps a record of every step.
Does it handle more than one brand at the same rooftop?
Yes. A store that sells two brands has two OEM portals, and StitchOps covers both. The monthly check looks at every portal at every rooftop.
Which OEM reports can it pull?
Any report your staff download from an OEM portal today: sales, incentive, warranty, parts and service reports. StitchOps pulls them on a schedule for every brand and rooftop and files them where your controller expects them.
Do you need our OEM portal passwords?
StitchOps uses logins kept in your password vault, such as 1Password or Keeper, or in the StitchOps vault. They are used only on a secure computer inside your network, and the AI never sees them.
Guides for this.
For your IT team
- Where it runs
- An agent runs an unattended desktop session on a dedicated worker VM in your environment, on Windows or macOS. It connects outbound only over TLS 1.2 or later. No inbound ports are opened.
- Credentials
- Credentials stay in your vault (1Password or Keeper) or in the StitchOps vault, encrypted with AWS KMS and resolved on the worker at run time. Models never see the values.
- Identity systems
- Changes in Okta, Entra ID or Active Directory can start a task. StitchOps carries them into dealer systems that have no SCIM or API. JumpCloud is supported through our joint program. StitchOps is listed in the Okta Integration Network.
- APIs where they exist
- Where a system offers an API, such as Authenticom DealerVault or Fortellis, StitchOps uses it. Everything else runs through browser or desktop automation, anywhere a person can log in and act.
- Logs and telemetry
- Every run keeps step level logs with status, timing and redacted results. Telemetry is content free: no field values, no personal data, no screenshots.
- Security reviews
- SOC 2 Type 2 audit completed. ISO 27001 certified. Penetration tested by a third party. The security packet is shared under NDA.
- AI assistants
- Approved tasks are available as MCP tools to Claude, ChatGPT and Copilot. Destructive actions need explicit confirmation.
Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.
Start with your OEM dealer portals logins.
Fifteen minutes on your top three manual jobs. We tell you which one to hand off first.