Discover exact pages
Identify brand, collection, series, and product URLs while keeping the original source hierarchy and HTML base resolution intact.
Product imports
ConfigAI treats every import as a source-backed product onboarding job. AI is used where interpretation is valuable; deterministic paths stay deterministic when a supplier already exposes structured product data.
Website
Agent research
Evidence extraction
pCon Catalog
Deterministic
pCon / OFML
Supplier source
Conversation
Agent-assisted
Manual
Direct entry
Evidence layer
identity · text · images · relations · source revisions
Product Setup proposal
Six ways in
Every source ends in the same Preview → Review → Apply flow, so adding a website importer or pCon connection does not create a parallel product database.
Research public product pages, preserve exact links and captured evidence, and let the agent propose product structure.
Extract text and page evidence, then use the same product-setup workflow rather than flattening the PDF into names only.
Read the provider's model list and source hierarchy directly. No AI prerequisite for the deterministic catalog path.
Connect authorised supplier data and preserve source product identities, family relations, configuration context, and assets.
Let a product owner describe the range, then convert the conversation into explicit fields, products, and open questions.
Create or correct products through the same Product Type fields and revision model used by every other import.
Website research
The website path is designed around exact source capture: start from authorised links, collect product text, JSON-LD and images, preserve low-confidence findings, and reuse captured evidence instead of re-fetching the same pages.
Identify brand, collection, series, and product URLs while keeping the original source hierarchy and HTML base resolution intact.
Store the text, structured metadata, images, and source revision the proposal depends on. JEV can accelerate bounded research and replay captured results.
Map only confident facts to products. Collection-level information remains collection-level unless the source proves a product-level claim.
pCon Catalog
The pCon Catalog path is intentionally deterministic: provider product identities and available source relations are imported directly, and available CAD can be converted and attached without making Gatekeeper or an AI agent a prerequisite.
Public catalog
Private / supplier data
When a supplier requires login or Gatekeeper-authorised access, credentials remain part of the connection boundary rather than being copied into product records.
Source authority stays separate from product authority.
ConfigAI records where a product came from; the reviewed ConfigAI revision remains the application-facing product definition.
Import protocol
The important part is not the crawler. It is making every import repeatable, idempotent, reviewable, and bound to exact product and source revisions.
ConfigAI workspace
The goal is not to scrape a catalog once. It is to create a durable, reviewable product system that can be reopened and updated when the source changes.