Files.com gives every supplier, carrier, fulfillment provider, and warehouse system its own account and folder on one hosted endpoint that speaks SFTP, FTP, FTPS, and AS2, and moves each file to your ERP, OMS, or WMS the moment it lands. Your counterparties will not build to an API. Files are the integration.
A late or dropped file is an order that does not ship, stock that oversells, or a truck that does not roll. Today those files ride on a server someone patches, a script per partner, or an attachment someone re-keys.
Every physical transaction has a counterparty and a file: the purchase order in, the manifest out, the tracking number back, the invoice after. The supplier, the carrier, and the 3PL each run their own systems on their own schedules, and none of them will build to your API.
So the exchange runs on a self-hosted server nobody dares retire, a bespoke script per connection, or attachments someone types into the ERP. On Files.com every partner is an account and a folder on one endpoint, every arrival triggers the next step, and the next partner joins the same pattern instead of getting its own plumbing.
Real companies. Real file flows. Real results.
Orders in, orders and inventory between systems, shipments and tracking with carriers, and the paperwork that follows the goods.
A customer exports purchase orders as a file and drops it in its own folder on your endpoint. An Automation hands it to the order intake your ERP or OMS already watches. The customer changed nothing about how it works.
Order exports leave the storefront on a schedule and land where NetSuite, SAP, or Dynamics 365 imports them. Inventory and pricing feeds come back the same way. Two systems with no direct integration exchange files through a folder both can reach.
Shipment manifests go out to the fulfillment provider; tracking numbers and proof-of-delivery files come back into the folder your systems read. FedEx, UPS, and DHL exchange files this way, as do the 3PLs that ship on your behalf.
Forwarders and shippers drop customs documents and invoices into per-partner folders. Retention rules keep them for as long as the import record requires, and the audit log shows who filed what and when.
Isolation per partner, a fixed endpoint, movement on arrival, and every protocol a trading partner might mandate.
Every supplier, carrier, 3PL, and system gets its own login, rooted in its own inbound and outbound folders. A partner sees its orders and nothing else, and onboarding the next one is a user and a folder rather than a project.
Partners connect to your own domain, over SFTP, FTPS, or FTP as they already do, and to two dedicated IP addresses their firewalls can allow-list. When your storage or your ERP changes behind the endpoint, no partner reconfigures anything.
Automations move or rename each file the moment it lands and a webhook tells your OMS to import it. The Files.com Agent carries files to a warehouse system inside your network over an outbound-only connection.
Some trading partners require AS2 with signed receipts. Files.com speaks it on the same site as SFTP, so the retailer that mandates AS2 and the supplier that only knows FTP land in the same folders. The EDI hub covers X12 documents and the transaction sets in detail.
The shift had to satisfy an Azure hosting constraint while handling partially written files, partner endpoints, and growing system-to-system traffic without custom code.
Read The Story
A workflow-by-workflow parallel run kept frequent carrier exchanges live while Files.com rebuilt transfers, automation, and access for cloud operations.
Read The Story
A cautious, hardest-first migration moved ten vendor exchanges off hand-maintained infrastructure and closed the inbound firewall paths behind them.
Read The Story
The team staged the cutover before its seasonal freeze, with Files.com handling API transfers, alerts, and code-free archiving behind the existing partner interface.
Read The Story
“Files.com is versatile — it can manage many different situations from a single platform. We've consolidated multiple tools onto it.”
“Files.com is robust and scales to a large enterprise. We get multiple files per minute, per second — and we're a 24/7 organization, so everything has to always be up.”
The three ways order files move today, and why each one is a shipment waiting to go wrong.
An FTP or SFTP box in the DMZ, re-provisioned by hand for every new partner, patched by whoever remembers. It carries live order traffic, which is why nobody retires it, and why every outage is an order that does not ship.
Each partner gets its own script or its own iPaaS flow, built to that partner’s format and schedule and owned forever. The estate grows one bespoke connection at a time, and only its author can safely change it.
Orders arrive as emailed spreadsheets and someone types them into the ERP. It scales exactly as far as that person’s day, and a typo becomes a shipment to the wrong address.
What integration and supply-chain teams ask before moving partner file flows onto Files.com.
Give the customer its own folder and login on your Files.com site. It drops the order file over SFTP, FTP, or a browser, an Automation moves the file into the intake folder your ERP or order-management system watches, and a webhook can tell that system to import it. The customer keeps exporting files the way it always has.
Yes. A sync pushes the order file to the vendor’s SFTP server on the schedule you set, and a second sync pulls the tracking and proof-of-delivery files the vendor posts back into the folder your systems read. The vendor’s host key is pinned and its credential lives in Files.com rather than in a script.
The warehouse or 3PL drops its inventory feed into its own folder on your Files.com endpoint, or Files.com pulls it from their server on a schedule. An Automation renames the file to the ERP’s convention and moves it to the import folder, and the Files.com Agent delivers it to an on-premises ERP over an outbound-only connection.
Yes. Files.com serves your site under your own hostname, can present the SSH host key your server used, and imports existing users with their password hashes, so suppliers keep the address, key, and credential they have. Replacing the SFTP server without a partner cutover is its own job, and this one runs on top of it.
No. Files.com receives and sends AS2 with signed MDN receipts on the same site as SFTP and FTP, so the retailer that mandates AS2 and the supplier that only speaks FTP land files in the same folders and trigger the same Automations. Files.com meets common AS2 standards; it is not Drummond certified. The AS2 and EDI page covers the mechanics.
Files.com carries X12 and EDIFACT documents byte for byte over SFTP and AS2, and TransformScript parses and reshapes them on arrival when a downstream system needs a different shape. The EDI hub covers the transaction sets, the translation, and the routing.
A Files.com custom domain includes two dedicated IP addresses, so partners with firewall allow-lists have fixed addresses to allow for connections in either direction. Enterprise sites can bring their own IP ranges and keep the allow-lists partners already hold.
Files.com Expectations know which file is due from which partner by when, and open an incident when it is missing, late, or malformed, so the stockout is an alert at 6 a.m. rather than a discovery at the loading dock.
Yes. A Remote Server Mount writes partner uploads straight into your Amazon S3, Azure Blob, or Google Cloud storage, and the Files.com Agent delivers files to a warehouse or ERP server behind your firewall without opening an inbound port. The partner sees one hosted endpoint; the files land where your systems read.
An account and folder per supplier, carrier, and 3PL, every protocol they use, and files moved to your ERP the moment they land. Start the 7-day free trial and onboard the first partner today.
No credit card required • Free for 7 days • Live in minutes
Transport, X12 translation, validation, and routing for every trading partner, plus the transaction-set library.
Move, convert, route, and notify on a schedule or on arrival — no scripts.
Bridge on-prem servers outbound-only — no inbound firewall change.
