Winter26 // are these features coming?

GraphQL Admin API Troubleshooting
1

Hey,

I just saw the renaissance release, and really was hoping to see the following:

  • mutation/query for purchaseOrder
  • query for storeCredit (top-level with filtering)
  • query for returns (top-level with filtering)
  • webhook to new/updated storeCredit/returns via adminAPI

I know it is hard to encapsulate everything in a release, but wondered how these are going as they are constant issues for alot of people.

2

Hi @ChrisBradley,

I’m afraid we are unable to comment on any requested features or updates that have not been announced publicly, or share any information on timelines for such features.

I do recommend keeping an eye on the Shopify Changelogs for any updates to requested features, and I will also be submitting some feedback on your behalf that you would like to see these things added to the platform in the future.

The more feedback we get for topics like these, the more likely and quicker they will be added, as we do take all of our merchant and partner feedback into great value when determining future updates and features added to the platform!

Regarding a Purchase Order API

This is something that has been requested somewhat often, and perhaps the workarounds suggested in this thread, can help you in the meantime.

Regarding querying Store Credit Accounts.

We do have the storeCreditAccount query, though you will need an actual StoreCreditAccount ID to use in the query.

You can also query Customers on the store, and view their credit accounts that way, however there is no direct filters to return only customers with credit accounts.

Here’s an example customers query that returns all customers on the store, and displays their credit account info if they have one.

{
  customers(first:10) {
    nodes{
      id
      tags
      storeCreditAccounts(first:20){
        nodes{
          id
          balance{
            amount
          }
        }
      }
    }
  }
}

Another potential workaround to allow you to query customers with store credit accounts specifically is to use customer tags that indicate if the customer has store credit or not, and filter the customers query by that tag.

  1. Add a tag to a customer when they have an active customer account.

    • This can be done with regular syncs, checking for customer accounts with the query above, and running tagAdd mutation for any customers with a credit account that does not have the tag already.
    • Or if you are adding store credit via the storeCreditAccountCredit mutation, you can use the tagAdd mutation as part of the workflow as well, adding a tag like hasStoreCredit to the customer after you run the storeCreditAccountCredit mutation.

  2. Then you can use the customer tag to filter the customers query like so, so that it returns only customers with store credit:

customers(first:10, query:"tag:'hasStoreCredit'") {
    nodes{
      id
      tags
      storeCreditAccounts(first:20){
        nodes{
          id
          balance{
            amount
          }
        }
      }
    }
  }
}

Regarding Querying for Returns.

You can use the orders query and filter with the return_status to get a list of returns on the store, like so:

{
  orders(first: 20, query: "NOT return_status:no_return") {
    nodes {
      id
      returnStatus
      returns(first: 20) {
        nodes {
          id
        }
      }
    }
  }
}

Regarding the Webhooks:

We do have Returns webhooks availabe, with the following topics. Though there is no topics specifically for Store Credit, so I will be sure to include that in the feedback I’ll be submitting on your behalf internally.

3

@Kellan-Shopify, I’d like to also +1 for a PurchaseOrders API. I remember when Transfers were introduced, but API access only came probably 4 years later. We had merchants constantly asking for it. Now that we’ve implemented a use for it, we only hear: when is PO access coming?? :sweat_smile:

1 Like
4

@Kellan-Shopify

I get there are workarounds, just some of them are not particularly all encompassing and limit the ability to actually pick up some of these new(ish) features entirely.

storeCredits and purchaseOrders are really frustrating TBH, both have so much potential (especially with appGen for the masses), but are limited by the ability to actually create/output via the graphQL.

1 Like
5

Hi @ChrisBradley,

I appreciate and understand that these workarounds may not be the most ideal for your usecases, and I can assure you that our developers are aware of this limitation and we have submitted feedback on your behalf as mentioned as well.

We can’t guarantee when or if these will be added, but I can assure you we do take all of our partner and merchant feedback with great value when determining future features and updates to the platform.

1 Like