Skip to main content
Use Kina to turn verified product facts into clearer descriptions, care guidance and answers to customer questions. This guide takes one product from its source facts to a reviewed edit, then explains how to check the result.

​
Choose a small starting set

Pick one product or a bounded group with a clear problem: missing care instructions, a vague material description or inconsistent tone. Name the product so Kina can use the correct source. Try:
Review this product description for clarity. Keep the verified material, dimensions and care facts. Use our brand guidance, flag unsupported claims and show a before-and-after draft. Prepare the change for review.

​
Inspect the draft

Check that sizes, composition, compatibility and care instructions match the source. Promotional language can accidentally become a factual promise. Terms such as “certified”, “waterproof” or “guaranteed” need evidence appropriate to the product. If a fact is missing, ask for the gap to be identified. Do not fill it with plausible wording. A shorter description that preserves the facts can be better than a longer unsupported one.

​
Prepare the source pack

You need the correct product record, current brand guidance and evidence for any factual claims. Start with the supported catalogue read. If relevant guidance is missing, identify it before drafting rather than asking Kina to invent a complete specification. Create a short factual checklist:
  • Material or composition, using the product’s own source.
  • Dimensions, size or compatibility where verified.
  • Care, use or safety instructions where applicable.
  • A customer question the description should answer.
  • Any phrase requiring evidence, such as a certification or performance promise.
Brand tone shapes how you explain these facts. It does not authorise new facts.

​
Work through a fictional product

North Coast Goods sells a cotton-blend overshirt. The current description says “A premium everyday essential”. The source gives the blend and a washing instruction but does not substantiate an environmental claim. Ask Kina:
Use the connected product facts to explain the material and care more clearly. Keep the wording plain and practical. Show the existing and proposed description, list the source facts you retained and flag anything you could not verify.
A useful draft replaces vague praise with the supported facts. It keeps “cotton blend” rather than converting it to pure cotton, preserves the correct washing instruction and omits unsupported certification language. Then refine: “Keep the opening to one sentence and make the care instruction easy to find.” This remains preparation. When you are satisfied, ask for the supported product change to be prepared for review.

​
Apply only the intended fields

Open the proposed change in Approvals. Check Before and After for every affected field and product. Confirm that the request did not expand from a description into a title, price or other unrelated change. Read whether your confirmation also makes the change or whether a separate execution control follows. After the effect, inspect View receipt. Verify the individual result and the provider record where appropriate. If one product’s source changed, resolve that item without assuming the whole batch completed.

​
Evaluate what the edit achieved

A good immediate outcome is accurate, clearer content on the intended record. A commercial outcome requires a separate measurement. Before judging performance, define the metric, dates and comparable baseline. If a promotion, traffic mix or stock level changed, retain those qualifications. An increase after the edit is not by itself proof that the wording caused it. Use Readouts or the available Results evidence to inspect the calculation and coverage.

​
Assess AI-shopping readiness

Where Growth Engine → Discovery is enabled, use the AI-shopping readiness information to find a concrete next job. Inspect the current report, its source and the product-level issues before asking for repairs. If a catalogue scan is available to your role, use it to check the current catalogue; a scan reads and assesses information rather than publishing a product change. Keep two questions separate. Catalogue readiness asks whether product information is present and usable: descriptions, images and their alt text, search titles and descriptions, tags, variant SKUs and relevant shop policies. Shopping or transaction readiness can assess a different set of protocol and purchase requirements. Improving a description does not establish that a shopping assistant can complete a purchase. Start with an issue the evidence supports. For example, a linen shirt might have a short description and images without alt text. Ask Kina to draft a factual description from its verified material and care facts, and describe what each photograph shows. Review the product identity and changed fields before applying any supported repair. A product with stock but not published may be deliberately held back; investigate that decision before requesting publication. A readiness score summarises the checks performed. It is not a guarantee of an AI recommendation, search ranking, checkout compatibility or sales. More words alone do not make content accurate. Missing or unavailable evidence is also different from a failed check: resolve source access before treating an incomplete report as a poor catalogue. After an approved repair completes, check the receipt and refresh the assessment through the available control. Compare the specific issue before and after, alongside the headline score. A better score demonstrates a change in those checks; measure discovery and commercial results separately.

​
Targeted recovery

If the product cannot be found, verify the company, source and product identity. If facts disagree, stop the factual rewrite and ask for the conflict to be shown. If the proposal expires, prepare and review a current version. If the execution result is uncertain, inspect the receipt before repeating the request. If the change was wrong, use the supported reversal when available rather than assuming every content field can be restored. Reviewed 2 October 2026.