How to automatically download price lists from email, FTP, or a link

Automatically downloading price lists from suppliers is a critical element of online store inventory management. Manually processing files from dozens of suppliers takes hours of work and creates the risk of information becoming outdated. Modern systems allow you to set up automatic price list imports from various sources: email, FTP/SFTP servers, direct HTTP links, and cloud storage.

In this guide, we'll cover all the main methods for automatically uploading price lists, their settings, advantages, and security recommendations. Proper automation will save you up to 15-20 hours a week on routine operations and ensure your catalog is always up-to-date.

Downloading price lists from email

Email remains one of the most common methods for receiving price lists from suppliers. Many companies send updated files via email on a daily or weekly basis.

Setting up automatic import from email

Basic connection parameters:

Protocol: IMAP or POP3 (IMAP is preferred for storing emails)
Server: imap.gmail.com, outlook.office365.com, or your ISP's server
Port: 993 for IMAP SSL, 995 for POP3 SSL
Authentication: login/password or OAuth2 for Google/Microsoft

Filtering emails

Set up processing rules for automatic price list recognition:

Sender: email addresses of specific suppliers
Email subject: keywords "price list", "catalog"
File extensions:.xls,.xlsx,.csv,.xml,.zip
Attachment size: spam protection limit

Benefits of Email Import

Does not require technical knowledge from the supplier
The supplier controls the frequency of shipments.
The history of all updates is saved in your mailbox.
It's easy to add a new supplier - just email

Safety recommendations

Use a dedicated email address only for receiving price lists. This simplifies filtering and improves security. Enable two-factor authentication and use app passwords instead of your primary email password.

Downloading from FTP/SFTP servers

FTP (File Transfer Protocol) and its secure version, SFTP, are the professional standard for exchanging files between companies. Large suppliers prefer this method for regularly updating their price lists.

Setting up an FTP connection

Connection parameters to the provider's server:

Host: ftp.supplier.com or the server's IP address
Port: 21 for FTP, 22 for SFTP
Login and password: provided by the supplier
File path: /prices/current.xlsx or /export/price_list.csv
Mode: Passive (PASV) for working through NAT/Firewall

FTP vs. SFTP: Security Issues

SFTP (SSH File Transfer Protocol) - a modern standard that necessarily uses encryption:

All data is transmitted in encrypted form.
Protection against interception of logins and passwords
GDPR and PCI DSS compliance
Ability to use SSH keys instead of passwords

Recommendation: Always use SFTP instead of regular FTP when working with sensitive data.

Automatic file downloads

Set up an FTP server check schedule:

Daily: for suppliers with frequent price changes
Weekly: for stable price lists
According to the schedule: on certain days of the week (for example, Monday and Thursday)
On file change: check modification date, download only when updating

Working with multiple files

Some suppliers host multiple files on FTP for different product categories. Use file masks for automatic processing:

price_*.xlsx - all files starting with "price_"
*_2025-10-*.csv - current month files
Processing by folders: /new/, /archive/

Download via HTTP/HTTPS link

Downloading a price list via a direct link is the simplest and fastest integration method. The supplier hosts the current file on the web server, and your system downloads it periodically.

Types of HTTP links

1. Direct link to the file

The simplest option is a direct link to the file:

https://supplier.com/exports/price_list.xlsx
https://partner.com/feeds/current_prices.csv
https://api.provider.com/files/catalog.xml

2. Dynamic URLs with parameters

Links with parameters for filtering or authentication:

https://supplier.com/export?key=YOUR_API_KEY&format=xlsx
https://partner.com/price?client_id=12345&date=today
https://api.provider.com/v1/prices?category=electronics

3. API endpoints

REST API for retrieving structured data in JSON or XML:

Requires an API key or authorization token
Return data in a standardized format
Supports pagination for large catalogs
May provide additional metadata

Setting up HTTP import

Main parameters:

URL: full file address or API endpoint
Method: GET (usually) or POST for APIs
Authentication: Basic Auth, Bearer Token, API Key
Headers: additional headers (User-Agent, Accept)
Timeout: response time (30-60 seconds)
SSL verification: certificate verification for HTTPS

Benefits of HTTP Download

Simplicity: does not require setting up an email or FTP client
Speed: direct download without intermediate steps
Reliability: works via the standard HTTP/HTTPS protocol
Monitoring: It's easy to check link availability
Caching: Using HTTP headers for optimization

Working with protected links

For security, many providers use authentication:

Basic Authentication: login and password in the request header
API Key: unique key in URL parameters or headers
OAuth 2.0: access token for API integrations
IP Whitelist: access only from permitted IP addresses

Cloud storage (Dropbox, Google Drive)

Cloud file storage services are becoming a popular way to share pricing, especially for small and medium-sized businesses.

Google Drive

Integration methods:

Public link: the provider makes the file available via a link
Shared folder: access to a folder with regularly updated files
Google Drive API: programmatic access via OAuth2
Service Account: automatic access without user intervention

Dropbox

Connection options:

Shared Links: direct links to files for downloading
Dropbox API: integration via API keys
Shared folders: file synchronization between accounts
Webhooks: file change notifications

OneDrive / SharePoint

