Hopi Integration

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.

1. If your goal is running cashback/discount campaigns through the Hopi app, you need the checkout-level code integration described above — this is coordinated directly with Hopi's partnership team and your POS/e-commerce provider, not a feed.
2. If your goal is listing and selling products inside Hopishop, that's the feed-relevant integration, and it works like a standard marketplace product upload.

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:

1. Manual or bulk product management inside the Hopishop seller panel, including downloadable template files for bulk product creation, price updates and stock updates.
2. Integration through e-commerce/ERP platforms that already have a Hopishop connector (examples cited by integrators include Ticimax, T-Soft and StockMount), which handle category matching and product transfer on the merchant's behalf.
3. Custom ERP-to-Hopishop XML generation, as seen in independently published integration tooling that matches products between an ERP system and Hopishop before submitting them.

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.

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:

1. Confirm your Hopishop merchant/seller account status and obtain your current delivery method and credentials directly from Hopishop merchant support.
2. Identify the current required fields and delivery format (panel upload template, ERP-connector format, or XML) for your account, since this has not been standardized in public documentation.
3. Connect your master product catalog — from your storefront, ERP, or existing feed — to Feedance as the single source of truth.
4. Map your catalog's fields to the attributes Hopishop currently expects (name, category, product code, barcode, brand, variant data, price, VAT, stock, shipping company, delivery timeframe, images), adjusting for any panel-specific requirements you confirmed in step 2.
5. Generate the output in the format your Hopishop connection actually consumes, and validate a small batch of listings before pushing your full catalog.
6. Automate recurring updates so price and stock changes on your side reach Hopishop without manual re-uploads.

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:

1. Category mismatch: products mapped to the wrong or an unsupported Hopishop category are a commonly cited cause of listing and matching failures during integration setup.
2. Missing mandatory fields: listings lacking a required field such as barcode, VAT rate, shipping company or delivery timeframe are typically rejected or left incomplete in the seller panel.
3. Variant data gaps: variant products missing per-variant images, price or stock entries commonly fail to display correctly on variant-based listings.
4. Stale credentials: since Hopishop API access is issued manually by merchant support rather than self-service, expired or misconfigured access tokens are a recurring integration blocker reported by third-party connectors.

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:

1. Keep product titles clear and attribute-rich (brand, model, key spec) rather than promotional, since marketplace search and category placement typically reward descriptive titles over marketing copy.
2. Assign the most specific matching category available rather than a broad parent category, to reduce the listing and matching errors integrators consistently flag as the top cause of marketplace upload problems.
3. Keep barcode and product code values stable and unique across updates — these are the keys most bulk-update and integrator tools use to match your existing listings.
4. Sync stock and price at least daily, and faster for limited or fast-moving inventory, to avoid orders on unavailable stock.
5. Supply complete variant-level data (images, price, stock) for every size/color combination rather than only the parent product, since incomplete variants are a common source of listing display issues.

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.