> 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

Add custom Shopify product metafields to exports sent to FactFinder or Infinity.

Use metafields for product attributes, marketing flags, or technical parameters outside Shopify’s standard product schema.

### Configure metafields

Select one or more [Shopify product metafields](https://shopify.dev/docs/apps/build/metafields) in the app configuration.

During an export, the app fetches each selected metafield as a separate product-data field.

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

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

### Mapping rules

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

The app exports metafields per product. It exports an empty field when a product has no value.

### Supported types

The app exports only these simple metafield types:

* Single-line text
* Multi-line text
* Email
* Integer

Other metafield types are not included in the product feed.

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

### 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 type.

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](/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 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://docs.fact-finder.com/shopify-connector/shopify-app/product-data-and-metafields.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.