datawebotDrHyman.com product data: fields, formats and bundles
Map DrHyman.com store products, vendor and SKU fields, package variants, supplement-facts grain, catalog facets, stacks, and recurring offers.
Separate the store listing, vendor, SKU and package option
DrHyman.com presents a mixed store catalog: a listing can carry a third-party vendor label, a source SKU and a selectable package. Keep those identities separate so a store page is not misread as a manufacturer record. The official Vitamin D Supreme listing, for example, names Designs For Health and shows SKU DFH-VDSUPRM60; capture the exact displayed value rather than inferring a code pattern.
Scroll to compare →
| Catalog entity | Source evidence to retain | Modeling boundary |
|---|---|---|
| Store listing | Product title and canonical product URL | One page is a store record; it does not establish who manufactures the item. |
| Brand or vendor | Exact brand/vendor label displayed on the listing | Keep the source label distinct from the store and from Mark Hyman as a person. |
| Source SKU | SKU string, such as DFH-VDSUPRM60 where shown | Preserve punctuation and capitalization; do not derive an ID from the name. |
| Package option | Selected count, size or other selectable package value | Keep each selected option tied to its displayed SKU and URL when the source provides them. |
| Product type | Supplement, multi-item stack, book, course or other listed type | Do not apply supplement-only fields to the entire store catalog. |
Read store filters as facets, not product evidence
The Shop All page groups items by health-benefit topics, dietary needs, delivery form and brand, while the same catalog also includes books and courses. These are useful navigation dimensions, but a filter label is not a verified ingredient, certification or clinical conclusion. Store the displayed facet separately from the product's own facts panel and source wording.
Scroll to compare →
| Displayed facet | Useful catalog field | Keep separate from |
|---|---|---|
| Health-benefit topic | Source category name and category URL | Ingredient composition, evidence quality or a claim about an outcome. |
| Dietary needs | Exact filter labels shown for the listing | An independently verified allergen statement or certification. |
| Delivery form | Source form label such as capsule, powder, liquid or book/course | Package quantity, serving size or product category. |
| Brand | The brand value associated with the store filter and item | Store operator, product-page author or manufacturer unless the source says so. |
| Catalog content type | Supplement, book, course or stack relationship | A single product schema that assumes every listing is a supplement. |
Keep supplement facts at serving and package grain
A product facts panel describes a serving; the package describes how many servings it contains. The reviewed Vitamin D Supreme listing displays both fields and has separate package-size options. Preserve this relationship in the data model, without converting it into a recommended dose or comparing products on a health basis.
Scroll to compare →
| Field group | Capture at source grain | Why it matters |
|---|---|---|
| Serving definition | The panel's serving size and its unit, exactly as displayed | An amount per serving cannot be compared with a package count on its own. |
| Package count | Servings per container and the selected package option | The same title can refer to more than one container size. |
| Fact-panel row | Ingredient or nutrient name, amount, unit and any displayed percent daily value | Keep each value attached to the panel and selected variant where applicable. |
| Panel notes | Asterisk, daily-value marker and footnote text | Symbols can change the meaning of the percent or amount column. |
| Other ingredients | The distinct other-ingredients statement | Do not merge it with active ingredient rows or turn it into a dietary guarantee. |
| Safety and disclaimer text | Source statements as a separate text block with page and observation date | Preserve context without editorializing or giving medical advice. |
Model stacks and recurring purchases as separate relationships
A stack groups component products; a subscription describes a repeat-purchase plan. Neither should be flattened into a single product variant. The Store FAQs also note that a stack may wait to ship while a component is out of stock, so a component listing is not proof that the bundle is immediately fulfillable.
Scroll to compare →
| Record | Fields to keep | Do not infer |
|---|---|---|
| Stack or kit | Parent listing, named components, component product URLs and observed membership | That every component is independently orderable or permanently included. |
| Component product | Its own title, vendor, SKU, package and facts-panel fields | A bundle's contents from the bundle name alone. |
| One-time offer | Displayed amount, currency, selected option, market and observation time | A durable price or an offer available to every visitor. |
| Subscription offer | Recurring-plan label, selected interval, displayed terms and observation time | A one-time purchase or a product variant. |
| Availability and fulfillment | Source state by item/stack, market and capture time | That an in-stock component makes the complete stack ready to ship. |
Keep the store, health publisher and related organizations distinct
DrHyman.com publishes articles, recipes and programs alongside a store. Its Store FAQs describe the UltraWellness Center team's role in product selection and state that the store and Function Health are independent companies despite a shared founder. The store's dated Terms page describes educational content and supplement disclaimers; this page models catalog information and makes no health recommendation.
Scroll to compare →
| Entity or statement | Source-grounded treatment | Boundary for product data |
|---|---|---|
| Dr. Mark Hyman | Person and public-facing physician/educator identity | Not interchangeable with a specific store item or its vendor. |
| DrHyman.com store | The retail catalog and its displayed product records | Record the actual store listing, facets and terms separately. |
| UltraWellness Center | The FAQ describes its clinical team as selecting store products | This does not make the clinic the manufacturer or seller of every item. |
| Function Health | The FAQ describes it as an independent company from the store | Do not join its membership or services to DrHyman.com product records. |
| Health statements | Attribute text to the exact product page and date if it must be retained | A store category or endorsement is source attribution, not independent medical evidence. |
Questions about DrHyman.com catalog data
These answers clarify the store's data structure; they are not supplement or health advice.
Scroll to compare →
| Question | Answer | Useful data distinction |
|---|---|---|
| Is every item a Mark Hyman-branded product? | No. The store's catalog includes a brand facet and product listings that display third-party vendors. | Keep store, vendor and brand as separate values. |
| Why store serving size and servings per container separately? | One describes the facts-panel serving; the other describes the package count. | Do not turn package size into dosage guidance. |
| Do a health-topic filter or dietary label prove ingredients or efficacy? | No. They are source-displayed catalog facets and should remain attributed labels. | Keep filters apart from the facts panel and independent evidence. |
| Is a stack just a variant of one supplement? | No. A stack is a parent grouping with component product relationships; a package option belongs to an item. | Preserve the parent, its components and each item's own options. |
| Should one-time and subscription offers share one price field? | No. They are different purchase plans and can have different intervals or terms. | Store offer type, currency, market and observation time together. |
Content reviewed 2026-10-07.