vAuto exchanges inventory, pricing, and appraisal data with the DMS and the tools downstream, as nightly CSV feeds over SFTP and FTP. Files.com is the managed layer that moves, reshapes, and audits every one of those feeds, unattended.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
Appraisal and pricing run on a file loop: the DMS exports inventory nightly, vAuto ingests it against a dealer ID and file-name convention, and vAuto’s own output feeds the recon boards, websites, and reports downstream. Each hop is simple. The loop as a whole is where things break: a rename nobody made, a stalled transfer nobody saw, a desktop script that retired with its author.
Files.com runs the whole loop as one governed service. Automations collect, rename, and deliver on the nightly schedule, TransformScript reshapes CSV per consumer, per-rooftop folders keep a group legible, and monitoring makes a stale pricing feed an alert instead of a bad week.
Each leg of the nightly loop runs automated and on the record, from the DMS through vAuto to everything downstream.
vAuto’s third-party integration setup asks for an FTP host, a credential, a dealer ID, and a file name. Files.com is that endpoint as a service: permanent hostname, per-integration credentials, and the nightly exchange running unattended.
Appraisal and pricing start from the DMS inventory export. Automations collect the export, enforce the file name vAuto’s intake expects, and deliver on the nightly schedule, with retries when a hop fails.
Recon boards, group websites, and reporting tools consume vAuto’s feeds. One arriving file fans out to every consumer, each copy renamed and reshaped to what that tool ingests.
Every system in the loop has its own column expectations. TransformScript reshapes CSV in the flow, so one canonical inventory file serves vAuto, the website, and the pricing reports without a desktop script translating in the middle.
A group runs one vAuto relationship across many stores. A folder and credential per rooftop keeps each store’s feed isolated and separately monitored. The audit log reads per-store.
Pricing decisions made on last week’s market file are decisions made wrong. Delivery monitoring knows when each feed is due and raises an alert when the window closes without a file, before the lot gets priced off stale data.
The nightly loop is only as reliable as the endpoint it runs through.
Set them once in vAuto and they stay set. The Files.com hostname and credential are permanent managed properties, so no server swap ever forces a re-setup on the vAuto side. Automations enforce the dealer-ID-and-file-name convention on every delivery.
Inventory tooling still runs plenty of plain FTP. Files.com serves SFTP, FTPS, and FTP from one site, so each party connects the way it already does, and your side gets the log either way.
Feeds run nightly in both directions. Scheduled syncs and Automations run the cadence unattended, retry on failure, and archive each night’s files for comparison and dispute.
Where the DMS export lands on a server inside the store network, the outbound-only Agent picks it up with no inbound firewall rule. Nothing in the dealership network gets exposed.
“Files.com's strengths are simplicity, ease of use, and the cloud connectors. We don't have to invent custom infrastructure for every partner.”
“Files.com is versatile — it can manage many different situations from a single platform. We've consolidated multiple tools onto it.”
“Files.com is robust and scales to a large enterprise. We get multiple files per minute, per second — and we're a 24/7 organization, so everything has to always be up.”
What dealership IT teams ask most when wiring vAuto file exchange.
A vAuto integration exchanges files over SFTP or FTP, on a nightly schedule, as CSV. The setup asks for a host, a credential, a dealer ID, and a file name. Files.com is the managed endpoint in that exchange, running the schedule unattended with retries and a complete log.
Yes. Files.com Automations collect the DMS export, enforce the file-name convention the intake expects, and deliver on schedule. A failed hop retries automatically and alerts if it can’t recover.
Yes. Files.com fans one arriving vAuto feed out to the recon board, the website, and reporting. TransformScript renames and reshapes each copy to what that consumer ingests. Adding a destination is a folder and a rule.
A Files.com folder and credential per store keeps every rooftop’s feed isolated and separately monitored. The group runs on one platform, with one audit trail that reads store-by-store.
The Files.com outbound-only Agent runs inside the store network, picks the export up, and carries it out with no inbound firewall rule and no VPN.
Files.com delivery monitoring defines when each feed is due and raises an alert when a window closes without a file. The appraisal desk never spends a morning pricing off a stale market file without knowing it.
No. Files.com serves SFTP, FTPS, and FTP side by side, so every party keeps its existing client and settings. The change is on your side: per-party credentials, monitoring, and a record of every transfer.
Yes. Every feed copies to a dated archive on Files.com, under retention policies you set. Any dispute about what was sent on a given night is settled by the file itself.
Yes. Files.com encrypts dealership data in transit and at rest, scopes access per party, applies PGP as folder settings where a counterparty requires it, and keeps a complete audit log. That is the posture the FTC Safeguards Rule expects when customer data rides along with inventory.
Files.com replaces the store-closet FTP server and the desktop scripts moving CSVs between the DMS, vAuto, and everything downstream. That setup runs on shared credentials with no monitoring, and a stalled feed gets discovered by the appraisal desk instead of by IT.
DMS to vAuto to every tool downstream: delivered on schedule, reshaped per consumer, with an alert when a feed’s window closes without files.
No credit card required • Free for 7 days • Live in minutes