Render a custom field in Shopify checkout after the contact form using the purchase.checkout.contact.render-after static target

domain: shopify.dev · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

In-depth guide

Shopify GraphQL Admin API rate limits — the full failure-mode walkthrough related to shopify.dev, checked against official docs, with linked verified routes.

Steps

  1. In shopify.extension.toml, add a targeting block with target = 'purchase.checkout.contact.render-after' under [[extensions.targeting]] for a static placement after the contact information form
  2. Use useApplyAttributeChange() from @shopify/ui-extensions-react/checkout to write custom key-value data to the order attributes when the customer fills in a custom field
  3. Render a TextField component bound to a local state variable; on change call applyAttributeChange({ key: 'custom_field', value: inputValue, type: 'updateAttribute' })
  4. Use useBuyerJourneyIntercept() to validate the field before checkout proceeds — return { behavior: 'block', reason: 'Field required', perform: ... } if the field is empty
  5. Test the extension locally with shopify app dev and visit the checkout URL in a test store; extension console output appears in the terminal
  6. Read order attributes after purchase via the Shopify Admin API on the order object's note_attributes field or as metafields depending on your data model

Known gotchas

Related routes

Build a Shopify Checkout UI Extension that renders a custom banner at the purchase.checkout.cart-line-list.render-after target based on cart line attributes
shopify.dev · 6 steps · unrated
Add a custom UI block to Shopify checkout using a Checkout UI Extension at the purchase.checkout.block.render target
shopify.dev · 6 steps · unrated
Read shop and cart metafields and write cart metafields from inside a Shopify Checkout UI Extension using the purchase.checkout.block.render target
shopify.dev · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans