Build Product Knowledge

#Product Knowledge is the Affiliate source of truth

Product Knowledge keeps the product instructions, common answers, and creative references the Agent may use in one place. It supports initial outreach, Creator replies, creative guidance, and follow-up. A Campaign defines the business goal; Product Knowledge keeps the facts used in communication consistent.

Open Affiliate → Product Knowledge. The library shows document state, coverage of the three content sections, linked Products, revision information, and freshness.

APP CAPTUREThe English light-theme Product Knowledge library with document state, content coverage, and Product bindings.

#1. Build the three content sections

Each knowledge set has three independent sections.

#Usage Instructions

Record positioning, intended audience, usage, specifications, cautions, fulfillment, and Sample rules. Prefer facts the team can verify and that will remain stable enough to maintain.

#Q&A

Write approved answers to common Creator questions: commission framing, Sample conditions, target markets, content rights, and delivery requirements. When an answer depends on judgement, state when the Agent must escalate.

#Popular Videos and Creative Cases

Capture effective content angles, hooks, use cases, assets, and performance observations so the Agent can discuss creative options with Creators.

APP CAPTUREThe English light-theme Creative Cases editor, organizing direction, performance observations, and assets.

Cases are inspiration, not a guarantee that another Creator will reproduce the same result. Do not convert one video’s performance into a promised outcome.

#2. Use Markdown for maintainable content

The editor supports headings, lists, and links. A maintainable knowledge set should:

• keep each fact in one canonical place;
• separate specifications, policy, prohibited claims, and human-handoff conditions with clear headings;
• record the reason and date when an operating rule changes;
• remove obsolete facts instead of appending contradictory notes.

Saving checks the revision to reduce the chance that simultaneous edits overwrite newer content. If a revision conflict appears, reload the latest version and merge the intended change.

#3. Use an Internal product code across Shops

When creating or editing Product Knowledge, you can add an Internal product code. It represents the same business Product in your own catalogue and does not need to match a TikTok Product ID or Seller SKU. For example, listings in US and UK Shops may use different Seller SKUs while sharing the code BLENDER-CORE.

Use 1–64 letters, numbers, dots, underscores, or hyphens. The code must be unique within the account. Archived Product Knowledge keeps its code reserved so an old Product identity is not accidentally reused for a new document.

The code does not create Product links by itself. It gives cross-Shop listings one business identity; the binding step below still records the exact Product in each Shop. Once linked, Manual Workbench can use the Internal product code to filter Sample Applications for all of those listings together.

#4. Discover and bind Products by Seller SKU

Enter a Seller SKU in the binding area to search across Authorized TikTok Shops. Seller SKU matching is exact and case-sensitive. Verify the candidate Product, Shop, and Product ID before binding.

APP CAPTUREThe English light-theme Product Knowledge bindings with Seller SKU discovery and cross-Shop Products.

Once linked, Shop ID and Product ID form the durable binding. One knowledge set can link the equivalent Product in several Shops, allowing the team to maintain one set of facts.

When markets have different specifications, prices, or compliance rules, do not force reuse. Create separate knowledge so the Agent cannot cite one market’s rule in another.

#5. Connect knowledge to real work

Product Knowledge supports:

• factual content in Campaign opening messages and follow-ups;
• answers to Creator questions about specifications, use, or collaboration;
• creative guidance and case references;
• post-Sample content follow-up.

It does not override the Campaign offer or bypass Approval Policy. A benefit written in Product Knowledge is still not authorized if the Campaign does not grant it.

A BD signing in with an individual login can open and read Product Knowledge but cannot create, edit, archive, restore, or change Product bindings. The account owner or Affiliate supervisor maintains these account-wide facts so separate BDs do not rewrite them independently.

#6. Archive, restore, and unlink

• Archive: stop using a document for new work while retaining history and revisions.
• Restore: return an archived document to active use.
• Unlink Product: remove a Product association without deleting the knowledge set.

Before archiving or unlinking, check whether an active Campaign still uses that Product. When replacing knowledge, finish and bind the new document before switching ongoing work.

#Maintenance rhythm

Collect recurring questions from Creator messages, Sample reviews, and Pending cases every week. Update immediately when specifications, offers, or policies change. Once a month, review bindings, freshness, and obsolete cases. Reliable Product Knowledge lets the Agent complete more routine communication while human review stays focused on genuine commercial judgement.