Microsoft cloud solutions for corporate clients:

Integration with Office 365 / Microsoft 365
Microsoft Graph API for file access
Azure AD support for authentication
Versioning and file change history

Advantages of cloud storage

Convenience: a familiar interface for suppliers
Automatic synchronization: files are always up to date
Version history: the ability to roll back to a previous version
Sharing: easy to manage rights
Mobility: access from any device
Reliability: backup and high availability

Setting up automatic downloads

To work with cloud storage you will need:

Access a file or folder from a provider
Set up an API connection (for automation)
Specify the path to the file in the cloud
Set a schedule for checking for updates
Configure processing of new file versions

Automating the download process

After setting up data sources, it is important to properly organize the automatic process of updating price lists.

Update schedule

Factors in frequency selection:

Price volatility: How often do supplier prices change?
Competition: the criticality of relevance to your niche
System load: data volume and processing time
Supplier's working hours: when he updates prices

Recommended intervals

High frequency products (electronics, currency-dependent): every 2-4 hours
Average frequency (clothing, shoes, accessories): 1-2 times a day
Stable assortment (furniture, building materials): once a day or every other day
Rare changes (books, stationery): 2-3 times a week

Processing order

When working with multiple suppliers, it is important to organize the queue correctly:

Prioritization: key suppliers first
Parallel processing: several price lists at the same time
Night loading: main process during non-working hours
Division by categories: grouping similar price lists

Error handling

Typical problems and solutions:

File unavailable: try again in 15-30 minutes
Invalid format: administrator notification, file skipping
Partial data: decision to apply or reject
Authentication error: credentials verification, notification
Timeout: increase waiting time or optimization

Logging and monitoring

Keep detailed logs of all operations:

Download start and end time
Uploaded file size and number of records
Operation success or error code
Changes in data (new products, price changes)
Processing time and resources used

Problem notifications

Set up alerts for critical situations:

Email or SMS if key price lists fail to load
Notification about a long absence of updates
Price Change Warning (Possible Error)
Alert when there is a significant change in the quantity of goods

Versioning and backups

Save the history of downloaded files:

Archiving source files: storage 30-90 days
Database snapshots: before applying changes
Price change history: to analyze the dynamics
Rollback option: restore previous version

Safety and compliance

Automatic price list downloads involve the transfer of confidential commercial information. Reliable data protection is essential.

GDPR Compliance

When working with European suppliers, please consider GDPR requirements:

Data encryption: during transmission (TLS/SSL) and storage
Data minimization: upload only the necessary information
Access rights: restricting access to credentials
Logging: audit of all data transactions
Data Processing Agreement: agreement with suppliers

Secure storage of credentials

Recommendations:

Do not store passwords in clear text in configuration files.
Use an encrypted vault for credentials
Use different accounts for different providers
Change your passwords regularly (every 3-6 months)
Use strong, unique passwords

Malware protection

Files from external sources may contain threats:

Antivirus scan: scanning all downloaded files
Isolated processing: sandbox for file parsing
Format validation: checking for compliance with the expected type
File size: maximum size limit
Extension whitelist: only allowed file types

Network security

Firewall: limiting outgoing connections
IP Whitelist: connect only to known servers
VPN: secure channel for critical data
SSL/TLS: mandatory encryption for all protocols
Certificate Pinning: checking server certificates

Backup

Ensure secure storage of critical data:

Daily backup of the price list database
Archiving source files from suppliers
Storing backups in a separate physical location
Regularly check for recovery possibilities
Documenting the disaster recovery procedure

Conclusion

Automatic price list uploading isn't just a time saver; it's a fundamental element of a modern online store's competitiveness. A properly configured system allows you to:

Save 15-20 hours a week on manual file processing
Improve data accuracy by eliminating the human factor
Ensure prices are up-to-date in real time
Scaling your business without proportional growth of staff
Improve relationships with suppliers through secure data exchange

Selecting a download method

Email import Suitable for small stores with 5-10 suppliers, does not require technical skills from contractors.

FTP/SFTP Optimal for large providers with large volumes of data, provides high reliability and security when using SFTP.

HTTP/HTTPS links - a universal solution that combines easy setup with high loading speed. Ideal for API integrations.

Cloud storage Good for small businesses and startups, they provide ease of use and automatic synchronization.

Next steps

To implement automatic price list downloading:

Conduct an audit of current methods for obtaining price lists from suppliers
Prioritize suppliers by volume and frequency of updates
Agree with key suppliers on a preferred data transfer method
Start with 2-3 suppliers to test the system
Gradually add other data sources
Set up monitoring and notifications
Regularly analyze logs and optimize processes

Ready to automate price list uploads?

Platform Elbuz Provides a complete set of tools for automatically downloading and processing price lists from any supplier. Support for all modern protocols, flexible scheduling, and intelligent data processing.

Learn more about automated price list processing

Save a link to this article

Elbuz Team

Copywriter Elbuz

We build Elbuz, an e-commerce automation platform: price list imports, product matching, pricing rules, and marketplace exports. Our guides are written from the product's source code: the developer who built a feature drafts the article, and a separate reviewer checks every claim against the code. We write about the software we design and maintain ourselves.