Regarding the PHP vulnerabilities disclosed on October 21, 2026 (CVE-2026-109618 and CVE-2026-109619), we have reviewed their impact on all of our Shopify apps: Japan Order CSV, Delete Me, Mockingbird, Mypage Blocks, and B2E, our employee sales app. None of these apps use PHP, so they are not affected by these vulnerabilities. Merchants using our apps do not need to take any action, such as updating or changing settings.

We continuously monitor published vulnerability information and will notify our users promptly if any impact is expected. If you have any questions about this matter, please contact the support desk for the app you use.

Contact us
Contact
Back to Glossary

Metafield / Metaobject

ShopifyData Modeling

Definition

  • Metafield: Shopify's mechanism for attaching custom attributes to existing resources — products, customers, orders, collections, and more — defined in the namespace.key format.
  • Metaobject: A standalone custom data type not tied to any particular resource, for managing structured data such as brand information, store content, and reusable content modules.

Background

Metafields are the first choice for business requirements that Shopify's standard fields cannot express — product subtitles, series names, search-exclusion flags, tier-specific attributes, and so on. They are accessible from themes, apps, and Flow alike, serving as a single source of truth. Metaobjects, by contrast, handle collections of records that exist independently — catalog-like data — making them the key to CMS-style use cases and sophisticated data modeling.

Flagship's Involvement

We design Metafields in nearly every project — for example, search-visibility flags and storage for benefit-granting logic. Choosing between Metafields and Metaobjects — carton-size management in B2B projects, content template definitions, and more — is a data modeling decision we make at the start of each engagement.

Back to Glossary Top