From Quote to Artwork Exchange: A Packaging Converter Connects Claris FileMaker to Files.com

A North American flexible packaging converter prints and converts the films, laminations, pouches, and rollstock that carry food, healthcare, pharmaceutical, and personal care products, running several plants across the United States.

Every one of those packages starts as artwork. Before a job goes to press, packaging graphics and high-resolution print data travel between the customer's brand team, the converter's graphics operation, and the print partners who put the work on press. Proofs go out for approval, and revisions come back. The front end of every packaging job is file exchange with people outside the company.

The Graphics System Could Open a Job, but Not a File Exchange

For years, that exchange ran by hand. Artwork moved to and from print vendors person-to-person. Files went to customers as email attachments, which left no record of what had been sent and no way to end access once granted. The graphics archive, and much of the exchange around it, lived on Dropbox.

The gap sat in the company's own systems. The application the graphics business ran on could generate a job code for every piece of work, but there was no transfer service to hand that code to. Nothing existed for the system to call to open a controlled place for a customer or vendor to deliver files. So every new customer, and every new job, needed a person to stand the exchange up and walk the files through it.

The risk bothered the company as much as the labor. An email attachment carries no history, and an anonymous upload page takes in files from whoever finds it. The converter wanted every inbound file tied to a named, credentialed user, so that anything arriving from outside the company left a record of who sent it. As the graphics operation systematized its quoting and job management, hand-run file exchange became the one step no system could reach.

A Transfer Service Claris FileMaker Could Call

What the converter needed was not another sharing tool for people to click through. It needed a transfer service its Claris FileMaker estimating and quoting application could drive: an API the system could call to create a folder and issue a link, permissions that scope each customer to their own space, credentials that put a name behind every upload, and access that expires on its own. The company selected Files.com to be that service and connected the application directly through the REST API.

Provisioning a Customer Exchange Became an API Call

The company first chained a random-password generator into the Files.com CLI so that a single Bash command created a customer's folder, generated a share link, and emailed it to the address the operator supplied.

Then the application took over. The converter's estimating and quoting system ran on Claris FileMaker, and the company wired it directly to the Files.com REST API. The application called the endpoints that created a directory and a share link, using plain cURL, so the same workflow that priced a job also created the place its artwork would arrive and the customer-facing link that pointed to it. Every link carried the site's controls with it, including expiry, so access granted for a job ended on its own.

Regular customers moved onto named, credentialed Files.com accounts. Per-folder permissions and root-folder scoping gave each customer a view of their own space and nothing else, inside a folder structure that kept internal and external users apart, and every upload was logged against the named user who made it. Files.com webhooks notified the graphics team in Microsoft Teams when files landed, so nobody watched a folder waiting for a proof to come back.

In May 2025, the company completed the consolidation and moved the graphics archive itself off Dropbox and onto Files.com, with the bulk of it moving over SFTP.

Controlled Exchanges, With a Name on Every File

With the Files.com workflow in production, the converter replaced a person-to-person exchange with one its own systems provision.

• Opening a controlled exchange for a customer is something the estimating application does itself. Instead of stopping to build folders and send links by hand, the graphics team can keep the job moving through its existing workflow.
• Every inbound file is attributable. Regular customers connect as named, credentialed users, so an upload from outside the company always arrives with an identity and an audit trail behind it.
• Access ends on its own. Share links expire, replacing attachments that could be forwarded forever.
• The exchange runs at production volume, with multi-gigabyte partner uploads landing several times a day.

The pattern compounds. The next customer costs the company a folder, a credential, and a link the estimating system already knows how to create. No new integration work is required, and no new infrastructure. And with the archive consolidated, the company's own graphics archive and customer exchange no longer live in Dropbox: the files, the exchange, and the record of both live in one place.

File Exchange Became a Service the Converter's Systems Call

Today, the exchange begins inside the system that opens the job—not with a person composing an email or setting up a Dropbox share.

The company's business system could generate a job code but could not move a file. It did not need transfer infrastructure built around it. It needed a transfer service it could call, and Files.com became that service: the API behind the quoting system, and the credentialed front door its customers walk through.