Skip to content

Updates

Product development notes.

A curated view of the product capabilities and operating methods that make catalog work more deliberate.

Product principles

Progress that keeps control with the catalog team.

Tessaire evolves around a consistent promise: preserve source truth, make quality issues visible, and keep every AI-assisted change under human review.

Archive
9 curated notes
Focus
Catalog decisions
Control model
Human approved

Development archive

What has changed across the product.

  1. Public experience

    Original catalog methodology joined the resource library

    The resource library presents practical guidance for catalog quality, Arabic commerce content, visual merchandising, and human-reviewed AI content.

    • Four original articles share one reusable reading template.
    • Each article connects product practice to an explicit human control point.
  2. Public experience

    Seven fashion-commerce use cases became explorable

    Seven catalog and merchandising use cases now connect each operating problem to a workflow, output, and control model.

    • One consistent structure connects the index and all seven detail views.
    • Arabic localization, visual discovery, clienteling, and marketplace responsibilities remain explicit.
  3. Public experience

    Product and workflow narratives gained full operating context

    Product and Workflows pages connect catalog intake, AI-content review, quality resolution, controlled outbound work, discovery, styling, and insights.

    • The product story separates buyer outcomes from operating controls.
    • The workflow story separates AI confidence from channel readiness.
  4. Public experience

    A customer-facing homepage replaced the root redirect

    The homepage introduces Tessaire through shared navigation, accessible page structure, and a connected catalog workflow.

    • Public information routes use a separate, data-free layout.
    • Authenticated destinations keep their existing session boundary.
  5. Catalog truth

    Source attribution became more precise

    Source-synced products show where their data came from, while connected-source counts reflect active connections instead of every stored source record.

    • Product source labels follow each workspace’s source history.
    • Inactive source records no longer inflate the connected count.
  6. Human-reviewed AI

    AI-content review kept approval with the catalog team

    Structured AI suggestions preserve imported values and enter an accept, edit, or reject workflow before any value becomes approved product data.

    • Provider and model context remain attached to each run.
    • Your team approves everything that moves into product truth.
  7. Connector boundary

    Shopify source intake gained a read-only adapter

    The source workflow separates connector configuration, connection state, and imported catalog evidence while keeping the supported operation read-only.

    • The supported operation is read-only.
    • Connection health is reported independently from stored source configuration.

  1. Product-page controls

    Brand product-page profiles became editable controls

    Tenant- and brand-scoped profiles can express field preferences, locale requirements, voice guardrails, channel needs, and review thresholds without auto-approving suggestions.

    • Required, optional, and hidden fields shape readiness and review.
    • Arabic and English requirements remain peer product concerns.
  2. Client experience

    Core client workflows received responsive hardening

    High-density client surfaces were tightened for smaller viewports while preserving readable states, actions, and product workflow context.

    • Primary workflow surfaces use more stable responsive layouts.
    • The polish keeps customer-facing pages consistent across workflow states.

Explore the method

Read the thinking behind the product work.