datawebotShopZaza product data: forms, quantities and reports
Map ShopZaza product forms, weight and pack units, public lab-report references, and dated offer and destination context.
Keep product form and source labels distinct
ShopZaza's catalog spans flower, concentrates, edibles, vapes and pre-rolls. The source uses different category facets and labels across those product forms.
Scroll to compare →
| Record dimension | Preserve | Boundary |
|---|---|---|
| Product form | Source category, form label and canonical product URL | Do not flatten flower, extract, edible, vape and pre-roll records into one attribute set. |
| Storefront labels | Displayed brand line, source-defined strain/category, and product type | Keep labels source-reported; do not convert them into effect, potency or health claims. |
| Product identity | Product title, exposed source product/variant identifier and selected option | A collection filter or strain label does not replace the product or variant identity. |
Use package fields that fit each product type
A displayed weight, number of pieces and serving basis describe different things. Keep the value with the exact product form and label that provides it.
Scroll to compare →
| Product form | Useful source fields | Keep separate |
|---|---|---|
| Flower | Package amount/unit, size label and any source-reported category | A size label is not a strain, variant ID or potency result. |
| Concentrate | Named extract/form, package amount/unit and listed option | The product form does not establish a test result or a comparable strength value. |
| Edible | Product form, package count, published serving basis and label amount when shown | Do not derive a dose or usage recommendation from the package label. |
| Vape or pre-roll | Source-labeled device/product form, package unit/count and option identity | A device, extract name and package count are separate fields. |
Match public lab reports only to disclosed identifiers
The public Lab Results index is a separate searchable list of PDF reports. Preserve the report as its own source artifact and connect it to a product or lot only when the report itself supports that match.
Scroll to compare →
| Report field | Record | Match rule |
|---|---|---|
| Public report reference | PDF URL/title, index category, observation date and source page | Keep the report document distinct from the storefront product row. |
| Report identity | Laboratory, report date, sample or lot identifier and result units when disclosed in the report | Do not infer an exact batch match from a similar product or strain name alone. |
| Product association | Product label/URL and the report identifier that supports the association | The index lists reports by product name/category; a name-only match is not an exact batch match. |
Date the offer and destination context
Price and availability belong to a selected offer at a specific time. Store the storefront's destination eligibility separately from inventory so one observed state does not stand in for every product or market.
Scroll to compare →
| Observation | Keep together | Source-specific distinction |
|---|---|---|
| Offer state | Product/variant, seller/channel, currency, displayed amount basis, promotion, stock label and observation time | A promotion or availability label applies to the observed listing/option, not the whole catalog. |
| Destination eligibility | Product family, destination, source-published eligibility label and policy review date | ShopZaza publishes product-family shipping conditions separately from its general U.S. shipping scope; keep destination status distinct from inventory. |
Content reviewed 2026-10-07.