Xyppy Help Center

Appearance

Edit metafields in bulk ​

Update product or variant metafields at scale.

When to use ​

  • Populate missing data (e.g., brand, material) across many products.
  • Correct incorrect metafield values.

Prerequisites ​

  • Sync your metafield definitions from Shopify (click Sync metafields if prompted).
  • The app will automatically detect the metafield type from the definition.

Steps ​

  1. Open Bulk Edit → filter products/variants (need ideas? the Filters & search guide includes metafield recipes).
  2. Choose field: Metafield → select the metafield from the dropdown (namespace.key).
  3. The Type field is auto-populated and read-only based on the metafield definition.
  4. Enter a value in the Value field. This is a write-in text field for all metafield types and supports inserting tokens.
  5. Insert dynamic values: Click Insert variable or Insert product field below the value input to add pattern tokens directly. See the Pattern variables reference.
  6. Auto-formatting rules (we format what we can; Shopify validates the final value when the job runs; errors show in Job History):
    • List types (list.*): you can type a, b, c (or one per line) and we’ll send a JSON array like ["a","b","c"]. You can also paste a JSON array directly.
    • JSON: you can paste JSON (like {"key":"value"}), or plain text (like blue) and we’ll convert it to a JSON string.
    • Booleans / numbers: we normalize common inputs (like yes/no, 1/0, 12.34) when possible.
    • Reference types (product/collection/metaobject/etc.): Shopify ultimately expects GIDs (for example gid://shopify/Product/1234567890).
      • For metaobject references, the app will try to resolve a typed handle/name into a metaobject GID when possible. If it can’t resolve it (or the store/app doesn’t allow metaobject search), Shopify will reject the value and you’ll see the error in Job History.
  7. Click Preview and validate the changes.
  8. Run the edit and verify in Job History.

Rollback ​

Metafield edits store the “before” namespace/key/value, so you can use Job History → Rollback to revert them. Review the rollback coverage table for caveats (for example, if the metafield definition type changed after the original job).

Tips & limits ​

  • Types must match: updating a number into a string metafield will fail.
  • For complex objects or lists, test with a small sample first.

Was this helpful? ​

Questions? Visit the Support & contact checklist for what to include (shop URL, job ID, namespace/key, sample product), then email support@xyppy.com or open an issue at GitHub Issues.