7 Tips to Compare Products
No-code custom feed builder: create partner-ready feeds without engineering
NetAmplify’s Custom Feed Builder lets you create bespoke product feeds when there is no ready-made connector. Think affiliate networks, price comparison sites and publishers, or a one-off partner with a CSV/JSON spec. If you used “My Custom Channel” before, this follows the same idea: map fields, transform values, filter products, validate, and schedule delivery - all without asking developers.
Table of content
When a custom feed is the right move
- Pilots and quick tests: a partner sends a simple spec; you want to go live this week, not next quarter.
- Local opportunities: a country-specific comparison site needs a slightly different field set or language.
- Affiliate programmes: networks often request their own column names, formats and image rules.
- Publisher placements: curated lists or gift guides that require a lean product feed.
- Internal consumers: merchandising or BI teams need a tidy subset with exactly the columns they use.
What you can control — without code
- Formats: CSV, TSV, XML or JSON.
- Field design: names, order, data type, separators, date and price formats.
- Transformations: if–then rules, find/replace, concatenate, strip HTML, round prices, currency convert.
- Lookups: brand normalisation, category mapping, shipping classes.
- Filters: include/exclude by stock, price, margin band, category, brand, labels, season.
- Variants: parent only, one row per variant, or flattened — as the partner requires.
- Delivery: secure URL (token) or SFTP push if the partner prefers files.
- Schedules: daily, several times per day for fast movers, or ad-hoc on demand.
Example partners and use cases
- Affiliate networks: Awin, CJ, Tradedoubler — bespoke column names and validation rules.
- Comparison engines: Idealo, Kelkoo, ShopMania — specific category and price fields.
- Publishers: top-list placements that need lean feeds with hand-picked attributes.
- Remarketing tools: niche platforms that accept JSON endpoints or compact CSVs.
Mapping to a partner CSV spec (worked example)
| Partner requires | Map from your data | Transformation | Notes |
|---|---|---|---|
| id | item_id | none | Stable variant or SKU ID |
| title | brand + " " + product_type + " " + key_attribute | concatenate | Keep under 150 characters |
| description | description_html | strip HTML | Remove styles/scripts |
| price | price | 2 decimals + currency | e.g. 129.90 EUR |
| sale_price | promo_price | fallback to price if empty | Leave blank if no promo |
| availability | stock_quantity | if stock > 0 then "in stock" else "out of stock" | Plain text values |
| image_link | image_primary | ensure https | Absolute URL required |
| additional_image_link | image_2,image_3 | join with comma | Respect partner max count |
| brand | brand | lookup normalisation | “NIKE Inc.” → “Nike” |
| category | internal_category | lookup to partner taxonomy | Send exact partner node |
| gtin | gtin | validate length | Digits only; checksum ok |
Transformations you will actually use
- Title tidy: remove boilerplate like “Official Store”.
- Colour normalisation: “Dark Navy”, “Navy Blue” → “Navy”.
- Size mapping: split “W32 L32” to separate waist/leg fields if required.
- Price rounding: round to .99 for specific categories.
- Exclusions: drop out-of-stock items, low-margin ranges, or products missing GTIN or a primary image.
Validation and safety
- Required fields: block export when id, title, price, availability or image are missing.
- Value ranges: flag negative prices, zero dimensions, invalid GTINs.
- Row counts: compare today’s rows with yesterday’s; alert on big swings.
- Preview: download a 100-row sample to share with the partner before switching on the full feed.
Scheduling and delivery
- Frequencies: daily at set times, or several times per day for fast movers.
- File naming: include channel, country and date, e.g. partnername_de_2025-09-11.csv.
- Time zones: align refresh with partner ingestion windows to avoid stale data.
- Distribution: share a tokenised URL, or push to the partner’s SFTP if they prefer nightly pulls.
Governance and teamwork
- Version history: record who changed mappings/rules and when.
- Clone and adapt: duplicate a working channel for a new country; change currency/language and a few rules.
- Access control: restrict who can publish changes on live feeds; use drafts for testing.
Common mistakes to avoid
- Near matches: bundles and packs must match the partner’s definition or the feed will be rejected.
- Missing identifiers: GTIN and consistent brand naming improve reach and trust.
- One-off fixes: solve with a rule so the next 1,000 SKUs inherit the improvement.
- Unclear ownership: agree sign-off for field names, image policy and price formatting before go-live.
Next steps
👉 Learn more about Custom Feed Builder 👉 Connect to affiliate and comparison partners 👉 Improve feeds with optimisation rules 👉 Request a demo
Our guides
Boost your e-commerce performance with Lengow
Centralize, optimize and distribute your product catalogs across every sales channel.