Skip to main content

Product information assistant

The right manual for the wrong variant is still the wrong answer.

A product information assistant answers customer questions using the exact product, variant and current source records. It can explain specifications, compare documented compatibility and direct stock or price questions to the relevant service. Werkon would validate this pattern around claim-level citations and a correction process, with qualified product and safety owners responsible for consequential advice and approved changes.

Identify the item before answering

A family name, photograph or similar part number can point to several products. The answer may depend on color, size, pack, lot, serial number, hardware revision or firmware. Keep the identifier issuer and namespace with each candidate, and ask for the smallest missing detail when variants produce different answers. A valid barcode or checksum does not establish authenticity, ownership, purchase or warranty entitlement.

Account, order, registration, service and unpublished product fields require their own access checks. A public product lookup does not authorize a private serial-number search. Keep customer data to the minimum needed for the question and prevent instructions inside manuals or linked pages from changing access.

Keep the conditions attached to each claim

Preserve source wording, units, tolerances, warnings, exclusions and footnotes when simplifying an answer. Nominal and measured values, net and gross weight, product and package dimensions, typical and guaranteed performance, and certification claims and verified scope carry different meanings. Conversions, rounding and localized terminology need approved rules.

Sustainability, origin, performance, health, comparative and warranty claims need evidence for the relevant market and language. An expired certificate, badge or supplier filename cannot establish approval. Product, engineering and regulatory owners decide contested claims and consequential calculations such as dosage, loading, electrical protection or chemical compatibility.

Explain compatibility and live offers precisely

Compatibility depends on the direction of the relationship, intended use, interface, dimensions, ratings, software, region, installation and required adapters. A product may physically fit while remaining unsupported or unsafe for that use. Preserve required, optional, tested, conditional, incompatible, unknown and superseded states. Route safety-sensitive questions to the qualified owner and retain current approved warning or stop-use wording. Never recommend bypassing a guard, interlock, warning or installation requirement.

Inventory answers must distinguish sellable stock from reserved, allocated, backordered, in-transit, damaged, expired or quarantined units. Visibility events require reconciliation for duplicates, late arrivals and corrections. Price answers need the exact offer, currency, tax, mandatory fees, quantity, eligibility and effective period; negotiated or personalized prices cannot become a general quote. Say whether a live source was actually checked.

Repair answers when the source changes

Keep the answer linked to its atomic claims and source versions. A correction may require invalidating earlier answers, notifying affected customers and issuing a revised explanation. Retain the earlier error and the qualified correction decision. Generated, sent, displayed, accessed and acknowledged are separate states.

An escalation needs an accepted owner, a due target and a fallback if the receiving team declines or transfers it. Catalog corrections, compatibility reviews, safety inquiries, stock checks and warranty requests follow distinct workflows. Later purchases, returns or silence do not establish suitability, satisfaction or value caused by the assistant.

Product-answer boundary

Answer the question without collapsing the product graph.

Identity, descriptive truth, compatibility, safety, stock and price belong to different authorities. Four boundaries preserve the answer.

01

Exact item and requester context

Resolve tenant, brand, manufacturer, family, model, trade item, SKU, part number, variant, pack, lot, serial, revision, software, market, locale and intended task at the granularity required by the answer; verify private-field authority and ask when evidence is ambiguous.

Required evidence: Tenant and channel, requester and access scope, customer or representative role where relevant, identifier issuer and namespace, GTIN or other trade-item key, seller SKU, manufacturer part, model, variant attributes, pack and unit, lot and serial, hardware and software revisions, market, installed context, question intent, decision time, match candidates, contradictions and disambiguation receipt.

02

Governed facts, claims, and source precedence

Bind each atomic claim to the field-specific source, product scope, market, language, version and effective time; preserve units, conditions, warnings and conflicts and distinguish approved claims from supplier text, community reports and model summaries.

Required evidence: Claim identifier and type, original source and passage, issuer and rights, product and market scope, value, unit, tolerance and condition, source and effective version, obtained time, normalization and translation, authority rule, competing source, review and approval, publication state, expiry, challenge, correction, supersession and dependent-answer links.

03

Compatibility, safety, and policy boundary

Represent compatibility directionally between exact products or bounded classes with interface, revision, region and conditions; apply current warning, recall, market and support policy and route consequential, unsupported or conflicting uses to qualified owners.

