A National Retailer Moves Multi-Gigabyte Vendor Files With Files.com, Without Vendor Accounts or a New Repository

A national specialty retailer operates hundreds of stores across the United States alongside an online business.

Behind those stores sits a corporate operation that runs on very large files, and many of the people who need those files are not the retailer's employees. The design team produces print-ready files and sends them to printers, including printers in China and other countries. Real estate and construction teams work with huge documents for every location. Legal sends confidential material to outside counsel. The payloads run to tens of gigabytes, and the retailer needed to move them outside the company without creating vendor accounts or adding another content repository.

Multi-Gigabyte Files, With Email as the Only Way Out

For most corporate staff, the sanctioned way to get a file to an outside party was email. Email cannot carry files that size, so IT actively capped what corporate users could send. There was no platform for exchanging files with vendors at all, which meant every large transfer to a printer, a contractor, or outside counsel was an exception someone had to work around.

Two things made the obvious fixes wrong. The counterparties were external and largely one-off: printers, contractors, and counsel change from project to project, so provisioning an individual credential for every vendor engagement would have created an account-administration burden with no end. And the retailer explicitly did not want another content repository. Corporate files already live on departmental OneDrive and local storage on both sides of every exchange, and the team wanted them to stay there. The missing piece was never a place to put files. It was a way to move them.

A Transfer Layer Over the Storage Teams Already Had

The requirements followed directly from those constraints. The solution had to move multi-gigabyte payloads over SFTP, including connections to international printers. It had to let an internal user hand a file to a vendor without anyone ever creating a vendor account. And it had to meet corporate security standards, with two-factor authentication enforced across the board and access restricted by geography. The retailer selected Files.com to be that transfer layer.

The architecture is deliberately thin. Files stay resident on local and OneDrive storage on each side; Files.com carries the secure transfer between them and stores nothing anyone treats as a system of record. Heavy production work, including transfers to printers in China and other countries, runs over SFTP.

Vendors never need accounts on the platform. For a one-off project, an internal user generates a one-way outbound Files.com Share Link, encrypted and set to expire, and the vendor downloads it in a browser. No vendor credential is provisioned, and none has to be revoked later, because none ever existed. The links run under the retailer's own domain and branding, so what a printer or a law firm clicks looks like the retailer, not a third-party tool.

Internal access is governed the way the rest of the corporate environment is. Users get individual accounts under group-based departmental permissions, two-factor authentication is enforced globally, and geo-blocking restricts where logins can come from. IT set that security baseline first, then enabled the departments one at a time: design, real estate, construction, legal.

Large Transfers Through One Governed Channel

With Files.com in production across the corporate departments, the retailer replaced an email-capped exception process with a standard channel for exchanging files with vendors.

• The corporate departments now move their largest files through one governed channel instead of pushing against email limits.
• Vendor account administration never started. The next printer, contractor, or counsel engagement costs a link, not a credential that has to be created, tracked, and eventually revoked.

Moving Files Stopped Being the Exception

Nothing about where the retailer's files live has changed. Design files still sit with the design team, and departmental documents still sit on OneDrive. What changed is what happens when a file has to leave: a multi-gigabyte print run goes to an overseas printer over SFTP, and a confidential set goes to outside counsel as an encrypted link that expires when the job is done. Before Files.com, IT's role in large-file exchange was limiting it. Now the company runs it at volume, and fixing that never required another repository. A transfer layer over the storage teams already used, with credential-free outbound links, removed the email caps and the vendor account burden at once.