Listing ID and Title Naming Conventions for Multi-Marketplace Game Sellers

Why naming conventions matter when you sell on several marketplaces

One marketplace is easy to run from memory. You know your offers, you recognize your titles, and you can spot a mistake at a glance. Add a second, third, or fifth marketplace and that stops working. The same Level 60 account batch might be called "EU Lvl 60 Starter" on one site, "Starter Acc 60 EU" on another, and "batch-14" in your spreadsheet.

The problems show up later:

• You cannot tell which sold order maps to which row in your source stock.
• A restock creates a duplicate because the old offer was named slightly differently.
• Price reviews become slow because you cannot compare like with like across platforms.
• Staff or helpers misread listings and delist the wrong thing.

A naming convention does not need to be fancy. It needs to be consistent, readable by humans, and easy to carry through a spreadsheet. Then every tool you use, including a multi-marketplace seller panel like Sellerbot, has clean data to work with.

The three layers: internal ID, marketplace title, description

Separate your naming into three layers. Each has a different job, and mixing them is the most common mistake.

The internal ID never has to be pretty. The marketplace title has to be tuned for each platform's buyers. The description should be a template with a few variables, not a blank text box you retype every time.

Designing an internal listing ID

A good internal ID encodes just enough to be useful when you read it in a spreadsheet or order list. A reliable pattern is:

TYPE-GAME-REGION-VARIANT-SEQUENCE

Pick fixed segments

• TYPE: ACC for accounts, CUR for currency, ITM for items, SVC for services.
• GAME: a short uppercase code you define once, such as OSRS, WOW, or VAL.
• REGION or SERVER: EU, NA, ASIA, or a server name when it matters to buyers.
• VARIANT: the attribute that changes the price, such as level, rank, platform, or item tier.
• SEQUENCE: a zero-padded number that never repeats, even after something sells.

Rules that save you later

1. Never reuse an ID. If ACC-VAL-EU-RADIANT-0031 sold, that number is retired.
2. Avoid spaces and special characters. Underscores or hyphens only, so IDs survive CSV exports and copy-paste.
3. Keep it short enough to say out loud. If a helper cannot read it over chat, it is too long.
4. Document the code list. Keep one tab in your sheet with every game code and variant code.

For currency and bulk items, the ID usually identifies a stock pool rather than a single unit, for example CUR-OSRS-GP-POOL-A. The quantity lives in a separate column. That keeps the ID stable while stock goes up and down.

Building marketplace title templates

Each marketplace has its own category structure, title rules, and buyer habits. Always check current limits and rules in each seller dashboard, because they change. What you control is the template, a fixed order of information that you fill in from your source data.

A flexible template looks like this:

[Key attribute] [Game/Region] [Product type] - [Differentiator] - [Delivery note]

Examples:

• Level 60 EU Account - Fresh Start - Instant Delivery
• 100M Gold NA Server - Safe Delivery - Fast
• Rank Diamond Account NA - Full Access - Email Included

Keep the order stable, adjust the wording

The key attribute should come first because buyers scan for it. If one marketplace shortens titles or ignores certain characters, trim the differentiator or delivery note first, not the key attribute.

Maintain a title variant per marketplace only when needed

Start with one master title per internal ID. Create a platform-specific variant only when a marketplace forces a different structure, for example when it has a separate category field that makes part of the title redundant. Record the variant in a column such as title_eldorado or title_g2g, not in your head.

Standardizing descriptions with reusable blocks

Descriptions are where time disappears. Instead of rewriting, split them into blocks:

1. What you get: a bullet list populated from your stock data (level, region, included items).
2. Delivery steps: the same wording each time, adjusted only for delivery method.
3. Policies and notes: warranty or support wording that matches your own practice.
4. Contact or support line: how buyers should reach you through the marketplace.

Keep the blocks in your source file or a template document. Fill the variable bullets from the same columns you used for the title. That way a change in one place, such as updating your delivery wording, does not require editing 200 offers by hand.

Carrying the convention into bulk restock

A naming system pays off most during a restock. When you prepare a batch, each row already has an internal ID, a master title, a description fragment, quantity, and price. Before upload, you can:

• Check that no internal ID appears twice in the batch.
• Check that the ID is not already live on the target marketplace.
• Confirm required columns exist for every platform you are uploading to.

If you use Sellerbot's bulk restock and field mapping, the consistent column names also make mapping faster. You map the same source columns to each marketplace's required fields, instead of re-deciding what each column means every time. You can also check the supported platforms to see which marketplaces you can handle from one place.

If you want the full upload prep flow, browse the other guides on the Sellerbot blog.

Using IDs to keep sold stock in sync

When an order arrives, the first question is always "which stock unit was this?" If your marketplace titles map back to an internal ID, you can answer in seconds. Practical habits:

• Store the internal ID in the source sheet next to every marketplace listing reference you have.
• When something sells on one platform, mark that ID as sold in your source of truth right away.
• Review the other platforms for the same ID and make sure the listing is removed or the quantity reduced.

Sellerbot is built to help sync sold stock across the supported marketplaces, but the cleaner your IDs, the easier it is to verify the results yourself. You can see how the panel presents this in the live preview.

Making price reviews easier with consistent naming

Competitive pricing only works when you compare equivalent offers. If your titles follow a fixed template and your internal IDs share a variant code, you can group offers by variant and see whether your price on one marketplace is out of line with the others. When you review price suggestions, group by variant first, then decide on adjustments.

Pair this with price floors so a suggestion never drops below your minimum margin. The goal is a repeatable review process, not constant manual tweaking.

Common naming mistakes to avoid

• Encoding the price in the ID. Prices change, IDs should not.
• Using marketplace order numbers as your only ID. They differ per platform and do not describe the stock.
• Different spellings of the same attribute. "Lvl", "Level", and "LV" in different rows will break filters and duplicate checks. Pick one.
• Free-text region fields. Use a short controlled list such as EU, NA, ASIA.
• Editing IDs after listing. If an ID has to change, record the old one in a notes column.

A simple rollout plan

You do not have to rename everything at once. Use this order:

1. Define your code list: game codes, type codes, region codes, variant codes.
2. Apply the ID format to new stock only, starting with the next restock batch.
3. Create the master title and description templates in your source file.
4. Backfill your best-selling live listings by adding their internal IDs to your sheet.
5. Audit weekly: filter for duplicate IDs, missing IDs, and listings with titles that do not follow the template.

Once a few batches have followed the convention, the rest of your catalog tends to follow naturally because mismatches become obvious.

Quick checklist

• Every stock unit or pool has a unique internal ID that is never reused.
• Titles follow one template with the key attribute first.
• Descriptions are built from reusable blocks.
• Column names are the same across every batch file.
• Sold items are marked by ID in one source of truth.
• Weekly audit checks duplicates and unmapped listings.

If you are ready to run listings across Eldorado, G2G, iGVault, Racoon, and GameBoost from one place, take a look at the Sellerbot plans or open the seller panel to start organizing your catalog.