Define your own custom fields on SKUSavvy records, with types, validation, and how strictly they're enforced.
A metafield schema defines a custom field of your own choosing on a SKUSavvy record, with a type and validation rules. Today you can attach custom fields to inbound (purchase) orders — for example a Buyer Reference number or a Tax Exempt flag that doesn't exist as a built-in field.
This is entirely a SKUSavvy feature — it doesn't read from or sync with Shopify metafields. Syncing specific Shopify metafield namespaces onto products and orders is a separate setting under Company > Shopify.
1) Go to Company > Metafield Schemas and click Create
2) Enter a Field Name in namespace.field_name format, for example custom.buyer_reference
3) Choose a Type: Text, Number, Date, JSON, Boolean, Email, URL, Phone, or Money
4) Choose an Enforcement level
5) Save
The Enforcement level controls how strictly the field is required, and where:
Optional — the field is never required.
Required in app, optional for integrations — the app's Create Inbound Order form requires a value, but a purchase order created directly through the API can still omit it.
Required everywhere — the field is required both in the app and for any API call, including tokens created under API Tokens.
Pick Required everywhere for anything that must never be missing, like a compliance field. Pick Required in app if it's fine for automated integrations to skip it.
Money and Number fields can have a Minimum Value and Maximum Value. Text, Email, URL, and Phone fields can have a Min Length, Max Length, a Regex Pattern, and a custom Pattern Error Message shown when a value doesn't match. Date, JSON, and Boolean fields have no extra validation options.
Once a schema exists, its field shows up on the Create Inbound Order form automatically if it's required, or behind an Add Metadata button if it isn't. To fill it in or change it after the order already exists, open the inbound order and choose Edit Metadata from its menu.