> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/shopify-connector/shopify-app/product-data-and-metafields.md).

# Product Data & Metafields

Export Shopify metafields and selected standard fields.

Add standard Shopify fields and custom metafields to exports sent to FactFinder or Infinity.

Use these fields for product attributes, marketing flags, and technical parameters.

### Configure metafields

Select one or more metafields in the app configuration. You can also select these standard Shopify fields:

* Shopify core fields: `publishedAt`, `updatedAt`, `createdAt`, `compareAtPrice`, `inventoryPolicy`, `collectionIds`, and `masterName`.
* Product media URLs: `mediaUrls`. The export includes the first five product-media image URLs.
* [Product metafields](https://shopify.dev/docs/apps/build/metafields).
* Variant metafields.

The app fetches every selected field during CSV exports and real-time synchronization.

For FactFinder, each selected field becomes a dedicated field. Configure it for search, filtering, or sorting in [Fields](https://docs.fact-finder.com/docs/basic-settings/fields.md).

{% hint style="info" %}
Treat every selected metafield or standard field as part of the target system’s product schema.
{% endhint %}

### Mapping rules

Each field uses a stable export name. For FactFinder, this name must match the configured field.

Product and variant metafields use a scope prefix. This prevents name collisions:

* Product metafields use `product:namespace.key`.
* Variant metafields use `variant:namespace.key`.

Product-level values apply to every exported variant. Variant-level values apply only to that variant.

FactFinder column names cannot contain colons. The app replaces each colon with an underscore. For example, `variant:custom.color` exports as `variant_custom.color`.

The app exports an empty field when a product or variant has no value.

### Supported types

The app supports these metafield types:

* Single-line text
* Multi-line text
* Email
* Integer
* Date
* Boolean
* URL
* JSON
* List-type metafields
* Metaobject references
* File and image metafields, including lists

Metaobject references export as Shopify GIDs. File and image metafields export as object GIDs, not URLs.

{% hint style="info" %}
File and image metafields are supported in CSV exports and real-time synchronization.

To verify an integration, select a file or image metafield, export a product with a value, and confirm its object GID appears in the target field.
{% endhint %}

{% hint style="warning" %}
Adding, removing, or changing a metafield **changes the product schema**. Plan the corresponding system change before exporting.
{% endhint %}

### Shopify data retrieval limits

The app uses Shopify’s GraphQL API. Each request has a maximum query cost of `1000` points.

To keep exports stable, the app applies these limits:

* Collections: `10`
* Variants: `100`
* Product metafields: `100`
* Variant metafields: `100`

The configuration UI paginates through all available metafields. The previous `250`-metafield discovery limit no longer applies.

Exports query selected metafields through GraphQL aliases. Configured fields are not omitted because of populated metafields from other apps.

### Change fields safely

The required process depends on the selected target system.

{% stepper %}
{% step %}

#### Review the change

Identify whether you are adding, removing, or changing a metafield.

Check that the configured target field has a matching name and type.
{% endstep %}

{% step %}

#### Update FactFinder or contact Infinity Support

For FactFinder, add or edit the corresponding field in [Fields](https://docs.fact-finder.com/docs/basic-settings/fields.md). The field type must match the exported value.

For Infinity, contact Support before making the app change. Infinity fields cannot be changed in the app.
{% endstep %}

{% step %}

#### Export after confirmation

Run a new export only after the target-system change is confirmed.
{% endstep %}
{% endstepper %}

The app cannot create, update, or remove fields in FactFinder or Infinity automatically.

### Remove a metafield from a FactFinder export

If you remove a metafield from the export, rebuild the FactFinder database structure before exporting again.

{% stepper %}
{% step %}

#### Open the FactFinder UI Panel

Open the FactFinder UI Panel.
{% endstep %}

{% step %}

#### Open the channel configuration

Navigate to the affected channel's management configuration.
{% endstep %}

{% step %}

#### Rebuild the database structure

Start the Installation Assistant to rebuild the database structure.
{% endstep %}

{% step %}

#### Confirm the removed field

Confirm that FactFinder no longer expects the removed metafield column.
{% endstep %}

{% step %}

#### Export again

Run the import again or trigger a new export from the app.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
This step is mandatory. The app cannot automatically update or remove existing FactFinder database fields.
{% endhint %}

### Best practices

Treat metafield changes as schema changes.

* Do not remove fields that the target system still expects.
* Change field types only after reviewing their existing usage.
* Use a test channel only when one exists. Coordinate its use with your Technical Consultant or Business Consultant.

{% hint style="success" %}
Before changing production metafields, review the current field configuration.

Coordinate significant changes with your FactFinder team.

Test changes on a staging or test channel when possible.
{% endhint %}


---

# 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.fact-finder.com/shopify-connector/shopify-app/product-data-and-metafields.md?ask=<question>&goal=<user_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.