Required evidence: Source and target identifiers, relation and direction, intended function, physical, electrical, protocol, software and firmware constraints, adapters and exclusions, test or bulletin, issuer and version, supported state, installation and warning sources, market eligibility, recall or corrective status, warranty and support boundary, risk route, reviewer and decision.

04

Live offer, answer, and correction

Retrieve inventory and price from their authoritative services at answer time, state freshness and scope, compose claim-level citations, deliver accessible wording and preserve escalation and source correction through re-answer and customer notification where required.

Required evidence: Exact item and location, physical, system, reserved, allocated, sellable and available-to-promise states, event and read times, offer, customer class where allowed, currency, tax, fees and effective time, answer claims and citations, uncertainty and expiry, approval, rendering, delivery and access, challenge, accepted case, corrected source, invalidated answers, notification, re-answer and resolution.

Question-to-correction path

Keep identity, facts, answer, and correction separate.

The fastest response is not useful when it silently switches the variant, market or source version.

  1. 01

    Establish question and product scope

    Classify the requested fact or task, determine public or authorized context, resolve candidate identifiers to the necessary item, pack, lot, revision and market granularity and ask the smallest disambiguating question when answers diverge.

    Owner
    Catalog, identity, privacy, product and customer-support owners
    Evidence
    Requester and role, access decision, question intent, locale and accessibility, identifiers and issuers, candidate products and variants, pack, lot or serial where needed, revision and software, market and installed context, matching rules, ambiguity, disambiguation and selected identity receipt.
  2. 02

    Assemble the field-authoritative source packet

    Retrieve current catalog, manufacturer, technical, regulatory, policy and seller records under claim-specific precedence; preserve source text, units, conditions, language, versions, corrections and conflicts and reject injected or unauthorized content.

    Owner
    Product, PIM, engineering, regulatory, safety, policy, localization and data-governance owners
    Evidence
    Source and field allowlist, publisher and rights, record and passage, product and market scope, source and effective versions, obtained time, value, unit, tolerance and conditions, warning and claim state, translation, transformation, conflict, correction, supersession, access and lineage.
  3. 03

    Validate compatibility and consequential boundaries

    Resolve directional product relations and exact interface, mechanical, electrical, software, firmware, regional and installation constraints; check current warnings, recalls and market policy and require qualified review for consequential, unsupported or conflicting use.

    Owner
    Product engineering, safety, regulatory, warranty, security and support owners
    Evidence
    Source and target products, relation type and direction, purpose, interface and dimensions, ratings, protocols, software and firmware range, adapters, exclusions, test or manufacturer bulletin, evidence version, supported state, warnings, recall or corrective record, market eligibility, warranty boundary, reviewer, decision and expiry.
  4. 04

    Retrieve live commerce facts and compose the answer

    Read exact item and location inventory plus exact offer and price at response time, apply field authority and freshness rules, produce atomic source-linked claims, show identity and uncertainty and either answer, ask, abstain or create a complete escalation.

    Owner
    Inventory, pricing, commerce, catalog, support and communication owners
    Evidence
    Item-location match, inventory states and event times, availability service and age, offer, currency, unit, tax, fees, eligibility and effective interval, selected source claims, deterministic calculations, wording and locale, citations, missingness and conflict, safety route, approval where required, answer expiry and escalation packet.
  5. 05

    Deliver, challenge, correct, and measure

    Preserve generated, displayed and accessed states, accept source or answer challenges, require a qualified owner to correct the controlling record, invalidate dependent answers and notify or re-answer affected customers where policy requires before evaluating service outcomes.

    Owner
    Channel, catalog, engineering, safety, customer-support, correction and outcome owners
    Evidence
    Answer and source snapshot, renderer and channel, generation, provider acceptance, display and access, challenge and evidence, case and accepted owner, correction decision, revised source and version, affected claims and answers, withdrawal or safety route, notification, re-answer, repeat contact, resolution, customer outcome and attribution review.

Authority map

Separate product controls, language assistance, and qualified authority.

A model can retrieve a sentence about a connector. It cannot certify that a device is safe, supported or in stock.

01

Deterministic product controls

