Back to Intelligence
Platform UpdatesGlobal

Shopify clarifies what checkout footer visibility settings hide

For Shopify Plus checkout-branding integrations, HIDDEN still hides merchant-configurable footer content, but it does not suppress Shopify-provided footer copy.

Ecomwith EditorialEcommerce intelligence desk

Published
Updated
Risk
low

Reported details

What happened

Shopify says the visibility fields for CheckoutBrandingFooterContent and CheckoutAndAccountsConfigurationBrandingFooterContent now control only merchant-configurable footer content, such as policy links and copyright copy.

Shopify-provided transaction information may appear in the footer regardless of the visibility setting; the changelog says this copy is not configurable through checkout branding.

The changelog says no GraphQL Admin API fields, input types, enum values, access scopes, or mutations changed, and existing apps do not need to change their API requests.

The clarification applies to API versions where the corresponding branding types exist and affects apps managing checkout branding for Shopify Plus stores; apps that do not manage footer visibility are unaffected.

Business relevance

Why it matters

A preview showing footer text after HIDDEN is not necessarily evidence that the setting failed: the remaining copy may be Shopify-provided rather than merchant-configurable.

The distinction matters most to teams that test or render checkout-branding previews, because treating the footer as a single hideable block can make a valid checkout look incorrect.

For merchants outside the specified Shopify Plus checkout-branding use case, the changelog does not indicate a required change.

Editorial perspective

Analysis & judgment

  1. The setting governs a category of content, not the entire visual footer: Shopify separates merchant-configurable material from its own transaction information. That changes how an integration should interpret HIDDEN, but the evidence does not specify exactly which transaction copy appears in each checkout.

  2. If an app or internal QA process expects an empty footer whenever HIDDEN is set, Shopify-provided copy could be mistaken for a branding defect and trigger unnecessary investigation. This consequence is relevant to preview and test workflows; the changelog does not establish how any particular app currently renders its previews.

  3. Keep existing API requests unless a separate issue calls for a change, and assess previews against the content boundary Shopify describes rather than an empty-footer expectation. The decision applies to integrations managing footer visibility on Shopify Plus and should be revisited if Shopify documents further behavior or the store’s setup differs.

Applicability

Seller impact

Shopify Plus merchants whose apps manage footer visibility should expect HIDDEN to remove merchant-configurable footer content, not necessarily every item in the footer.

Merchants using previews or checkout tests may need to distinguish Shopify-provided copy from policy links or copyright text when reviewing the result.

The changelog reports no required GraphQL request changes; it identifies apps that do not manage footer visibility as unaffected.

Action plan

What to do now

  1. 1

    Check what your preview treats as hidden

    now

    If your Shopify Plus app manages checkout footer visibility, verify that HIDDEN is not being interpreted as a guarantee of an entirely empty footer.

  2. 2

    Review footer test expectations

    this-week

    If you own checkout-branding QA, separate merchant-configurable content such as policy links and copyright copy from Shopify-provided transaction information in test results.

  3. 3

    Watch for additional Shopify guidance

    monitor

    If your integration depends on the exact transaction copy shown, consult Shopify’s current documentation or changelog for details beyond this clarification.

What not to do yet

  • Do not change GraphQL Admin API requests solely because of this clarification, or treat HIDDEN as proof that the entire footer must be empty.

Sources & context

Evidence and sources

A source may provide only a headline or summary. Read the evidence scope below. Links and workflow checks are not independent fact verification. Internal confidence values are workflow signals, not probabilities of factual correctness.

  1. 01

    The visibility fields on CheckoutBrandingFooterContent and CheckoutAndAccountsConfigurationBrandingFooterContent now control only merchant-configurable footer content. Checkout can display Shopify-provided transaction information in the footer regardless of this setting. Existing apps don’t need to change their GraphQL Admin API requests, but apps that preview or test checkout branding shouldn’t assume that HIDDEN produces an empty footer. What changed Checkout can now display Shopify-provided copy in the footer for eligible orders. This content is part of checkout and isn’t controlled by the footer content visibility setting or configurable through checkout branding. The visibility setting continues to control merchant-configurable footer content, including merchant policy links and copyright copy. Setting it to HIDDEN hides that merchant-configurable content without suppressing Shopify-provided footer content. The descriptions for the following GraphQL Admin API fields now clarify this boundary: CheckoutBrandingFooterContent.visibility CheckoutBrandingFooterContentInput.visibility CheckoutAndAccountsConfigurationBrandingFooterContent.visibility CheckoutAndAccountsConfigurationBra

    Shopify Developer Changelog · Workflow status: single-source

    Source link

    Retrieved: October 15, 2026 at 04:07 a.m. UTC

    Claim is bounded to the ingested title or summary; no source body or quotation is retained.

Related tutorials and tools

Ecomwith tutorials