In short
Check the myshopify.com domain, Shopify account access and your Reacast session, then identify the stage where connection fails. Restart from Settings when an attempt has expired. After authorization, check Connected separately from catalog synchronization to choose the appropriate recovery action.
Check prerequisites
Use the permanent store.myshopify.com domain, not a product URL or custom storefront domain. Check that your Shopify account can install the app on that store.
The app must be available for your store. A distribution-related refusal cannot be fixed by editing your product record.
Check whether Connect is available and what status the card shows. A message saying Shopify is not configured requires action on the Reacast side; changing your domain does not resolve configuration. If status is Connected, separate product import issues from store authorization issues.
Restart the connection
- Sign in to the correct Reacast workspace and start Connect from Settings > Integrations. Use the same Reacast origin for departure and return from Shopify.
- If the attempt expired or the session changed, restart from Settings rather than reusing an old link. Review permissions before approving.
On return, read the Settings message before starting again. “Store already linked” identifies association with another workspace; “session ended” requires an active Reacast sign-in. In both cases, keep the correct store’s permanent domain rather than randomly testing similar addresses.
Locate the failing stage
Before Shopify: check the entered domain and form error. On Shopify: check your account and installation availability for that store. After returning to Reacast: check session, workspace and saved status. Identifying that stage is more useful to support than “it does not work.”
Fictional example: authorization started from a Reacast preview address, but the return arrives at another address where you are not signed in. Restart from Settings on the address intended for that connection with your active workspace. Avoid manually copying callback parameters between the two addresses.
Provide the useful error
Keep the message, store domain and time for support. Do not copy a callback URL containing authorization parameters or send secrets. Connected status with an absent catalog is instead a synchronization issue.