> For the complete documentation index, see [llms.txt](https://claimlane-docs.gitbook.io/claimlane-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://claimlane-docs.gitbook.io/claimlane-docs/troubleshooting-and-faqs/how-to-properly-set-up-a-data-source-for-shopify-variants.md).

# How to Properly Set Up a Data Source for Shopify Variants

Setting up a data source for Shopify variants ensures Claimlane can accurately identify and match product data from your store. Here's a quick guide to help you get it right:

### Step-by-Step Instructions <a href="#h_5b984c2899" id="h_5b984c2899"></a>

1. Open Your Company Dashboard\
   From Claimlane’s inbox, navigate to your company dashboard.

   <img src="https://downloads.intercomcdn.com/i/o/tbixbicd/1634101130/6058301567c350ac3e0063c5a109/Captura+de+pantalla+2025-07-23+a+las+10_54_03.png?expires=1759142700&#x26;signature=373f81cfae774731fe57e730282122bfec335fae19b63866f61b7222cd59257c&#x26;req=dSYkEsh%2BnIBcWfMW1HO4zQD99zqUyIS%2Bx%2BGAnpRHpPWUkALFED01V%2F5UPHbQ%0ADXs5%0A" alt="" width="590">
2. Go to Data Sources\
   In the dashboard, go to Data Sources and select the one you want to configure.

   <img src="https://downloads.intercomcdn.com/i/o/tbixbicd/1634102095/2a88ed181cb2a2e274d40dfb036c/image.png?expires=1759142700&#x26;signature=abf397ede9145c38281fdb3e266d3323dc5e21f066387b05ff5d49f1bbcf6e11&#x26;req=dSYkEsh%2Bn4FWXPMW1HO4zZNcSMLmm4uhzhkR4gpyqUzShSl94aEKqCvebsy9%0AMAdJ%0A" alt="" width="590">
3. Navigate to Product Upload\
   In the left-hand menu, click Product Data > Product Upload, then select Data Blueprint.

   <img src="https://downloads.intercomcdn.com/i/o/tbixbicd/1634102505/a6f9be1a44f1e580b65b1d8f6590/image+%281%29.png?expires=1759142700&#x26;signature=27c8d4e430c856e30cad8400b1ecd59eac60767122904135b6025794d47ceb86&#x26;req=dSYkEsh%2Bn4RfXPMW1HO4zQ8ozQCx%2BvGztlAZGXTzQa2XVLdk0aHdb2jMNq%2FY%0A9iXq%0A" alt="" width="590">
4. Create Your Variants (If Needed)\
   In the Data Blueprint, scroll down and click the ➕ Add button to create a new variant entry if you haven’t done so already.

   <img src="https://downloads.intercomcdn.com/i/o/tbixbicd/1634103071/83c4b34ad9370f3ccf274e979652/image+%282%29.png?expires=1759142700&#x26;signature=960e97d37f1225bf074bc1413977d39c5f8a97f8542796b835d7dd2c3717aa93&#x26;req=dSYkEsh%2BnoFYWPMW1HO4zSLVCdfP2z9hXbLO%2B3dlF%2BIc16tXEvtR3Zkfvzk6%0AbBPi%0A" alt="" width="590">
5. Name and Match the Technical Label
   * Give your variant a clear, recognizable name.
   * Make sure the Technical Label exactly matches the technical label used for that variant in Shopify (e.g., length, color, size, itemName).

📝 Note: Matching the technical label is essential for correct data syncing between Shopify and Claimlane.

### 🎉 That’s It! <a href="#h_00ab3f00df" id="h_00ab3f00df"></a>

You’ve now successfully set up your data source for Shopify variants!


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://claimlane-docs.gitbook.io/claimlane-docs/troubleshooting-and-faqs/how-to-properly-set-up-a-data-source-for-shopify-variants.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
