FTP in E-Commerce: Real Workflows and Modern Alternatives

E-commerce file transfer covers more ground than most non-operations teams realize. Product catalog feeds, dropship order routing, vendor EDI for inventory and pricing, marketplace integrations, marketing-asset delivery from agencies, image and video CDN seeding, returns/refund file exchange. FTP — and its modern descendants SFTP and FTPS — has historically been the protocol for most of these. Modern e-commerce platforms (Shopify, BigCommerce, Magento) have replaced many of them with REST APIs and webhooks, but FTP-shaped workflows still exist for legacy partners, large-file media delivery, and EDI compliance. This post is the practical guide to what's still FTP-shaped, what's moved to APIs, and how to handle both.

For the broader retail-industry view, see our retail and e-commerce file transfer guide.

Where FTP still shows up in e-commerce

1. Product catalog feeds from suppliers

Suppliers push product catalog feeds — new SKUs, pricing updates, image URLs, descriptions — to retailers on a schedule. Typically a CSV / XML / JSON file delivered nightly or every few hours.

Modern shape: SFTP for traditional suppliers; REST API for digitally-native ones. The retailer's product information management (PIM) system ingests both. Most established e-commerce platforms have a "product import via SFTP" workflow that hasn't materially changed in a decade because it works.

Files.com pattern: the retailer provisions an SFTP user per supplier, each chrooted to their own directory. Suppliers push daily; a downstream pipeline picks up the new files and runs the import.

2. Image and asset delivery from agencies

Marketing and creative agencies ship product photography, video, and finished campaign assets to the brand. The files are large (50–500 GB per shoot is normal), and the workflow is "drop everything, brand-side picks up."

Modern shape: SFTP for established agency relationships. Specialized large-file services (MASV, Filemail, WeTransfer Pro, Frame.io) for ad-hoc work. The brand's DAM (digital asset management) system ingests from whichever channel the agency uses.

3. Vendor EDI for inventory and orders

For B2B e-commerce — wholesale, distributor relationships, dropship vendors — EDI documents (purchase orders, advance shipping notices, invoices, inventory snapshots) flow between trading partners. Major retailers mandate AS2 for EDI; smaller relationships often use SFTP.

Modern shape: AS2 for Walmart / Target / Amazon-dropship-style supplier relationships (cryptographically signed receipts are non-negotiable). SFTP for the long tail of smaller vendors. See our retail and e-commerce file transfer guide for the AS2-vs-SFTP details.

4. Marketplace integrations and dropship order routing

When you sell on Amazon, eBay, Walmart Marketplace, Etsy, or similar, the marketplace pushes order data to you and you push fulfillment data back. The protocol depends on the marketplace's modernity.

Modern shape: REST API for Amazon, Shopify, BigCommerce, Magento, modern marketplaces. SFTP for legacy marketplace integrations and some traditional dropship workflows. The middleware (an order management system like ShipStation, Brightpearl, or Pipe17) translates between the marketplace's protocol and the merchant's fulfillment system.

5. Marketing-asset delivery to advertising platforms

Product feeds for Google Shopping, Meta catalog ads, TikTok Shop, and similar — XML or CSV files describing the catalog with images, pricing, availability, and links. Updated nightly or hourly.

Modern shape: mostly HTTPS / API now. A handful of legacy ad platforms still accept FTP. The merchant generates the feed file and either pushes it via the platform's API or hosts it at a URL the platform crawls.

6. Returns and refunds reconciliation

For larger merchants, returns and refunds files flow between the e-commerce platform, the payment processor, and accounting systems. Reconciling "did the refund actually get issued?" depends on these files arriving reliably.

Modern shape: APIs for cloud-native stacks; SFTP for legacy payment-processor integrations and traditional accounting back-ends.

Where e-commerce has moved past FTP

Three categories that used to be FTP-shaped and mostly aren't anymore:

• Website deployment. Shopify, BigCommerce, Magento Cloud, WooCommerce on managed hosting — none of these require FTP to deploy. Theme and code changes go through Git or the platform's admin UI. Only self-hosted Magento on a VM still uses FTP routinely for theme/extension deployment.
• Customer-facing file delivery. Receipt PDFs, order confirmations, digital downloads — all HTTPS now. FTP for customer delivery would be weird in 2026.
• Real-time inventory sync. Webhooks have replaced scheduled SFTP-based inventory feeds for any modern platform. Inventory deltas push as events, not as batch files.

Choosing the right shape for your e-commerce file workflows

The decision tree:

