.ainu-review{font-family:-apple-system,BlinkMacSystemFont,’Segoe UI’,Roboto,Helvetica,Arial,sans-serif;color:#1a2332;line-height:1.7;max-width:860px;margin:0 auto} .ainu-review .eyebrow{font-size:.78rem;font-weight:700;letter-spacing:.12em;text-transform:uppercase;color:#2563EB;margin-bottom:.4rem} .ainu-review h1{font-size:2rem;font-weight:800;line-height:1.2;color:#1F3D5C;margin:0 0 1.2rem} .ainu-review .intro-grid{display:grid;grid-template-columns:1fr 260px;gap:2rem;align-items:start;margin-bottom:2rem} @media(max-width:680px){.ainu-review .intro-grid{grid-template-columns:1fr}} .ainu-review .score-badge{background:linear-gradient(135deg,#1F3D5C,#2563EB);border-radius:16px;padding:1.8rem 1.4rem;text-align:center;color:#fff;position:sticky;top:1rem} .ainu-review .score-badge .score-num{font-size:3.6rem;font-weight:900;line-height:1;letter-spacing:-.03em} .ainu-review .score-badge .score-label{font-size:.78rem;text-transform:uppercase;letter-spacing:.1em;opacity:.85;margin-top:.3rem} .ainu-review .score-badge .score-verdict{font-size:.9rem;font-weight:700;margin-top:.8rem;padding:.45rem 1rem;background:rgba(255,255,255,.18);border-radius:8px} .ainu-review .quick-facts{margin-top:1.2rem;text-align:left} .ainu-review .quick-facts dt{font-size:.72rem;text-transform:uppercase;letter-spacing:.08em;opacity:.8;margin-top:.7rem} .ainu-review .quick-facts dd{font-size:.88rem;font-weight:600;margin:0} .ainu-review .intro-text p{margin-top:0;font-size:1.05rem} .ainu-review h2{font-size:1.3rem;font-weight:800;color:#1F3D5C;margin:2.2rem 0 .7rem;padding-bottom:.4rem;border-bottom:2px solid #EAF1FB} .ainu-review h3{font-size:1.05rem;font-weight:700;color:#1F3D5C;margin:1.4rem 0 .4rem} .ainu-review .score-bar-wrap{margin:.5rem 0 1rem} .ainu-review .score-bar-row{display:flex;align-items:center;gap:.8rem;margin:.35rem 0} .ainu-review .score-bar-label{width:200px;font-size:.82rem;color:#374151;flex-shrink:0} .ainu-review .score-bar-track{flex:1;background:#EAF1FB;border-radius:99px;height:9px;overflow:hidden} .ainu-review .score-bar-fill{height:100%;border-radius:99px;background:linear-gradient(90deg,#2563EB,#1F3D5C)} .ainu-review .score-bar-num{width:32px;text-align:right;font-size:.82rem;font-weight:700;color:#1F3D5C;flex-shrink:0} .ainu-review .pricing-table{width:100%;border-collapse:collapse;font-size:.88rem;margin:1rem 0} .ainu-review .pricing-table th{background:#1F3D5C;color:#fff;padding:.7rem 1rem;text-align:left;font-weight:700} .ainu-review .pricing-table td{padding:.65rem 1rem;border-bottom:1px solid #e5eaf2;vertical-align:top} .ainu-review .pricing-table tr:nth-child(even) td{background:#f5f8ff} .ainu-review .pros-cons{display:grid;grid-template-columns:1fr 1fr;gap:1.2rem;margin:1rem 0} @media(max-width:560px){.ainu-review .pros-cons{grid-template-columns:1fr}} .ainu-review .pros-box,.ainu-review .cons-box{border-radius:12px;padding:1.2rem 1.4rem} .ainu-review .pros-box{background:#edfaf3;border:1px solid #a7f3d0} .ainu-review .cons-box{background:#fff5f5;border:1px solid #fca5a5} .ainu-review .pros-box h4{color:#065f46;margin:0 0 .6rem;font-size:.85rem;text-transform:uppercase;letter-spacing:.07em} .ainu-review .cons-box h4{color:#991b1b;margin:0 0 .6rem;font-size:.85rem;text-transform:uppercase;letter-spacing:.07em} .ainu-review .pros-box ul,.ainu-review .cons-box ul{margin:0;padding-left:1.1rem;font-size:.88rem;line-height:1.6} .ainu-review .pros-box ul li,.ainu-review .cons-box ul li{margin:.25rem 0} .ainu-review .faq-item{border:1px solid #dde6f5;border-radius:10px;margin:.7rem 0;overflow:hidden} .ainu-review .faq-item summary{padding:.9rem 1.2rem;font-weight:700;font-size:.92rem;color:#1F3D5C;cursor:pointer;list-style:none;display:flex;justify-content:space-between;align-items:center} .ainu-review .faq-item summary::-webkit-details-marker{display:none} .ainu-review .faq-item summary::after{content:”＋”;font-size:1.1rem;color:#2563EB;flex-shrink:0} .ainu-review .faq-item[open] summary::after{content:”－”} .ainu-review .faq-item .faq-body{padding:.2rem 1.2rem 1rem;font-size:.9rem;color:#374151} .ainu-review .related-links{background:#EAF1FB;border-radius:12px;padding:1.2rem 1.4rem;margin:2rem 0} .ainu-review .related-links h4{color:#1F3D5C;font-size:.85rem;text-transform:uppercase;letter-spacing:.07em;margin:0 0 .6rem} .ainu-review .related-links ul{margin:0;padding-left:1.1rem;font-size:.88rem} .ainu-review .related-links ul li{margin:.25rem 0} .ainu-review .related-links a{color:#2563EB;text-decoration:none;font-weight:600} .ainu-review .related-links a:hover{text-decoration:underline} .ainu-review .verdict-box{background:linear-gradient(135deg,#EAF1FB,#dbeafe);border:2px solid #2563EB;border-radius:14px;padding:1.4rem 1.6rem;margin:1.5rem 0} .ainu-review .verdict-box h3{color:#1F3D5C;margin:0 0 .5rem;font-size:1rem} .ainu-review .verdict-box p{margin:0;font-size:.92rem;color:#1a2332} .ainu-review .callout{background:#fff8e1;border-left:4px solid #f59e0b;border-radius:0 8px 8px 0;padding:.8rem 1.2rem;margin:1rem 0;font-size:.9rem;color:#78350f}
Constructor Review (2026): Features, Pricing & Verdict
Constructor is the most analytically validated ecommerce search and product discovery platform in 2026 — a Gartner Magic Quadrant Leader, Forrester Wave Leader, IDC MarketScape Leader, the only vendor named a Customers’ Choice in Gartner Peer Insights 2025, and the only vendor to rank first in three of five use cases in Gartner’s Critical Capabilities for Search and Product Discovery. In FY26 it grew its customer base by 82%, retained 96% of gross revenue, and powered 322 billion product discovery interactions — 10,000 personalised shopping experiences per second — a 266% increase over two years. The platform’s founding philosophy separates it from every other search tool reviewed in Cat 23: Constructor optimises for business outcomes (revenue, conversion rate, profit) rather than for search relevance. Where conventional search engines rank products by how well they match a query, Constructor’s Commerce Reasoning Engine ranks products by how likely they are to convert for that specific shopper in that specific context — using first-party behavioural data, catalogue data and inventory signals to make ranking decisions that directly serve the retailer’s commercial goals rather than treating relevance as a proxy. The transparent AI — “not a black box” per client quotes — allows merchandising teams to see why results are ranked the way they are and apply boost, bury and pin controls alongside the automated ranking. Enterprise clients including Sephora, Petco, Birkenstock and Grove Collaborative report consistent $10M+ revenue lifts. Constructor was founded in 2015 by Eli Finkelshteyn and Dan McCormick; it operates in 20 languages; and all pricing is custom enterprise with usage-based structure.
- Best for
- Enterprise ecommerce with high traffic needing revenue-optimised search, browse & recommendations
- Scale
- 322 billion interactions in FY26 · 82% customer growth · 96% revenue retention
- Clients
- Sephora · Petco · Birkenstock · Grove Collaborative · Backcountry · Bonobos
- Analyst recognition
- Gartner MQ Leader 2026 · Forrester Wave Leader Q3 2025 · IDC MarketScape Leader
- Pricing
- Custom enterprise · usage-based · no public rates
What Is Constructor?
Constructor is an AI-first search and product discovery platform purpose-built for enterprise ecommerce, founded in 2015 in San Francisco. Its Commerce Reasoning Engine powers search, browse, autosuggest, recommendations, collections, product finders, quizzes and an AI Shopping Agent from a single unified platform — sharing the same behavioural learning loop across all discovery touchpoints rather than running each as a separate optimisation silo. Constructor’s stated differentiation from competitors is revenue-first optimisation: where other platforms optimise for relevance (does the result match the query?) or engagement (do shoppers click?), Constructor optimises for conversion and revenue directly, using real commercial outcomes as the training signal for its ML models.
Core Features
Commerce Reasoning Engine — revenue-first ranking
Constructor’s core technology is the Commerce Reasoning Engine — a machine learning system that ingests first-party behavioural clickstream data, product catalogue attributes, inventory data and business rules, then uses that combined signal to rank search results, category pages and recommendations based on predicted revenue and conversion contribution rather than keyword relevance alone. In controlled production A/B tests, this outcome-optimised ranking consistently outperforms relevance-ranked search in revenue per visitor and checkout conversion. The engine learns continuously: as shopper behaviour accumulates on a specific retailer’s site, the ML models become increasingly calibrated to that retailer’s specific customers and products, improving results over time without requiring manual rule updates. The transparency of the system — merchandising teams can understand why the AI ranked products the way it did — is a documented differentiator from black-box competitors and a specific reason cited by client switch decisions.
AI Shopping Agent — agentic commerce
Constructor’s AI Shopping Agent, launched in 2026 as the platform’s agentic AI capability, is purpose-built for enterprise ecommerce discovery rather than adapted from a general-purpose LLM chatbot. The agent is integrated with the Commerce Reasoning Engine — it shares the same data model, product understanding and learning loop as the rest of the platform, meaning it reasons about products using the same attributes, hierarchies, inventory constraints and shopper intent signals that power search and recommendations. This architecture enables it to handle complex, attribute-specific queries that generic LLMs struggle with: “waterproof hiking boots for wide feet under £150 with good ankle support” requires reasoning about multiple product attributes simultaneously, which product-grounded AI handles better than a chatbot drawing on parametric knowledge. Belk’s mobile rollout of the AI Shopping Agent on its mobile app — where nearly 40% of its business transacts — demonstrated the agent’s ability to personalise discovery conversations at scale without scripted form-based paths.
Search, browse and recommendations — unified learning
Constructor’s full suite covers the complete product discovery journey: Search with NLP, typo correction, synonym matching and zero-result recovery; Autosuggest that guides shoppers toward high-converting products in real time; Browse (AI-optimised category pages that re-rank products based on individual shopper signals); Recommendations across PDP, cart, search and email; Collections and Product Finders for curated and guided discovery experiences. The critical architectural advantage is that all of these operate from the same data model and learning loop — improvements in search signal quality improve recommendations quality, and behavioural data from browse improves search ranking. Most competitor platforms run search and recommendations as separate systems with separate data pipelines and separate definitions of success; Constructor’s unified approach compounds learning faster and produces more consistent personalisation across the full shopper journey.
Scored Categories
Pricing
| Model | Structure | Notes |
|---|---|---|
| Enterprise custom | Usage-based (volume of search/discovery interactions) | Charges vary with traffic volume, catalogue size and features activated |
| Revenue impact | $10M+ lifts documented | Constructor consistently cites $10M+ revenue improvements for enterprise clients in marketing materials |
| Access | Sales engagement required | Contact constructor.com/contact — no self-serve or trial |
Strengths
- Gartner Magic Quadrant Leader 2026 + Forrester Wave Leader Q3 2025 + IDC MarketScape Leader
- Only vendor named Gartner Peer Insights Customers’ Choice — highest user satisfaction recognition
- Revenue-first optimisation: ranks by conversion/revenue, not just relevance
- 322 billion interactions in FY26 — 10,000 personalised experiences/second
- 96% gross revenue retention — customers stay and expand, rarely churn
- Transparent AI — merchandising teams can see and understand ranking decisions
- Unified platform: search, browse, recommendations, quizzes share one learning loop
- $10M+ revenue lifts documented for enterprise clients
- 82% customer growth in FY26 — accelerating adoption
Weaknesses
- Enterprise-only — meaningful minimum traffic required for ML training effectiveness
- No published pricing — requires sales engagement before cost evaluation
- Steep learning curve — weeks of onboarding before teams are fully productive
- Implementation requires engineers — not a plug-and-play solution
- Early-stage stores and SMBs are not viable candidates regardless of intent
- Analytics reporting rated slightly lower (4.2/5) vs search quality (4.8/5) on RFP.wiki scoring
Verdict: 8.7 / 10 — The Analytically Validated Leader in Revenue-Optimised Ecommerce Search
Constructor earns its 8.7 — the highest score in Cat 23 — through a combination of metrics that are difficult to argue with: triple analyst leadership recognition (Gartner, Forrester, IDC), 96% gross revenue retention reflecting genuine customer satisfaction, 82% customer growth reflecting expanding market validation, and documented $10M+ revenue lifts from an enterprise client base that includes Sephora and Petco. The revenue-first optimisation philosophy is the right approach for enterprise ecommerce in 2026 — relevance is a means to conversion, not the end goal, and Constructor’s Commerce Reasoning Engine is built around that principle more rigorously than any competing platform. The 8.7 rather than a higher score reflects the enterprise-only reality: Constructor is a significant investment requiring meaningful traffic, implementation resources and commercial commitment. For retailers at the scale where those conditions are met, it is the strongest search and product discovery platform available.
Frequently Asked Questions
What makes Constructor’s search different from standard ecommerce search?
Most ecommerce search engines rank results by relevance — how well a product matches the keywords in a query. This produces search results that are accurate in a keyword-matching sense but not optimised for what actually matters to the retailer: conversion and revenue. Constructor’s Commerce Reasoning Engine adds a commercial optimisation layer that uses real behavioural data — what shoppers click, what they add to cart, what they purchase, and what they return — to learn which products convert best for which shoppers under which query contexts. Results are then ranked by predicted revenue contribution rather than query relevance. In controlled A/B tests, this consistently produces higher revenue per visitor than relevance-ranked search. The system improves over time as it accumulates more behavioural data specific to your store, becoming increasingly calibrated to your specific customers and product catalogue.
What does “transparent AI” mean in Constructor’s context?
Constructor’s transparent AI refers to the fact that merchandising teams can see and understand why the platform’s AI ranked specific products in specific positions — unlike “black box” ML systems where ranking decisions are opaque and teams cannot explain or verify what the system is doing. In Constructor’s admin interface, merchandising teams can view the signals the AI used to rank a result, apply manual boost, bury and pin controls alongside the automated ranking, and understand how their business rules interact with the ML layer. One client specifically cited this transparency as the reason they chose Constructor over competitors: “None of it is black box — we don’t have to guess what it’s doing or why.” For enterprise retailers where merchandising governance, regulatory compliance, or brand control requirements mean that AI-driven decisions must be explainable and auditable, this transparency is a meaningful procurement differentiator.
How long does Constructor implementation typically take?
Constructor’s integration with Commercetools-based headless ecommerce architectures typically completes in around six weeks, with Constructor’s own engineers performing most of the development work in collaborative sessions with the client’s engineering team. For other ecommerce platforms and custom stacks, implementation timelines vary based on architecture complexity, catalogue size and the breadth of Constructor features being activated. The platform provides APIs and SDKs for custom integrations. Constructor’s account teams are closely involved in the implementation process — the 96% gross revenue retention reflects in part the quality of ongoing customer success support post-launch. Teams should plan for a few weeks of onboarding before merchandising teams are fully productive in the platform, and for the ML models to accumulate sufficient behavioural data to produce optimal results — typically a matter of weeks for high-traffic stores.