Constructor is the AI-driven ecommerce product search and discovery platform that scales, learns, and adapts to how shoppers actually buy. Its central Commerce Reasoning Engine uses reinforcement learning to improve with every shopper interaction, serving the right product to the right person at the right time — everywhere. By learning directly from real shopper behavior on your ecommerce site, Constructor continuously drives stronger performance across the metrics that matter most to your business and improves conversion across every channel onsite and offsite including agents, answer engines, search, recommendations, retail media, and more. Purpose-built for ecommerce, Constructor generates consistent $10M+ lifts for leading brands such as Sephora, Footlocker, Under Armour, Helly Hansen and GAP. Learn more at constructor.com.

The integration brings Constructor's search and merchandising into every search and browse surface in the Tapcart app. Once enabled, the same blocks merchants already drag into App Studio start serving Constructor results — no block swap, no second editor.

• Keyword search — query-driven product results with Constructor's relevance and personalization

• Category browse — Shopify collections served via Constructor's category browse

• Autocomplete — search suggestions, product autocomplete, and category suggestions

• Pod recommendations — campaign-driven carousels keyed by Constructor pod ID (e.g. "home_page_1", "pdp_complete_the_look")

• Search redirects — query-to-URL redirects configured in the Constructor dashboard

• Sort & dynamic filters — sort options and facets returned per request, including range facets

• Personalization signals — every PLP open, carousel render, search submit, autocomplete keystroke, and product detail view is sent to Constructor as a collection view, browse view, search event, or item-detail event, stamped with the customer's identity so the ranking models can personalize subsequent results

Eligibility: The integration is available to all Tapcart Enterprise customers who also hold a Constructor contract.

1. In the Constructor dashboard, generate a public API key for the storefront index.

2. Decide whether collections in your index are keyed by Shopify collection handle or by numeric collection ID. Constructor uses a single category identifier — it must match what your feed publishes.

3. Open Tapcart Dashboard → Integrations → Search & Merchandising and select Constructor.

4. Paste the API key, enable Send tracking events, and toggle Browse by handle to match your feed.

5. Save. The next render of any Tapcart screen with a search-aware block will start hitting Constructor.

The Search page in App Studio is composed of four blocks. All four switch automatically once Constructor is selected as the search provider — no per-block setting is required.

• Search Input (Search page) — resolves search redirects when a query is submitted.

• Trending Search Results (Search page) — suggested search terms from autocomplete.

• Trending Collections (Search page) — suggested categories from autocomplete, hydrated to Shopify collections.

• Search Results - Products (Search page) — search results for the typed query, plus autocomplete previews for partial queries.

In the Constructor dashboard, make sure the autocomplete response includes the three sections Tapcart consumes:

• Search Suggestions — drives the chips in Trending Search Results

• Products — drives the autocomplete grid in Search Results - Products

• Categories — drives Trending Collections

If a section is missing, the corresponding block silently renders empty.

Search redirects are read by the Search Input block on submit. Configure them in Constructor dashboard. When a redirect URL is returned, Tapcart navigates to that specific screen or collection instead of opening the search results page.

Sort options and facet definitions come back dynamically on every request — Tapcart does not need a static sort or filter list in the integration config. Update them in Constructor dashboard, and the Sort and Filter Header block on the search results page picks them up automatically.

Tapcart's Product List Page is the collection page. Two blocks consume the search client there:

• Product Grid (PLP) — category browse for the active collection.

• Sort and Filter Header (PLP) — sort options, facets, and applied filters from the same call.

Constructor browse is keyed off a single field, configured by the Browse by handle toggle in the integration settings:

• Toggle ON — Tapcart sends the Shopify collection handle (e.g. summer-sale). Use this if your Constructor feed publishes handles.

• Toggle OFF — Tapcart sends the numeric Shopify collection ID (e.g. 286682349611). Use this if your feed publishes numeric IDs.

Tapcart auto-resolves the missing identifier from Shopify, so a collection with only a handle in the URL still works when your feed expects an ID, and vice versa.

Carousel and grid blocks placed on the homepage, custom screens, or PDP each get their own isolated search-client instance so their pagination and filters never interfere with each other.

• Product Carousel (Homepage, custom screens) — category browse for the configured collection.

• Large Product Carousel (Homepage, custom screens) — same as above.

• Tabbed Product Carousel (Homepage, custom screens) — one browse call per tab/collection.

• Tabbed Product Grid (Homepage, custom screens) — one browse call per tab/collection.

• Collection - Product Grid (Custom screens, PDP, PLP rails) — browse for a specific collection.

Each carousel/grid block in App Studio has a Collection picker. The chosen Shopify collection is what Tapcart sends to Constructor as the browse target.

Constructor recommendations (pods) are surfaced through the same recommendations API Tapcart already uses. To drive a carousel from a Constructor pod instead of a Shopify collection, the block's recommendation config must include a Pod ID. Supported settings:

• Pod ID — Constructor pod ID (e.g. home_page_1).

• Num Results — maximum products to return.

When Constructor integration is enabled, the customer's interactions with search and merchandising surfaces flow back to Constructor as the customer browses:

• Collection views — every PLP open is sent as a browse view for the underlying collection, carrying the active sort and filters.

• Search activity — search submits and autocomplete keystrokes are sent as search events with the typed query.

• Product detail views — PDP opens are sent as item-detail events from the React Native shell via the existing analytics adapter, so Constructor can factor product affinity into ranking and recommendations.

• Eligibility — Enterprise plan only; both a Tapcart Enterprise contract and a Constructor contract are required.

For Tapcart-side questions (block configuration, App Studio settings, identity wiring), reach out to your Tapcart account team. For Constructor-side questions (index setup, pod configuration, merchandising rules, dashboard access), contact your Constructor customer success representative.