Liquid objects and data

Upstorr supplies only the data appropriate for the current route and render context. A product page receives a product; a collection page receives collection data; a route without that resource receives an empty value.

Available everywhere

  • shop.name and shop.currency
  • global settings
  • routes
  • request.preview, request.template and request.kind
  • localization.current and localization.available
  • store_name, images, current_year, content_pages and policies
  • shared shopper-facing labels

Section and block data

  • section.id, section.dom_id, section.settings, section.blocks and section.block_count
  • each block's id, dom_id, type, settings, children and editor identity
  • local_blocks and local_block_defaults
  • preset_blocks and declared preset_slots
  • behavior_state when the section registers a platform behavior

Storefront resources

  • product and products
  • collection and collections
  • blog and article
  • page
  • cart and prepared cart_view
  • registered menu variables and linklists

Product presentation includes identity, title, handle, description, media, prices, currency, vendor, stock presentation, fulfillment kind, category, review summary, options, variants, selected variant, URL and featured image when those values exist.

Collection presentation includes identity, title, handle, description, image, product counts, filters, sorting, pagination, URL and its prepared product list.

Important rule

These are presentation views, not raw database records. Do not rely on an undocumented property merely because it appears in one preview. Use this reference or the generated Theme SDK types. If required public data is missing, expand the shared contract rather than reading a private endpoint.