Constructor

Constructor is a cloud platform for ecommerce search and product discovery, founded in 2015. It interprets shopper behavior, context, and intent to support search, autosuggest, browsing, recommendations, collections, quizzes, and retail media. The AI Shopping Agent guides shoppers through natural-language product requests, while a Product Insights Agent answers personalized product questions. Merchant Intelligence Agent and Merchandiser Controls provide merchandising insights, dashboards, reports, controls, and experiments. B2B capabilities include account-segmented pricing and availability, personalization, and discovery across large catalogs. The platform supports hybrid and vector search, faceted search, zero-result reporting, search conversion tracking, and result click analytics. Catalog data can arrive through platform connectors, scheduled JSON, JSONL, or CSV feeds, or REST API updates. APIs and browser or server-side client libraries support retrieving results, sending behavioral events, and updating catalog data or configurations; documented libraries include JavaScript, Swift, and Kotlin. Constructor says it reduces personal-data exposure with anonymous IDs, truncated IP addresses, and hashed identifiers. Listed platforms are Android, API, iOS, and web. Pricing is not published; prospective customers can book a demo.

Constructor combines shopper discovery tools with merchandising controls and APIs. Retailers considering it will need to request a demo to discuss pricing.

Constructor is aimed at retailers seeking ecommerce search and product discovery tools. Its dedicated B2B capabilities address businesses that need account-specific pricing, availability, and discovery across large catalogs.

Overview

Constructor is a commerce discovery platform for retailers that want search, recommendations, and merchandising tools to work together. Its strongest fit is a retailer or B2B ecommerce team managing a large catalog and investing in personalized product discovery.

Key features

The suite covers ecommerce search, autosuggest, browse, recommendations, collections, quizzes, and retail media. Hybrid and vector search, faceted navigation, and zero-result reporting address different parts of the discovery experience: shoppers can narrow results, while teams can find queries that return nothing. Search-conversion tracking and result-click analytics help assess whether those changes lead to engagement and sales. This breadth is useful when search is part of a larger merchandising program, but is likely unnecessary for a store that needs only a basic search box.

Constructor's Commerce Reasoning Engine uses clickstream and other shopper and market data to personalize discovery across touchpoints in real time. The AI Shopping Agent uses natural-language queries to guide shoppers and recommend products; the Product Insights Agent handles personalized product questions. These tools make sense for enterprise ecommerce teams pursuing conversational product discovery, rather than buyers looking for a small standalone add-on.

Merchant Intelligence Agent and Merchandiser Controls give teams analytics, dashboards, reports, controls, and experiments. That pairing lets merchants shape discovery as well as review it, which is valuable for teams actively managing product presentation. B2B capabilities include account-segmented pricing and availability, personalization, and discovery across large catalogs—more relevant to complex B2B storefronts than to simpler retail operations.

Catalog data can arrive through platform connectors, scheduled JSON, JSONL, or CSV feeds, or item-by-item REST API updates. The REST API also supports retrieving results and changing settings such as synonyms, redirects, and searchandising. Browser JavaScript, iOS Swift, and Android Kotlin client libraries support result retrieval, behavioral events, and catalog or configuration updates. Constructor's integration team can help configure accounts and indexes, map data, review integrations, and test results with merchandising and business teams; that support is useful for complex rollouts, though implementation still calls for coordination across teams.

Technology partners include Akeneo, BigCommerce, commercetools, Contentful, Salesforce Commerce Cloud, Shopify, and VTEX, among others. Constructor says its service is independently audited under SOC 2 Type 2 and ISO 27001, with reports shared under NDA. It also describes multi-factor authentication, device trust, role-based access, and regular external penetration tests. Its stated privacy practices include anonymous IDs, truncating the last IP octet, and hashing identifiers to reduce links to personally identifiable information.

Pricing

Custom enterprise pricing: Constructor does not publish a plan price; prospective customers are directed to book a demo. This suits organizations prepared to discuss requirements with sales, but makes it harder for buyers to compare costs or make a quick self-serve decision. No per-seat, quota, trial, or renewal terms are provided.

Platforms

Constructor supports Android, iOS, web, and API access. Its deployment is cloud-based, with a REST query interface and client libraries for browser JavaScript, iOS Swift, and Android Kotlin.

Who it's for

Constructor is built for retailers, with dedicated solutions for B2B ecommerce and several retail sectors. It is most compelling for organizations that need discovery, personalization, analytics, and merchandising controls in one platform, particularly those handling large catalogs or account-specific B2B pricing and availability. A smaller retailer seeking a low-cost tool with a published price may find the demo-led, custom-pricing model a poor fit.

Pros and cons

• Pro: Search, recommendations, collections, retail media, and shopping agents sit alongside merchandising controls, making the suite suitable for teams coordinating discovery across multiple storefront touchpoints.
• Pro: Hybrid and vector search, facets, zero-result reporting, conversion tracking, and click analytics give teams both discovery controls and ways to evaluate shopper response.
• Pro: Multiple catalog ingestion methods, client libraries, and integration-team support can accommodate varied implementation needs.
• Con: Custom pricing and a required demo make it difficult to assess cost without a sales conversation.
• Con: The enterprise orientation and broad feature set may be excessive for stores that need only basic product search.

Alternatives

Choose Algolia if a freemium option and explicit entry-level quotas matter: its free plan includes 10K search requests per month, 50K records, 5K recommendation requests per month, and 5K crawls per month, with no credit card required. Prefixbox Search Analytics is worth considering for retailers focused on search measurement; its free plan is designed for retailers with more than 150,000 searches per month and includes over 100 search metrics. Consider Empathy Platform if self-managed components and deployment on your own infrastructure or a hosting option are priorities; its SmC plan is priced per query, not per API call.

Unbxd is another paid alternative. Bloomreach Content is a paid option without a free plan, while Nosto offers custom modular pricing based on a base platform fee, store volume, selected modules, and support and scalability level. Bloomreach Discovery is also a paid alternative. For a lower-cost starting point, Searchanise has a free plan for up to 25 products and a Basic plan at $19 a month for up to 1,5k products.

Related directories: Search Analytics Software, Email Personalization Software, and Search Databases.

Verdict

Constructor is best for retailers and B2B ecommerce teams that want a broad discovery platform, real-time personalization, and merchant controls supported by implementation help. Its breadth and dedicated B2B capabilities are the main reasons to choose it; custom pricing and a sales-led buying process are the clearest reasons to look elsewhere if you need a quick, budget-transparent purchase.