Epicor estates run on files: EDI documents read off disk by translators, order channels feeding the ERP, retailer AS2 mandates. Files.com is the governed exchange around all of it: partners connect to a modern SFTP endpoint, and the ERP, old or new, stays exactly as it is.
No credit card required · 7-day free trial · Live in minutes
Real companies. Real file flows. Real results.
Between trading partners on one side and an Epicor ERP on the other, the whole order flow is file transfer: EDI documents landing on the disk a translator reads, order files feeding pick tickets, acknowledgements and invoices moving back out. The systems of record are usually the last thing anyone wants to touch, whether that’s Kinetic, Prophet 21, or a Prelude system on UniData that has run the business for decades. The exchange around them is usually the first thing that breaks.
Files.com modernizes the exchange without touching the ERP. Trading partners deliver into scoped folders over SFTP, FTP, or mandated AS2; documents land on the disk the translator reads within moments; every order file is preserved through outages; and the audit trail knows where every document went.
EDI to the translator’s disk, AS2 brought in-house, order channels that never lose a file, and customer forms converted on the way in. Every one runs in production.
Epicor-connected EDI translators read documents off a local directory. With a mount or the Agent, a vendor’s document lands on that disk the moment it’s written to its Files.com folder: immediate delivery to the translation layer, no polling script in between.
Retail partners like Walmart and Target mandate AS2 with signed receipts. AS2 is built into Files.com: certificates, MDNs, and partner onboarding are configuration. Meeting the mandate stops being a week-plus, vendor-dependent build.
When every order arrives as a file, a dropped transmission is revenue lost silently. Files.com is the store-and-forward layer that preserves every order file, queues transmissions through outages, and leaves the ERP unchanged.
Plenty of Epicor estates run systems of record that aren’t going anywhere. Files.com delivers into the folder the existing 15-minute sync or import already reads. The modernization happens around the ERP, not to it.
Standardized customer forms arrive, convert to the shape the Epicor workflow ingests, and route in. TransformScript handles the conversion as configuration instead of a purpose-built Azure server handling it as infrastructure.
A missing order file is a pick ticket that never prints. Delivery monitoring knows each trading partner’s cadence and alerts when a delivery window closes without a file, before the warehouse wonders why it’s slow.
Retailer mandates and partner separation land on IT, and the ERP can’t be the thing that changes.
EDI translation happens where the translator reads. The outbound-only Agent runs beside it, holds no inbound firewall rule, and lands each arriving document on the local directory within moments of upload.
Files.com generates the certificates, exchanges signed MDN receipts, and onboards trading partners. Retail AS2 mandates get met from your own endpoint, and a test transfer proves it before a partner ever asks.
Each retailer, marketplace, and vendor gets its own credential and folder. Order files, acknowledgements, and invoices stay separated per relationship, with the audit trail reading the same way.
A working prototype revealed the lasting security and maintenance burden of self-hosting, while Files.com provided a direct path into Epicor without another server to run.
Read The Story
Files.com became the store-and-forward layer that preserves every order file, queues transmissions through outages, and leaves Enginetech’s Prelude UniData ERP unchanged.
Read The Story
“Files.com's strengths are simplicity, ease of use, and the cloud connectors. We don't have to invent custom infrastructure for every partner.”
“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.”
What manufacturing and distribution IT teams ask most when wiring trading-partner exchange around Epicor.
EDI reaches an Epicor system through a translation layer: an EDI translator reads documents from a directory and hands structured data to the ERP. Files.com delivers each trading partner’s documents onto the disk that translator reads, via mounts or the outbound-only Agent, the moment the partner writes them.
AS2 moves signed, encrypted payloads with MDN receipts that prove delivery. Files.com carries AS2 natively: you generate certificates, onboard the partner, and prove your endpoint with a test transfer, on your own platform instead of a hosted EDI supplier’s timeline.
Yes. Older Epicor systems are a standing pattern for Files.com: systems of record on older platforms, including Prelude systems on UniData, keep running untouched. Partners connect to a modern Files.com endpoint, and files land where the ERP’s existing sync or import already reads. The modernization happens around the ERP, not to it.
The order files survive. Files.com is a store-and-forward layer: every arriving order file is preserved, queued transmissions retry through the outage, and nothing is lost because a receiving system was down for an hour. The audit log shows exactly what moved when service resumed.
Automation Studio is Epicor’s embedded Workato, and it owns API-level workflow across Epicor and third-party apps. Files.com owns the file layer beside it: partner protocols, AS2, PGP, and store-and-forward. It’s the same division of labor as Workato itself, with webhooks and the REST API joining the two.
Yes. Files.com stages conversion and migration files for Epicor’s Data Management Tool: they land, validate, and reshape into the layouts DMT expects, then wait where the import reads. Every staged file is logged, so a conversion’s paper trail writes itself.
Yes. TransformScript converts CSV, XML, and JSON in the flow, and Automations rename and route, so each partner’s format quirk is handled once, in configuration, instead of in the translator’s error queue.
Delivery monitoring in Files.com knows each partner’s cadence and alerts when an expected file is late: a same-hour alert instead of a warehouse asking where the orders went.
Yes. Files.com encrypts order and customer data in transit and at rest, scopes each trading partner to a least-privilege folder, runs PGP as configuration, applies retention to delivered files, and logs every access.
Files.com replaces the hosted FTP account that dropped order files, the week-plus vendor builds for each new trading partner, and the EDI supplier that owned your AS2 endpoint. The File Orchestration Platform runs the trading-partner exchange as one governed layer, and the ERP keeps doing its job.
Trading partners get a modern endpoint, and EDI lands on the translator’s disk in moments. Every order file is preserved, and Epicor stays exactly as it is.
No credit card required • Free for 7 days • Live in minutes
Order, inventory, and shipment files with suppliers, carriers, and 3PLs on one endpoint.
ACH, positive-pay, and settlement files with every bank, encrypted with its key, before its cutoff.
Move, convert, route, and notify on a schedule or on arrival — no scripts.