Every field your products actually need

Shopify sees your metafields. Only your team sees your PIM fields. Define both once, edit them with proper typed controls, and keep product data structured across every store.

Trusted by 50+ top merchants worldwide

Two data layers

Storefront data and internal data need different rules

Peak PIM separates the custom product information Shopify should receive from the structured operational data only your team should see.

Shopify's standard fields run out fast

Materials, care instructions, certifications, supplier references, and internal review states need a structured home beyond title, price, and description.

Metafield structures drift between stores

Definitions created separately in each Shopify admin can use different types, validations, names, and coverage even when they describe the same data.

Private workflow data falls back to sheets

Supplier SKUs, deadlines, quality notes, and approval status end up in disconnected spreadsheets because they should never reach the storefront.

Public and private

One field system for the whole catalog

Publish structured metafields to Shopify, keep private workflow fields in Peak PIM, and work with both through familiar catalog tools.

Synced

Publish metafields to Shopify

Define typed metafields once, connect them to the right stores, edit values with validation, and publish them through the same pipeline as the rest of your catalog.

Private

Keep internal fields inside Peak

Create workflow status, supplier references, notes, owners, and deadlines as PIM-only fields. They stay structured and filterable without ever syncing to Shopify.

Everywhere

Use custom data like native fields

Work with value-based custom fields on entity pages, in bulk edit, import and export, completeness checks, translations, and connected AI workflows.

Typed all the way down

Define once, validate everywhere

Custom fields are part of the product model rather than a bolt-on tab. Their type, scope, store presence, and validation follow them through every supported editing surface.

Choose the right type and validation

Use text, numbers, booleans, dates, URLs, colors, measurements, lists, and workflow selects with controls that match the data being edited.

Scope fields to the right records

Define fields for products, variants, collections, or media files, then arrange their display order around how your team reviews each record.

Replicate definitions across stores

Link a metafield definition to all stores or a subset, see where it exists, and create it in another Shopify store without rebuilding it by hand.

Validate every editing surface

The same field rules apply on detail pages, in the bulk grid, and during spreadsheet imports, so invalid values are blocked before publishing.

Give every product field a proper home

Publish the data customers need and keep internal catalog workflows structured, private, and ready for your team.

10-day free trial. Free setup. No credit card.

Frequently asked questions

Everything you need to know about Shopify metafields and private custom fields in Peak PIM.

Metafields are custom Shopify data that Peak PIM can define, edit, and publish to selected stores. Custom fields are PIM-only fields for internal data and workflows. Their values stay in Peak PIM and never sync to Shopify.

You can scope fields to products, variants, collections, or media files so each type of record shows the structured information relevant to it.

Metafields support typed values such as single-line and multi-line text, integers, decimals, booleans, dates, JSON, URLs, colors, dimensions, weights, and list variants. PIM-only fields support text, numbers, booleans, dates and date-times, URLs, emails, colors, and custom single- or multi-select options.

No. PIM-only fields are designed for internal information such as workflow status, supplier references, deadlines, ownership, and quality notes. They remain inside Peak PIM and are never published to a storefront.

Yes. Metafield definitions are managed at account level with per-store presence. Link a definition to all connected stores or a subset, replicate it in one click, and publish it natively to each selected Shopify store.

Connecting a store imports its existing metafield definitions into Peak PIM. You can then see their store coverage and use Health Center structure checks to find definitions that are missing or inconsistent across stores.

Yes. Custom fields appear as columns in the bulk editor, and value-based fields can be mapped during import and included in exports. Reference-type metafields are editable on entity pages but are not import-mappable.

Yes. Add metafields to Health Center completeness criteria, and manage translatable metafields alongside product and collection content in the translation grid.

Yes. Assistants connected through Peak PIM's controlled AI Connector (MCP) can read and write custom fields like other catalog data, within the permissions granted to the connection.

Still have questions?

Reach out to our team and we’ll help you find the right setup.