Store state → linked metrics → products → math → crop.
- Use one clear reporting period
- Keep revenue, orders and AOV compatible
- Use synthetic customer and order data
Step 1: define the fictional store state
Choose a clear scenario: launch day, slow week, viral product, steady growth, high traffic with poor conversion or another specific business moment. That scenario determines which metrics should move together.
Write a one-line brief such as “the store just crossed $50k this month after a product launch.” It is much easier to build coherent revenue, orders and chart shape around a statement like that than around a random big number.
Step 2: pick a small set of linked metrics
Step 3: invent products and orders that fit
Use fictional product names, prices and order details that match the store niche and revenue story. If the dashboard says the store sells inexpensive accessories, an extremely high average order value may need explanation.
Avoid copying real customer data into the mockup. Invent names and order details so the visual can be shared safely with editors or collaborators.
Step 4: decide how deep the dashboard needs to go
A single analytics page may be enough for a short-form insert. A longer screen recording may need product lists, order views or secondary analytics. Build only the screens that will actually appear.
If the project needs a persistent fictional store with deep backend state, compare dedicated ecommerce simulators. If the dashboard is one scene in a larger creator story, a broader interface studio may be more efficient.
Step 5: test the math for obvious contradictions
You do not need perfect financial modeling. Check the basic relationships: revenue divided by orders suggests an average order value; visitors and conversion imply an order range; product prices should not be wildly incompatible with the totals.
This quick check prevents a visually polished dashboard from undermining itself with numbers that clearly cannot coexist.
Step 6: build for the medium
For a presentation, dense detail may be acceptable. For a vertical reel, emphasize one headline metric and one supporting chart or statistic. Test the mockup inside the final aspect ratio rather than judging only from the full browser window.
If the scene will be screen-recorded, rehearse the navigation path and remove any panels that add time without adding story information.
Common ecommerce-mockup mistakes
The biggest problems are usually inconsistent business math and generic filler. If the revenue, orders and average order value do not relate, the scene can feel artificial even when the interface is polished.
Likewise, random product names and customer rows add little if the viewer never sees them. Spend time on the metrics and details that support the fictional store narrative, then leave the rest simple.
GET SOLD REALITY.
About this resource
Published by Sold Reality. Sold Reality product details are based on the current V1 product; competitor-specific factual claims are checked against the public sources linked on comparison pages.
Questions
Do I need a real Shopify or ecommerce store?
No. A fictional dashboard can use entirely invented store data.
How do I keep revenue and order metrics consistent?
Use basic relationships such as revenue, order count and average order value, then check the visible values for obvious contradictions.
Can I make a recurring fictional store?
Yes. Saved scene states and consistent identity details can help a store return across episodes.
Can simulated revenue be used in an investor deck as real results?
No. Use genuine store and accounting data for real performance claims.