What's new

You can now target customer-defined user segments across most searchandising rules—not just Boost & Bury. That means you can adjust ranking, recall, content, and slotting for specific audiences (e.g., "US App Users", "Loyalty Tier Gold", "Clicked Meta Ad A") without rebuilding pages or bluntly applying rules to everyone.

You can now

• Apply segments to key rules and surfaces
  • Boost & Bury — Search, Browse, Campaigns, Recommendations, Global
  • Item Slotting (incl. CSV & faceted browse) — Search, Browse, Campaigns, Recommendations
  • Attribute-based Slotting — Search, Browse, Campaigns, Recommendations
  • Allowlist / Blocklist — Search, Browse, Campaigns, Recommendations (Blocklist also on Global)
  • Content Rules — Search, Browse, Campaigns
• Preview as a segment when creating Campaigns: Impersonate a selected segment to see exactly what that audience will experience before you ship.

Why it matters

Previously, segments were available for Boost & Bury only. Teams either ignored insights or applied broad rules to all shoppers, diluting performance. With segments available across your core rule types, you can:

• Tune the same PLP differently per audience (locale, device, lifecycle stage).
• Move faster from marketing signal to on-site personalisation without duplicating pages.
• Protect performance by narrowing rules to only the shoppers they're meant for.

Example workflows

• Campaign continuity: For users who clicked a specific ad or email, slot the exact products that match the message they saw, right on arrival.
• Locale nuance: Slot a colorway or size range for only a particular country/segment without touching other markets.
• Compliance fast-track: Blocklist prohibited items for a single region while keeping them live elsewhere.
• Channel-aware content: Show different banners/copy to app users vs web visitors on the same PLP.

Who benefits

• Merchandisers partnering with Marketing: align landing experiences to campaign promises.
• Region/brand owners: tailor assortment and messaging by locale without forking your catalog.
• Compliance & ops teams: react quickly to region-specific restrictions.

Coming soon

• AI-generated segments
• Segments in Content Rules (Global)
• Segments in Variation Slicing
• Impersonation for Search, Browse, and Global

Learn more

• Configure searchandising rules
• Create a searchandising campaign

To learn more, please contact your Customer Success Manager or support team.

What’s new

We’ve supercharged Collections so merchandisers can build, reuse, and refine PLPs with fewer clicks.

You can now

• Export item IDs to CSV from a Collection in one click—for analysis or to seed a new Collection.
• Add, edit, and remove item IDs inline in the Collections UI—no extra CSV wrangling required.
• Copy a Collection across indexes or within the same index—reuse successful setups with minor tweaks.

Why it matters

Previously, small changes took a big effort—exporting item IDs required workarounds, editing meant creating and re-uploading CSVs, and reusing a Collection often meant rebuilding from scratch.

Now you can:

• Move faster from idea to live PLP.
• Keep Collections fresh with quick, precise Item ID updates.
• Replicate proven merchandising strategies across storefronts without busywork.

Example workflows

• Re-launch a winning PLP in a new market: Copy the Collection to another index, adjust a few IDs inline, and publish.
• Clear handoff material: Provide item ID CSVs for cross-team reviews, ensuring everyone’s working from the same list.
• Tweak on the fly: Paste a handful of new item IDs straight from a spreadsheet and remove outdated ones in seconds.

Learn more

• Create a Collection
• Manage a Collection

Introducing Online LLM Burying Models—a new AI-powered enhancement that makes your search results cleaner, sharper, and more relevant in real time.

Our system now analyses each query as it happens, identifying and removing the least relevant results on the fly. Unlike the previous offline model, which could only filter precomputed query–item pairs, this new online model works on every search call, ensuring consistent precision across your entire catalog.

Benefits include:

• Higher precision: Irrelevant or misleading products are automatically detected and pushed down or removed.
• Smarter intent understanding: The model interprets the true meaning of each query to deliver more accurate matches.
• Improved search quality: Cleaner and more relevant results help users find what they need faster.

This update strengthens your search engine’s ability to interpret intent and deliver only the most meaningful results, helping shoppers find exactly what they’re looking for with confidence.

This enhancement is now available in AB test to all our customers.

To learn more, please contact your Customer Success Manager or support team.

We are excited to announce the general availability of Customizable User Roles with View/Edit permissions. This powerful new capability is now live in the Constructor dashboard for all customers. 

