Lyst Integration

Lyst only sells products it can market and check out with confidence, which means a clean, well-structured product feed is the entry ticket to visibility, not just a technical formality.

1. Large, high-intent audience: Lyst reports a 4.64% conversion rate on its own platform, which it states is roughly 3x a typical affiliate-referral average, backed by average order values ranging from around $108 (contemporary) to $404 (premium) to $1,085 (luxury), depending on category tier.
2. No upfront listing cost: Lyst's partner program is explicitly performance-based, with no listing fees — retailers only pay when a sale actually happens through the platform.
3. Retailer keeps pricing control: Lyst's own partner materials state "No Discounting Required" — brands and retailers are not forced to discount to be listed or to rank well.
4. Ranking rewards good data: Lyst's published ranking system explicitly scores listings on Relevancy, Popularity, Conversion, Value and Personalisation — several of which (relevancy, conversion, value) are driven directly by how complete and accurate the underlying feed data is.

Lyst operates on a commission (revenue-share) model rather than a flat listing fee. Lyst's own retailer contract for its Magento integration channel discloses the mechanic concretely: the retailer chooses at sign-up between Lyst taking 16% of "Sales Before Returns" or 20% of "Sales After Returns," with the remaining "Merchant Share" paid out to the retailer's connected Stripe account at the time of each order. This example shows how the model is structured; the exact rate offered to any given retailer today is individually negotiated as part of onboarding and can vary by category and channel.

Commission isn't just a payment mechanic — Lyst's published ranking methodology states that the commission rate directly feeds into the "Value" score used to rank products in search results, alongside relevancy, popularity, conversion likelihood, and personalisation. In other words, the commission a retailer agrees to can influence how often its products are shown.

Lyst does not onboard retailers through a manual product upload screen — its documented partner journey runs through a technical integration step described on Lyst's own partners page as "catalog synchronization" via API, with a dedicated block of the onboarding timeline (days 4–12 of a roughly two-week rollout) reserved for "product feed connection" and payment setup through Stripe.

Lyst's Magento retailer agreement is explicit about what data it needs access to via that connection: GTINs (where available — Lyst's contract defines a GTIN as the 14-digit unique product identifier), product types, product names, product images, product descriptions, sizes, inventory, current retail prices, and delivery/shipping options by country. Feed-management partners that build direct Lyst connections, such as Mulwi, generate the outbound file in CSV format. Feedance maps your existing catalog data (Shopify, WooCommerce, PrestaShop, custom PIM, etc.) to this same schema so nothing has to be built or maintained by hand.

Based on Lyst's own retailer contract terms and the field-level guidance published by Lyst's feed-integration partners, the following attributes are the core building blocks of a workable Lyst feed:

1. Connect your store or PIM to Feedance so your full catalog — titles, descriptions, GTINs, images, prices, sizes, stock and shipping data — is available in one place.
2. Feedance maps your fields to the attributes Lyst's retailer agreement asks for (product type, name, images, description, sizes, inventory, current retail price, and delivery/shipping options by country), filling in size_system and GTIN gaps wherever your source data allows.
3. Feedance generates and hosts the connected feed so it lines up with the "product feed connection" step of Lyst's own onboarding timeline, ready for Lyst's technical/QA review.
4. Once Lyst approves the connection and your Stripe payment setup is complete (per Lyst's documented onboarding flow), Feedance keeps price, stock and size data continuously synced so listings stay accurate after launch — without manual re-exports.
5. Feedance surfaces feed-level warnings (missing GTIN, missing size_system, missing images) before they can turn into rejected listings or failed checkouts on Lyst.

Lyst's own retailer contract sets a real contractual floor here: retailers must notify Lyst at least one week in advance of changes to shipping/delivery/policy data, and must push through any actual data changes "as soon as reasonably practicable" after they happen. That obligation exists because Lyst's checkout is a live transaction, not a click-through referral — Lyst's Integrated Checkout Service processes payment on Lyst itself, so out-of-date stock or price data can turn directly into a failed order rather than just a bad click.

Lyst doesn't publish a single universal sync interval, so Feedance's practical recommendation is to sync inventory and pricing at least daily, and ideally in near real time for high-velocity SKUs, precisely because Conversion and Value — two of Lyst's five published ranking factors — are scored partly on how reliably a listed product can actually be bought.

Lyst does not publish a Google Merchant Center-style catalog of feed disapproval codes, but two real, verifiable failure patterns are worth building checks around:

1. Missing or incomplete size data: listings without size and size_system data are excluded from Lyst's filtered size search and, per Lyst's own feed guidance, measurably convert worse.
2. Missing GTIN: Lyst's retailer contract asks for GTINs "where available" specifically because they're used to identify products reliably; feeds that omit them weaken matching and can dilute relevancy scoring.
3. Stock and price drift: because Lyst completes checkout itself via Stripe/Klarna rather than redirecting to the retailer's site, a product that goes out of stock or changes price between the last feed sync and the moment of purchase is a documented cause of orders failing after the customer has already paid.

Keeping the feed continuously synced through Feedance is the most direct way to avoid all three.

1. Populate size and size_system on every variant — Lyst's own data ties this pair of fields to a measurable, double-digit-relevant conversion lift (6.3%).
2. Supply 4–8 images per product, the range recommended by Lyst's feed-integration partners, to support both relevancy and conversion scoring.
3. Fill in GTINs wherever your source system has them — Lyst's contract asks for them specifically "where available," implying they materially help identification and matching.
4. Keep product type/category, brand and price fields complete and current — all three are named directly in Lyst's published ranking factors (Relevancy and Value).
5. Treat your negotiated commission rate as a ranking lever, not just a cost line — Lyst states commission feeds directly into the Value score used in ranking.
6. Prioritize real-time stock and price sync over batch updates, since Lyst's checkout completes the purchase itself rather than referring the shopper onward.

Is there a fee just to list products on Lyst?
No. Lyst's partner program is explicitly performance-based with no listing fees — retailers pay only when a sale is made through the platform.

How is Lyst's commission calculated?
As a percentage of the order value, individually negotiated per retailer. Lyst's own retailer contract for its Magento channel discloses a concrete example: 16% of Sales Before Returns or 20% of Sales After Returns, chosen by the retailer at sign-up.

How long does onboarding to Lyst take?
Lyst's own partners page documents a roughly two-week process: days 1–3 for scoping and API access, days 4–12 for product feed connection, Stripe payment setup and testing, and days 13–14 for final QA and launch.

Do I lose control of my pricing on Lyst?
No. Lyst's partner materials state "No Discounting Required" — pricing control stays with the retailer.

Why would an order fail after a customer pays on Lyst?
Because Lyst's Integrated Checkout Service completes the transaction itself rather than redirecting to the retailer's site, stock or price data that has gone stale since the last feed sync is a real, documented cause of post-payment order failures — which is why keeping the feed continuously synced matters more on Lyst than on a simple click-through channel.