Einkaufen24 Integration

Listing on Einkaufen24 puts your catalog in front of Swiss shoppers who are actively comparing prices before they buy — traffic that is typically further down the purchase funnel than generic display or social traffic. Because Einkaufen24 sits inside the shopping24 commerce network, a correctly built feed is also a foundation for expanding into the network's other portals (shopping24.de, discount24.de, fashion24.de, living24.de and the international shoparound.* sites) without re-engineering your data from scratch for each one.

Einkaufen24 does not publish a separate feed specification of its own. Instead, shopping24 GmbH maintains one shared "Feed-Spezifikationen" whitepaper that governs product data across all ten of its portals, Einkaufen24 included. In practice this means: build one feed to the shopping24 network's field names and formatting rules, and — once your account is set up and activated per portal by your shopping24 account manager — the same data structure can, in principle, supply Einkaufen24 as well as the network's other shopping-search portals.

Per shopping24's official feed specification, the network accepts product data feeds in two formats:

1. CSV — the first row must contain the field names (e.g. sku, title, ...), each subsequent row is exactly one product, and the delimiter must be a pipe (|), semicolon (;), or tab.
2. XML — the following characters cannot be used directly and must be entity-encoded: < as <, > as >, & as &, " as ", and ' as '.

Files must be encoded in UTF-8 or ISO-8859-1. Feeds are delivered either via a webserver URL (http/https download, with credentials if needed) or via an FTP server (server name, file path and login credentials); the specification explicitly asks merchants to always keep the same file name across updates so the feed can be re-fetched automatically. Fields that can carry multiple values (e.g. several product images) are marked "Mehrfachangaben möglich" and must either use a List suffix (e.g. imageUrl becomes imageUrlList, with values separated by a comma, semicolon or pipe that differs from your CSV delimiter) or a numeric suffix (imageUrl1, imageUrl2, ...).

The shopping24 network specification defines mandatory ("Pflichtfelder"), recommended, and optional fields. The mandatory fields that must be present and filled for every product are:

Beyond these, shopping24 lists a further tier of "recommended" fields (e.g. googleShoppingUrl, base-price fields referencePriceAmount/referencePriceQuantity/referencePriceUnit, color, clothing/shoe size fields, sustainability, secondHand) plus dozens of category-specific optional attributes (from EnergyEfficiencyGrade to camera, watch and appliance-specific fields), which the whitepaper says directly improve categorization and listing performance.

Feedance can generate an Einkaufen24-ready feed from your existing product catalog without you having to hand-build a CSV or XML file:

1. Map your store's product fields to the shopping24 network's schema — at minimum sku, title, description, productUrl, imageUrl, price, oldPrice, deliveryCosts, deliveryTime, category, brand, gtin and itemGroupId, plus genderAge for fashion items.
2. Choose CSV (pipe, semicolon or tab delimited) or XML output, encoded as UTF-8 or ISO-8859-1, matching what the shopping24 network expects.
3. Publish the feed at a stable URL (or push it to an FTP location) and keep the file name constant across every update, as the specification requires.
4. Share the feed URL or FTP credentials with your shopping24/Einkaufen24 account manager to complete activation — onboarding to a network portal is handled by shopping24's team rather than through a self-service signup form.

If a fully custom feed isn't feasible, shopping24's own documentation notes they will also consider importing an existing feed you already maintain (they cite Google Shopping/PLA feeds as an example) — worth raising with your account manager if you already run Feedance feeds for Google Merchant Center.

Shopping24's feed specification states only that your feed is "regularly checked for updates," without publishing an exact required interval. Feed-management partners in shopping24's own integration program (e.g. Channable) advertise automated syncing anywhere from hourly to daily depending on the merchant's needs — but that describes what the tooling supports, not a rule Einkaufen24 enforces. Because price accuracy is treated strictly (the spec repeatedly stresses that price must match your landing page and must never be 0), a daily refresh is a reasonable baseline, with more frequent updates for fast-moving price or stock changes.

These are error conditions the shopping24 specification explicitly calls out as invalid or harmful to a listing:

1. Submitting price as 0, or a price that doesn't match what's shown on the actual product page.
2. Leaving oldPrice empty — it must always be populated, even with the same value as price when there is no discount.
3. Missing base-price fields (referencePriceAmount, referencePriceQuantity, referencePriceUnit) for products sold by weight, volume, length or area — German price-labeling law (Preisangabenverordnung) makes the merchant liable for omissions here.
4. Submitting a gtin that isn't a valid GTIN under the official GS1 validation guide.
5. Images that are placeholders, watermarked, bordered, blown-up thumbnails, below the minimum size (100x100px, or 250x250px for apparel), or over the 16MB/64-megapixel ceiling.
6. URLs (productUrl, directLinkUrl, imageUrl) that aren't properly RFC 2396/1738 encoded — e.g. an unescaped comma instead of %2C.
7. Reusing the same field name twice in one feed, or malformed multi-value lists (wrong separator on a ...List field, or a separator that collides with your CSV delimiter).
8. Omitting genderAge on fashion-category products, where it's mandatory.

These are general product-feed best practices, not Einkaufen24-specific guarantees:

1. Fill in as many of the "recommended" and "optional" attributes as apply to your catalog (color, size fields, energy-efficiency class, material, etc.) — shopping24's own documentation states this directly improves categorization and listing economics.
2. Keep sku and itemGroupId values stable across every feed update so product history and variant grouping aren't lost.
3. Write plain, accurate titles and descriptions — no promotional phrases like "free shipping," no all-caps, and no links to your storefront inside the description field.
4. Double-check that price, delivery cost and delivery time in the feed always match what a shopper actually sees on your landing page, since mismatches are treated as a compliance issue by the network.

Is Einkaufen24 the same as einkaufen24.de?
Not currently — einkaufen24.de 301-redirects to discount24.de. The live "Einkaufen24" property is einkaufen24.ch, a Swiss shopping-comparison portal.

Who operates Einkaufen24?
Shopping24 GmbH, based in Hamburg, Germany, which runs the wider shopping24 commerce network of ten shopping-search portals.

Can the same feed also supply other shopping24 portals?
The network shares one feed specification across all ten portals (including shopping24.de, discount24.de, fashion24.de and living24.de), so a single correctly-built feed can be the basis for listing on more than one — each portal still needs to be activated on your account separately by shopping24.

Does every product need a GTIN?
gtin is listed as a mandatory field in the specification, but only valid GTINs (per the GS1 validation guide) should ever be submitted — don't fabricate one for products that don't have one; raise the exception with your account manager.

Where do I find the full list of accepted values for fields like color or material?
The specification notes that for several attributes (e.g. color, camera/appliance feature lists), the complete list of supported values is only available on request from your shopping24 account manager.