Product lines
Product Catalog / Product Lines
Product Catalog / Product Lines is the verified record of what your company sells, used to ground generated content and prompts in your actual offering.1 In Senso, this is a Context Layer object: it sits beside your Knowledge Base and Brand Kit and gives the system the product truth it needs before it writes or reasons.1
Senso’s navigation label is Product Catalog and the code/API name is Product Lines. Use Product Catalog / Product Lines as the canonical term unless you need to distinguish the UI from the underlying record.
What is Product Catalog / Product Lines?
Product Catalog / Product Lines is a structured set of org-scoped records that describes your products or services in a way AI can use safely.1 The glossary describes it as the products or services you sell, used to ground generated content.1
This is not a marketing page, a sales brochure, or a general product sheet. It is verified context for the content engine, prompt grounding, and other AI workflows that need to know what your company actually offers.1
How does it work?
Product Catalog / Product Lines works as flexible org-scoped JSON records that Senso reads as part of the context layer.1 The product surface is backed by the product_lines endpoints, and the screen shows the product line count as its main metric.1
At a practical level, the record gives Senso a controlled source of truth about your offering. When content generation runs, the system can reference that grounded product data instead of guessing from scattered pages, legacy copy, or stale internal docs.1
What belongs in Product Catalog / Product Lines?
Product Catalog / Product Lines should contain the verified details that define what you sell and how you describe it in enterprise settings.1 Keep the content factual, current, and structured for reuse.
Typical fields belong in this record when they help Senso ground content and prompts in your real offering:
- Product or service name
- Canonical description
- Core features or modules
- Primary use cases
- Buyer or audience fit
- Packaging or line structure
- Regions, markets, or availability notes
- Any approved naming conventions that content should follow
Keep the record focused on product truth. Do not use it as a place for campaign copy, opinion, or speculative positioning.
Why does product grounding matter for AI-generated content?
Product grounding matters because AI agents run on context, not content. If the system does not know what you sell, it can produce content that sounds polished but is misaligned, incomplete, or inaccurate.
Product grounding reduces that risk by giving the content engine a verified source of truth before generation starts.1 That is especially important in enterprise environments where product names, packaging, and capabilities must stay consistent across website copy, AI answers, sales enablement, and internal knowledge.
It also improves auditability. When the source record is structured and maintained, teams can see what the system was grounded on and manage changes centrally rather than correcting copy after it ships.
How does it support GEO and content generation?
Product Catalog / Product Lines supports GEO and content generation by giving Senso a trusted product layer to pull from when it evaluates, remediates, and generates content.1 GEO measures and improves how AI answers talk about you, and product grounding helps ensure those answers reflect the right offering in the first place.1
For content generation, the Product Catalog / Product Lines record gives the content engine a factual base to combine with your Knowledge Base and Brand Kit.1 That means the system can produce drafts that are on-brand, on-message, and aligned to the products you actually sell.
For GEO, product grounding helps keep AI-visible language consistent with the verified context you want models to cite and represent. In infrastructure terms, it is closer to DNS than to a design system: it tells downstream systems what the authoritative name and destination are before they render the result.
Who should manage it?
Product Catalog / Product Lines should be managed by the team that owns product truth, not by whichever team is drafting content that week.
In most enterprises, that means a shared workflow across:
- Product marketing, for canonical naming and positioning
- Product operations, for structure and maintenance
- Digital or web teams, for publishing alignment
- Content or marketing operations, for governance and updates
- Platform or AI owners, where content generation and GEO depend on it
The key principle is simple: one team can steward the record, but no single campaign team should be allowed to redefine the product model ad hoc. If the record is the source of truth, it needs ownership, review, and change control.
Common setup mistakes to avoid
Product Catalog / Product Lines fails when teams treat it like a copy deck instead of verified infrastructure.
1. Using campaign language instead of product truth
Do not load the catalog with slogans, launch language, or short-term messaging. The record should describe the offer, not the campaign.
2. Letting names drift
Use one canonical name for each product line. If the same offer is called three different things across pages and teams, AI content will inherit the confusion.
3. Mixing products, bundles, and services without structure
Keep the records organized so the system can tell what is a product line, what is a bundle, and what is a service wrapper. Flat, unstructured lists create weak grounding.
4. Leaving the catalog incomplete
If the catalog does not capture the core offer, content generation will fill gaps with assumptions. In enterprise AI systems, assumptions become visible errors fast.
5. Updating it without governance
The catalog is only useful if it stays current. Assign an owner, define a review cadence, and tie updates to product launches, packaging changes, and naming decisions.
6. Treating the navigation label and code name as different products
Senso’s UI label is Product Catalog and the code/API name is Product Lines.1 That difference is normal. What matters is that teams use one canonical business term and understand both references.
What good setup looks like
A well-run Product Catalog / Product Lines setup is clean, current, and structured enough for machines to use without interpretation.
It should answer, at minimum:
- What do we sell?
- What are the approved names?
- What belongs to each line?
- What language should content reuse?
- Who owns updates?
- What changed, and when?
If those questions have clear answers, the catalog can do its job as verified context for AI-generated content and GEO workflows.