This feature allows enterprise e-commerce companies to provide every member of their team with tailored access, ensuring they have exactly the tools they need to excel—without compromising security or control.

The Challenge: Scaling Operations Securely

As an e-commerce business scales, more teams rely on a central platform for daily tasks. The Merchandising team fine-tunes results across the product discover journey, the Marketing team builds campaign-specific collections, and the Development team manages integrations and indexes. Each team has a unique focus, and providing one-size-fits-all access can create bottlenecks and introduce the risk of accidental changes to critical settings.

The Solution: Granular Control, Tailored for Your Business

Customizable User Roles solve this challenge by providing precise control over what each user can do. This functionality allows you to:

• Safeguard Critical Settings: Protect company-level information, such as API tokens and user management, by restricting access to only designated administrators. 
• Isolate Access by Index: Assign users to specific indexes, making it perfect for managing different regions, websites, or environments (e.g., Staging vs. Production) without overlap. 
• Assign Feature-Specific Permissions: Grant Edit permissions for individual features. Empower your merchandisers to manage Searchandising and Facets while restricting access to A/B Testing or Recommendations for designated roles. 
• Promote Data-Driven Decisions with View-Only Access: Create view-only roles for executives, analysts, and other stakeholders. This allows them to access valuable performance reports and analytics without the ability to make changes. 

Putting Roles into Practice 

With this level of control, you can create highly specific roles that map directly to your operational structure: 

• The Digital Merchandiser (B2B): Gets Edit access to Searchandising, Facets , Collections, A/B Testing, and Global Facet Configuration for the B2B website index, but has View access everywhere else. 
• The Marketing Specialist: Can only Edit the Collections feature to prepare for an upcoming email campaign. 
• The Regional Manager (EU): Has View access to global indexes but can only Edit merchandising rules for the eu_site index. 
• The Developer: Is given Edit access to the staging_index to test a new integration but has only View access to the production environment.

How to Get Started

This feature is now available in your dashboard. Administrators can begin creating and assigning roles today by clicking on their name in the bottom left corner, then Team Members, then switch to the User Roles tab. For a detailed walkthrough on creating roles and assigning permissions, please visit our documentation guide.

If you have any questions or feedback on the new feature or the Constructor dashboard in general, please connect with your Customer Success Manager or contact us through support@constructor.io.

We’re excited to introduce the Continuous Optimization Report in your Constructor dashboard. This report gives you full visibility into how Constructor’s tailored Continuous Optimization Plan drives measurable revenue impact for your business.

💡 What is the benefit?

Constructor has always taken a unique approach to delivering value – not through one-size-fits-all algorithms, but by tailoring search and discovery variants to each customer’s goals and shopper behavior. Until now, these results were shared mainly in your touchpoints with our Customer Success and Data Science teams. With the Continuous Optimization Report, you can now track how experiments are generating value to your business directly in your dashboard, ensuring transparency and confidence in the ROI Constructor delivers.

📍 Where to find it?

You can access the Continuous Optimization Report in your dashboard by selecting Optimization from the side menu. There you’ll see the combined annualized revenue lift from completed experiments, a list of experiments with details like revenue lift, annualized projections, and important context about each experiment's hypothesis. Click any experiment to see its setup, metrics, and outcomes – all in one place!

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

We know many of you have been waiting for this one — and we’re excited to share it’s finally here!

We're introducing Merchandised Page Performance (MPP) — a brand-new report that finally gives merchandisers the data to prove when manual ranking rules are helping or hurting business metrics.

Until now, rules were a bit of a black box. You could push a product up or bury something you didn’t want to show, but measuring the impact was tricky. Were these rules actually helping your business goals? 

Besides unresolved questions, merchandisers have struggled to show stakeholders whether manual merchandising decisions — like boosting new arrivals, slotting hero products, or burying poor performers — were driving results or dragging down conversion. 

With Merchandised Page Performance, you don’t have to guess anymore. The report shows:

• All pages with active manual ranking rules in one place (search, category, collections, facet pages).
• Before-and-after performance (7-day windows) for the page overall (Page Impact) and for the items affected (Items Impact).
• Easy-to-read suggestions (our little lightbulbs 💡) telling you when a rule might be helping, hurting, or ready to retire.

Here’s how customers are already using it:

• When they launch a new set of rules, they monitor the report daily for the first week to see how things are progressing.
• As a go-to tool to clean up and remove rules that no longer serve their needs.

