Shopify staff invite email not sending — the team member never got the invite.

Several products can look like “Shopify emailed someone about access.” They do not share a toggle or a send log. Native staff / team member invite mail fires when an owner or admin completes Invite staff / Add team member under Settings → Users and permissions (Shopify’s staff accounts path). It is admin / operator access email — not a storefront customer notification.

Native customer account invite / activate is customer account invite not sending. Native customer login link / magic link is customer login link email not sending. Native customer password reset is customer password reset email not sending. When to use a staff seat versus collaborator access (and what each can do) is staff account vs collaborator— that comps page is not a missing-invite troubleshooting playbook. How Latch asks for collaborator access on your store is Shopify collaborator access. This page is only the invite email for a staff / team member seat that never landed.

Seven ordinary reasons that invite never lands: Invite staff was never completed, the invite email is wrong, the row is pending / expired / already accepted, you mixed it with collaborator request mail, you chased customer account invite instead, you tested customer invite / login link / password reset instead, or sender / spam hid a send that did fire. Walk them in that order. You already pay for Shopify. You do not need a user-management app rebuild to read Users and permissions.

Opening Settings → Users and permissions and staring at the list does not email anyone. Staff who paste a temporary password into Slack, share the owner login, or tell a contractor to “just create a Shopify account” leave the invite unused — Shopify did exactly what it was told.

Open Users and permissions. Look for a pending staff / team invite row with the email you intended. If there is no pending invite and no accepted staff user for that address, the invite was never submitted (or was revoked). Finish Invite staff / Add team member with the permissions you want, then wait for the invite — do not debug customer notifications for an admin invite that never left.

Permission picker abandoned mid-flow is the most common miss: someone opened Add staff, typed a name, then closed the modal without sending. There is nothing to deliverability-debug until a pending invite exists.

Staff invite mail sends to the email typed into Invite staff / Add team member. Open Users and permissions → the pending row. If the address is a typo, an old contractor domain, or the store’s own support@ alias nobody checks, Shopify has nowhere useful to deliver. That looks like “Shopify is not sending.”

A customer record email is not a staff invite. BCC to the owner is not proof the invitee got it. Shopify’s success toast after Invite staff means the invite was queued for that address — not that the person you meant opened it. Read the pending staff row, not the toast alone.

If Shopify did send and the address is wrong, revoke the pending invite and send a new one to the correct inbox. Resend to a typo does not invent a deliverable mailbox.

Pending means Shopify thinks it invited them and they have not finished accepting. Expired or stale pending invites are ordinary — revoke and reinvite rather than rewriting Liquid on a customer template. Already accepted means they may have an account and are stuck on login / 2FA / wrong store, not on a missing invite email. Revoked means staff cancelled the invite — nothing will land until you invite again.

Ask the invitee to search for Shopify and the store name in inbox and spam before you escalate. If the pending row still exists and they never got mail, wrong email and spam beat “rebuild notifications” almost every time.

Do not create a second staff invite to the same person while the first is still pending unless you revoked the first. Duplicate pending rows confuse both of you and do not prove deliverability.

Staff account invite and collaborator access request are different products. Staff seats are store team members under Users and permissions. Collaborator access is the Partner / agency request path an outside operator uses without a full staff seat. Mixing those two is how teams “never get the staff invite” while they actually sent (or expected) a collaborator request — or the reverse.

Name which path you meant before you rewrite anything. The comparison of what each can do is /staff-account-vs-collaborator. How Latch asks for collaborator access is /shopify-collaborator-access. This page only covers staff / team invite mail silence.

If the person is a contractor who should stay on collaborator access, stop sending staff invites. If they need a staff seat (POS, limited permissions you only grant to staff), send staff invite — not a customer account activate email.

Customer account invite / activate is for a shopper who needs a storefront account. Staff invite is for an operator who needs admin. Support that keeps clicking Send account invite on a customer record while expecting admin access will “never get the staff email” because they requested the wrong product. Debug /customer-account-invite-not-sending only when the missing mail is storefront activate — not this page.

