Game Currency Listings Across Marketplaces: Unit Size, Minimum Order, and Price-Per-Unit Mapping

If you sell in-game currency on more than one marketplace, the most expensive mistakes are rarely fraud or bad luck. They are unit mistakes. A price entered per million instead of per thousand, or a minimum order that is larger than your actual stock, can turn a profitable batch into a loss or a pile of unfulfillable orders.

This post covers a practical way to standardize currency offers across Eldorado, G2G, iGVault, Racoon, and GameBoost, and how to check them before upload. Always confirm each marketplace's current listing form, because field names and unit options can change and differ by game.

Why currency listings break differently than account listings

An account listing is a single item with a single price. A currency listing has several moving parts that all interact:

• Unit size: one unit, one thousand, one million, or a game-specific bundle.
• Price basis: price per unit, price per unit size, or a total price for the offer.
• Available stock: how much you can deliver right now.
• Minimum and maximum order: the smallest and largest quantity a buyer can choose.
• Delivery constraints: trade limits, delivery method, and server or realm.

When you copy an offer from one marketplace to another, any of these can silently change meaning. That is why multi-marketplace sellers benefit from a single source of truth rather than retyping numbers into each form. If you want background on the wider workflow, the Sellerbot features page explains how listing management, restock, and field mapping fit together.

Step 1: Choose one canonical unit

Pick one base unit for your own records and never change it. For most currencies, the safest base is the smallest tradeable unit, or one million units for currencies where single units are tiny.

Store three numbers per currency and server:

1. Stock in base units (for example, 500,000,000 gold).
2. Cost per base unit (what you paid or what it costs you to farm).
3. Target price per 1M units (a display figure you can sanity check at a glance).

Everything else is derived from those. If a marketplace lists per 1,000 units, you compute the number rather than guessing it. Avoid storing prices in marketplace-specific units in your master data, because you will eventually forget which unit a number was in.

Step 2: Build a field map for each marketplace

Before your first upload, write down how each marketplace expresses the same offer. Use a table like the one below as a template, and fill in the marketplace-specific answers yourself after checking the current listing form.

This is the same idea behind consistent identifiers, which we covered in the post on listing ID and title naming conventions. The field map is the numeric version of that discipline. The platforms page is a good place to review which marketplaces Sellerbot supports before you build the map.

Step 3: Work through a numeric example

Suppose you hold 500M units of a currency. Your cost is 3.20 per 1M, and you want a target price of 4.50 per 1M. The fee figure below is only an illustration. Use your own marketplace fee, payout, and withdrawal costs.

• Canonical price: 4.50 per 1M, which equals 0.0045 per 1,000 units and 0.0000045 per single unit.
• Assumed fee: 10 percent for this example.
• Net per 1M: 4.50 × 0.90 = 4.05.
• Margin per 1M over cost: 4.05 − 3.20 = 0.85.

Now the same offer on three marketplaces with different unit conventions:

• If a form lists per 1M, you enter 4.50.
• If a form lists per 1,000 units, you enter 0.0045.
• If a form wants a total for a fixed bundle of 10M, you enter 45.00.

The economics are identical. Only the presentation changes. If you derive each value from the canonical price, you remove the main source of unit errors.

Step 4: Set minimum and maximum orders deliberately

Minimum order is where many sellers get caught. Imagine you list 20M units with a minimum order of 5M on each of two marketplaces. A buyer takes 18M on one marketplace. The second offer now shows 20M for sale, but you only have 2M left, and the minimum order is above what you can deliver.

A few rules reduce this risk:

• Keep minimum order at or below your smallest realistic remaining stock.
• Reduce or remove offers when remaining stock falls below the minimum.
• Set a maximum order that matches one delivery session you are comfortable completing.
• Apply a reserve buffer per marketplace instead of listing all stock everywhere.

This connects directly to inventory allocation. For the deeper version of that problem, read how to prevent overselling when you list the same stock on multiple marketplaces.

Step 5: Handle rounding on purpose

Tiny per-unit prices make rounding matter. A price that looks like 0.0045 can be rounded to 0.005 by a form that supports fewer decimals, and that is an 11 percent change.

Use this approach:

1. Compute the price in your canonical unit with full precision.
2. Convert to the marketplace's unit.
3. Check how many decimals the form accepts.
4. If it rounds, switch to a larger unit size where available so the rounding error shrinks.
5. Recalculate your margin from the rounded price, not the ideal price.

Sellers often skip step 5, and it is the step that tells you whether the rounded offer is still profitable.

Step 6: Use a magnitude check before every bulk upload

Unit mistakes are almost always powers of ten. Add a simple check column to your restock sheet:

• Implied price per 1M: recompute from the value you are about to upload.
• Ratio to canonical price: implied price divided by your target.
• Flag: anything below 0.5 or above 2 needs review, and anything near 10, 100, or 1000 is almost certainly a unit error.

Pair this with the steps in the bulk restock batch prep checklist, which covers duplicate checks and column mapping for the rest of the batch. Running both takes a few minutes and prevents most of the painful corrections.

Step 7: Compare price suggestions in the same unit

When you review competitor-based price suggestions, convert everything to your canonical unit first. A competitor listing per 1,000 units can look ten times cheaper than your per-1M offer if you read them side by side without converting.

A safe review habit:

• Convert every suggestion to price per 1M.
• Compare it to your price floor, calculated from cost plus fees plus minimum margin.
• Reject any suggestion below the floor, no matter how small the gap looks.
• Approve moves in small steps rather than jumping to match the lowest offer.

The full approach to floors and review queues is in the post on price floors, undercut steps, and review queues. Sellerbot surfaces price suggestions for you to review, so the decision on what to accept stays with you.

Step 8: Keep one ledger for partial sales

Currency sells in partial amounts, which means one order rarely clears an offer. Every sale should reduce a single stock figure that all marketplaces reference. If you track remaining stock separately in each marketplace dashboard, the numbers drift within days.

A clean ledger has:

• Starting stock per currency and server.
• Sold quantity per order, with marketplace and order reference.
• Remaining stock, calculated rather than typed.
• Reserve buffer, so that you never list every last unit.

Sellerbot is built to sync sold stock across supported marketplaces, so this ledger does not have to live only in a spreadsheet. You can see how that looks in the live preview.

Pre-upload checklist for currency offers

Before you publish a batch, confirm each of these:

1. Canonical unit and base price are recorded for every currency and server.
2. Each marketplace's unit size and price basis are checked against its current form.
3. Prices are derived from the canonical price, not typed by hand.
4. Rounded prices still clear your margin after fees.
5. Minimum order is below deliverable stock on every offer.
6. Maximum order is set to a deliverable size.
7. Reserve buffer is applied per marketplace.
8. The magnitude check shows no flags near 10x, 100x, or 1000x.
9. Game and server names match your master list exactly.
10. Sold stock will update one shared ledger.

Putting it into practice

The goal is not to remember every marketplace's quirks. It is to make them irrelevant by keeping one canonical unit and converting at the edge. Once your field map and checks are in place, adding another marketplace is a matter of filling in one more column, not rebuilding your process.

If you manage several marketplaces today, review the Sellerbot plans to see what fits your volume, or open the seller panel to start mapping your first currency offers. For more workflow guides, browse the Sellerbot blog.