Salsify - FTP Integration and Automation

Common Integration Use Cases Between Salsify and FTP

• Bulk product catalog import from legacy systems into Salsify: Use FTP to move large product master files, SKU updates, and attribute spreadsheets from ERP, PIM, or legacy merchandising systems into Salsify on a scheduled basis. This supports centralized product enrichment while reducing manual file handling and accelerating onboarding of new assortments.
• Automated export of enriched product data to retailer FTP endpoints: After content is approved in Salsify, publish channel-specific product feeds, pricing files, and attribute sets to retailer or distributor FTP locations. This helps brands meet partner file-based requirements for marketplace onboarding, seasonal updates, and ongoing content refreshes without manual rework.
• High-resolution asset delivery to print and packaging vendors: Send approved images, lifestyle assets, and packaging artwork from Salsify to vendor FTP servers for print production, label generation, or packaging updates. This improves version control, shortens production cycles, and ensures external partners receive the latest approved creative files.
• Retailer-specific content synchronization for large file exchanges: For trading partners that require batch file submissions instead of APIs, Salsify can generate and export tailored product content packages via FTP. This is useful for large assortments, frequent assortment changes, and partners with strict file naming, folder, or delivery schedules.
• Digital asset backup and archival from Salsify to secure FTP storage: Periodically transfer approved product images, videos, and enriched content exports from Salsify to an FTP or SFTP archive for retention, disaster recovery, or compliance purposes. This gives marketing and operations teams a controlled backup of critical product content outside the primary platform.
• Inbound supplier content collection into Salsify through FTP drop zones: Suppliers can upload product specifications, compliance documents, and media files to a designated FTP folder that feeds Salsify for review and enrichment. This streamlines supplier collaboration, reduces email-based file exchange, and creates a repeatable intake process for new product launches.
• Batch update of channel content based on FTP-delivered feedback files: Retailers or internal channel teams can send performance reports, content error logs, or item rejection files back to an FTP location for ingestion into Salsify workflows. Teams can then correct missing attributes, replace assets, and republish improved content faster, improving digital shelf performance and reducing listing errors.