A catalog with a performance signal on every product
Hopi reads your products from the feed. Feedance sends a complete, valid feed plus the signals Hopi does not have on its own.
HopiChannel · Marketplaces and appsFeedance builds your Hopi feed and adds product-level labels for score, 4T segment, price position and broken sizes, so every product carries its own performance signal.
Hopi reads your products from the feed. Feedance sends a complete, valid feed plus the signals Hopi does not have on its own.
Hopi is a Turkish mobile loyalty and cashback app with more than 12.6 million members and partnerships with over 250 brands across fashion, grocery, food, travel, technology and other sectors. Shoppers earn Paracık — Hopi's reward currency, where 1 Paracık equals 1 Turkish lira — every time they shop at a partner brand and show their Hopi QR code at checkout, either in-store or online. Those Paracık balances can then be spent on future purchases at any partner brand, with no minimum basket size, until they expire at the end of the calendar month marking one year from when they were earned.
In 2021 Hopi also launched Hopishop, a marketplace layer inside the app where partner brands list products directly for browsing and purchase, similar in structure to other Turkish marketplaces such as Trendyol or Hepsiburada. This distinction matters for feed management: Hopi's core loyalty mechanic runs on transaction-level code integration rather than a product catalog, while Hopishop is the part of the ecosystem that actually consumes structured product data.
For brands selling through Hopishop, a clean and current product feed determines whether items are even visible to the app's member base browsing deals and offers, and whether prices, stock and variant data are accurate at the point of purchase. Because Hopishop listings sit inside an app millions of people already open to check cashback offers, keeping product data synced reduces the chance of orders coming in for items that are out of stock, mispriced, or miscategorized — issues that surface quickly on a marketplace with automated invoicing and shipping-label generation tied to order data.
It's worth being explicit about a distinction that trips up a lot of merchants: connecting to "Hopi" for cashback campaigns is a different integration than connecting a product feed to Hopishop. Hopi's own documentation describes brand partnerships as a code integration process — Hopi's team, the brand's team, and the brand's POS, e-commerce and ERP software providers coordinate to wire a campaign code into the checkout flow so that Paracık is awarded and redeemed correctly. Sales tracking for these campaigns runs through affiliate-style reporting and UTM-tagged links, not a product catalog.
Feedance is relevant to the second case. If you're unsure which applies to your business, that's a question for your Hopi account manager before any feed work begins.
Hopi has not published a public, self-serve feed specification (no open XML/JSON schema, developer portal, or field-level documentation was found for Hopishop, in either Turkish or English). In practice, based on seller-panel guides and third-party integrator documentation, merchants connect to Hopishop in one of a few ways:
API credentials (an access token) for Hopishop are obtained directly from Hopishop merchant support rather than through open self-registration. Because there is no published spec to build against with certainty, the practical approach is to confirm the current field requirements and delivery method with your Hopishop account contact, then map your source catalog to that format — which is exactly the kind of mapping work Feedance is built to handle once the target fields are known.
Hopi has not published an official attribute-level feed specification. The attributes below come from a detailed third-party walkthrough of the actual Hopishop seller panel's single-product and bulk-upload forms, not from an official Hopi developer document — treat them as a reliable starting point rather than a guaranteed current spec, and confirm against your own seller panel before mapping a feed.
| Attribute | Notes |
|---|---|
Product name | Required on both single and bulk product creation |
Category | Required; incorrect category matching is a common source of listing problems on Turkish marketplaces generally |
Product code | Merchant's internal SKU, required for bulk price and stock updates |
Barcode | Required |
Brand | Required |
Size / variant attributes | Required for variant products, each with its own images, price and stock |
Sales price | Required; set independently per variant where applicable |
VAT rate | Required |
Stock quantity | Required; set independently per variant where applicable |
Shipping company | Required |
Delivery timeframe | Required |
Product images | Required; separate images per variant where applicable |
Because Hopishop doesn't offer an open, universally documented feed format, connecting it through Feedance is a coordination-plus-mapping process rather than a one-click template:
Hopi has not published a required or recommended update cadence for Hopishop. Third-party integrators describe stock levels as being "kept current" through connected accounting/ERP systems and sales being reported back daily, which suggests at least daily synchronization is standard practice among sellers using automated connectors. As general e-commerce practice, price and stock should sync at least daily — and ideally in near real time for fast-moving or limited-stock items — since a marketplace listing showing incorrect availability or price directly risks order cancellations and support overhead.
No Hopi-specific, publicly documented list of Hopishop error messages or rejection codes was found. The issues below are general marketplace-integration patterns noted across Turkish e-commerce integrators working with Hopishop and comparable marketplaces — use them as a checklist, not as verified Hopi error text:
If you encounter an error message not covered here, the most reliable path is confirming its meaning directly with Hopishop merchant support, since Hopi does not publish a public error-code reference.
These are general marketplace feed best practices, not Hopi-specific requirements:
Is Hopi the same thing as Hopishop?
No. Hopi is the loyalty/cashback app built around Paracık rewards and brand campaign codes; Hopishop is a marketplace feature inside the Hopi app, launched in 2021, where partner brands list and sell products directly. Feed management applies to Hopishop, not to Hopi's cashback campaign mechanic.
Does Hopi publish a public product feed API?
Not that could be verified. There is no public developer portal or open feed specification for Hopishop; credentials and integration details are obtained directly from Hopishop merchant support, and many sellers integrate through e-commerce/ERP platforms that already have a Hopishop connector.
Do I need a registered company to sell on Hopishop?
Yes — like other Turkish marketplaces, Hopishop requires a tax-registered company that can issue invoices; opening a store itself is free, based on merchant guidance published by third-party integrators.
Can Feedance generate a Hopishop-ready feed automatically without any setup?
Not out of the box, because Hopishop has no fixed public spec. Feedance can map and automate your feed once you've confirmed the current field and delivery requirements with Hopishop merchant support, and then keep that feed synchronized going forward.
What's the single most useful thing to fix before connecting a Hopishop feed?
Get your category mapping right first. Incorrect category assignment is the most frequently cited cause of marketplace listing problems in integrator documentation, and it affects everything downstream — visibility, search placement, and required attribute sets.
Hopi is a Turkish mobile loyalty and cashback app. Members collect Paracık, Hopi's reward currency, when they shop at partner brands in stores or online, and can spend it on later purchases with any partner brand. The app works with brands across fashion, grocery, food, travel, technology and other sectors.
Hopi also runs Hopishop, a marketplace inside the app where partner brands list products that members can browse and buy. This is the part of Hopi that uses product data. Joining Hopi's cashback campaigns is a separate integration that connects a brand's checkout and point-of-sale systems with Hopi, and it does not require a product feed.
Hopi has not published a public feed specification for Hopishop. Merchants usually manage products through the Hopishop seller panel with bulk upload templates, through e-commerce or ERP platforms that offer a Hopishop connector, or through custom XML integrations arranged with Hopishop support, which also provides API credentials.
For sellers on Hopishop, accurate product data keeps the in-app shop reliable. Correct product names, categories, barcodes, brand and variant data, images, prices and stock levels help members find products and reduce orders for items that are out of stock or wrongly priced.
Connect your feed and GA4. We show Product Score, 4T, Price War and Broken Size on your own catalog.