Shopify Makes Store Builders Verify Their ID

By

Shopify quietly changed how store builders get into client stores. On July 9, it switched on identity verification for Partners, and if you or anyone on your team sends a collaborator request to a merchant store, you now have to prove who you are with a government photo ID and a selfie or liveness check. It is optional today. Shopify says it becomes mandatory “in the coming weeks,” with no fixed date attached.

Disclosure: This post contains affiliate links. If you buy through them, I may earn a commission at no extra cost to you. I only recommend tools and services I trust to help you build a profitable ecommerce business. My goal is to create helpful content to assist you in making an informed decision. By signing up through my affiliate link, you'll be getting the best deal available and you'll be supporting my work to create valuable content to entrepreneurs everywhere. Thank you for your support. If you have any questions or want to contribute to my blog, please feel free to email me at trevor@ecommerceparadise.com — Trevor Fenner, Owner of Ecommerce Paradise

That sounds like a developer footnote. For anyone running a high-ticket store the way most of us do, with an agency, a builder, or a virtual assistant touching the backend, it is a real operational change. At Ecommerce Paradise, every done-for-you build my team ships runs through exactly this door: a collaborator request into the client’s Shopify admin. This post breaks down what changed, why Shopify did it, what it means for your store, and the five-minute move that keeps your next build from stalling.

You are about to hand a platform your government ID and a selfie. Control what else of yours is public. Northwest uses their own address on your LLC filings, so your home address never lands on the public record. See how Northwest keeps your info private →

Shopify Now Requires ID Verification to Send Collaborator Requests

Here are the mechanics, straight from the source. According to Shopify’s developer changelog, as of July 9 a Partner can verify their identity before requesting collaborator access to a merchant’s store. The check runs through Stripe and asks for two things: a government-issued photo ID, and a selfie or liveness check that matches your face to the document.

Two details decide who has to act. The verification is per user, not per organization. The account owner verifying does nothing for the account managers, freelancers, or VAs who actually send the collaborator requests during onboarding. Every individual who sends a request has to run their own ID check.

The second detail: it only gates new collaborator requests. Stores where a merchant has already granted you access are untouched. Your current client roster keeps working. The wall sits in front of every new request from here forward, which is exactly where client onboarding lives.

Right now the check is optional, and Shopify recommends completing it early so nothing breaks when enforcement flips on. After that switch, an unverified user simply cannot send a new collaborator request until they finish the check. There is no grace-period workaround described anywhere in the announcement. You verify on the Request collaborations page inside the Partner Dev Dashboard, and the whole thing takes a few minutes per person if you have your ID and a camera handy.

One thing worth flagging so you do not confuse it with something you already did: this is not the merchant identity check tied to Shopify Payments. Per Shopify’s Help Center documentation on collaborator accounts, partner verification proves the individual sending the request, while the older merchant verification proves the store owner for payments. Same document types, different systems, different people. If a client asks whether their Payments verification covers your agency, the answer is no.

Shopify shipped a second change the same day that flew under the radar. Public app plan limits doubled from four to eight, and private plans went from ten to fifteen, alongside no-charge plan testing for developers. If you productize any service as a Shopify app, that ceiling jump is worth a look at your pricing tiers. For most store operators, the ID gate is the one that matters.

Store-Takeover Scams Are the Reason Shopify Is Checking IDs

Collaborator access is one of the most powerful things a merchant can hand out. When a store owner approves a request, they are giving a stranger keys to a live store: products, themes, apps, sometimes orders and customer data. Shopify calls it one of the clearest trust moments between a merchant and a partner, which is why enforcement starts here rather than at app installs or theme downloads.

The problem this solves is real. Collaborator requests are the front door that legitimate agencies and freelancers walk through, and they are also the front door scammers use when they impersonate an agency to reach a store they want to take over. A government ID gate raises the cost of running fake-agency and account-takeover schemes without adding a single step for the merchant. This is the same know-your-customer tightening that has already worked through payment processors and banks, now arriving at the partner side of Shopify. The check runs on the same kind of infrastructure that Stripe Identity already powers across thousands of platforms.

The new requirement stacks on top of collaborator rules that already existed and that high-volume builders already juggle. A partner can hold at most ten collaborator requests open at once. Collaborator access expires if you do not log into a store within a rolling 90-day window. And a merchant can require a four-digit request code before any request even reaches them. None of that is new. What is new is that the very first step, sending the request, can now hard-fail for anyone who skipped a five-minute ID check. Day-one friction has already shown up in the Shopify developer community thread, so if you are testing this week, budget a little time for rough edges.

What Shopify Partner Verification Means for Your High-Ticket Store Build

If you run a high-ticket store, you are touched by this in one of two ways, and it pays to know which.

The first: you hired someone to build or manage your store. An agency, a freelance developer, a Shopify partner. That person or team reaches your admin through a collaborator request, and once enforcement lands, they cannot send you that request until they verify. If your builder is disorganized about who on their team sends requests, your onboarding can stall at the worst possible moment, right when you are excited to get moving. Ask any builder you are about to hire one question: is your team verified? A good shop already handled it.

The second: you are the builder, for yourself or for clients. This is where my team lives. Every store I build through the done-for-you build service starts with a collaborator request into the client’s Shopify admin. The monthly store management we run after launch depends on that same access.

If you build client stores under the white-label agency program, the rule applies to your name and every person you delegate to. Verification is not something you do once for the whole shop. It follows each individual who sends requests.

