Get Listing Products

This tutorial explains how the Get Listing Products process works for the Trendyol integration in the Marketplace Dashboard.

For channel-level setup (feature flags, category mapping, failed integration rules, etc.), see Trendyol Marketplace Setup Configurations tutorial.

This flow runs in the opposite direction from Product Insert and Product Update: instead of sending Omnitron data to Trendyol, it reads Trendyol's own approved-product list and uses it to fill in or correct the corresponding product's data in Omnitron.

What is Get Listing Products?

When a product is sent through Product Insert, Trendyol doesn't make it sellable immediately — it first goes through Trendyol's own approval process. Product Insert itself doesn't wait around for that approval to finish; it only logs a product as a real success once it's approved (see Approval Is Required for a Real Success).

Get Listing Products is what closes that loop. It periodically pulls the list of product variants that Trendyol has already approved but not yet marked as on sale, matches each one to its corresponding product in Omnitron by SKU, and makes sure that product carries Trendyol's content ID — the identifier Trendyol uses to know which listing an update request refers to. If that identifier is missing or out of date on the Omnitron side, this flow fills it in.

When Does It Run?

• Unlike the other Trendyol flows, this one has no feature flag — it always runs automatically, on a fixed schedule of every 2 hours. It cannot be disabled from the channel settings.
• Each run looks back 7 days from Trendyol's variant-approval date by default.
• It can also be run for a specific date range or a specific list of barcodes, for a targeted re-sync instead of the rolling 7-day window.
• Runs are not overlapped: if a previous run of this flow is still in progress when the next scheduled run is due, the new run waits for the running one to finish before it starts.

Which Products Are Matched?

A Trendyol variant is picked up if it is:

• Approved on Trendyol.
• Not yet marked as on sale (Trendyol's notOnSale status) — once a product is fully reflected as on sale, it drops out of this list.

For each variant, Omnitron is searched for the matching product using its SKU by default. If the channel has a custom StockCode attribute configured in Omnitron, that attribute is used to match instead.

Fetching Approved Products from Trendyol

Approved-but-not-yet-on-sale variants are fetched page by page:

GET {mp_host}/product/sellers/{supplierId}/products/approved
    ?status=notOnSale
    &size=100
    &dateQueryType=VARIANT_CREATED_DATE
    &startDate={start_date}
    &endDate={end_date}

All pages are collected before the results are processed further.

Matching and Updating Omnitron

For each returned variant:

1. Its stock code is used to find the matching product in Omnitron.
2. If no matching product is found, the variant is logged as failed and skipped.
3. If a match is found:

   • If the product doesn't yet have Trendyol's content ID stored, it is added, using the contentId Trendyol returned for that variant.
   • If the product already has both, it's already in sync and nothing changes.

How the Process Works — Summary

1. Trendyol's approved-but-not-yet-on-sale variants are fetched for the configured date range (or the default rolling 7-day window).
2. Each variant is matched to its Omnitron product by SKU or a configured custom attribute.
3. Unmatched variants are logged as failed.
4. Matched products that are missing Trendyol's content ID have that information filled in.
5. Products that are already fully in sync are skipped without a separate log entry.
6. The outcome of every variant becomes visible on the Logs screen.

Monitoring

1. From the left menu, go to Trendyol > Marketplace Operations > Logs.
2. Filter by flow name Get Listing Products.
3. Use the SKU or Execution ID filters to locate a specific product.

This flow does not use the numbered error codes used by Product Insert/Update — a failed line simply carries Trendyol's or Omnitron's raw error response. Click the ResponseData box on a failed log row to see the underlying reason (e.g. the product genuinely could not be found in Omnitron).

Related Settings

• Mapper — if products are matched via a custom Omnitron attribute instead of SKU, that mapping is defined the same way as in Product Insert/Product Update.
• A custom StockCode attribute in Omnitron, if defined for the channel, changes the field this flow uses to match a Trendyol variant to its Omnitron product.