Type: Developer Guide / Fix · Stage: Optimize · Topic: Customer Accounts / Footer / Localization
On this page
Quick answer
Shopify’s customer-account.footer.render-after target is a fixed slot below native policy links. You can add a branded, translated footer there, but cannot use the extension to move it above Policies. The storefront theme footer does not control the hosted customer-account pages.
Why the theme footer does not apply
New customer accounts render separately from online-store Liquid templates. Changing sections/footer.liquid affects storefront pages, not the order-history, profile, settings, or account app pages. Shopify’s footer extension target is static across those pages. Returning null collapses its content but does not remove the slot. Treat placement as a platform contract rather than a CSS bug.
Choose the supported surface
| Need | Approach |
|---|---|
| Account colors, logos, typography | Checkout and accounts editor; supported branding settings. |
| Account header menu | Shopify customer-account menus. |
| Persistent help, social, app, or contact links | Customer-account footer UI extension. |
| Footer above Shopify policy links | No supported reordering target; redesign hierarchy. |
| Localized labels | Extension locale files and shopify.i18n.translate(). |
Build a small localized footer
In an existing customer-account UI extension using API 2026-10, declare the target in shopify.extension.toml:
[[extensions.targeting]]
target = "customer-account.footer.render-after"
module = "./src/Footer.jsx"
Use Preact and supported Polaris web components. This minimal example intentionally avoids copying theme HTML and JavaScript:
import '@shopify/ui-extensions/preact';
import {render} from 'preact';
export default function extension() {
render(<Footer />, document.body);
}
function Footer() {
return (
<s-stack direction="block" gap="base">
<s-text>{shopify.i18n.translate('helpTitle')}</s-text>
<s-link href="https://example.com/pages/contact">
{shopify.i18n.translate('contact')}
</s-link>
</s-stack>
);
}
Add locales/en.default.json with {"helpTitle":"Need help?","contact":"Contact us"} and a corresponding locales/fr.json. Regional files such as en-CA.json are supported. Shopify resolves customer locale, non-regional language, shop locale, and finally your default file. Theme translations are not automatically imported into the extension.
US and CA versions need more than translation
Translate labels separately from link destinations. A Canadian English link may need a different URL from its US counterpart even when the visible words are identical. The localization API exposes country context, but it may be undefined during initial rendering. Provide a safe default, then use a deliberate country-to-URL mapping. Do not assume the account subdomain shares the storefront’s relative paths.
Keep the extension light. It appears on every account page, so avoid fetching storefront menus on each render. Heavy requests cause layout shift, and Shopify recommends static content or placeholders in the footer target. Keep native policy links intact rather than duplicating them.
Common misunderstanding
“I can move the footer with Liquid or CSS.” Not on hosted customer accounts. “Returning null removes the slot.” Shopify says the slot remains. “US and CA content only needs language translation.” Destinations and labels must both be checked.
How to test this
- Preview on a development store with new customer accounts enabled; confirm the extension is below native policy links.
- Check order index, order status, profile, settings, and a full-page account app on desktop and mobile.
- Switch English and French locales and verify missing-key fallback.
- Test US and CA destinations independently; inspect cross-domain and market redirects.
- Check keyboard navigation, accessible labels, and layout shift.
- Temporarily return
null; verify native policy links still render.
Sources and further reading
- Shopify: footer target and placement
- Shopify: localization API
- Shopify: locale fallback
- Shopify: customize customer accounts
Documentation checked October 21, 2026.

