Troubleshooting
A generation failed
It happens: AI providers time out, networks hiccup. When it does, you’ll see an error explaining what went wrong in plain terms, and the credits for that action come back to your balance automatically. Usually a retry just works. If the same step fails twice in a row, stop retrying and hit the Report button in the top bar so we can look at it. The report includes the technical context we need, so a one-line description from you is enough.
A seamless job looks stuck
A full seamless page takes several minutes, and the forge screen stages tick over slowly near the render steps. That’s normal. The job runs on our side, so closing the tab, losing wifi, or going to lunch doesn’t kill it. Come back to the project and the forge screen picks up wherever the job actually is.
If a job genuinely dies, it won’t hang forever: stalled jobs are detected, marked failed, and refunded automatically. If you see one stuck well past the fifteen-minute mark, report it.
Generated images don’t look like my product
Nine times out of ten this is a reference photo gap: the AI never saw the angle or the feature it got wrong. The fix is the reference photo guide, especially the part about close-ups of any feature your copy mentions. Then regenerate the slot in modular, or use a spot edit in seamless. Regenerating with the same thin references mostly produces new variations of the same guess.
I’m getting warnings when I approve
Approval warnings mean the draft steps outside one of Amazon’s structural rules, like a title over the length limit or a missing required field. They’re advisory: you can approve anyway if you know your category tolerates it. The point is that you’ll never break a rule silently.
The screen says my window is too small
The builders need room for editor and preview side by side, so ListingSmith wants a desktop-sized window. It isn’t built for phones. On a laptop, going fullscreen is enough.
My credits look wrong
The account page has a full transaction log: every charge, every refund, timestamped per action. Check it first, refunds sometimes land a minute after the failure. If the numbers still don’t add up, contact us with the project name and roughly when it happened. Billing questions get answered by a person.
Something else is broken
The Report button in the top bar is the fastest path: it attaches the technical context automatically and lands directly with us. For anything longer-form, questions, feedback, or a stuck account, use the contact page.