The next useful step.
Keep the repair moving.
Most file and source questions can be resolved in your workspace. Start with the step that needs attention.
My catalog was rejected.
Use a current Shopify-style CSV with explicit SKUs and variant identifiers. Export only this family, preserve the original headers and options, and stay within 25 SKUs and 750 KB. Read the exact supported format.
My supplier document cannot be read.
Use a text-based PDF, TXT, CSV, or XLSX, up to 3 MB per file. A scan without readable text needs a text version. Keep the combined set within five files and 30 pages.
The sources disagree.
Open the evidence for that field. Choose a supported source value if you can establish it is correct, or keep the existing catalog value. A conflict does not become a fact just because one document looks more recent.
I lost my project link.
Open the workspace and use the recovery code saved in your private access file. If you still have the full project link, paste it into the private-link form. Project names alone do not grant access.
I paid, but the download is still locked.
Return to your private workspace and refresh the payment status. Confirmation may take a moment. If the status remains unresolved, contact support with the payment receipt and project name. Do not include your private access token.
The recheck shows a difference.
Compare the expected value with the value in your fresh export. Follow the package’s import instructions and check that the correct product and variant were updated. Other changed fields are reported separately so you can see changes outside the repair.
Need billing or delivery help?
Send the project name or workspace ID, the step that failed, and the exact visible error. Keep private links, recovery codes, customer records, and unrelated files out of the message.
This support channel handles service problems. The product does not include custom catalog research, a call, or a manual decision on conflicting supplier facts.