Hey folks - thanks to everyone who’s shared feedback of the impact on your apps and merchants. We’ve heard the feedback and have some additional context to share for clarity.
To start, it’s important to mention that collections that only use features supported by earlier Admin API versions remain readable and manageable in those earlier versions. The null response only occurs when a collection uses new model features that versions before 2026-07 can’t represent.
Regarding collections using the new model/features, I want to manage expectations and be transparent that this null filtering behaviour on versions earlier than 2026-07 won’t change. The supported path is to move affected collection queries to Admin API 2026-07 or later.
If you’re facing a specific migration blocker, let us know where you’re stuck. The more context we have about how these changes are affecting your apps, the more we can help work through it with you and identify any gaps along the way. There is also this Community thread where a number of different questions have been addressed that you may want to take a look at as well:
We’re also here to help separate expected API-version behaviour from bugs that need fixing. If an issue persists on 2026-07 or doesn’t match the documented behaviour, please share the x-request-id from the request and a summary of what you’re seeing that’s unexpected so we can investigate.
For reference, the new Collection model changelog has the migration guidance. We advise keeping an eye on the changelog for the latest updates, especially those marked Action required
I recognize this may not be the exact answer you’re looking for, but I’m doing my best to be transparent about where things stand today. I hope this helps set expectations, and please let me know if I can clarify anything further.