Compartner Integration

This section is general context rather than a confirmed Compartner benefit, since we could not verify the platform's current merchant program or traffic. Multi-country brand and accessory directories of the type Compartner appears to have run are built to capture searches for a specific brand, model, or compatible part, then route that shopper to a retailer who stocks it. For compatibility-driven categories — the descaler, water-filter, and coffee-machine accessory listings we found are a good example — this kind of "find the right accessory for your brand" catalog can convert well precisely because it removes the guesswork a generic marketplace search leaves shoppers with.

If some successor to Compartner is still accepting retailer feeds in your market, the usual rationale for feeding it automatically still applies: it keeps prices, stock, and availability synced without relying on a one-time manual upload that goes stale.

We could not locate any public feed specification, developer documentation, or merchant help-center article published under the Compartner name — not on compartner.nl before its redirect, not via search, and not through Producthero's own help center. Comparison and CSS-style platforms in this space typically accept XML or CSV/TXT feeds modeled on the Google Merchant Center schema (identifiers, brand, price, availability, image link, and so on), and Producthero — the platform Compartner's domain currently redirects to — does follow that Google Shopping feed convention for its own merchants. That said, we have no evidence confirming Compartner used the same format, and no way to verify field names, delimiters, encoding, or file-size limits specific to it.

Given this gap, we'd treat any Compartner feed specification found elsewhere with caution and confirm current requirements directly with the platform, or with whoever manages the integration, before building anything to spec.

Feedance can generate a merchant product feed in common industry formats — XML, CSV, or a Google Shopping-style schema — and host it at a stable URL a receiving platform can pull on a schedule, or you can export it manually. Since no Compartner-specific onboarding process is publicly documented, the steps below describe the general integration pattern rather than a confirmed, Compartner-verified procedure:

1. Create a feed in Feedance and map your catalog fields (title, price, brand, availability, image, identifiers) to a standard schema, since no Compartner-specific field list exists publicly.
2. Export the feed as XML or CSV, matching whichever format the receiving platform confirms it can ingest, and copy the hosted feed URL Feedance generates.
3. Submit that feed URL through the platform's merchant or retailer onboarding process. We could not find a public "become a retailer" or advertiser sign-up page for Compartner itself, so this step will likely require contacting the platform directly — or Producthero, given the domain redirect — to confirm whether merchant onboarding is still available at all.
4. Once (and if) a connection is live, use Feedance's scheduling to keep the feed refreshed automatically rather than re-uploading it by hand.

No Compartner-specific update-frequency requirement is publicly documented. As general good practice for any price- and availability-driven feed, a daily refresh is a reasonable default, with same-day pushes for stock-outs or price changes where the receiving platform supports near-real-time updates. Confirm the platform's actual pull or crawl frequency once a live integration exists, since we cannot state one with confidence here.

The following are general product-feed practices rather than confirmed Compartner requirements, offered because no platform-specific guidance could be found:

1. Use accurate GTINs/EANs and brand names — brand-organized catalogs and comparison sites rely heavily on correct brand and identifier matching.
2. Write descriptive, consistent titles that match how shoppers search by brand and model, which matters most for compatibility-driven categories like accessories and replacement parts.
3. Keep price and availability fields current so shoppers aren't sent to out-of-stock or mispriced listings.
4. Use clear, high-resolution primary images, since brand and category browsing pages typically lean on imagery to build shopper trust before a click-through.

Is Compartner still active? We could not confirm this. As of 2026, its main domain (compartner.nl) redirects entirely to producthero.com, and we found no independent Compartner site, merchant page, or documentation still online.

Is Compartner the same company as Producthero? We can't confirm this either way. The domain redirect is the only link we found; Producthero's own published company history does not mention Compartner by name.

What feed format does Feedance generate for this kind of integration? Feedance can output XML, CSV, or Google Shopping-style feeds. Use whichever format the receiving platform confirms it accepts, since no format is officially published for Compartner.

What should I do if I've been asked to integrate with Compartner specifically? Confirm with the requester, or with the platform directly, whether the integration is still live before building a dedicated feed — we found no current public onboarding path for merchants.