An Automotive Electronics Distributor Built an Upload-Only FTPS Drop Point on Files.com From Its Supply Chain Team

A North American automotive electronics distributor is the regional arm of a larger manufacturer, importing and distributing electronic control units, microphones, and sensors.

The US operation runs lean by design. A handful of people handle the business, and there is no local IT function. Day-to-day operations depend on a third-party warehouse outside the company, which sends the company operations files on a daily and weekly cadence: customer financial information, forecasts, and sales data. The company wanted one credentialed path for those files, and it had to sit entirely outside the corporate network.

A Drop Point That Had to Live Outside the Perimeter

The corporate network the distributor works inside is reachable only over VPN with corporate credentials, and it admits no outside parties. The company had no external-facing FTP or SFTP endpoint a partner could deliver into, and it wanted one: a single credentialed place for the warehouse to put each daily and weekly file, and for its own staff to collect it.

Opening the corporate network to the warehouse was not an option, and the US office wanted a drop point it could stand up without building and running a server. So the requirements were set. The exchange had to live entirely outside the corporate perimeter, accept files only from a credentialed account, speak FTPS so the warehouse could push files directly from its own systems, and be simple enough for a business owner to stand up and run without engineering help.

The distributor selected Files.com to be that exchange point.

An Upload-Only Account Outside the Corporate Perimeter

Files.com became the company's external file interface: a credentialed drop point sitting entirely outside the corporate perimeter, where an outside partner can deliver and internal staff can collect.

The warehouse was provisioned as its own user on the company's Files.com site, with its own folder and a credential scoped to upload only. The account can deposit files and do nothing else. Transfers run one way, inbound over FTPS, using the protocol support the company required from the start. Files land in the warehouse's folder and sit there, and the company's supply chain, accounting, and finance staff retrieve them when they need them.

Nothing in the design touches the corporate network. The warehouse got no VPN account, no exception was carved into the perimeter, and no server had to be stood up in a DMZ. The exchange happens on infrastructure neither company has to open to the other.

A supply chain manager configured the warehouse account, the folder, and the upload-only permissions using Files.com's per-user, per-folder access controls, and administers the site today.

Daily Files Arrive on Their Own and the Network Never Opened

With the FTPS workflow in production, The distributor gave its warehouse partner one credentialed path for every file it sends, and the daily and weekly cadence runs without anyone handling a file.

• Customer financial, forecast, and sales data arrives over credentialed FTPS on the same daily and weekly cadence it always ran, into a folder only the warehouse can write to.
• The manual step is gone. The warehouse's system delivers each file to the site automatically, and company staff collect it when they need it.
• The exchange fits the corporate security posture with no exception in the internal network. The perimeter is exactly as closed as it was before.
• All of it was stood up, and is operated, by the US office’s supply chain team.

The pattern also generalizes. The site is organized per partner, so adding another counterparty is another credential and another folder, provisioned the same way.

Outside the Perimeter, on Purpose

What changed is larger than one file feed. A business inside a sealed corporate network now exchanges sensitive data with an outside partner as a matter of routine, because the exchange does not happen on that network at all. A locked-down network never has to admit an outside party to exchange files with it. It needs a governed exchange point outside the perimeter. The distributor put that point on Files.com, and a supply chain manager built it alone.