Distinguish download errors, example tracking, real order questions, and language corrections.
Identify the kind of problem before asking for help. An image download, a product-option preview, an ordering outcome, and a spelling concern require different information.
| Question | Retain |
|---|---|
| Download did not work | Asset identifier, page, selected action, and observed result |
| Preview looks wrong | Design, product options, device, and the visible problem |
| Order status is unclear | Actual confirmation or reference and the designated support channel |
| Language seems incorrect | Exact wording, supplied meaning, and proposed clarification |
The Store’s public navigation provides FAQ, terms, privacy information, and Track order. Read the actual information shown rather than assuming those screens all represent completed live services.
The checked project’s tracking page explicitly describes a mock-order lookup and future real-status connection. A sample identifier or a displayed demonstration shipment is not evidence that your product is in production or transit.
For a genuine order offered by the running Store, use its real confirmation and published support process. This documentation does not promise a carrier integration, delivery date, or order outcome that has not been established.
If the artwork wording is unclear, retain the asset page and expression. Explain whether you are asking about spelling, meaning, translation, or cultural context. A technical download report alone will not communicate that language question.
Read language and dictionary context before creating a changed version of the design.
The public catalog can grow beyond its initial image assets, and the available products and conditions can change. Use the running Store for the current item information and policies. These guides explain the journey so you can understand what is being offered and what still needs clarification.
