Concepts

Products, variants and fields

Review the datawebot. product and variant data schema, including source identifiers, prices, availability, images and record relationships.

Synthetic catalog data · not a retrieval result
02 / Inspect the example
Fictional product variants created for this example
VariantSKUExample priceExample availability
Small / NavyDEMO-TEE-S-NVUSD 32.00Example: available
Medium / NavyDEMO-TEE-M-NVUSD 32.00Example: available
Medium / SandDEMO-TEE-M-SDUSD 34.00Example: unavailable
Large / NavyDEMO-TEE-L-NVUSD 32.00Example: unknown

All names, identifiers, prices and availability values are fictional. They do not describe a merchant’s catalog or inventory.

Product fields

FieldTypeMeaning
idstringSource product ID
title / urlstringTitle and public product URL
vendor / product_typestring | nullReported vendor and type
description_htmlstring | nullSource HTML; treat as untrusted
imagesstring[]Source image links
variantsarraySource-reported variants
provenanceobjectSource, storefront, retrieval time, schema version
warningsstring[]Mapping or source limitations

Variant fields

FieldTypeMeaning
id / skustring / string | nullSource identifiers
optionsobjectNamed options such as Size
priceobjectDecimal-string amount and currency
compare_at_priceobject | nullSource comparison price
availableboolean | nullObserved availability; null means unknown

Identifiers and prices

Keep product IDs, variant IDs and SKUs as strings. Floating-point coercion can lose precision or leading zeros. Keep source identity alongside each ID.

A price such as 16.00 is a decimal string with its currency. Use decimal arithmetic or integer minor units in calculations.

Missing values

False availability means the source reported unavailable; null means no usable value was provided. Neither is an inventory quantity.

Missing descriptions, vendors and comparison prices remain null. datawebot. does not generate missing facts.

Need help? Contact support.