This means less manual effort, faster insights, and more confidence that every merchandising decision is helping you hit your targets.

You can find Merchandised Page Performance today in your dashboard under:

 Analytics → Rule Performance → Merchandised Page Performance

We’re thrilled to see how you’ll use it to fine-tune your strategy. And this is just the beginning — we’re already working on making the report more granular (down to individual rules), faster  and even more powerful.

📖 Learn more in our documentation.

We’re excited to announce a new capability that makes it much easier to manage time-sensitive changes in your catalog: Metadata Overrides.

Until now, if you wanted an attribute like price to change at a specific time (for example, to match the start of a sale at exactly 9pm ET), you had to carefully time your ingestion and indexing. That was always a hassle, especially when marketing campaigns needed precise alignment with communications.

With Metadata Overrides, you can plan ahead. You simply ingest future values in advance (e.g. price_october_campaign) and then configure them to automatically override the main field (price) at the exact date and time you choose. During that window, Constructor will serve the override value in all relevant APIs (Search, Browse, Autosuggest), and once the window ends, it will automatically fall back to the original field.

💡 How it helps

• No more late-night ingestions: Set it once, and the switch happens at the exact time you want.
• Perfect campaign alignment: Prices, badges, and other metadata can flip in sync with marketing messages.
• Reliable rules: Filtering, sorting and searchandizing rules will respect the override values, so everything behaves as if the new value was the original.
  
  

🧩 How to use it

1. Ingest your future fields in advance
   
   

   • Add additional fields in your feed that hold future values (e.g. price_october_campaign, promo_price_q4, black_friday_visibility).
   • These should mirror the structure of your main fields and be in the same metadata section.
     
     

{

  "id": "coffee_machine",

  "facets": {

    "price": 10,

    "price_october_campaign": 5

  }

}

1. Configure override rules
   
   

   • Use the Metadata Override APIs to tell Constructor when to swap fields.
   • Example: from Oct 1st 9pm UTC until Oct 7th 11:59pm UTC, use price_october_campaign instead of price.
     
     

{

  "field_name": "price",

  "field_path_in_metadata": "facets.price",

  "rules": [

    {

      "start_time": "2025-10-01T21:00:00Z",

      "end_time": "2025-10-07T23:59:59Z",

      "replaced_field_name": "price_october_campaign",

      "replaced_field_path_in_metadata": "facets.price_october_campaign"

    }

  ]

}

1. Constructor takes care of the rest

   • During the configured window, all API responses will return the override value.
   • Once the window expires, the original value is automatically restored.
     
     

🔗 API Reference

• Summary page Metadata Overrides
• GET Metadata Overrides 
• POST Metadata Override 
• PATCH Metadata Override 
• DELETE Metadata Override 

ℹ️ Limitations / Information to note

• Supports Search, Browse and Autosuggest for now, Recommendation support is coming soon.
• Up to 5 override rules per catalog key.
• Only one active override per field per time window.
• Overrideable fields need to be ingested and configured at least a week before the campaign start date.
• If an override field is missing for an item, the system will return the original field value.
• Start & end time values must be formatted as an ISO date & time string, with a timezone UTC offset at the end (yyyy-MM-dd hh:mm:ss.SSS±hh:mm). An entry with a missing timezone specification is assumed to be UTC.

✅ What to do next

• Start including override fields (e.g. price_october_campaign, promo_price_q4, etc.) in your feeds now.
• Configure rules via the new Metadata Overrides APIs.

• Once configured, you can test results using the `now` parameter. It allows you to override the desired time with a specific timestamp.

  • For example, to search for "cookies" and see the results as if the query was being executed on May first at one minute past midnight:

    • https://ac.cnstrc.com/search/cookies?key=[API key]&now=1651388460
    • The now parameter requires a Unix epoch timestamp
    • This query requires an API token in addition to an API key
    • Setting a now parameter can only be set to future times
• Rules will come into effect automatically at the exact times you need.
  
  

👉 This feature removes the headache of timing ingestions and gives you reliable control over campaign/sales related changes.

Constructor now supports Directed Acyclic Graphs (DAGs) for category hierarchies—making it easier to model real-world structures where a single category belongs to multiple sections.

Instead of duplicating categories like “Wireless Headphones” to appear in both "Electronics" and "Gifts," you can now assign multiple parent paths and control which one is shown based on where the shopper is navigating from.

