Define Customer-Level Metafield Definitions

I want structured custom fields on customer profiles — not tags, not a segment, an actual metafield definition my team can search and report on consistently.

Create these metafield definitions scoped to the Customer object:


  [FIELD_1_NAME, e.g. “Referral Source”] — type: [FIELD_1_TYPE, e.g. “single line text from a defined list: Instagram, Friend Referral, Google, Influencer, Other”].
  [FIELD_2_NAME, e.g. “Preferred Contact Channel”] — type: [FIELD_2_TYPE, e.g. “single line text from a defined list: Email, SMS, Phone”].
  [FIELD_3_NAME, e.g. “Account Manager”] — type: [FIELD_3_TYPE, e.g. “single line text”] — [FIELD_3_PURPOSE, e.g. “only used for our top wholesale accounts”].
  [FIELD_4_NAME — optional].


For each definition, set the validation rules I specified (list options, required/optional) and confirm the field appears on the customer detail screen once created.

After the definitions exist, populate values for customers in [SCOPE, e.g. “everyone who placed an order in the last 30 days”], using this source data: [DATA_SOURCE, e.g. “the table I’ll paste: customer email → field values” or “each customer’s existing order-note history as a starting guess”].

Show me a table of customer → field → proposed value before saving anything. Flag any customer where a value can’t be confidently determined, and leave those blank for manual entry. Apply only after I confirm, then report how many customers were updated per field and how many were left blank.