Chapter 2
Create the product record
Turn create the product record into a verified Tapmy setup step in 30–45 minutes, with a concrete output and buyer-path check—without mixing draft files and buyer-facing assets.
What you’ll get
- Primary setup: Open the product area.
- Working asset: Add the internal basics.
- Exit signal: the buyer can pay, receive the correct asset, and know what to do next.
Before you begin
Bring the final buyer asset, page copy, preview visuals, intended price, support address, and a device or account you can use for a clean test. Keep draft files outside the delivery folder.
| Setup decision | Evidence | Pass condition | Next action |
|---|---|---|---|
| Create the product record | Live preview, test purchase, received asset, or support record | The buyer sees the intended information and receives the correct result | Continue only after the path passes |
Conversion checkpoint
The product page and checkout must make the result, price, delivery, and next action predictable. Treat every unanswered question as friction. Verify the live buyer experience rather than relying on an internal dashboard state.
Open the product area
In the Tapmy dashboard, open the area used to manage products, then choose the current new product control. Select the digital product or downloadable product type that matches the delivery method.
If the dashboard presents multiple commerce formats, verify that the selected type supports the intended file or access delivery before continuing.
Add the internal basics
Enter:
- Product name
- Internal identifier or slug, if available
- Product type
- Cover image
- Draft status while you work
Use an internal name that remains recognizable when your catalog grows. Do not rely on “Untitled product” or “Final final version.”
Finish line
Build it in Tapmy
Complete and verify the live setup at Tapmy. Do not increase traffic until one fresh buyer-path test reaches the intended delivery result.
