A name typed into a text field is not personalized game merch
Most product customizers work the same way. The buyer opens a product page, types a name into a field and picks a font. The result is one design for everyone with a single line changed, and it only happens if the buyer does the typing.
A game already knows more than a text field can ask. It knows the nickname, the level, the rank the player finished the season at, the clan they belong to and the skin they grinded for. Players screenshot exactly these things. Personalized game merch puts them on a product without asking the player to fill in anything.
That is what the API is for. Your studio decides which attributes may become artwork and sets the art direction. With the basic API, available today, your game sends those fields for one player as the text and picture layers of your template, or as a finished image, and gets a mockup back. When the player pays, your game places the order and the same design goes to print. No variant existed before that order, so there is no catalog of pre-made designs to maintain.
If you would rather hand over raw player data and have the artwork drawn on our side, we build a custom extended API for your game on request.
How personalized game merch gets from click to parcel
The player opens the merch screen inside your game or from a season email. Your game already knows who they are, so it asks the API for a mockup and the first thing they see is their own shirt, not a blank one.
They pick a size and pay. Your game places the order through the API, it routes to the closest production partner, and the parcel ships with tracking.
Player data that makes a good print
Six groups of attributes most games already store.
Identity
Nickname, avatar, chosen character, class. The core of a personal item.
Progress
Level, rank, season placement, hours played, win streak.
Belonging
Clan or guild name, emblem, roster position, founding date.
Loot
Weapon, skin, mount, artifact — the thing they grinded for.
Moments
First-kill dates, tournament placement, launch-day participation.
Safety rails
Your game filters what it sends. Banned-word lists and manual review on our side come with a custom extended API.
A text field on the product page vs. a design generated from the account
| Typical product customizer | Merch5 API | |
|---|---|---|
| Where the content comes from | The buyer types a name or uploads a picture | The player's account: nickname, level, clan, skin, season stats |
| What the player has to do | Fill in the fields and check the spelling | Nothing. Your game already knows them and shows their item |
| What ends up on the print | One design for everyone, with a line of text changed | A layout built per player inside your art direction |
| Proof of achievement | Anyone can type any rank | Rank, level and placement come from your game, not from the buyer |
| Variants to maintain | A listing per design, color and text option | None. Each design is made when the player asks for it |
| Print file | Varies by tool; personal text often needs a manual check | Made from the same design the player saw in the mockup |
| Moderation | Whatever was typed goes to print unless someone reads it | Your game's filter decides what is sent; banned-word lists and manual checks on our side come with a custom extended API |
| Setup | A plugin and a product template | An API integration on your side: the basic API is ready with docs, a custom extended one is scoped with you |
| Minimum run | Depends on the printer behind the tool | One |
Product customizers differ, and some handle uploads and layouts well. The difference here is the source of the design: the game, not a form. A store with fixed designs needs no integration and can run while the API is being connected.
What a demo with your game looks like
Three steps. Nothing is agreed before you have seen the result.
Send one character or logo
Write to hello@merch5.com with a piece of your art and a sample player: a nickname, a level, a clan name. A made-up player is enough.
We render a real example
We place your art in a template and show you a rendered, print-ready result: the preview a player would see and the file production would get.
You decide what comes next
If it fits, you get a key for the basic API, or we scope a custom extended one for your game. A store with fixed designs can be live in a day in the meantime.
Where personalized merch shows up
Inside the game
A merch tab beside the cosmetics shop, or a prompt after a season ends. Your screen asks the API for the player's mockup; a store with fixed designs opens as a web view, so nothing ships inside an app-store build. Six placements that work
On your website or launcher
A store with fixed designs sits behind a link on your site. Personalized items are ordered from your own page through the API. Add the widget to your site
In a reward email
Send a prepaid link to tournament winners or creators. The recipient picks size and address, and you pay only for links that are claimed. Prepaid merch links
Personalized game merch questions
Merch whose design is built from one player's own account: nickname, level, rank, clan, skin or a season result. Each item is generated for that player and printed after they order, so no two have to be the same.
Yes. The basic API is available now: the catalog with your prices, designs from an image or from text and picture layers, mockups, orders and status updates by webhook. Keys are issued on request: write to hello@merch5.com. A custom extended API, such as a generator that draws the artwork from raw player data, is built on request.
No. Your game already knows the player, so it sends their data to the API and the first thing they see is their own item. They pick a size and pay. A store on our side that opens from the game session is part of a custom extended API.
Only the fields you choose: what appears on the print, usually a nickname and a couple of numbers, and the delivery address once the player orders.
A store with fixed designs can be live in a day. The basic API is ready today, so the timing is your side of the integration: send the design, show the mockup, place the order. A custom extended API is scoped and quoted per game.
That is exactly what a demo is: we take one of your characters or logos and show a rendered, print-ready result before anything is agreed.
Yes. A store with fixed designs opens as a web view or a link, so nothing has to be shipped inside an app-store build. The API is called from your backend, so it works with any client.
With the basic API your game decides what text it sends, so your own nickname filter applies. Moderation on our side, with banned-word lists and a manual check on flagged orders, is part of a custom extended API.
No. The minimum print run is one, which is what makes a design per player possible.
There is no production run to fund: printing and shipping are charged out of each order after the player pays, and you set the retail price. A store with fixed designs is free to open. Ask about API access and a custom build for your game when you request the demo.
Season rewards, clan drops, tournament prizes, launch-week runs, creator kits and an in-game store tab. The six placements are described on the game merch ideas page.
We do. Each order is routed to the production partner closest to the buyer and ships with tracking to more than 100 countries. Print and delivery problems are on us, not on you.
Your margin adds to your balance in the dashboard. We pay it out automatically every two weeks, or right away when you ask, once $50 is available. You set the retail price, so you decide what that margin is.
Want to see it with your game data?
Write to hello@merch5.com and we will render a real example.