Catalog intake and source staging
CSV and XLSX upload, field mapping, row validation, asynchronous commit, source sync history, and staged differences share one local operating path.
Product
One product truth, carried to a channel decision.
Tessaire connects catalog intake, product structure, human review, quality signals, readiness, and controlled outputs without treating a suggestion as approved commerce data.
End-to-end product
Each capability keeps its operating boundary attached.
Canonical product truth
Committed products, variants, assets, attributes, source lineage, edits, and audit history remain reviewable in the tenant-scoped product graph.
Governed enrichment review
Mock-first enrichment writes structured suggestions with confidence. Reviewers accept, edit, or reject before approved values become product attributes.
PDP, asset, and channel quality
Quality issues can be reviewed and resolved alongside readiness rollups, keeping missing content and channel blockers visible before downstream use.
Controlled exports and writeback
CSV and JSON exports, staged approvals, writeback batches, and per-item results are implemented. Fixture contracts explicitly record that no vendor operation was called.
Client-safe catalog insights
Catalog quality, source health, freshness, review progress, readiness, and blockers are aggregated without exposing HQ commercial or provider diagnostics.
Discovery and styling workbenches
Visual Search, Shop Similar, Outfit Graph, Shop-the-Look, and styling briefs are authenticated review or preview surfaces, not public storefront delivery.
Local or open-weight enrichment
A non-mock local enrichment backend has not shipped. Hosted OpenAI and Anthropic enrichment paths are removed by architecture decision.
Credentialed Shopify read-only import
The token-ready adapter needs a separately supplied local read-only token. Without it, source sync remains in truthful fixture-contract mode.
Decision signals
Confidence and readiness answer different questions.
- Attribute confidence
- How strongly an enrichment suggestion is supported, and whether it should enter human review.
- Channel readiness
- Whether the approved product record satisfies the content, asset, quality, and channel requirements needed for the next decision.
Operating model
Follow the states, then decide what moves forward.
The workflow view shows where validation, review, approval, staging, and explicit external boundaries enter the sequence.