Market level product variant Metafields

This document outlines the structure and usage of market-specific metafields for product variants. These metafields enable market-specific order limit tracking, and shipping information display.

1. Market Preorder Count Metafield

Configuration

  • Key: market_preorder_count

  • Type: json

  • Namespace: restockrocket_production

  • Owner: Product Variant

Purpose

  • Tracks the current number of preorders for a variant per market

  • Used for market-specific inventory management

  • Automatically updated when orders are processed in different markets

  • Stored as a JSON object mapping market IDs to counts

Accessing in Liquid


{% assign market_preorder_count = product_variant.metafields.restockrocket_production.market_preorder_count.value | json %}
Example value of market_preroder_count =>
{ 
  "market_id_1": 1,
  "market_id_2": 5,
  "market_id_3": 3
}

2. Market Preorder Max Count Metafield

Configuration

  • Key: market_preorder_max_count

  • Type: json

  • Namespace: restockrocket_production

  • Owner: Product Variant

Purpose

  • Sets the maximum number of preorders allowed per market

  • Controls market-specific inventory policy switching

  • Triggers blocking orders when count reaches max in specific markets

  • Stored as a JSON object mapping market IDs to maximum counts

Accessing in Liquid

Example Usage: Market-Specific Preorder Count and Max Count

3. Market Shipping Text Metafield

Configuration

  • Key: market_shipping_text

  • Type: json

  • Namespace: restockrocket_production

  • Owner: Product Variant

Purpose

  • Stores market-specific shipping/delivery timeline text

  • Allows different shipping information per market

  • Stored as a JSON object mapping market IDs to shipping text

Accessing in Liquid

Accessing via GraphQL

Query for Market-Specific Metafields

Query for Multiple Variants with Market Data

Last updated