Shopify collaborator request email not sending — the owner never got the access invite.

Several products can look like “Shopify emailed someone about access.” They do not share a toggle or a send log. Native collaborator request / collaborator access invite mail fires when a Partner, agency, or outside operator submits Request access on your store — and Shopify emails the store owner (or the account that must approve) to accept or decline. It is admin / operator access email — not a storefront customer notification, and not a staff seat invite under Users and permissions.

Native staff / team member invite silence is staff invite email not sending. 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-request-email troubleshooting playbook. How Latch asks for collaborator access on your store (the DIY handoff steps) is Shopify collaborator access— that page is not “why the request email never landed.” This page is only the request / access-invite email that never landed.

Seven ordinary reasons that request never lands: Request access was never submitted, the owner inbox is wrong, the request is pending / declined / expired / already accepted, you mixed it with staff invite mail, you chased customer account invite instead, you tested staff invite / 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 an access-management app rebuild to read pending collaborator requests.

Opening Settings → Users and permissions and staring at staff seats does not email a collaborator request. Partners who paste a temporary password into Slack, ask for the owner login, or tell the merchant “just add me as staff” leave the collaborator request unused — Shopify did exactly what it was told.

Ask the Partner / agency: did they finish Request access on your store URL from their Partner Dashboard (or the current Shopify collaborator request path), with the permissions they need? The store owner should see a pending collaborator request to approve or decline. If there is no pending request, nothing left Shopify for this path — finish the request first, then wait for the invite email.

Permission picker abandoned mid-flow is an ordinary miss: someone started Request access, typed a note, then closed without submitting. There is nothing to deliverability-debug until a pending collaborator request exists.

Collaborator request mail sends to the store owner (or the account Shopify routes approvals to) — not to every staff seat, not to support@ by default, and not to the Partner’s own inbox as “proof the merchant got it.” If the owner email on the Shopify account is an old personal Gmail, a founder who left, or a shared alias nobody checks, Shopify has nowhere useful to deliver. That looks like “Shopify is not sending.”

A staff invite email typed under Invite staff is a different product — see /staff-invite-email-not-sending. A customer record email is not a collaborator request. BCC to the agency is not proof the owner got it. Shopify’s success toast after Request access means the request was queued for the owner path — not that the human you meant opened it. Read the pending collaborator request and the owner account email, not the toast alone.

If Shopify did send and the owner inbox is wrong, update who owns the store (or who can approve collaborators) and ask the Partner to resubmit. Resending to a dead alias does not invent a deliverable mailbox.

Pending means Shopify thinks it emailed the owner and they have not finished approve / decline. Declined means the owner (or someone with approval rights) rejected it — nothing more will land until a new request is submitted. Expired or stale pending requests are ordinary — ask the Partner to resubmit rather than rewriting Liquid on a customer template. Already accepted means collaborator access may already be live and the “missing email” is someone looking for a second confirmation — check Users and permissions / collaborators, not deliverability alone.

Ask the owner to search for Shopify, collaborator, and the Partner / agency name in inbox and spam before you escalate. If a pending request still exists and they never got mail, wrong inbox and spam beat “rebuild notifications” almost every time.

Do not stack five duplicate collaborator requests while the first is still pending. 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 (Invite staff / Add team member). 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 collaborator request email” while they actually sent (or expected) a staff invite — or the reverse.

Name which path you meant before you rewrite anything. Staff invite silence is /staff-invite-email-not-sending. The comparison of what each can do is /staff-account-vs-collaborator. How Latch asks for collaborator access (DIY steps after you buy) is /shopify-collaborator-access. This page only covers collaborator-request / access-invite mail silence.

If the person needs a staff seat (POS, limited permissions you only grant to staff), send staff invite — not a collaborator request. If they should stay on collaborator access, stop sending staff invites and debug this page instead.

Customer account invite / activate is for a shopper who needs a storefront account. Collaborator request is for an outside operator who needs limited admin. Support that keeps clicking Send account invite on a customer record while expecting Partner access will “never get the collaborator 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 collaborator access. Do not install a second helpdesk or “user invite” app to “make sure collaborator 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.

Completing Invite staff / Add team member proves staff invite mail — see /staff-invite-email-not-sending— not collaborator request. Previewing a customer notification or clicking Send account invite on a customer proves customer invite mail — see /customer-account-invite-not-sending. 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 collaborator access mail. Sending a staff invite or customer invite and only reading that inbox is how teams declare “access mail works” while collaborator requests still deliver nothing.

Honest test: use a Partner / agency account that is not already a collaborator on the store. Submit Request access with limited permissions. Confirm a pending collaborator request appears for the owner. Wait a minute. Then search the owner inbox and spam for Shopify, collaborator, and the Partner name. If there is no pending request, the bug is never-sent / cancelled mid-flow — not “Shopify email is down.”

Reading the Latch /shopify-collaborator-access DIY page proves you know the handoff steps after purchase — it does not prove a live Request access email fired. Shopify Flow “send internal email” is staff mail from Flow, not the collaborator-request path. If what you built is a Flow workflow that never runs, that is Shopify Flow not running, not a collaborator-request bug.

Shopify can send and the owner still reports nothing. Collaborator request 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 a pending collaborator request exists for the right store, have the owner search spam, promotions, quarantine, and the exact from-address Shopify used. If there is no pending request, go back to never-sent / wrong inbox / declined — 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 collaborator request exists and the owner 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: Request access actually submitted, correct owner inbox, pending vs declined vs expired vs accepted named, staff vs collaborator path named, real collaborator-request test (not a staff invite, customer invite, login link, or password reset), spam checked. Submit one live Request access and read the owner inbox. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related: staff invite email not sending, staff account vs collaborator (which seat to use), Shopify collaborator access (Latch DIY handoff), 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 request toast — it is connecting the stack you already have so collaborator handoff, staff access, customer mail, ops alerts, and exceptions are one live path instead of a pending collaborator request 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.