The same catalogue, rendered twice.
Flip between an untouched Tebex webstore and the same fourteen packages on the
server's own store page. Neither side has its own list: both read
demos/northpoint/content.js through the same module, and the whole catalogue is
printed further down this page so you can check both of them against it.
Before and after
Whole pages, top to bottom, captured from the two real pages
Both are full-page captures of the two real pages on this site, taken from the same catalogue on 9 August 2026. Neither is a mock-up and neither is trimmed. Open them live and check: the before · the after.
The before is a reconstruction, not a screenshot of anybody's store.
It reproduces what Tebex's own default storefront looks like, from the same catalogue as the build beside it. No real server has been photographed, named or used as the bad example, and the before capture carries that statement across the top of itself rather than only here.
One catalogue, two renderings
This is the evidence. The two captures above are the illustration
Fourteen packages across four categories. Every name and every price below appears on both
captures above, because there is one array and two renderers, not two lists. If the two could ever
disagree, the comparison would stop being evidence and start being a brochure — so a test
in tests/stock-storefront.test.js reads this demo's real
content.js and fails the build if a single price does not reach the stock page.
Prices are AUD, which is the currency of the real Tebex store this demo is modelled on. They are in-game packages for an invented server, and nothing to do with what a website from Your Future Site costs.
What changed
Every line is something you can see by flipping between the two above- The server is on the page. A name, a colour, a mark, and writing that could only be about this server. The default has none of that, not because it is badly made but because it has no way of knowing any of it.
- Packages are grouped, with a sidebar that goes somewhere. Same four categories, but a visitor can jump to the Garage instead of scrolling past four support tiers to reach it.
- Every package says what it actually is. The descriptions exist in both stores. Only one of them has anywhere to put them.
- The sale is legible as a sale. Tailored suits are $11.99 down from $14.99 on both sides. On the right it reads as a reduction; on the left it is a struck-out number with nothing saying why.
- There is room to say none of it is pay to win. The single most common question a store gets, answered on the page where the buying happens. A default storefront has nowhere for that sentence to go.
- The address belongs to the owner. A stock webstore lives at a tebex.io subdomain the owner does not control and cannot rank under their own name.
- Checkout does not move. Tebex still takes the payment and still pays out. This is a presentation layer over the same catalogue, not a change to how anybody gets paid.
What is deliberately not claimed
The most important section on this pageThe stock storefront is not broken, and nothing here says it is.
It is responsive, it holds together on a phone, it loads quickly and its checkout works properly. Those are all true and none of them are being argued with. A claim a prospect can disprove in five seconds is worse than no claim, and "their store is broken" is exactly that claim.
This build has no basket, and that is the tier rather than an omission. Perth RP is the Makeover Pro, $500 demo: 5 pages, live player count, and a store page grouped into categories reading the owner's real catalogue. A basket with quantities, coupons, gift cards and creator codes is the Storefront, $1,000 tier, and it is demonstrated on The Ends RP and Taverns RP rather than claimed here.
Nothing here needs Tebex Plus. The catalogue is read through the public Headless API, which Tebex documents as needing no authorisation and no paid plan. That claim is in every quote and it is checkable.
The boundary, stated here as everywhere else
We make it look right. We do not make it work in-game. The site, the storefront's look, the images and the descriptions are ours. Whether a purchase actually puts the car in the player's garage is a Tebex command or a script on the server, and that stays with the owner or their developer.
Ask what this would look like for your server →