Software owns tenant and identifier boundaries, source and field authority, access, versions and effective times, unit conversions, typed product relations, compatibility rule gates, safety blocks, inventory and price calls, claim citations, action rights and receipts.

  • Tenant, product, variant, pack, lot, revision, claim, relation, answer, case and correction identifiers
  • Identifier, source, field, market, language, version, effective-time, unit and freshness validation
  • Compatibility, safety, recall, inventory, price, access, disclosure and escalation enforcement
  • Question, source packet, answer, delivery, challenge, correction, notification and outcome receipts
02

Bounded AI assistance

Models can classify questions, propose product identity candidates, retrieve source passages, compare source-linked facts, explain approved terms, draft localized answers and surface missing evidence, but cannot create product truth or take action.

  • Intent and product-candidate ranking with ambiguity visible
  • Source passage and claim extraction with exact citations
  • Conflict, stale-field and compatibility-evidence gap summaries
  • Customer answer, disambiguation question and escalation-note drafts
03

Human product and safety authority

Qualified people own product identity exceptions, source corrections, claim approval, compatibility, safety and regulatory interpretation, market and support policy, translations, remedies, customer communication and stop decisions.

  • Product, variant, pack, revision and source-of-truth decisions
  • Claim, certification, compatibility, warning, instruction and translation decisions
  • Safety, recall, market, warranty, return, substitute and customer-remedy decisions
  • Catalog correction, affected-answer notification, service resolution and retirement authority

Product-answer components

Build a product-to-correction ledger, not a catalog chatbot.

A catalog row, compatibility assertion, inventory event and customer answer have different lifecycles.

01

Identity and product graph ledger

Bind organization, brand, manufacturer, family, model, trade item, seller SKU, manufacturer part, variant, pack, lot, serial, hardware and software revisions and market to typed family, contained, bundle, accessory, consumable, spare, equivalent, alternate, substitute, successor and replacement relations.

Operating contract: Name is not identity, valid key is not authenticity, family is not variant, unit is not pack, product is not instance, seller SKU is not universal, related is not compatible, alternate is not equivalent, successor is not replacement for every use and possession is not proven by a product lookup.

02

Claim, source, and policy ledger

Preserve atomic attributes, specifications, materials, dimensions, ratings, instructions, warnings, certifications, marketing and warranty claims by source, passage, product and market scope, unit, condition, version, language, review, expiry, challenge, correction and supersession.

Operating contract: Supplier text is not approved claim, badge is not certification, typical is not guaranteed, nominal is not measured, normalized value is not original wording, translation is not authority, current source is field-specific and fluent summary is not evidence.

03

Compatibility, safety, and commerce ledger

Record directional compatibility conditions, tests and support state plus warnings, recalls, market eligibility, inventory positions and events, exact offer, price, unit, currency, tax, fees, location, freshness and unknown state.

Operating contract: Shared connector is not compatibility, fit is not safe use, absence is not support, listing is not market eligibility, warning is not risk assessment, event is not balance, on-hand is not sellable, available-to-promise is not delivery guarantee and product information is not a customer offer.

04

Answer, escalation, and correction ledger

Store question and requester scope, resolved identity, source packet, atomic claims and citations, wording, uncertainty, approval, generation, display, access, challenge, accepted escalation, corrected source, invalidated answers, notification, re-answer and realized service evidence.

Operating contract: Draft is not approved, generated is not displayed, displayed is not understood, link click is not purchase, assigned case is not accepted ownership, corrected source is not repaired customer knowledge, no repeat contact is not satisfaction and later outcome is not assistant causation.

Delivery path

Prove one product family through corrections, not only happy answers.

Start with a bounded family whose variants, manuals, compatibility, stock and customer questions can be replayed.

  1. 01

    Choose one bounded question set

    Select one product family, market, channel and the attribute, setup, compatibility, safety, availability or price questions in scope; name catalog, product, engineering, safety, regulatory, inventory, pricing, support, localization and stop owners.

  2. 02

    Map identities, sources, and corrections

    Inventory identifiers, variants, packs, revisions, manuals, claims, warnings, compatibility matrices, policies, inventory and price services; trace field authority, versions, units, languages, access, conflicts, correction and recall paths.

  3. 03

    Build claim and abstention gates

    Encode exact identity, field authority, effective-time, unit and localization checks, directional compatibility, safety escalation, inventory and price freshness, atomic citations, ambiguity questions and unsupported-case abstention.

  4. 04

    Pilot with adversarial product cases

    Use sanitized wrong-variant, stale-manual, misleading supplier claim, compatibility gap, recalled lot, stock conflict and injected-document cases; let qualified reviewers score claims, citations, wording, escalations and correction behavior.

  5. 05

    Release narrowly and close the correction loop

    Permit only proven low-risk question classes, monitor exact-product and claim coverage, require accepted handoffs and propagate source corrections through invalidation, notification and re-answer before expanding scope.

