Tools
EU-hosted product feed tools
Product feeds carry prices, stock, margins via custom labels and sometimes supplier data, and a feed tool holds a copy of all of it. If your procurement or DPO asks where that copy lives, most vendors' pricing pages do not say. This page is a checklist for evaluating an EU-hosted product feed tool, with the questions to put to any vendor and the answers Textfinity gives from its own infrastructure.
We connect your store, build the feed and keep it in sync. Updated 2026-10-27.
At a glance
- Ask four things: where processing runs, where AI inference runs, who the operator is, and whether channels fetch from the tool or the tool pushes to them.
- Of the two enterprise feed vendors whose pages we fetched today, neither states a hosting region; one lists ISO 27001.
- Textfinity processes feeds on Hetzner infrastructure in Germany, runs AI on Vertex AI EU endpoints, and is operated by Datafinity AB in Sweden.
- The same EU infrastructure serves every Textfinity catalog, large or small, so the EU answer is not an enterprise-only answer. We set the feeds up in Textfinity for you and quote per catalog.
What 'EU-hosted' should mean for a product feed tool
A feed tool touches product data in four places, and 'EU-hosted' is only meaningful if it covers all four. Storage: the copy of your catalog the tool keeps between syncs, including every column you map and every column you do not. Processing: the servers that run mapping, filtering and feed generation. AI inference: if the tool writes titles or descriptions with a model, the endpoint that model runs on, which is often a different provider and region from the application itself. Delivery: the URL channels fetch from, or the API the tool pushes to.
Ask vendors to answer per layer. A tool can run its web app in Frankfurt and still send every description to a model endpoint in the United States, and a pricing page that says nothing about hosting is not a 'no'; it is a question to put in writing before you sign.
The checklist, with Textfinity's answers
The table lists the questions in the order a DPO usually asks them, and what Textfinity publishes for each. The vendor column is deliberately about what to ask rather than what competitors do, because the pages we fetched for this comparison did not state hosting regions.
| Question to ask | Why it matters | Textfinity |
|---|---|---|
| Where are feeds processed? | The bulk of your data lives here between syncs | Hetzner infrastructure in Germany |
| Where does AI inference run? | Titles and descriptions leave the app for the model | Vertex AI Gemini on EU endpoints |
| Who is the operator and where? | Determines the contracting entity and applicable law | Datafinity AB, Sweden |
| Does the tool pull or push? | Pull means channels fetch a URL you control the contents of | Pull: channels, Google and Meta included, fetch a CSV or TSV URL on their own schedule |
| What leaves the EU by design? | Channels like Google and Meta receive the feed wherever they run | The feed file itself, fetched by the channel |
| Can you see it run on your own data? | Lets you verify behavior on real products, not a demo | Setup is done with you on your own catalog |
| Security certification | Evidence beyond a statement | not published |
Textfinity answers from its own infrastructure description, checked 2026-10-27.
What the bigger vendors publish about hosting
For this page we fetched the pricing and product pages of two enterprise feed platforms on the date shown. Productsup's pricing page lists ISO 27001 certification and partner badges but does not state a hosting region, a price or a trial. Lengow's pricing page lists scale figures and a demo request and does not state a hosting region, prices or limits. That is not evidence they are outside the EU; it is evidence you will have to ask. The questions above are the ones to send.
The honest limit on Textfinity's side: it does not publish a security certification such as ISO 27001, so a procurement process that requires one will need to weigh the published infrastructure facts against that gap.
Hosting is one criterion; the feed still has to be good
A tool that keeps data in the EU and produces a poor feed solves the wrong problem. Textfinity's feed features, and the infrastructure they run on, are the same for every customer: Shopify, CSV (by HTTPS or SFTP), Google Shopping-format XML and Google Sheets as sources; channel templates for Google Shopping and free listings, Microsoft Ads, Meta Ads, TikTok Ads, Pinterest Ads, Snapchat Ads, Amazon Ads, eBay, Kelkoo, Prisjakt and PriceRunner, plus custom feeds with any channel's columns for Idealo, Awin or Criteo; 13 mapping transforms including regex and an advanced DSL; 26 filter operators; merged sources for joining supplier sheets; and feed hygiene profiling for completeness, over-long values, mixed languages, inconsistent spellings and bad URLs. AI titles, descriptions and translation run on the same EU endpoints for every catalog that uses them.
What it does not do matters for the same evaluation: no Merchant Center diagnostics import, no image editing, no marketplace order handling, and no native plugin for WooCommerce, Magento or PrestaShop, which connect through their export URL.
Multi-market feeds from one EU-hosted catalog
European stores are usually multi-market by default, and the EU question often comes with a translation question. Textfinity reads Shopify markets and locales, generates translated titles or descriptions through an AI config with a target language (accepted in review before a feed uses them), and publishes one feed per market with the right currency string in the price column via a mapping rule. The data stays on the same infrastructure for every market feed.
Per-market price and language rules
price (SE feed) -> advanced: [variant_price] + " SEK" (feed set to the SE market)
price (DE feed) -> advanced: [variant_price] + " EUR" (feed set to the DE market)
title (DE feed) -> replace from AI config "title-de" (fallback: title)
filter (DE feed) -> include only if [ships_to_de] is equal to trueSources checked
Examples
Worked examples, by situation
Three European stores with a hosting requirement and the feed rule that mattered once the requirement was met.
Exclude restricted categories before the data leaves
Before
Export includes 320 prescription-only items that must never appear in a feed
After
Feed carries 2,280 products; restricted items filtered on the EU-hosted side before any channel fetches the URL
How we set it up
We add two exclude filters: [category] is in list (Rx, prescription), and [pzn_restricted] is equal to true. The channel only ever fetches the filtered file.
One catalog, three market feeds, EU AI translation
Before
Titles in Swedish only; Norwegian and Finnish feeds disapproved for language mismatch
After
Three feeds with titles in Swedish, Norwegian and Finnish generated by AI configs on EU endpoints and accepted in review
How we set it up
We set up an enhance-title AI config translated into Norwegian (a second one for Finnish), reading title, color and size; the generations are reviewed and accepted. title maps with replace from AI config, falling back to the Swedish title for anything not yet accepted.
Keep cost columns out of the feed
Before
Export contains purchase_price and margin columns alongside the public price
After
Custom feed with only public columns; cost data never mapped to an output column
How we set it up
We build a custom feed that maps only id, title, price, link, image_link and availability. Unmapped source columns are not written to the feed. Feed hygiene confirms the output column set before publishing.
Copy this plan
Evaluate an EU-hosted feed tool in one afternoon
Evaluate on real data so the evaluation covers the actual feed, not a demo.
01
Send the four hosting questions in writing
Processing region, AI inference region, operator entity, pull or push delivery. Keep the answers with the contract.
02
Run a real catalog, not a demo
Shopify connects natively; other platforms through an export URL. A slice of 100 SKUs is enough to see every rule type.
What we set up: We connect your Shopify store, or read the CSV or XML export URL you send us.03
Build one Google Shopping feed
Start from the template and map the required attributes, then add one regex cleanup and one filter.
What we set up: We create the feed from the Google Shopping template, clean description with remove from regexp and add an exclude filter you choose.04
Check what columns leave
Open the published feed URL and confirm only mapped columns are present. Run feed hygiene for completeness.
What we set up: We publish the feed, send you its URL to inspect, and run feed hygiene on it.05
Test AI on a sample if you need it
Create one AI config for titles in a second language, review and accept the generations, and check the output language consistency with the hygiene checker.
What we set up: We set up an enhance-title AI config with a target language and review a sample with you.06
Add the feed URL in the channel
Paste the feed URL into the channel as a scheduled source. This step happens in the channel's console.
What we set up: We add the URL in Merchant Center or Commerce Manager with access you give us, or walk you through it on a call.
Customization tips
Make it yours
Map only what the channel needs
Unmapped columns never reach the feed. The trade-off is that a column you later need means another sync, which takes minutes, not days.
Treat AI as a separate data flow
Even with EU endpoints, generated text is derived from your product data. Choose source attributes for the AI config deliberately and keep cost fields out.
Do not assume silence means non-EU
A vendor page without a region is a question, not an answer. Ask, and get it in the contract. Textfinity publishes its answer; ask it to confirm in writing too.
Weigh the certification gap honestly
Textfinity does not publish ISO 27001 or similar. If your process requires one, published infrastructure facts may not be enough.
FAQ
Questions about eu hosted product feed tool
Is Textfinity hosted in the EU?
Yes. Feed processing runs on Hetzner infrastructure in Germany, AI generation runs on Vertex AI Gemini EU endpoints, and the operator, Datafinity AB, is based in Sweden.
Does product feed data leave the EU when I use Google Shopping or Meta?
The channel fetches your feed file wherever the channel runs; that is inherent to advertising on Google or Meta. An EU-hosted tool keeps the processing and the stored copy in the EU; it cannot change where Google processes the feed afterwards.
Which product feed tools publish their hosting region?
Of the vendor pages fetched for this page on 2026-10-27, Productsup's and Lengow's pricing pages do not state one. Textfinity publishes Hetzner (Germany) for processing and Vertex AI EU endpoints for AI. Ask any vendor for the answer in writing.
Do I need an enterprise contract to get EU hosting?
Not with Textfinity. Every catalog runs on the same infrastructure in Germany with the same EU AI endpoints, whatever its size; pricing is quoted per catalog after a short call, not by hosting region.
Does EU hosting cover AI-generated titles and descriptions?
In Textfinity, AI configs run on Vertex AI Gemini EU endpoints. Ask any other vendor specifically about the model endpoint, since it is often a different provider and region from the application.
Set up for you
Have your catalog set up on an EU-hosted feed tool.
Send us your store and the channels you sell on. We set up feeds in Textfinity that map only the columns each channel needs, published from infrastructure in Germany.
Tell us your store and channels. We reply within 24 hours.