• Can the partner speak REST API? Use it. Real-time, structured, well-documented. APIs replace SFTP wherever both sides support them.
• Does a major retailer (Walmart, Target, Amazon dropship) mandate AS2? Use AS2. The contract wins.
• Is the partner technical but pre-API? Use SFTP. The protocol is mature, well-supported, and not going anywhere.
• Is the partner non-technical? A branded HTTPS upload portal beats sending them SFTP credentials.
• Is the workflow large-file media? SFTP works fine; large-file specialty services (MASV, Filemail) work better.

Most operating e-commerce merchants end up with several of these running side-by-side — APIs for the modern integrations, SFTP for the long tail, AS2 for the few partners who require it.

The compliance angle

E-commerce file transfer touches several compliance frameworks:

• PCI DSS — if any file contains payment-card data (un-tokenized PANs), the entire transfer chain is in PCI scope. Most modern setups tokenize at intake; check.
• GDPR / CCPA — customer PII in product reviews, account data, return addresses. Customer-data files require regional data-residency awareness.
• SOC 2 — for B2B-heavy merchants whose buyers ask about controls. The file-transfer platform's SOC 2 posture inherits to your customer-facing answers.

A managed file transfer platform with documented compliance posture removes most of this scope from your own program.

The modern way

Files.com is the File Orchestration Platform we'd recommend for e-commerce file workflows in 2026. The platform handles every protocol e-commerce touches:

• SFTP, FTPS, FTP, WebDAV, AS2 on the same backend — supplier feeds, EDI partners, marketplace integrations, dropship vendors all on one endpoint.
• REST API + SDKs in 8 languages for direct integration with Shopify, BigCommerce, Magento, your ERP, or your own custom storefront.
• Branded HTTPS upload portals for non-technical partner intake.
• Webhook automation — file arrives, downstream pipeline triggers immediately.
• Audit logging on every operation — per-file, per-user, immutable. Inherits into SOC 2 / PCI evidence.
• SOC 2 Type II, HIPAA-BAA, GDPR-ready, PCI-capable posture out of the box.

Start a free Files.com trial — no credit card.

For merchants that must run file-transfer infrastructure inside their own datacenter (some regulated payments workflows, some sovereign-cloud requirements), the free ExaVault on-premise appliance handles the same protocols from a self-hosted VM image.

FAQ

What is an FTP site in e-commerce?

A loose term for a server (or hosted service) that accepts file uploads / downloads over the FTP protocol. In e-commerce specifically, it's typically the endpoint where suppliers drop product catalog feeds, agencies deliver marketing assets, or fulfillment partners push order updates. In 2026, "FTP site" usually means SFTP (encrypted) rather than plain unencrypted FTP.

What FTP protocol do e-commerce platforms use?

Modern platforms (Shopify, BigCommerce, Magento Cloud) mostly use REST APIs and webhooks instead of FTP. For the workflows still using a protocol — supplier feeds, marketplace EDI, legacy dropship integrations — SFTP is the default; AS2 for some larger retail / marketplace partners.

Why does an SEO or marketing agency need FTP for e-commerce?

To exchange large files with clients — content asset deliveries, analytics export drops, marketing creative, product imagery. SFTP is the technical default; a branded HTTPS upload portal at the agency's domain is friendlier for the non-technical client side of the relationship. See our branded FTP guide.

How do I connect Shopify / BigCommerce / Magento with FTP?

For new integrations, use the platform's REST API instead — better real-time behavior, structured data, no batch-file parsing. For legacy partners that can only speak FTP, the canonical pattern is: SFTP endpoint on a managed file transfer platform (Files.com) → middleware (a connector service or custom integration) → the e-commerce platform's API. The platform itself rarely accepts direct FTP uploads in 2026.

Can e-commerce file transfers be automated?

Yes — most production e-commerce file workflows are scheduled or event-driven. Scheduled for things like nightly product catalog updates. Event-driven for things like order webhooks. A managed file transfer platform with webhook + automation features (file arrives → run a transformation → push to the next system) handles both patterns without custom scripting.

What's the best file transfer service for e-commerce?

Depends on the workflow mix. For multi-protocol (SFTP + AS2 + share links + API) and B2B-heavy operations, a full managed-file-transfer platform like Files.com is the right tool. For SFTP-only with a handful of partners, simpler services (SFTP To Go, SFTPCloud) work. For internal team file sharing, cloud collaboration (Dropbox / Drive / OneDrive) plus a separate B2B file-transfer layer is the common pattern.

How do dropship vendors use FTP for order routing?

The merchant pushes orders to the dropship vendor as a batch file (CSV / XML) on a schedule — typically every few hours during business hours. The vendor returns fulfillment data (tracking numbers, shipped quantities) the same way. Both ends usually use SFTP; AS2 is uncommon outside enterprise dropship programs. Modern dropship platforms (Spocket, Pipe17, Convictional) have replaced this batch flow with real-time APIs, but the FTP-shaped pattern persists for legacy vendor relationships.