Release controls

Six controls before a product answer can be trusted.

More catalog content cannot repair an ambiguous variant or a source with no authority for the requested claim.

Identity matches the answer granularity
Bind family, model, trade item, SKU, part, variant, pack, lot, serial, revision, software, market and installed context as required; preserve issuer namespaces and ask when candidate products produce different answers.
Every claim has field-specific authority
Link atomic facts to source passage, product and market scope, version, effective time, unit, conditions, language, rights and review; expose conflicts, expiry, corrections and supersession instead of applying one global source rank.
Compatibility is directional evidence
Require exact source and target, purpose, interface, dimensions, ratings, protocol, software, firmware, region, installation, adapters, exclusions, test or bulletin, issuer and support state; never infer safety from similarity or fit.
Safety and policy can stop the answer
Retrieve current warnings, instructions, recall or corrective state, market eligibility and qualified policy for the exact product; preserve controlled wording and route consequential, unsupported or conflicting use to accountable people.
Inventory and price are live scoped services
Query the exact item, location and offer at answer time, distinguish physical, system, reserved, allocated, sellable and available-to-promise states and bind price to currency, unit, tax, fees, eligibility and effective time with visible freshness.
Corrections reach dependent answers
Store source-linked claims and recipients or sessions only as permitted, accept challenges, require qualified source correction, invalidate affected answers, notify or re-answer where policy requires and measure correction latency and repeat harm.

Proof model

Measure exact-variant truth and repair, not answer volume.

A fast answer can reduce a contact while increasing returns, setup errors or safety risk.

Baseline

  • Organizations, brands, manufacturers, product families, models, trade items, SKUs, parts, variants, packs, lots, serial classes, hardware and software revisions, markets, channels, languages, question classes, source systems and owner groups
  • Current identifier and variant ambiguity, field-source coverage, source age and conflicts, unit and language transformations, claim expiry, compatibility evidence, warnings, recalls, inventory and price freshness and correction latency by material cohort
  • Current exact-product answer accuracy, atomic claim and citation coverage, disambiguation, abstention, unsupported compatibility blocks, safety escalation, localization and accessibility findings plus reviewer changes and burden
  • Current display and access, accepted escalations, repeat contacts, catalog corrections, invalidated answers, customer notifications, returns, complaints, setup or service outcomes kept separate from assistant causation

Outcome evidence

  • Correct product, variant, pack, lot, revision, software and market resolution, authorized field access, complete source and version lineage, unit and condition preservation, conflict exposure and minimal disambiguation
  • Accurate atomic claims with inspectable citations, approved wording and localization, directional compatibility evidence, correct safety and policy blocks, current inventory and price scope and appropriate abstention
  • Accessible direct answers, honest uncertainty and freshness, accepted qualified escalations, low unsupported-action rate, replayable delivery, effective challenge handling, source correction, answer invalidation, notification and re-answer
  • Customer comprehension, repeat contact, product selection, setup, return, complaint and service outcomes measured separately, with inventory, price, product, policy and channel changes visible and causal value withheld without suitable comparison

Guardrails

  • Wrong tenant, family, model, trade item, SKU, part, variant, pack, lot, serial, revision, software or market; valid identifier assumed authentic; image or name merged; account, order, warranty or unpublished field exposed; ambiguity hidden
  • Supplier text called truth, badge called certification, expired claim used, unit or tolerance dropped, translated warning changed, community content outranks manufacturer correction, injected manual controls retrieval, conflict silently resolved or citation points to wrong version
  • Related called compatible, shared connector called safe, direction reversed, firmware or adapter omitted, unsupported use recommended, recalled lot missed, listing called eligible, event called stock, on-hand called sellable, stale price quoted, another location or variant substituted
  • Model decides safety, compliance, warranty or remedy, reserves stock, changes catalog or price, escalation assignment called acceptance, corrected source not propagated, customer not notified where required, non-return called suitability or fewer contacts and sales attributed without evidence

