Merchant Notes Empower Store Credit Transactions in Shopify API 2027-01

Shopify’s 2027-01 API adds optional merchant‑only notes to store credit credits and debits, giving merchants better context without affecting customers. Learn what changed, who’s impacted, and how to implement the new note field today.

Merchant Notes Empower Store Credit Transactions in Shopify API 2027-01
6 sections

Shopify just rolled out a handy addition to its Store Credit API. Starting with GraphQL Admin API version 2027-01, merchants can attach a private note to every credit, debit, or debit‑revert transaction. The note stays invisible to customers, but it’s instantly readable via the API, making it easier to track refunds, adjustments, or internal accounting details directly within the platform.

What Changed

  • Input fields expanded – Both StoreCreditAccountCreditInput and StoreCreditAccountDebitInput now accept an optional note string.
  • Transaction object updated – StoreCreditAccountTransaction.note returns the stored note for credit, debit, and debit‑revert transactions (null for expiration transactions).
  • Length limit – Notes can be up to 5,000 characters. Exceeding that limit triggers a NOTE_TOO_LONG user error and the transaction isn’t created.
  • Merchant‑only visibility – Notes are never exposed to customers, preserving privacy.
  • No edit after creation – You can set a note when you create the transaction, but you can’t modify it later.
  • No new permission scopes – Existing read_store_credit_account_transactions and write_store_credit_account_transactions scopes remain sufficient.
  • Who Is Affected

    The update is relevant for any app—or custom integration—that manages store credit via the GraphQL Admin API. Only versions 2027-01 and newer expose the note fields; earlier versions (2026-10 and before) will ignore them. Both developers building apps and merchants using third‑party credit apps should be aware of the new capability, though no immediate code changes are required for existing functionality.

    How to Implement Notes in Your App

  • Target the new API version – Update your app’s GraphQL endpoint to use 2027-01 (or later).
  • Add the `note` field when creating a transaction – Include the string in the input object.
  • Read the note back – Select note in your query to retrieve it.
  • Here’s a minimal example for a credit transaction with a note:

    `mutation {

    storeCreditAccountCredit(

    input: {

    storeCreditAccountId: "gid://shopify/StoreCreditAccount/123456789",

    amount: "50.00",

    note: "Refund for order #1001 – product out of stock"

    }

    ) {

    storeCreditAccountTransaction {

    id

    note

    }

    }

    }`

    If the note exceeds 5,000 characters, the API will return a NOTE_TOO_LONG error, so you may want to validate length client‑side before sending the request.

    Testing and Verifying

  • Create a dev store – Use a development store to experiment without affecting live data.
  • Run the mutation – Submit the above mutation (or a debit variant) with a short note.
  • Check the response – Confirm the note field appears in the returned StoreCreditAccountTransaction object.
  • Edge cases – Attempt a note longer than 5,000 characters to ensure your error handling surfaces the NOTE_TOO_LONG user error.
  • By following these steps, you’ll guarantee that the new note functionality works smoothly before rolling it out to production.

    Key Takeaways

  • No breaking changes – Existing integrations continue to work unchanged.
  • New optional note field provides internal context for merchants.
  • Only the latest API version supports the feature; upgrade when you’re ready.
  • No additional permission scopes are required.
  • Validate note length client‑side to avoid NOTE_TOO_LONG errors.
  • Conclusion & Next Steps

    Adding merchant notes to store credit transactions is a low‑effort win for anyone managing refunds, promotions, or internal adjustments. Update your app to target the 2027-01 API, start attaching meaningful notes, and give merchants the audit trail they need—without exposing any extra data to shoppers. Need help upgrading your integration? Reach out to our developer support or drop a comment below, and we’ll walk you through the change.

    Tags
    Sources

    Related Articles

    Why Your Partner App Must Enable Bulk Operations Now (and How)

    Why Your Partner App Must Enable Bulk Operations Now (and How)

    Shopify now requires partner apps to explicitly enable bulk queries or mutations before using the GraphQL Admin API. Learn who’s affected, the exact steps to enable access, and best‑practice code snippets to keep your app running smoothly.

    November 6, 20263 min
    Enable Bulk Operations: New Permission Requirement for Shopify Apps

    Enable Bulk Operations: New Permission Requirement for Shopify Apps

    Starting today, Shopify apps must explicitly enable bulk query and mutation access before running bulk operations via the GraphQL Admin API. Learn what changed, who’s impacted, and how to enable the permissions in minutes.

    November 6, 20264 min
    Multi‑Group Location Ranking Arrives in Shopify’s Unstable Functions API

    Multi‑Group Location Ranking Arrives in Shopify’s Unstable Functions API

    Shopify’s latest Function API upgrade lets order routing functions rank a single location across multiple fulfillment groups, simplifying multi‑warehouse logic. Learn what changes, who it impacts, and how to update your code today.

    November 5, 20264 min
    Review App Access and Security Directly in Shopify Admin

    Review App Access and Security Directly in Shopify Admin

    Shopify now lets merchants see detailed app activity, permissions, and security measures right in the admin. Learn what changed, who it impacts, and how to act now.

    November 5, 20264 min