Vendor's Guide to Setting Up SFTP

June 27, 2026

Summary

For vendors: set up an SFTP server, format inventory/order/tracking files, share access securely, and agree on a transfer schedule.

This guide is for vendors working with a Flxpoint customer who will exchange data over SFTP (Secure File Transfer Protocol) instead of the portal. You’ll set up an SFTP server, prepare flat files for inventory, orders, and tracking, share access details securely, and agree on a transfer schedule.

What this covers

Set up a server

Stand up an SFTP server with a dedicated folder for FLX files.

Prepare flat files

Format inventory, order, and tracking files to spec.

Share access

Send your host, port, and credentials securely.

Agree a schedule

Set upload/download frequency and file naming.

Step 1 — Set up your SFTP server

If you don’t already have a server, here’s the shape of it:

Task	Details
Choose a solution	Use an existing server or a provider such as FileZilla Server, AWS Transfer Family, or a hosted service (ExaVault, GoAnywhere). Make sure it supports SFTP, not just FTP.
Configure it	Install/set up the software and create a dedicated directory for FLX files, e.g. /flx-integration.
Set credentials	Create a unique username (e.g. flxvendor1) and a strong password (12+ chars, mixed). Optionally use an SSH key pair instead of a password for added security.
Test the connection	Log in with an SFTP client (WinSCP, Cyberduck) to confirm the server is reachable.

Not tech-savvy?

Ask your IT team or your Flxpoint contact for help choosing and setting up an SFTP solution.

Step 2 — Prepare your flat files

FLX exchanges CSV or XLSX files. Your Flxpoint contact provides the exact templates and column headers — this is the general shape:

File type	Typical columns	Direction
Inventory	SKU, quantity, price, product name	You upload (e.g. daily)
Orders	Order ID, SKU, quantity, shipping address	You download from SFTP
Tracking	Order ID, tracking number, carrier, shipment date	You upload after fulfilling

Save files in your integration directory, e.g. /flx-integration/inventory.csv. Always ask your Flxpoint contact for exact headers and sample files.

Once your server is ready, send your Flxpoint contact:

Detail	Example / note
Hostname	sftp.yourdomain.com or an IP address
Port	Usually 22 unless customized
Username	The one you created (e.g. flxvendor1)
Password or SSH key	Share the password or the public SSH key — never the private key
Directory path	Where files live, e.g. /flx-integration/

Never send credentials over plain email or text

Use a secure channel — encrypted email or a password-manager share link — to protect your server. Share only the public key, never the private key.

Step 4 — Coordinate the exchange schedule

Agree with your Flxpoint contact on:

Item	Example
Upload frequency	Inventory & tracking, e.g. daily at 2 AM
Download frequency	Checking for new order files, e.g. hourly
File naming	Consistent names like inventory_YYYYMMDD.csv

Test the whole process by uploading a sample inventory file and asking your contact to confirm receipt.

Troubleshooting & good practice

Connection or transfer issues

Check that your network allows traffic on port 22, that your credentials (or SSH key) are correct and scoped to the FLX integration directory, and review server logs (often in /var/log/) for errors. Keep file names consistent.

Keep it secure over time

Keep your SFTP server updated, rotate passwords/SSH keys periodically, share only public keys securely, and restrict access to just the integration folder (e.g. /flx-integration).

FAQs

Does it have to be SFTP, or is FTP okay?

Use SFTP. It encrypts the connection; plain FTP does not. Most providers support SFTP — just confirm before you commit.

What columns do my files need?

Inventory needs SKU, quantity, price, product name; orders need order ID, SKU, quantity, shipping details; tracking needs order ID, tracking number, carrier, shipment date. Your Flxpoint contact provides the exact headers and sample files.

How do I share credentials safely?

Never by plain email or text. Use encrypted email or a password-manager share link, and send only the public SSH key — never the private key.

Bulk transfer isn’t working — where do I start?

Confirm port 22 is open, your credentials are correct and limited to the integration directory, and your file names are consistent. Then check your server logs for specific errors.

Back to Vendor Portal