Fit test

Use this pattern when product truth can be versioned and corrected.

Good reason to begin

  • One bounded product family and market has named catalog, product, engineering, safety, regulatory, inventory, pricing, commerce, support, localization, accessibility, correction and stop owners with review capacity.
  • Stable family, model, trade-item, SKU, part, variant, pack, lot, revision and software identifiers plus field authority, effective versions, units, languages, market rules and access boundaries are explicit.
  • Compatibility relations have directional product, interface, revision, condition, test and support evidence, while warnings, instructions, recalls and consequential questions have qualified escalation routes.
  • Exact item-location inventory, offers, price, answer delivery, challenges, source corrections, affected answers, notifications, re-answers and later service outcomes can be replayed from the answer-time packet.

Resolve before beginning

  • Product identity, variant granularity, source ownership, units, market, language, compatibility authority, warning or recall source, inventory freshness, price service, escalation owner or correction path is undefined.
  • The process cannot distinguish family from variant, unit from pack, claim from source text, related from compatible, fit from safe, listing from eligibility, inventory event from sellable balance or generated answer from customer understanding.
  • Safety, regulated use, unsupported configurations, warranty and remedy questions have no qualified owner, or catalog corrections cannot invalidate and repair answers already delivered.
  • The assistant is expected to infer identity or ownership, browse arbitrary sources, invent product facts, certify compatibility, diagnose safety, trust stale stock, quote unscoped price, modify catalogs, reserve items, approve remedies or promise service and commercial outcomes.

Source basis

Sources behind the control model.

  • 01

    GS1

    Global Data Model 2.18.0

    GS1 lists version 2.18.0, published 21 August 2026, as the current Global Data Model for standardized product attributes and code lists in specified fast-moving consumer-goods categories. It does not cover every sector or product, authenticate a provider or identifier, guarantee record completeness or currentness, choose local field authority, prove an exact item match or compatibility, supply inventory or price, approve customer wording or prove an answer or outcome.

  • 02

    GS1

    GS1 Web Vocabulary 1.18.0

    GS1 describes its current Web Vocabulary, version 1.18.0 published 1 June 2026, as linked-data terms for consumer-facing product properties, offers, parties and related resources, including product relationships. A vocabulary term or supplier-defined relation does not authenticate a source, prove the physical item, make data complete or current, establish directional compatibility or safe substitution, authorize a claim, determine inventory or price, certify compliance or prove customer outcome.

  • 03

    GS1

    EPCIS 2.0.1

    GS1 lists EPCIS 2.0.1, published 1 July 2025, as the latest version of its standard for sharing supply-chain visibility events with business context. It does not authenticate an event producer, guarantee identifier mapping, completeness, ordering or current location, provide a sellable inventory balance or customer promise, establish product attributes or compatibility, authorize disclosure or action, certify safety or prove answer or outcome.

  • 04

    EUR-Lex

    Regulation (EU) 2023/988 on general product safety, consolidated 29 May 2026

    The current consolidated EU General Product Safety Regulation addresses consumer-product safety, interconnection considerations, online and distance-sale product identification, manufacturer or responsible-person details, warnings, recalls and accessible safety information within its scope. It does not govern every product, jurisdiction or sector-specific duty, identify a particular item, verify source truth, approve compatibility, instructions or wording, determine inventory, price, warranty or remedy here, replace qualified review, certify compliance or prove safer use or outcome.

[ WORKFLOW / SYSTEMS AUDIT ]
THE FIRST ENGAGEMENT

Start with one real workflow

A Systems Audit is the usual starting point. If the opportunity is already clear, we can move directly into a focused build.

Show Us the WorkflowStart with the free automation readiness checklist

OBSERVEQUANTIFYDECIDEBUILD

Continue with the work

Choose the next useful path.

Stay with the operating question. The technology can wait until the work is clear.

01

Explore governed AI agents

Compare other bounded agent patterns and the evidence, authority and recovery contracts they require.

Open path02

Design governed knowledge workflows

Connect source authority, permissions, retrieval, review, correction and retirement across organizational knowledge.

Open path03

Build retail and commerce systems

Frame catalog, inventory, offer, order and customer workflows around operational truth and measurable outcomes.

Open path04

Separate order facts from product facts

Answer authorized order questions at line and package scope without turning commercial or carrier state into product truth.

Open path