Senior Shopify + Claude Code Automation Expert — Build Agency-Wide Multi-Store Workflow

Senior Shopify + Claude Code Automation Expert — Build Agency-Wide Multi-Store Workflow We are looking for a highly experienced Shopify + Claude Code automation expert to help us architect and implement an internal development system for our agency. This is NOT a normal Shopify theme development job. We manage many Shopify stores for clients and want to build a scalable workflow where Claude Code can handle day-to-day Shopify development requests without us constantly having to log in, switch Shopify stores, reconnect accounts, or manually configure Claude for each client. What We Want to Achieve Our ideal workflow is extremely simple. A client sends us a request such as: “Make the product images larger on mobile and move the reviews underneath the Add to Cart button.” I should be able to give that request to Claude Code, specify the client/store, and Claude should be able to: 1. Identify the correct client and Shopify store 2. Access the correct repository/theme 3. Authenticate with the correct Shopify store automatically 4. Pull/sync the latest theme 5. Understand the existing theme architecture 6. Make the requested changes 7. Run Shopify Theme Check / relevant tests 8. Show what files and code were changed 9. Push the changes to a development/unpublished theme 10. Give us a Shopify preview URL 11. Wait for approval before anything goes live 12. Deploy after approval 13. Allow us to roll back changes if necessary The important part is that we should NOT need to manually log into Shopify or reconnect Claude/Shopify every time we switch between client stores. ⸻ Multi-Store Architecture We need someone who can build this properly for an agency managing many Shopify stores. We do NOT want a temporary workaround that works for 2–3 stores. It needs to be designed so adding another Shopify client is straightforward. For example, we would ideally have commands/workflows similar to: shop client-name shop client-name pull shop client-name preview shop client-name deploy shop client-name rollback Or another architecture if you can recommend something better. The goal is that the system automatically knows: * Which Shopify store it is working with * Which repository belongs to the client * Which theme should be used * Which credentials/authentication should be used * Which development rules Claude should follow * Which design system belongs to that client ⸻ Claude Code Setup We want Claude Code to become an internal Shopify development assistant for our agency. Each client/project should ideally have its own context/instructions so Claude understands the store before making changes. This could include: * CLAUDE.md * Store information * Theme architecture * Development rules * Brand/design system * Important components * Coding conventions * Shopify limitations * Client-specific instructions We are also open to using: * Claude Code hooks * MCP * Custom commands/skills * Scripts * Headless/programmatic Claude Code * Other automation if they improve the workflow. We want someone who already understands these systems and can recommend the correct architecture. ⸻ Shopify Authentication This is one of the most important parts of the project. We currently do not want to constantly: * Log into different Shopify accounts * Switch stores manually * Reconnect Shopify integrations * Reauthenticate Claude every time We need a secure multi-store authentication architecture. You should be experienced with things such as: * Shopify CLI * Shopify Theme Access * Shopify Admin API * Shopify GraphQL Admin API * Shopify OAuth * Offline access tokens * Shopify app development * Shopify Partner / Dev Dashboard * Multi-store authentication * Secure secrets management We are open to building our own internal Shopify agency app if that is the best long-term solution. The app could potentially be installed once on each client’s store and provide controlled access for our internal development system. However, we want YOU to recommend the best architecture rather than blindly implementing this approach. ⸻ Security Is Extremely Important We manage client stores, so Claude should never accidentally make changes to the wrong store. We need strong safeguards. For example: Client request → Claude development → Theme Check → Git diff → Development/unpublished Shopify theme → Preview → Human approval → Production Claude should NOT automatically make uncontrolled changes to live stores. We also want: * Proper Git version control * Rollback capability * Store verification before deployment * Production safeguards * Secure credential storage * No credentials committed to Git * Least-privilege Shopify permissions where possible * Clear logs/history of changes ⸻ Git / GitHub Each Shopify client should have either a dedicated Git repository or another properly isolated structure. We want every important Claude change tracked. Ideally: Client request → Claude modification → Git diff → Test → Preview → Approval → Commit → Deploy If something goes wrong, we need to be able to quickly restore the previous version. ⸻ Beyond Theme Development Initially, theme development is the most important part. However, we want the architecture to potentially support Shopify Admin operations later. For example: * Products * Collections * Metafields * Metaobjects * Menus * Navigation * Product data * Store configuration * Other Shopify Admin API operations Therefore, experience with Shopify’s Admin GraphQL API is highly valuable. ⸻ What We Need From You We don’t just need someone to write a few scripts. We need someone who can: 1. Audit our current setup Understand how we currently use: * Shopify * Shopify CLI * Claude Code * Git/GitHub * Client stores 2. Design the architecture Explain the best approach before implementation. 3. Build the system Implement the actual multi-store workflow. 4. Configure our first stores Help us onboard several real Shopify stores and make sure the workflow works properly. 5. Document everything Create clear documentation so we can add new client stores ourselves. 6. Train us Show us exactly how to use and maintain the system. ⸻ Required Experience Please apply only if you have strong practical experience with several of the following: * Claude Code * Shopify CLI * Shopify theme development * Shopify Admin API * GraphQL * Shopify app development * OAuth * Multi-store Shopify architecture * Git/GitHub * Bash/shell scripting * MCP * Claude Code hooks/automation * API authentication * Secrets management * DevOps / developer tooling Strong Shopify experience alone is NOT enough. Strong AI experience alone is NOT enough. We need someone who understands how to connect these systems properly. ⸻ Important Please do NOT apply with a generic proposal. Start your application with: “CLAUDE SHOPIFY SYSTEM” Then answer these questions: 1. Have you built production workflows using Claude Code before? Explain briefly. 2. Have you worked with multiple Shopify stores through Shopify CLI or APIs? 3. How would you avoid manually authenticating every time we switch between Shopify client stores? 4. Would you use Theme Access, Shopify OAuth/internal app authentication, or something else? Why? 5. How would you prevent Claude from accidentally deploying changes to the wrong client’s live store? 6. How would you securely manage credentials for many Shopify stores? 7. How would you structure Git repositories for this setup? 8. How would you make onboarding a new Shopify client as simple as possible? 9. Have you worked with MCP or custom Claude Code automation? 10. Give us a short overview of the architecture you would recommend. Please be specific. I would rather receive a short technical answer that proves you understand the problem than a long generic proposal written by AI. End Goal We want to eventually be able to open Claude Code and write something as simple as: “Venor: Client wants the Add to Cart button taller on mobile and the product title moved above the reviews.” The system should know which project/store we’re referring to, safely make the changes, test them, create a preview and let us approve the deployment. We want someone who can help us build that entire system properly from the beginning.