Feedoptimise shares their practical approach to feed setup, taxonomy mapping, and image compliance
“Fruugo integrations tend to succeed on one thing: product data quality at scale.
Feedoptimise is a feed management and optimisation cloud software that connects to your store data, transforms it into Fruugo’s required structure, validates it, and publishes it. Feedoptimise also includes AI tools for tasks that are often manual, like taxonomy mapping, image processing, and optimisation of titles and other attributes.
What Fruugo needs from your feed
At minimum, you want to plan for:
● A consistently structured feed (CSV or XML) served from a static URL that Fruugo can retrieve on a schedule
● Frequent updates (daily minimum, more often if your prices or stock move quickly)
● Clean product identifiers and attributes, so products can be matched and classified
(for example, GTIN coverage is important for many catalogues)
● Compliant product images, including a minimum size and white background (plus rules
around watermarks and placeholders)
Where sellers usually lose time
These are the common issues that slow onboarding or create recurring warnings:
- Taxonomy mismatch
Your store categories seldom map to a marketplace structure without manual work. Category mapping by hand does not scale once you have thousands of SKUs or frequent new product drops. - Attribute gaps and inconsistencies
Brand naming, variant values (size, colour), materials, and identifiers often vary by supplier, even within the same catalogue. - Image requirements
Fruugo requires product images to meet minimum size requirements and sit on a white background, and images are only updated when the filename changes. If your catalogue contains lifestyle images, mixed backgrounds, or inconsistent naming, you end up in a time-consuming clean-up loop.
How Feedoptimise supports a Fruugo integration
Feedoptimise turns whatever your source data looks like today into a stable, compliant Fruugo-ready feed that keeps running.
1) Connect to your store or source feed
Feedoptimise supports multiple input methods, including common carts plus feed URLs, APIs, and file-based methods (FTP/SFTP).
You can start with what is available now, then upgrade the connection method later without rebuilding everything.
2) Map attributes and build the Fruugo export
Once your source data is connected, you can set up the field mappings and transformations yourself, or have Feedoptimise’s team do it via their inclusive managed service, so Fruugo receives the format it expects. This is where you typically handle:
● Required field mapping
● Variant normalisation (parent/child logic, option naming)
● Formatting rules (for example, numeric formatting in CSV feeds)
● Exclusions (out of stock ranges, restricted products, bundles you do not want
syndicated)
3) Taxonomy mapping with AI (so categories do not become a manual project)
Category mapping is one of the highest-effort parts of any marketplace integration.
Feedoptimise positions “AI Feed Optimisation” around enrichments including categories and taxonomy mapping, which you can use to automate classification rather than maintaining category rules per product line by hand.
For example:
● Automatically classifying new SKUs into the right category structure
● Reducing “miscellaneous” or fallback categorisation
● Making category rules easier to maintain as your catalogue grows
4) Make images Fruugo-compliant, including white backgrounds
Fruugo’s retailer documentation specifies that the primary image should meet minimum size requirements and sit on a white background, and it also notes restrictions such as no watermarks or placeholders.
Feedoptimise includes an image editor that supports background removal and replacement with solid colours, and AI-driven template workflows for image optimisation.
With these tools, sellers can:
● Remove non-compliant backgrounds from product images
● Standardise output to a clean white background for Fruugo
● Create consistent image formatting across a large catalogue
Tip: Because Fruugo only updates images when the filename changes, make sure your
publishing process outputs new filenames when you intentionally replace an image, or use
Feedoptimise’s image editor, which updates filenames automatically when changes are made.
5) Publish reliably and keep it updated
Feedoptimise publishes feeds via common delivery methods such as HTTPS and FTP/SFTP, which aligns with Fruugo’s requirement for an automated feed accessible for scheduled imports.
You want to stay live without daily manual intervention, not just get the feed published once.
A simple Fruugo integration checklist
If you are planning your integration, this is a useful order of operations:
● Confirm feed format (CSV or XML) and publishing method (static URL / scheduled retrieval)
● Audit identifiers and key attributes (brand, GTIN coverage, variant consistency)
● Set taxonomy mapping rules, then add AI-assisted classification for scale
● Standardise images (size, white background, no watermarks), and ensure your workflow supports filename changes for image updates
● Set update frequency (daily minimum, more often if you need it)
● Add validation checks before publishing, so issues surface before Fruugo pulls the feed
Closing note
Most Fruugo integrations stall because the data is hard to maintain, not because data is missing. A toolchain that connects to your sources, maps and validates your catalogue, handles
taxonomy mapping with AI, and keeps images compliant (including white backgrounds) will smooth out onboarding and day-to-day feed operations.
If you’re setting up your Fruugo integration and want to avoid manual feed maintenance, Feedoptimise can help you get your catalogue Fruugo-ready and keep it updated You can sign up for a 7-day trial to see how it works with your catalogue”
