OpenCreators in one minute
- A store combines creator profile data, a published product catalog, and a selected template.
- The public URL uses the creator's claimed username and can be shared directly.
- Product type determines whether the customer purchases in OpenCreators or continues to a game-store offer.
An OpenCreators store is a public creator profile connected to a selected catalog. The creator builds the store once, publishes it to a username-based URL, and can then share that address with an audience. Visitors see the creator identity and the currently published products rather than the private setup screens.
The store is not a static mockup. It is assembled from account information, creator profile data, published catalog records, media variants, and a chosen storefront template. This separation allows the same underlying products to render appropriately on desktop and mobile.
From setup to a public store
Setup begins with a creator direction and a small set of topic tags. OpenCreators uses those choices to request product recommendations. The creator can keep or remove recommended items, edit supported service details, select a currency, and choose a storefront template before publishing.
On mobile, the guided flow explicitly includes currency and username steps. Desktop and mobile reach the same published model even though their step order and presentation differ. The important boundary is publication: draft choices are preparation; the public storefront represents what has been saved and published.
How products appear
Every product card uses the stored product title, description or game short description, price, currency, and best available image variant. Opening a card leads to a product-specific page. Service pages focus on the creator's offer; game pages can include the game description, tags, publishers, developers, and available store offers when that data is present.
A creator should keep card copy concise enough to scan while putting exact scope in the product description. Images should represent the actual offer. The uploader accepts JPG, PNG, and WebP media, up to five images, with a maximum of 10 MB per file in the current builder.
How customer actions differ
For creator products, the primary button starts the OpenCreators purchase process. Purchase creation is protected with an idempotency key so an accidental repeat action can be handled safely by the client and API. A resulting order can later appear in relevant account and chat contexts.
For game products, OpenCreators requests a redirect for the selected offer and then sends the customer to the external store URL returned by the service. The external seller controls the final checkout, availability, regional eligibility, and transaction terms.
How updates reach visitors
The public page reads the current creator profile and catalog. Changing the chosen template updates how the same store data is presented; updating a product changes the product information shown to visitors after the new data is saved. A shared store URL remains the durable entry point as the catalog evolves.
Creators should review the public page after meaningful changes, especially image crops, long descriptions, currency, and the destination of game offers. The preview is useful, but the published URL is the final customer-facing check.
Frequently asked questions
Can two creators have the same store URL?
No. The username portion is checked when it is saved, and a conflicting or unavailable value must be changed before publication can complete.
Does changing a template change the product data?
The template changes presentation. Product titles, descriptions, prices, media, and type-specific information remain catalog data and should stay consistent across templates.