Tringify Help Center
English
Back to Metafields

Import, export, and lifecycle

Move custom data in bulk and understand deletion and app cleanup.

Product exports include columns for every product and variant metafield definition. Other supported resources use the Custom data import, update, and export jobs. Values are parsed and validated with the same shared type rules as an individual edit.

Product Update CSV files patch metafields by definition. A populated cell updates that metafield, while an omitted or blank cell leaves its current value unchanged. Enter __CLEAR__ to remove the value for that specific metafield without affecting the owner's other metafields.

Reference values use stable resource identifiers. Product CSV columns use the portable references documented for the Products importer. The generic Custom data CSV uses stored resource identifiers and file references exactly as shown in its template; preview validates that every reference belongs to the same store before a job can start.

Deleting a resource removes its own metafield values and their translations in the same database transaction. For Brand, Vendor, Category, and Collection custom data, subscribed endpoints receive translation-deleted and value-deleted events before the owner deletion event. A definition cannot be deleted while values still reference it. Removing an app schedules removal of its definitions and values after a 48-hour recovery window; reinstalling during that window keeps the data.

Bulk jobs are store-scoped, validate before applying, and record one job-level audit entry. A failed row never borrows a definition or referenced resource from another store.