Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- For a store previously held as Client transfer, Collaboration describes the merchant-owned store that the Partner continues to access as a collaborator.
- Type and Status are separate columns. Collaboration / Active means access is active; Completed specifically means the transfer is done and no collaborator relationship remains.
- The client accepts the transfer by email. An unaccepted pending invitation expires after seven days, and the client selects the plan.
- The merchant controls collaborator permissions. Labels do not establish a particular account’s plan, paid invoices, or financial-product eligibility.
- Financial products can block a transfer, but Collaboration itself is not an error requiring those products to be deactivated.
Why a handed-off store becomes Collaboration
On October 13, 2026, Shopify staff member Paige-Shopify explained a Developer Community handoff question and reaffirmed the answer on October 14. When a Partner-owned Client transfer store is handed to its client and the Partner retains access, its type changes to Collaboration. The client becomes the owner; the Partner keeps a collaborator relationship.
This clarifies an existing workflow. Current official documentation also says that the merchant takes ownership, the store leaves the Partner organization, and collaborator access remains by default. In a known Client transfer handoff, the Collaboration label should not immediately be read as a failed transfer.
A Collaboration can also result from a separate access request for an existing merchant-owned store. The type alone cannot reconstruct ownership history or verify every detail of a particular account. For a specific handoff, the client and Partner should check their respective store records and transfer notices.
Read Type and Status separately: Completed has an extra condition
Type describes the current store relationship. Client transfer covers a store the Partner organization still owns while building it for a client. Collaboration covers access to a merchant-owned store. Neither is a payment-status field.
For client transfer statuses, In development means the store remains in the organization and has not been handed off. Pending transfer means an invitation is waiting for client acceptance. Neither establishes that ownership has already changed.
The documentation gives Completed a further condition: ownership has transferred and no collaborator relationship remains, so the Partner no longer has access. A store with retained access can appear under Collaboration; removing useful access just to obtain a Completed label is unnecessary.
Active on a Collaboration means that collaborator access is active. It does not identify the client’s paid plan, confirm that an invoice has been paid, or establish financial-product availability. The documentation also says the Plan column is populated only for Active collaborations; a dash on another status does not establish that the store has no plan.
An expired seven-day invitation: check the current record first
To start a handoff, open Stores in the Dev Dashboard, filter by Type is Client transfer, find the store, and choose Transfer store from its three-dot menu. This opens the store admin’s transfer settings. Enter the client’s email and send the request for the client to accept.
An unaccepted pending invitation expires after seven days. While it is Pending transfer, Manage transfer on the row offers resend and cancel actions. After expiration, first check the current type and status, then use the available transfer actions to send a new invitation. An expired old email is not a reason to repeatedly restart a handoff for a store already listed as Collaboration.
The client should check the target store and recipient identity before accepting. The authentication-code sequence in the community question is one user’s experience, not a universal verification workflow. If an invitation or identity check fails, follow the current email, page instructions, and official support.
The client selects the plan; labels cannot replace billing checks
Official developer documentation says the Partner cannot directly change a Client transfer store’s plan: transfer it first, and the client selects a plan when receiving the transfer. The Help Center says clients begin paying for their stores after ownership is transferred and they select a paid plan. Partners can build these stores for free without a time limit before handoff.
Treat ownership, plan selection, and payment as separate acceptance checks. Ask the client to inspect the current plan and actual billing records in their admin. Collaboration, Active, and continued Partner access are not evidence that a payment succeeded. This guide has not inspected any individual store’s payment state and provides no universal charge amount or timing.
Review the store address and billing currency with the client before handoff. For a project using POS Pro, official documentation notes per-location subscription charges once the store has a paid plan; the client should check actual charges. Transferred client stores are not eligible for promotions or free trials, so ordinary self-service trial promises should not be applied to this handoff workflow.
What access remains after handoff
Access retained after handoff is controlled by the merchant. Being able to open the store does not make the Partner its owner or authorize transferring it on the merchant’s behalf. Collaborators can reach only the areas the merchant has granted; the merchant should review any requested permission changes.
Access also has an inactivity boundary. If nobody in the organization logs into the store for 90 days, collaborator access expires. The documented Re-request access flow needs merchant approval again. This is separate from the seven-day ownership invitation; resending a transfer invitation is not the way to renew collaborator access.
Handle an actual financial-product blocker through the right route
The current Help Center lists active Shopify Payments, including test mode, Shopify Balance, Shopify Credit, and Shopify Capital as transfer blockers. An active product can remove the handoff option from transfer settings. Activation after the invitation is sent can also cause failure when the client accepts.
Check these conditions when an actual handoff is blocked; do not deactivate financial products merely because the type became Collaboration. Preserve the error and its time, and have the client confirm the relevant products and handoff arrangements. Official guidance separates Shopify Payments from Balance, Credit, and Capital: the latter three require Shopify Support to handle deactivation.
Changes involving payments, funds, or credit should be handled by an authorized party who understands the effects and follows official support guidance. Resume an unfinished handoff after the blocker is resolved. A merchant-owned Collaboration should not be transferred again simply to obtain a different label.
Sources
- Shopify staff clarification: Collaboration after handoff (October 13–14, 2026)
- Shopify developer documentation: Client transfer stores
- Shopify developer documentation: Collaborations
- Shopify Help Center: Client transfer stores and collaborations
- Shopify Help Center: Getting started — client plan selection and payment
Frequently Asked Questions
Does Collaboration prove that the store previously went through a client transfer?
No. A Collaboration can also come from an independent access request for an existing merchant-owned store. This guide concerns a known former Client transfer store. Other cases need their transfer notices and current records checked; the type alone does not reveal the full history.
Does Collaboration / Active prove that the client selected or paid for a plan?
No. It describes the relationship and access state. The client must separately check the plan and billing records in their admin; it does not confirm that an invoice was paid.
Are the seven-day invitation and 90-day access period the same countdown?
No. Seven days applies to an ownership invitation waiting for acceptance. Ninety days applies to collaborator access expiring after nobody in the organization logs in. They affect different objects and use separate transfer and access workflows.
Can an app-testing Dev store be transferred directly to a client?
Current documentation says Dev stores cannot be transferred to clients. Use a Client transfer store to build and hand off a client’s store. Do not confuse legacy development-store terminology with the current Dev store type.
Does retained collaborator access consume the client’s staff allowance?
Official collaboration documentation says collaborator access does not count toward the store’s staff limit. The merchant still controls the granted areas, and the Partner organization needs the relevant permissions. It does not confer unrestricted administration.