What’s new

You can now use Collections in Offsite Discovery, making it easy to include curated (and optionally personalized) collection results in offsite channels like email, SMS, and push.

• Choose a Collection as a content piece when building a notification campaign
• Combine collections and recommendation pods in the same campaign (up to 4 content pieces total — e.g., 4 collections, 4 pods, or 2 of each)
• Our reasoning engine automatically picks the best products within your chosen collection for every shopper
• Preview a campaign before you send it

💡 Why it matters

This unlocks new marketing and merchandising use cases beyond recommendations — teams can promote curated assortments (e.g., seasonal picks, sale edits, best-of lists) through offsite campaigns while still benefiting from Constructor’s ordering and personalization when a user identifier is available.

📍 Where to find it

In Offsite Discovery / Notification Campaigns, choose a Collection as the content source (instead of a recommendation pod) and use the generated snippet/API to render product cards in your email service provider (ESP).

Learn more / questions

• Newly created collections may take ~10–15 minutes to show results in the preview.
• You don’t need to build a new collection PLP on your site — campaigns generate PDP links and redirect shoppers there. (If you want a “View all” experience linking to a collection-specific PLP, you’ll need to create that page on your end.)
• If you have any questions or feedback, please connect with your Customer Success Manager or contact us through support@constructor.io.

We’ve added badge support to Recommendations, so shoppers can see the same high-signal labels directly on recommended items — creating a more connected experience across Search, Browse, Product details pages and Recommendations.

Why this is important

Badges are small visual labels that highlight key information about an item  and can encourage purchasing by making it easier for shoppers to decide what to click next.

What it unlocks for you

• A more consistent shopper journey: the same merchandising cues can show up across onsite touchpoints, so shoppers don’t lose decision signals when they move from Search/Browse into recommendation modules.
• Higher engagement with recommendations modules: badges help shoppers quickly identify standout items, which can translate into stronger interaction with recommendations.
• A scalable merchandising lever: once badges are configured, they update automatically over time.

If you’re interested in using badges in Recommendations, please connect with your Customer Success Manager — they can guide rollout and best practices.

We’ve released Image Search v2, which adds optional automatic image segmentation to Image Search. This lets shoppers upload a scene photo (for example, an outfit or a room) and get results for each detected item — instead of treating the whole image as a single query.

What’s enabled

• A new endpoint: POST >
• Optional segmentation mode (use_segmentation=true) that detects multiple objects in an image and searches each one
• Optional per-segment metadata in the response (return_segments=true) so clients can render selectable regions (bounding boxes / masks)
• Segment crop options: search_crop_type=bbox (default) or search_crop_type=segment (masked crop)

What it unlocks for you

• Multi-item discovery: Let shoppers go from “this whole photo” to “show me results for the jeans / shirt / shoes”.
• Better relevance on complex images: Reduced noise when the upload contains multiple products or background clutter.
• Stronger demo / evaluation flows: Make “shop from photo” experiences more interactive by letting users select what they mean within the image.

API docs

• Image Search v2 reference: https://docs.constructor.com/reference/v2-image-search-retrieve-search-results

If you have any questions or feedback, please connect with your Customer Success Manager.

We’ve enabled Product Details API endpoints that let customers fetch enriched information for items and variants, so PDPs can be powered by the same enrichment layer as the rest of the Constructor experience.

This is especially important for PDPs as it’s where shoppers make high-intent decisions. Having enriched signals available (instead of only on listing pages) makes the experience more consistent and easier to trust.

What’s enabled

• Retrieve enriched data by item
• Retrieve enriched data by variation
• Return enriched signals that customers can use to improve PDP UX (including badges)

What it unlocks for you

• Consistency: Badges and other enriched signals don’t disappear after a shopper clicks into a product.
• Cleaner integrations: A dedicated PDP-friendly retrieval path, instead of repurposing PLP responses.
• Better PDP storytelling: We’re especially excited about serving badges on PDP, so key signals can show up exactly where purchase decisions happen.

API docs

• Retrieve item product details: https://docs.constructor.com/reference/v1-product-details-get-items
• Retrieve variation product details: https://docs.constructor.com/reference/v1-product-details-get-variations

If you have any questions or feedback, please connect with your Customer Success Manager.

You can now paginate through Items and Variations with cursor-based pagination for more reliable, scalable listing - especially for large catalogs.

What’s new

• GET /v2/items and GET /v2/variations now support cursor-based pagination via next_page_cursor.
• Each response may return next_page_cursor; pass it in the next request to fetch the next page of results.

Why it matters

• More reliable pagination for large result sets (reduces offset-related gaps/duplication).
• Easier to build long-running or resumable export/audit workflows.

Common customer use cases

• Catalog audits / backfills: Iterate through the full catalog safely, without relying on offset math.
• Resumable scripts: Store the last cursor to resume processing after interruptions.
• Large-catalog integrations: Reduce risk of missed/duplicated entities when the underlying catalog is changing.

How to use it (high level)

• Make a request and read next_page_cursor from the response.
• Repeat requests with next_page_cursor until it’s empty/omitted.

Notes

• next_page_cursor can’t be combined with page or offset.
• When using cursor pagination, total_count is omitted.

Learn more about Retrieving Items

You can now export your catalog data from Constructor using the Tasks API. This gives your team a repeatable, self-serve way to generate an export file on demand and download it once it’s ready.

What’s new

• Create a Catalog Export task and get back a task ID.
• Check status and download the export file once it’s ready.

