Define Order-Level Metafield Definitions

I want structured custom fields on orders themselves — not a free-text note, but a real metafield definition my team can filter and report on.

Create these metafield definitions scoped to the Order object:


  [FIELD_1_NAME, e.g. “Delivery Instructions”] — type: [FIELD_1_TYPE, e.g. “multi-line text”] — [FIELD_1_PURPOSE, e.g. “visible to warehouse staff on the packing slip”].
  [FIELD_2_NAME, e.g. “Engraving Text”] — type: [FIELD_2_TYPE, e.g. “single line text, max 40 characters”].
  [FIELD_3_NAME, e.g. “Gift Wrap Requested”] — type: [FIELD_3_TYPE, e.g. “true/false”].
  [FIELD_4_NAME — optional].


For each definition, set the validation rules I specified (character limits, required/optional, allowed values) and confirm the field appears on the order detail screen once created.

After the definitions exist, populate values on orders in [SCOPE, e.g. “all unfulfilled orders placed in the last 7 days”], using this source data: [DATA_SOURCE, e.g. “the table I’ll paste: order number → field values” or “the matching text already sitting in each order’s customer note, if present”].

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