Skip to main content
Eligible orders over US$80 ship free by sea No minimum order US · UK · CA · AU
P078 · C56 Ingredient↔Format Hub · index, follow · automatic filter URLs remain utility crawl-space and should canonicalize to the hub.
Ingredient ↔ Finished Format Map · C56

Browse Herbs by Product Format

See where released herbal ingredients actually appear—tea, food, paste, incense, topical or moxa—without confusing ingredient presence with efficacy or turning this reference hub into a duplicate shop category.

The same botanical ingredient can appear in very different finished-product formats. A herb used in tea is not automatically equivalent to the same herb in incense, a topical oil, a foot soak, a warming patch or moxa.

Presence ≠ EfficacyFormat ≠ Plant PartSame Herb ≠ Same ExposureScent Name ≠ Formula Proof
Relationship rule: P078 only renders verified Ingredient Entity ↔ Released SKU ↔ Format relationships. Product titles, scent names and traditional use are not enough to infer composition.

Direct Answer

A product format describes how a finished product is presented or used. Tea, food, incense, topical and moxa are different exposure contexts. Ingredient presence in a format is a relationship fact—not evidence that every product in that format has the same composition, safety or health effect.

Current architecture

Format Overview

Counts are deliberately omitted until verified relationship records are loaded. Shop pages own transactions; P078 owns discovery and relationship context.

T

Tea & Drink

Ingestion context with preparation, caffeine, serving, allergen and product-label considerations.

Shop Herbal Tea →
F

Foods / Pastes

Botanical foods, pastes and drink mixes require current formula/BOM and food-label relationships.

Explore Foods & Pastes →
I

Incense

Aroma and combustion context. A scent name alone is not proof that the named botanical material is present.

Shop Chinese Incense →
Live verified relationships

Ingredient ↔ Format Registry

Only public relationships backed by current formula/BOM, label/specification or released product records should render.

No verified public Ingredient ↔ SKU ↔ Format relationships are loaded in this static preview. P078 remains indexable; unverified ingredient cards and fake counts are not shown.
Three different questions

Presence, Amount & Benefit Are Not the Same Thing

The relationship layer must not silently upgrade “present in formula” into “meaningful dose” or “proven effect.”

1 · Presence

Is the ingredient actually there?

Use current BOM, formula, label or verified material record. Scent name and product title are not enough.

2 · Amount

How much is present?

Only show a percentage, serving or amount when the current product specification discloses it.

3 · Claim

What does the evidence support?

Ingredient presence alone does not establish efficacy, safety or a market-authorized finished-product claim.

Example: “Sandalwood scent” ≠ verified Santalum material. “Mugwort moxa” ≠ mugwort tea. “Used topically” ≠ safe to ingest.
Canonical routing

Which Page Owns Which Question?

P078 is intentionally narrow so it does not cannibalize plant-part, safety, entity or commerce pages.

Plant Part

Which material part?

Root, rhizome, leaf, flower, fruit, seed and other material identity belongs to P077.

Browse Plant Parts →
Safety

What changes with exposure?

Use ingredient/product safety owners; P079 handles cross-herb principles.

Herb Safety →
Format changes safety context

Same Herb, Different Exposure

The same botanical name across formats does not create an equivalent exposure, dose, preparation or risk profile.

Tea / Food

Ingestion

Serving, caffeine, nutrition, allergens and market food-use rules matter.

Extract / Paste

Concentration

Concentration and serving may differ from a tea or whole-food use.

Topical

Skin Exposure

Local irritation, allergy and intended external-use instructions matter.

Incense

Combustion

Formula, smoke, ventilation, fire and product instructions matter.

Moxa

Heat + Smoke

Moxa is a distinct heat/combustion format with its own safety owner and home-use rules.

SEO & filter governance

Browse Without Duplicating Shop or Creating Thin URLs

Format filters are useful UI states, but they do not automatically deserve separate indexed landing pages.

P078 Hub

  • /ingredients/product-formats/ → index, follow
  • explains the relationship model
  • shows verified Ingredient ↔ SKU ↔ Format records
  • links outward to canonical product/category pages

Automatic Filters

  • ?format=tea
  • ?format=incense
  • ?format=topical
  • default noindex / canonical back to P078 unless a future landing page independently earns value
Format questions

Frequently Asked Questions

These answers keep ingredient identity, product format, amount, safety and shopping intent separate.

What are common herbal product formats?

Tea, foods and pastes, incense, topical products and moxa are major formats in the current SanYuan architecture.

Is product format the same as plant part?

No. Plant part describes the material identity; product format describes how the finished product is presented or used.

Can the same herb appear in multiple formats?

Yes, when real records support those relationships.

Does it work the same way in every format?

Do not assume so. Exposure route, amount, formulation, evidence and safety context differ.

Can topical ingredients be swallowed?

Not unless the exact product is intended for ingestion.

Does incense scent prove the botanical is present?

No. A fragrance or scent name is not sufficient formula proof.

Can I see exact ingredient percentages?

Only where current label or specification data discloses them.

Does appearing on P078 prove a health effect?

No. It proves only the verified relationship shown.

Can I buy products here?

Use the linked current Shop category or product page. P078 is primarily a relationship and discovery hub.

Why are filter URLs noindex?

Because they are utility combinations unless they independently earn a unique, useful landing page.