A destination is a configured export: Vendably formats your product data and delivers it to a specific channel or platform. You can have multiple destinations running from the same product source, each with its own field mapping, schedule, and delivery method.
For platform-specific setup steps, see the per-destination articles. Google Shopping feed setup is a good starting point if that is your first destination.
What you need before you start
- An active product source connected in DataHub with at least one completed import.
- Login credentials or API access for the platform you are connecting to (where authentication is required).
A good feed health score before adding a destination reduces how many products are flagged on first export. Fixing data quality issues in DataHub first is quicker than resolving disapprovals after submission.
Destination types
Vendably supports the following destination categories:
- Shopping: Google Shopping, Microsoft Shopping, PriceGrabber, Kelkoo
- Ads: Google Ads, Criteo, AdRoll
- Social: Facebook Ads, Facebook Shops, Instagram, Pinterest, Snapchat, TikTok
- Affiliate: Awin, Awin XML, Tradedoubler, Rakuten, Webgains
- Email and CRM: Emarsys
- Marketplaces: Amazon
- Custom: Custom XML, Custom CSV, Custom JSON, Custom TXT
Reviews Feed destinations are system-managed and are configured separately when you connect a reviews integration.
Adding a destination
Open DataHub in the main navigation, then go to Destinations (under the Distribute group). Select Add destination to open the setup wizard. The wizard guides you through:
- Platform selection: choose the channel or platform from the list above.
- Authentication: for platforms that require it, you authorise Vendably via OAuth or by entering API credentials. Credentials are stored against your account and reused for subsequent exports.
- Delivery method: choose how Vendably delivers the feed to the platform.
- Schedule: set when Vendably exports data to this destination.
- Field mapping: review or adjust how your product fields map to the platform's required fields. Vendably pre-fills a standard mapping for each platform; you only need to change it if your data structure is non-standard or you want to customise what is sent.
- Test export: run a test against a sample of your catalogue before activating the destination. The test export does not submit data to the live platform.
Delivery methods
| Method | How it works |
|---|---|
| Hosted URL | Vendably generates and hosts the feed file. You give the URL to the platform, which fetches it on a schedule. |
| API Push | Vendably pushes product data directly to the platform's API. Only changed products are submitted on each run; Vendably diffs the current export against the previous one to avoid unnecessary re-submissions. |
| SFTP / FTP | Vendably writes the feed file to your SFTP or FTP server. |
| Vendably emails the feed file to a specified address on each export. | |
| Webhook | Vendably POSTs the feed payload to a URL you specify. |
For most major platforms, API Push is available and preferred: it reduces latency and limits unnecessary submissions.
Export schedule
Each destination can run on its own schedule. Options are:
- Inherit from source: the destination exports after each successful source import.
- Custom schedule: set a specific frequency (hourly, daily, or a custom cron expression).
- Manual only: exports only when you trigger them from the destination detail page.
Feed validation
Before each export, Vendably validates every product against the destination's requirements. Products that fail validation are flagged in the export log and excluded from the export; valid products are exported without interruption. Validation errors show which field failed and why, so you can fix the underlying data or add a rule to correct it.
Destination health
Each destination shows a quality score (0-100) and a health status: healthy, warning, error, or inactive. The health status reflects the most recent export: whether it completed successfully, whether there were validation failures, and whether the delivery method is reachable. A destination in error state has a log entry explaining the failure.
See also
- Google Shopping feed setup — step-by-step guide for the most common destination type
- Feed health score explained — how your catalogue quality affects export outcomes
- How the Rules Engine works — transforming product data before it reaches a destination
- Custom fields — adding fields that exist only in Vendably, for use in destination mapping