Why it matters

• Makes it easier to validate your catalog, troubleshoot issues, and share data with downstream systems.
• Gives you a self-serve way to generate exports without needing manual support.

Common customer use cases

• Catalog QA after an ingest change: Export items/variations and compare against your source feed to confirm the right fields are present and updated.
• Troubleshooting unexpected search/browse behavior: Pull an export to spot missing attributes, incorrect values, or out-of-date availability/pricing.
• Downstream processing / audits: Generate a point-in-time export to load into your own tools (data warehouse, scripts, BI) for analysis and reconciliation.
• Taxonomy review (item groups): Export item groups to review hierarchy structure and naming, and to validate updates before broader changes.

How to use it (high level)

• Create an export task → get a task ID.
• Check status until it’s DONE.
• Download the file using the returned URL.

Notes

• Only one export can be queued or running per ac_key at a time.
• Depending on what you’re exporting, you may need to provide both ac_key and section.

Learn more about Catalog Export API

At Constructor, we strive to give merchandisers transparent visibility into what drives performance - and with this update, rule performance analytics now show up right within the merchandising workflow in the Searchandizing Search and Browse tables, so you can spot underperforming rules and act faster.

With this update

• You can see Page Impact and Items Impact badges directly in the Searchandizing tables.
• The tables now surface key metrics like Pageviews, Purchase Rate, Purchases, and Revenue.
• Hover a badge for a quick overview of rules impact, or click to open a side panel with a full breakdown of the impact on clicks, add-to-carts, and purchases, as well as individual rule impact.

How to get started

1. In the dashboard, go to Searchandizing → Search (or Searchandizing → Browse).
2. Find the Rule Impact column and review the impact badges.
3. Hover a badge to see a quick summary, or click it to open the detailed impact panel.

Learn more about manual rules impact

If you have any questions or feedback, please connect with your Customer Success Manager.

Keeping your catalog clean is hard when it’s built from multiple upstream sources—products can disappear upstream but still linger in Constructor. Whitelist Action gives you a fast way to clean up stale catalog data by telling Constructor what to keep.

With this update:

• Upload a keep-list of item, variation, and/or item group IDs.
• Anything not on the list is removed, so you can do a “keep this set, drop the rest” cleanup without a full feed re-upload.
• Supports CSV, JSON, JSONL, and .tar bundles containing any mix of supported files (items, variations, item groups).
• Includes built-in safety checks to help prevent accidental large deletions (override available for intentional large cleanups).

How to get started

• Supported entity types: items, variations, and item groups.
• File formats: CSV, JSON, JSONL, or a .tar bundle containing any mix of supported files.
• Built-in deletion safeguards: by default, Whitelist Action won’t delete more than 50% of a catalog in a single run (override available).
• Cascade rules: deleting items also deletes their variations; deleting item groups validates that the tree structure won’t break.
• Payload requirement: whitelist payloads must include only ID fields; extra fields will error.
• Override option: override the failsafe threshold with the forcewhitelist keyword (use with caution).

📓 Links to additional documentation

Catalog upload operations, Create or replace catalog. 

Merchandising Recommendations just got a big upgrade: you can now benefit from the same powerful set of preview and rule capabilities that you know and love in Search and Browse.

With this update

• Preview pods with full context controls:
  • Use Impersonate to preview pod experience for a particular segment of shoppers.
  • View Changes explicitly communicates the impact of boost and bury rules.
  • Select Attributes to be displayed on product tiles.
• Use the affecting rules dropdown to see which rules are already impacting the pod’s shopping experience before creating new ones.
• More controls to curate pod experience:
  • Use Ranged Slotting to keep a curated set of items within a position window while still letting ranking optimize the exact products and order inside that range. Learn more
  • Use Variation Slicing with filters to control which variations appear based on explicit conditions. Learn more
  • Use drag-and-drop slotting from the carousel to quickly create slot rules.
• Move faster with import/export: Download a CSV of your variation-level slotting rules, edit in bulk, then upload it back — ideal for large promos, quick iterations, and sharing setups without manual clicking. Learn more

How to get started

1. Go to Recommendations → Rules.
2. Open an existing campaign (or create a new one).
3. In preview, you will find the updated merchandising toolkit:
   • Affecting rules
   • Segment impersonation
   • View changes
   • Attributes on product tiles
   • Ranged Slotting
   • Variation Slicing with filters
   • CSV Item Variation Slotting import/export

If you have any questions, please connect with your Customer Success Manager or contact us through support@constructor.io.

Merchandising calendars move fast — and updating collections by hand at the right time can be challenging, especially early in the mornings or on weekends. The new Scheduled Item Sets feature lets you plan item rotations in advance, while keeping a single stable collection.

With this update you can:

• Create multiple time-bound item sets inside a single collection (with optional start/end dates).
• Automatically serve the right items without creating separate collections per promo window.

How to get started

We will gradually roll out Scheduled Item Sets over the coming weeks. If you would like early access, please reach out to your Customer Success Manager.

1. Go to Searchandizing → Collections.
2. Open a collection.
3. In Scheduled Item Sets dropdown at the top right, click Create new scheduled item set.
4. Add items (item IDs, .csv, or conditions) and optionally set a Start/End date.

Note: Updates are evaluated on a short interval, so an item set scheduled for a specific time may activate/deactivate within up to 2 minutes after the scheduled time.

If you have any questions or feedback, please connect with your Customer Success Manager or contact us through support@constructor.io.