> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/model-your-data/dbt-model-reference/chord-oms/variants.md). # Variants ### x\_fct\_trans\_variants | Name | Description | | ------------------------------ | ----------------------------------------------------------------------------------- | | Product Store Id | Unique key generated by our models that uniquifies a store. | | Product Store Name | The name of the store. | | Product Store Oms Admin Url | The Admin URL of that OMS. | | Product Store Oms Id | Unique key generated by Chord that uniquifies an OMS. | | Product Store Oms Store Id | Unique key generated by our models that uniquifies a store. | | Product Store Oms Type | The type of the OMS. | | Product Store Id | Unique key generated by our models that uniquifies a store. | | Product Store Tenant Id | Unique key generated by Chord that uniquifies a tenant. | | Product Store Url | The Storefront URL of of the store. | | Variant Cost Price | The manufacturing cost of the variant. | | Variant Depth | The depth of the variant. | | Variant Height | The height of the variant. | | Variant Id | Unique key generated by Chord to identify a unique product variant. | | Variant Is Backorderable | Whether the stock item has at least one location where it is back-orderable or not. | | Variant Is Inventory Tracked | Whether the inventory should or should not be tracked for this variant. | | Variant Is Master | Whether this represents the master SKU or not. | | Variant Is Subscribable | Whether or not a customer can ask to subscribe to this product. | | Variant Oms Variant Id | Unique key generated by Solidus that identifies a variant. | | Variant Option Color | Color of the variant. | | Variant Option Format | Format of the variant. | | Variant Option Quantity | Quantity of item for the variant. | | Variant Option Size | Size of the variant. | | Variant Position | The position of the variant in the list of variants. | | Variant Sku | The SKU of the variant. | | Variant Weight | The weight of the variant. | | Variant Width | The weight of the variant. | | Variant Created At (Universal) | Reflects when the entity was first created in Solidus - Universal Time Zone. | | Variant Deleted At (Universal) | Reflects when the entity was deleted - Universal Time Zone. | | Variant Updated At (Universal) | Reflects when the entity was last updated in Solidus - Universal Time Zone. | | Average Count On Hand | The sum of on-hand stock currently available for the variant. | | Count On Hand | The sum of on-hand stock currently available for the variant. | *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chord.co/model-your-data/dbt-model-reference/chord-oms/variants.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.