Get collaborator access to a client's Shopify store

Confirm the client’s Shopify store, confirmed by its store URL. Ask the client to identify the account they actually use for the work in scope, rather than choosing from a familiar-looking name. Also agree whether the immediate objective is assessment, configuration or ongoing delivery. These details determine which permission is reasonable and what your team will check afterward. If the client is unsure which asset belongs to the project, resolve that ownership or account-selection question before they approve access to an unrelated account.

The request needs the store owner or authorized store administrator who can review the collaborator request. Send the instructions to that person or ask the client to involve them. A staff member who can read a dashboard may still lack permission to invite an agency. Repeating the same request with the same insufficient role will not fix that distinction. The authorized person should review the requested asset, recipient and permission before proceeding, and retain their own independent access after the agency is added.

The agency chooses the permissions in its collaborator request, and the store owner reviews them. Request the store areas needed for the work rather than treating collaborator access as unlimited access. Start by naming the actions the agency must carry out, then match the role to those actions. If the team only needs to inspect Shopify, explain why a viewing role may be sufficient. If a later task requires more authority, make that a deliberate scope decision with the client. Avoid requesting the broadest available role simply to prevent a possible future question; the current engagement should explain the permission being requested.

The onboarding step collects the client’s collaborator request code. The agency requests access through its Partner Dashboard, and the client approves or edits that request in Shopify. Read the status in the context of that workflow. An invitation, a client confirmation and usable Shopify access are related milestones, but they do not always happen at the same moment. Assign responsibility for the next step before marking delivery as ready. This prevents an agency teammate from arriving at a scheduled task and discovering that a required acceptance or platform action is still outstanding.

Use the agency’s Shopify Partner account submitting the collaborator request. Verify it before creating or sending the onboarding request, especially when the agency works through more than one account. Ask the actual recipient to confirm the identity they will sign in with. A forwarded email or a similar display name is not reliable proof that the correct account has been added. For a staffing change, arrange the replacement person’s appropriate access and remove obsolete assignments through the relevant platform process.

After the platform action, open the approved store through the agency Partner account and confirm the store URL and available areas before beginning any store changes. Record who performed that check and whether any required work remains blocked. Prefer a harmless viewing check over an unnecessary live edit. If a teammate cannot reach the asset, compare the actual recipient and role with the original request before asking the client to start again. Completion should mean the right person can reach the intended asset with the agreed capability, rather than only that a message or notification was received.

The Shopify step coordinates collaborator access only. Agency Pilot does not import the store’s orders or products through this connection. Keep the client’s reporting expectation explicit in the service brief. If a metric is needed for a report, identify its source, date range and definition before promising that it will appear. A successful access step establishes only the capabilities described for this particular integration. It should not be used as evidence that another platform, a separate dataset or an unrelated source of business results has also been connected.

If the request cannot be completed, confirm the store URL and current collaborator code with the client. If access is limited, compare the approved permissions with the tasks agreed for delivery. Start with account identity and authority because those determine what the client can share. Write down the exact stage where the flow stopped rather than repeatedly recreating the same request. If Shopify shows an account-specific restriction, the appropriate platform administrator may need to resolve it first. Avoid broadening permissions or switching to another asset just to make a completion indicator appear; verify the intended account instead.

No. It enables the agency to make the collaborator request; the store owner still reviews and approves it. Treat code received, request sent and request approved as separate stages. After approval, verify the store and permitted areas through the agency Partner account. This avoids scheduling storefront work while the request is still awaiting the client’s decision.

The described Shopify collaborator arrangement is separate from a staff account and does not use a store staff seat. It is intended for external work through the agency Partner account. The store owner still reviews the requested permissions. The practical question is which store areas the agency needs, rather than using a collaborator request as a reason to seek unrestricted access.

No. The integration described on this page coordinates access and does not import Shopify orders or products. If an engagement needs ecommerce reporting, identify the actual reporting source and its separate setup. A successful collaborator request should not be represented to the client as evidence that order data, product feeds or a revenue dashboard has been connected automatically.

Identify the correct store URL, the work the agency will perform, the requested permission areas and the person who approves publication. Agree how the team will review proposed storefront changes before they affect customers. These instructions belong in the project brief; collaborator approval alone does not define them. Also note whether product management remains with the client or another team to avoid overlapping changes.

Compare each requested area with the actual agency task and adjust the request before approval where appropriate. If the agency cannot explain why it needs a capability, clarify the scope rather than approving it for convenience. Afterward, verify that the approved arrangement supports the agreed work. A later requirement can be discussed separately without treating the first collaborator request as unlimited permission for future projects.

Remove the collaborator from the Shopify store’s users area and review any separate advertising or website services. Decide the ownership and maintenance of delivered store work separately from access removal. Agree a handover point before removing access that is still needed to finish approved work. Confirm the business retains the people and permissions it needs after the agency leaves. Keep permission removal separate from decisions about delivered work or historical reporting data; those are different questions. Record which Shopify assignments were removed and which, if any, remain for an explicitly agreed support period, with a clear owner for the final review.

Open the approved store through the agency Partner account and review the exact storefront task. Confirm the area or theme where work should occur and the person who approves publication before making customer-facing changes. If product-feed or advertising work is also required, coordinate Merchant Center or Meta access separately. The first useful delivery outcome is a reviewable store change within the approved permissions, rather than assuming that a collaborator code or approval connected every ecommerce reporting source.