Customer login link / magic link and password reset are also customer notifications: /customer-login-link-email-not-sending and /customer-password-reset-email-not-sending. None of those grant admin. Do not install a second helpdesk or “user invite” app to “make sure staff mail fires.”

Gift card created and order confirmation are storefront customer mail too — different products: /gift-card-email-not-sending and /order-confirmation-email-not-sending.

Previewing a customer notification or clicking Send account invite on a customer proves customer invite mail — see /customer-account-invite-not-sending— not staff invite. Continue with email / Get a login link proves customer login-link mail — see /customer-login-link-email-not-sending. Forgot password proves password-reset mail — see /customer-password-reset-email-not-sending. A paid checkout proves order confirmation — not staff access mail. Buying once or sending a customer invite and only reading that inbox is how teams declare “invite mail works” while staff invites still deliver nothing.

Honest test: use an inbox you own that is not already a staff user on the store. Settings → Users and permissions → Invite staff / Add team member with limited permissions. Wait a minute. Then search that inbox and spam for Shopify and the store name. Confirm a pending staff row exists for that email. If there is no pending row, the bug is never-sent / cancelled mid-flow — not “Shopify email is down.”

Shopify Flow “send internal email” is staff mail from Flow, not the Users-and-permissions invite. If what you built is a Flow workflow that never runs, that is Shopify Flow not running, not a staff-invite bug.

Shopify can send and the invitee still reports nothing. Staff invite mail often comes from Shopify’s own addresses, not your storefront customer-notification from-address. Corporate inboxes, Google Workspace filters, and “unknown Shopify” rules drop it into spam or quarantine. A shared alias nobody monitors also looks like silence.

If Users and permissions shows a pending invite for the right email, have the invitee search spam, promotions, quarantine, and the exact from-address Shopify used. If there is no pending invite, go back to never-sent / wrong email / revoked — do not buy a deliverability app for mail that never left.

Do not install a second “team invite” or SSO app to “make sure it fires” until you have proven a pending invite exists and the inbox was checked. You will add another login path without fixing the ordinary miss.

Stay DIY if you can spend one afternoon on the list above: Invite staff actually sent, correct email on the pending row, pending vs expired vs accepted named, collaborator vs staff path named, real staff-invite test (not a customer invite, login link, or password reset), spam checked. Send one live staff invite to an inbox you own. Read the inbox. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related: staff account vs collaborator (which seat to use), Shopify collaborator access, customer account invite not sending, customer login link email not sending, customer password reset email not sending.

Pay for help when the work is not the invite toast — it is connecting the stack you already have so staff access, collaborator handoff, customer mail, ops alerts, and exceptions are one live path instead of a pending staff invite plus a shared owner password plus a helpdesk nobody checks, lead capture is not dying in DMs, and exceptions show up in a channel you already check. That is the Latch AI Ops install.

What $997 USD one-time buys: lead capture on the live store, ops alerts in a channel you already check, and a checkout-ready workflow. 72 hours after collaborator access, not after payment. One live Shopify store. Access plus a delivery thread. Store URL collected at checkout. Not a SaaS seat, not a staff-SSO rebuild, not a Klaviyo rebuild, not a Gorgias implementation, not a support VA, not a brand or theme job.

Other shops’ public ranges, not testimonials: a Shopify Flow or access-workflow install typically runs $500–$2,500. A Klaviyo-only flow rebuild typically runs $2,000–$5,000. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as a ticket-cut number or recovered checkout revenue.

What it does not buy: fewer WISMO tickets, recovered checkout revenue, a lift in conversion, or a case study. Latch AI Ops has not published customer proof because there are no customers yet. You are buying the install.

Checkout is on Whop. Operator is Nico. United States offer. You can revoke collaborator access after handoff. We do not take owner passwords.