Tommy Bahama's Photo Studio Owns the Exchange Point of Its Three-Party Pipeline on Files.com

Oxford Industries is a house of American lifestyle brands, and Tommy Bahama is its largest, selling nationwide through retail, e-commerce, and wholesale channels. At that scale, product photography is not a marketing task. It is the storefront.

Tommy Bahama's in-house studio in Seattle shoots weekly across women's, men's, product, flats, and still-life rotations, and every image follows the same route: captured on set, retouched by an external partner, and published through Adobe Scene 7 into AEM for the website. Three parties touch every photograph. And the path connecting them belonged to none of them. Finished images traveled over an FTP server the studio did not control.

With the retouch team working in a different time zone, a queue that formed during the studio's afternoon waited overnight, and a stall cost a day.

Every Finished Image Traveled Over a Server the Studio Did Not Control

Creative Force, the studio's production platform, handed finished captures to the retouch team over the partner's FTP server, and retouched work came back the same way. Creative Force's own monitoring flagged assets stuck in post, with finished work waiting to move. The studio wanted the exchange point on infrastructure it operated, sized to its own shoot volume.

The studio's cadence left no slack to absorb any of it.

A pipeline moving files continuously, image by image, cannot be paused for a rebuild; the next rotation is always days away. And the exchange point sat in infrastructure Tommy Bahama did not operate. The studio could see exactly where its queue was and had no way to clear it.

The rest of the pipeline ran on hands. Staff moved files manually in Cyberduck, a desktop FTP client, both for the retoucher exchange and for delivering finished assets to Scene 7. At the end of each shoot day, digitechs, the technicians who run the capture stations, backed up the day's work by hand. That was the handling for an archive growing by terabytes every year.

Files.com Became the Exchange Point the Studio Owns

The bottleneck was structural. Shoot volume kept growing, and the exchange point had to grow with it, so the studio decided to own that exchange point itself. What the studio needed was specific: an exchange point it controlled itself, speaking the FTP and FTPS its production platform and retouch partner already used, keeping each party inside its own folders, running the onward publishing without a person in the loop, and cutting over without pausing the weekly shoot. Tommy Bahama made Files.com that exchange point.

Rather than routing production through a server it did not operate, the studio put Files.com in the middle and connected each party to it on its own terms.

Creative Force and the retouch partner each got scoped access to dedicated folders. Separate users and root folders isolated new production jobs from live work, allowing the team to stand up and test them without disrupting production. Folder names carried job and date tokens, so assets sorted themselves as they landed.

The routing runs itself. Files.com Automations trigger on arriving files and move them folder to folder through the retouch loop, and syncs carry finished assets onward to Scene 7 and into AEM on a nightly cycle. That is the delivery work that used to be a manual Cyberduck session.

Backup became a drag and a drop. The Files.com desktop app went onto the Mac capture stations, with Okta sign-in and Finder integration. Digitechs drag the day's shoot into Files.com at the end of the day, and that is the backup.

The cutover ran alongside live production rather than in place of it. Both outside parties tested their credentials before anything moved, and only then was Creative Force's upload target repointed to Files.com. The weekly shoot never paused.

The Studio Now Operates the Pipeline It Used to Watch

With Files.com in the middle of the loop, Tommy Bahama replaced a pipeline it could only watch with one it operates.

The exchange point now runs on infrastructure the studio operates, delivery to Scene 7 and AEM runs nightly, and nobody opens an FTP client to move an image.

• End-of-day backup became a drag-and-drop into Files.com, and a single nightly backup sync moved thousands of files.
• Adding a new production job is a folder and a credential, isolated from live work, which is how the studio has kept extending the pipeline since the cutover.

A Hub the Studio Keeps Branching From

Files.com did more than remove one bottleneck. It is now a hub the studio can keep extending as production changes, with new jobs branching from the governed exchange without disrupting the path already live.