Here is the piece that catches most operators. If you hire virtual assistants to run store setup or backend work, and a lot of high-ticket owners hire from OnlineJobs.ph, each VA who sends a collaborator request needs their own verified identity on file. That means a government ID from a team member who may be on the other side of the planet. Paying that team across borders stays simple with a service like Wise, but the verification step is on each person individually. Build it into your hiring and onboarding checklist now, because a blocked request from an unverified VA is a client-visible delay, not a private inconvenience.

There is a security upside worth naming too. A high-ticket store doing real revenue is a target, and store-takeover attempts hit exactly the kind of Shopify admin that processes four and five-figure orders. An ID gate on collaborator access makes it materially harder for someone to slip into your backend by pretending to be a contractor. Pair it with a managed fraud tool like the options in my ClearSale vs Sift breakdown. Add a trust-badge setup from my TrustedSite alternatives guide so buyers and bots both see a legitimate store.

This is also a good moment to tighten the rest of your business identity. You are already handing a platform your face and your ID. Do not also leave your home address sitting on a public LLC filing where anyone can pull it. Getting your entity set up cleanly with a service like Bizee keeps that buttoned up from the start. I cover when you actually need one in my guide on whether your ecommerce store needs a business license.

On the money side, a clean bookkeeping setup like Finaloop means you can see revenue moving while all of this tightens up. If Bizee is not your pick, LegalZoom is a fine formation alternative.

If reading all of this makes you want to skip the operational headache entirely, that is a fair reaction. Verifying a team, managing collaborator queues, keeping access alive across a 90-day window, and standing up the whole store on top of it is a lot. That is the exact reason my turnkey done-for-you service exists: my verified team handles the build, the access, and the launch, and you get a finished high-ticket store without touching the Dev Dashboard once.

New to high-ticket and not sure where the platform pieces fit? My free beginner guide walks you through building a real store from zero, the right way. Grab the free beginner guide →

How to Verify Your Team Before Shopify Locks Collaborator Requests

The cost of getting ahead of this is tiny. The failure mode, a blocked request in the middle of a client handoff, is not. Here is what to do this week, depending on how you touch Shopify.

  1. List every person who sends collaborator requests. Not who has access, who sends the requests. In most shops that set is wider and fuzzier than the org chart, because whoever is on the onboarding call tends to send the request. Name those people explicitly.
  2. Verify each of them now, in the Dev Dashboard. Send them to the Request collaborations page with a government photo ID and a camera-equipped device ready. Five minutes each. Do it before your next onboarding, not after a request fails.
  3. Route all future requests through verified users only. Decide which named people send collaborator requests and funnel every request through them. That single rule removes almost all of the surprise.
  4. Add verification to your VA onboarding checklist. Every new hire from OnlineJobs.ph who will touch client stores verifies on day one. Set them up with a password manager and a Surfshark VPN for secure access at the same time.
  5. Watch the 90-day clock on dormant stores. If access lapsed on an old client and you need it back after enforcement lands, re-requesting will require a verified user. Track verification status next to access status, not on a separate list.
  6. If you want it handled, book a call. I set up client access, verification workflows, and the whole store build for people who would rather not run the Dev Dashboard themselves. You can book a discovery call and map your launch. If you would rather learn to run it yourself, my high-ticket coaching gives you one-on-one help.

Whatever bucket you sit in, treat this as the template for where platforms are heading. Trust checks on the access side, more billing flexibility on the app side, both shipped the same day. The operators who fold identity, access, and money hygiene into standing procedures are the ones platform changes never rattle.

Frequently Asked Questions

When does Shopify partner identity verification become mandatory?
Shopify has only said “in the coming weeks” with no fixed date as of mid-July 2026. Treat any specific date you see quoted elsewhere as invented, and verify before your next collaborator request rather than waiting for a deadline.

Who on my team actually needs to verify?
Every individual who sends a collaborator request, not just the account owner. Verification is per person. If three people on your team send requests during onboarding, all three verify separately.

Will this break access to stores I already work in?
No. Existing granted access is untouched. The check only gates new collaborator requests. The catch is that access expires after 90 days of no logins, so re-requesting an old client later will require a verified user.

What do I need to complete the check?
A government-issued photo ID and a device with a camera for the selfie or liveness step. The flow runs through Stripe and takes a few minutes.

Does my Shopify Payments verification cover this?
No. That is merchant verification for the store owner. Partner verification is a separate system for the person sending collaborator requests. They do not substitute for each other.

I use overseas VAs. Can they still request access?
Yes, once each VA completes their own verification with a government ID. Build it into your hiring flow so a new hire is verified before they ever need to send a request through OnlineJobs.ph or anywhere else.

How does this connect to picking a niche or supplier?
It does not change your product strategy at all. If you are still at that stage, my 1,000 high-ticket niches list is the better starting point. For sourcing, my supplier directory is where I would send you next.

Want a fully done-for-you ecommerce business, verification and all? My team builds, verifies, and launches the whole thing so you skip the operational grind entirely. See the done-for-you options →

Get your team verified this week and this whole change costs you a few minutes. Ignore it, and it costs you a stalled client handoff at the worst possible time. Subscribe to the YouTube channel for daily breakdowns like this one. More breaking news later today.

Related Articles

If this was useful, these go deeper:

Share on Facebook
Post on X
Save
Share