datawebotSpice product data: origin, harvest and package size
A source-attributed guide to spice origins, producer relationships, package quantities, harvest and mill labels, and dated availability.
The catalog mixes spices, pantry products, bundles and nonfood items.
Diaspora Co.’s current shop separates whole spices, ground spices and spice blends, and also shows categories for tools and swag, bundles and a cookbook. Product and kit pages can include tea, beverage mixes and pantry goods. These are examples from the live catalog, not a permanent taxonomy: classify each page by its current source labels rather than treating every entry as a spice.
Scroll to compare →
| Catalog item | Record it as | Do not assume |
|---|---|---|
| Whole or ground spice | A product with its source-named type, variety, form and selected package | Whole and ground forms are not interchangeable product variants unless the page groups them that way. |
| Blend or seasoning | A separate formula with its own product identity and source-listed ingredients | A blend is not a single-origin crop simply because it contains a named spice. |
| Tea, beverage mix or pantry food | The page’s product class and package, with its own ingredient and advisory fields | Do not force pantry or beverage products into a spice-only category. |
| Bundle, sampler or kit | The bundle as a parent record plus each named component and package quantity | Do not turn bundle contents into one formula or one package size. |
| Tools, cookware, books or merchandise | A nonfood catalog item with its own type and options | It has no spice-origin, harvest or ingredient fields unless the page explicitly supplies them. |
A growing place, a grower and a sourcing partner are different fields.
A region label does not identify who cultivated or gathered an ingredient, and a sourcing collective is not automatically the producer. The following relationship examples are Diaspora Co.’s descriptions on the linked pages, checked 2026-09-30; they do not independently verify the contents of a particular tin or lot.
Scroll to compare →
| Source page example | Place and source-stated relationship | Keep separate |
|---|---|---|
| Nandini Coriander | The product page names Shedubhar, Gujarat, and the Sakariya family farm. | Product/variety, locality and farm relationship; do not attach this story to every coriander product or every package lot. |
| Wild Heimang Sumac | The page identifies Ningthi, Manipur, wild sumac on the Ukhrul hillsides, foraging by Tangkhul community members, and Hillwild as a community sourcing collective. | Species, wild collection, place, foragers and sourcing partner; do not flatten these roles into one farm field. |
| Sourcing Map entry | A product-to-place association as the company currently publishes it. | Keep the map page and observation date; do not infer a named grower where the map supplies only a region. |
Product form, ingredients and package quantity belong at different levels.
Keep a stable product identity beside the selected form and the exact package observed. On the Nandini page checked 2026-09-30, the displayed options are 30 g Everyday Tin and 115 g Chef Tin. Those are dated source labels, not current price or availability claims. The same page presents Ingredients and Allergen Warning separately; a recipe mention is not a complete product ingredient declaration.
Scroll to compare →
| Field | Useful source value | Comparison or attribution rule |
|---|---|---|
| Product identity | Exact source title, URL, category and source identifier when shown | Do not match products only by similar names or a shared origin story. |
| Form and selected option | Whole, ground, blend, tea or other source label; option name and SKU/variant ID only if displayed | Keep form at the page’s chosen product/variant grain. |
| Package amount | Displayed net weight, count and unit, with the page and observation date | Compare weight to weight and count to count; retain the original unit. |
| Bundle components | Parent kit plus each listed item, amount and count | Do not divide a bundle price across equal portions unless each component and quantity are stated. |
| Ingredients and advisories | The exact page’s ingredient field and any separate allergen/advisory label | Do not infer a full recipe, allergen safety or a family-wide claim from a related listing. |
Harvest date, mill date and printed best-by date are not interchangeable.
The official FAQ and a product-page FAQ do not give one uniform calculation. Their overlapping guidance should remain attributed to the page and answer where it appears; it is not a package-specific expiration calculation. Preserve the label actually printed on the selected package, its form and the observation date.
Scroll to compare →
| Current source statement | Scope as described by that page | How to record it |
|---|---|---|
| FAQ answer on how long spices last | Four years from harvest for single-origin spices; three years from mill for blends. | Keep this answer attached to that FAQ question and its check date. |
| FAQ answer defining the best-by date | Three years from harvest for whole spices; two years from mill for most ground spices. | Do not merge this rule with the other FAQ answer or calculate a missing label. |
| Nandini product-page FAQ | Most spices are described as good for two years from the mill date. | Keep the statement attached to the Nandini page FAQ; do not generalize it across forms. |
| Package label | The exact harvest, mill and best-by text printed on the selected tin or bag, if present. | These are separate date fields. Preserve missing values as missing. |
| Sold-out state | The About page says a sold-out harvest waits until the next season. | Attribute this as company policy; a current sold-out or waitlist label is not a restock date or discontinuation proof. |
Read the dated terms before using product content or source claims.
The Terms of Service page displays a last-updated date of September 1, 2021. Its Section 11 restricts attempts to access, search or download Services or Content through engines, software, tools, agents, devices or mechanisms such as spiders, robots, crawlers and data-mining tools, while naming Company-provided software/search agents and generally available third-party web browsers as exceptions. A separate Section 11 prohibition covers commercial purpose or third-party benefit. The same section also restricts specified uses of company names, marks, logos, site content and metadata without express written consent. The browser exception does not itself state permission for commercial access, collection or reuse. This summarizes the posted wording and is not a legal conclusion.
Scroll to compare →
| Terms topic | What the page states | Read it with care |
|---|---|---|
| Access, search and download | Section 11 names engines, software, tools, agents, devices and mechanisms; it lists company-provided software/search agents and generally available browsers as exceptions. | Do not turn the browser exception into a collection or reuse permission. |
| Commercial or third-party use | Section 11 prohibits using the Services, or any portion, for a commercial purpose, third-party benefit or otherwise impermissible manner. | Do not represent this informational guide as authorization to use the source’s Services or content. |
| Marks and hidden metadata | Section 11 restricts use or display of company names, marks, logos, proprietary information and page elements without express written consent; a separate clause mentions brand/product names in meta tags or hidden metadata. | Avoid logos, screenshots, embedded pages, copied descriptions and source names in hidden SEO fields. |
Content reviewed 2026-09-29.