A Legwear Manufacturer Replaced FileZilla With a Two-Way Salsify Pipeline on Files.com

A US legwear manufacturer and marketer runs a portfolio of its own brands and licensed lines.

A portfolio that broad runs on product photography. Every style in every brand needs imagery shot, processed to spec, and delivered to the teams and platforms that sell it. At the company that work belongs to marketing: brand and creative teams shoot and upload the lifestyle and product photography, and the e-commerce and sales teams consume it. The imagery does not stay inside the company, either. To get product images resized and renamed in bulk, the company sends them to Salsify, an outside digital asset management platform, and the finished versions have to come back. The marketing team sat between its own image library and a partner platform it did not control, with thousands of files needing to cross in both directions. The route between them was manual, and it ran file by file.

Thousands of Images, Moved One at a Time

To deliver a batch, an analyst either retrieved image URLs individually, downloaded files and re-uploaded them, or pushed them through a FileZilla session into Salsify’s FTP endpoint. Whichever path, a person handled every file. By April 2021 the question the team was asking was simple: how do we copy thousands of images over quickly?

The cost landed in two places. First, analyst hours. Every batch of photography bound a marketing analyst to mechanical transfer work instead of the multi-brand e-commerce content the images existed to serve, and per-file handling put a hard ceiling on how much photography could move at all. Second, the pipeline dead-ended at delivery. Once Salsify finished its bulk resize and rename, the output the sales team needed sat on the far side of the same manual gap, with no clean route home.

The problem persisted because neither end of it was fixable from where the team sat. Salsify’s FTP endpoint was the interface the platform offered, and the company could not change it. The people who needed the files moved were marketers, not engineers. As photography volume grew across the brand portfolio, the manual path stopped absorbing it, and what the team needed was specific: a connection between their image library and a partner’s FTP endpoint, carrying files in both directions, with no custom development, operable every day by the analysts who own the images.

The company used Files.com Remote Server Mounts to build exactly that connection.

Salsify’s FTP Endpoint, Mounted as a Files.com Folder

Using the Remote Server capability, the team configured a connection to Salsify’s FTP endpoint and mounted it onto an empty Files.com folder. From that point, Salsify’s digital asset store appears inside Files.com as an ordinary folder. Delivering a batch means opening the folder that holds the images and copying them into the mount. Files.com holds the FTP session to Salsify behind the scenes, so no image takes a detour through a desktop client, and FileZilla dropped out of the workflow entirely.

The build was not an engineering project. The company’s own digital marketing analyst configured the mount working with Files.com support, and four days passed between the initial question and Salsify confirming that files were arriving through the connection. Nothing changed on the partner’s side: Salsify kept its FTP endpoint, and the company kept its folders.

The pipeline soon ran in both directions: Salsify returned resized and renamed images over FTP into a separate Files.com folder for the sales team, without a custom integration or manual re-importing.

A Delivery Is Now a Single Copy

With the mount in production, the manufacturer replaced per-file handling with a repeatable folder-to-folder pipeline run by the people who own the images. The downloads, the re-uploads, and the one-at-a-time FTP sessions are gone.

• Bulk delivery to Salsify is a folder copy. Batches of hundreds of images move in a single operation, handled as routine work by the marketing and e-commerce staff themselves.
• The desktop client hop is gone. No image passes through anyone’s machine on its way to the partner platform.
• Renamed output reaches the sales team on its own. Salsify writes finished images back into a dedicated Files.com folder, so the round trip completes without anyone re-importing files by hand.

The mount is standing infrastructure rather than a one-time transfer. Each new batch of photography moves through the same connection with no new setup, and the brand and e-commerce teams that produce the most imagery are now the platform’s heaviest users. The pipeline took days to stand up and is operated by the analysts who use it, without depending on an engineering team.

An Integration That Behaves Like a Folder

What changed at the company is who can build this kind of connection. Linking the image library to Salsify took no custom development, no work on the partner’s side, and no engineers in the loop. A digital marketing analyst mounted the partner’s FTP endpoint as a Files.com folder, and from then on a two-way exchange with an outside platform was folder work: the thing the team already did all day.