Benefits include:

• Cleaner catalog setup with no duplication of categories
• Flexible hierarchy modeling that reflects real-world relationships
• Better navigation control using query-time path selection

This enhancement also introduces a new groups_path parameter that lets you specify which path to render during browse requests. This results in more precise breadcrumbs and a better contextual experience for shoppers.

🔧 Example Use Case
 A single category, like Wireless Headphones, can appear under:

• Electronics > Audio > Headphones > Wireless Headphones
• Gifts > Tech Gifts > Audio > Wireless Headphones

If no groups_path is passed during a browse request, Constructor automatically uses the first parent path ingested for that category - so you’re always covered by default.

How to Structure Parent Categories

To incorporate multiple parent categories, you’ll need to update your catalog format:

✅ Do this:

• Replace parent_id: "xyz" → with parent_ids: ["xyz"]
• For multiple parents: parent_ids: ["xyz", "abc"]

⚠️ Important:

• Only include parent_ids - do not include both parent_id and parent_ids
• Even a single parent must be wrapped in an array
• Ensure all parent categories are defined before ingestion

• You can send catalogs with multiple parents in either:

  • CSV format via item_groups.csv
  • JSON format via the /v2/item_groups endpoint

You decide which path to show based on the user’s journey - with full validation and fallback behavior built in.

DAG-based category hierarchies are already available in production to all our customers. 

Related docs: Retrieve item groups, Create or replace item groups, Update item groups, Retrieve item group, JSON / JSONL feed format - item groups (categories), CSV feed format - item groups (categories) 

We're beyond excited to unveil a powerful new capability in the Constructor dashboard: Customizable User Roles with View/Edit permissions, now available in beta!

With this release, companies can tailor access like never before. Empower your teams with precisely the tools they need, whether it's managing indexes, merchandising, or launching A/B tests. It's flexible, secure, and built to scale with your company.

Why this matters

Companies tend to have multiple teams working within the Constructor dashboard. From Merchant Teams responsible for all things merchandising, Marketing Teams that use Collections for email campaigns, and Dev Teams in charge of integrations, every group uses the dashboard differently. With Customizable User Roles, you can assign access and permissions that align with each team's responsibilities without compromising control or security.

What you can do

With this release, you can now create custom roles that:

• Control access to company-level settings, such as API tokens and user management
• Allow access to specific indexes (perfect for teams that manage different regions or websites!)
• Grant edit access to individual features, such as Searchandising, Global Facet Configuration, Recommendations, and more.

You can even create a view-only role to invite more stakeholders from different departments who might benefit from the information in the Constructor dashboard, such as reporting and analytics. 

How to get started

All roles start with view-only access permission across all indexes. From there, you can assign edit access to any index and specific features within those indexes. This can be done via the Constructor dashboard. 

For more information, please visit the documentation guide.

With custom user roles, your teams will benefit from tools and information available in the Constructor dashboard without the risk of accidental actions.

We are currently rolling out Customizable User Roles with View/Edit permissions in beta. Please, connect with your Customer Success Manager or contact us through support@constructor.io to get early access.

What’s new:

We’ve upgraded Variation Slicing to give merchandisers more precision than ever.

With the new Variation Slicing Conditions, you can choose exactly which product variations to surface — without slicing all possible variants for every item.

You can now:

• Highlight only the variations you want — e.g., new styles, sale items, or seasonal colors.
• Filter variations with powerful conditions such as Item ID, color, size, or other attributes.
• Mix and match conditions to target exactly the right subset of product variations.
• Visually merchandise your PLPs by promoting only the variations that matter for your campaign.
• Use a drag-and-drop preview to instantly tailor the shopper experience.

Why it matters:

Before, merchandisers had to make a tough choice:

• Slice all variations for an attribute (risking cluttered or irrelevant product listings), or
• Avoid variation slicing altogether — missing opportunities to spotlight specific variations.

Now, you can surgically control variation visibility to align perfectly with your strategy.

 For example:

• Launch a PLP for Valentine’s Day featuring only red dresses.
• Promote only the 12-pack size of a soft drink that’s on sale.
• Push new color drops for a top-selling shoe to the top of the page.

This means more relevant merchandising, more engaging shopping experiences, and more revenue potential — without sacrificing the integrity of your PLP layout.

Learn more in the documentation.