Shopify appears in the Data Sources tab on https://lengrowth.com/integrations. Like the other source cards, it attaches to a specific company workspace, so the integrations page asks you to choose a company first. If there is no company yet, LenGrowth tells you to create one before you continue. That workflow matters because the Shopify connection is stored against the company profile rather than treated as a loose account-level preference.

The backend usage metadata describes Shopify as revenue, orders, average order value, and repeat customer context. It says the source is used in founder reporting commercial sections and existing roadmap and task creation for ecommerce signals. That makes Shopify a company-revenue signal, not a storefront management product. LenGrowth uses it to inform reporting and the task flow when the business is ecommerce-based.

The setup form on the integrations page uses two explicit fields: Store domain and Admin access token. The placeholder for the domain is example.myshopify.com, which is useful because it tells the user exactly what kind of domain the app expects. The code does not ask for a public storefront URL. It asks for the admin store domain and a token that can read the store. The connect call posts those values to /integrations/shopify/connect.

Before you start, the backend guidance says to use a Shopify admin account that can create or install a custom app for the store. It also says to confirm the exact .myshopify.com store domain you want LenGrowth to read. That is important because the public store URL and the admin domain are not the same thing. The integration should use the admin domain, not the marketing website address the customer sees in a browser.

The backend instructions also point the user to Shopify admin Settings, then Apps and sales channels, then Develop apps. That is where the token comes from. The app expects a store domain and an admin access token with the right API scopes, so the connection is only as good as the underlying Shopify app permissions. If the token is copied partially, expired, or missing scopes, LenGrowth cannot read the company’s ecommerce data reliably.

Once the integration is connected, the card can show the selected store and sync state. The usage metadata says the connection unlocks live order, revenue, and repeat-customer signals. It also says ecommerce execution tasks stop waiting on store data once LenGrowth can sync the right storefront. That is the practical reason to connect Shopify. It lets the app ground its reporting and task priorities in real storefront behavior.

The route structure is straightforward. The frontend API uses /integrations/shopify/connect for setup, /integrations/shopify to check connection status, and the same base route for disconnect. That setup flow matches the UI: a company is selected first, then a store domain and access token are entered, then the card shows the connection state and selected store.

If setup fails, the backend guidance says to verify that the store domain is the .myshopify.com admin domain and not the public storefront URL. It also recommends rotating the admin access token if the old token was copied incorrectly or no longer has the required scopes. Those are the actual issues the code is built to handle. In other words, a Shopify connection problem is usually a store-identity or token-scope problem, not a LenGrowth-specific product bug.

Use Shopify when the company sells products through a Shopify store and wants LenGrowth to see revenue and order signals. If the company does not run on Shopify, there is no reason to connect it. If the company does run on Shopify, the integration gives LenGrowth a concrete ecommerce source that can improve reporting and task generation without inventing business metrics by hand.

The benefit is not only better visibility but also less manual reconciliation. Once the correct store is attached, the company workspace can refer back to the same store identity whenever reporting or task work needs ecommerce context. That keeps the source of truth stable even if the team is changing campaigns, products, or fulfillment priorities.

The setup flow also gives the user a clear place to sanity-check the store details before saving them. Seeing the .myshopify.com domain and the admin token field together makes it harder to confuse the public storefront with the admin connection that LenGrowth actually needs.

That separation matters because the reporting and the task flow only stay useful if they all point to the same store identity. A public storefront URL can look familiar, but the admin domain is what lets LenGrowth attach the real business source to the selected company.

That keeps ecommerce reporting anchored to one store instead of a guess.

It is a small check, but it prevents the wrong storefront from driving the report.

Related pages: