---
title: Metafield imports respect your definitions over column header types
date: 2026-06-16
description: When a metafield column header type differs from your store's definition, Altera now imports using the definition's type instead of failing.
tags: ["Imports","Products","Metafield Definitions"]
categories: ["Changelog"]
url: https://www.getaltera.com/changelog/2026-06-16-metafield-type-matches-definition/
---


When a column header and your metafield definition disagree on the type, the import used to skip the field. Now it goes with the definition and brings the value in.

---

### 🐛 Fixes

- **Metafield types** - When a column header specifies a type (like `[string]`) that differs from your store's metafield definition, Altera now imports using the definition's type instead of rejecting the value. Previously the mismatched metafield was skipped.
- **Google Shopping metafields** - Re-importing an export of `mm-google-shopping` fields, which Shopify stores with the legacy `string` type, now updates cleanly against the modern `single_line_text_field` definitions (see the [Google Shopping metafields guide](https://support.getaltera.com/en/articles/14282347-how-to-import-and-export-google-shopping-metafields-in-shopify)).