B2B platform for digital goods

How to Separate Steam, PSN and Xbox Regions in a Catalog

Each major gaming platform (Steam, PlayStation, Xbox) issues gift cards by region, and each region is a distinct product. A US Steam card and an EU Steam card are not variants of the same product β€” they are different products that serve different accounts.

How to Separate Steam, PSN and Xbox Regions in a Catalog


Short Answer

Each major gaming platform (Steam, PlayStation, Xbox) issues gift cards by region, and each region is a distinct product. A US Steam card and an EU Steam card are not variants of the same product β€” they are different products that serve different accounts. Your catalog must treat them as such: one SKU per brand per denomination per region. Mixing regions in one listing is the fastest way to generate wrong-region refund requests.


Definition: Region separation in a digital goods catalog means creating one unique product listing for each combination of brand, denomination and activation region β€” so Steam US $20, Steam EU €20 and Steam TR 100 TRY are three distinct products, not one product with regional variants.


Key takeaway: The catalog structure is where most region errors originate. Get the structure right and wrong-region complaints drop dramatically. The rule is simple: one SKU, one region, always.


Who This Guide Is For

  • Store operators setting up a gaming gift card catalog
  • Marketplace product managers defining catalog standards for digital goods
  • Developers building catalog import logic from a supplier API

Why Region Separation Matters

A customer searching for "Steam $20" on your store should only see cards that match their Steam account region. If you list "Steam $20 (US/EU)" as one product, customers cannot know which region they're buying, and wrong-region purchases are guaranteed.

The wrong way:

Product: Steam Gift Card $20
Regions: US, EU (combined)
Result: Customer guesses β†’ wrong region β†’ refund request

The correct way:

Product: Steam Gift Card $20 β€” US
Product: Steam Wallet Code €20 β€” EU
Result: Customer selects their region β†’ correct redemption

SKU Naming Conventions

Steam

Product Name Denomination Region Code
Steam Gift Card $5 β€” US $5 US
Steam Gift Card $10 β€” US $10 US
Steam Gift Card $20 β€” US $20 US
Steam Wallet Code €10 β€” EU €10 EU
Steam Wallet Code €20 β€” EU €20 EU
Steam Gift Card Β£10 β€” UK Β£10 UK
Steam Gift Card 100 TRY β€” Turkey 100 TRY TR

PlayStation Store

Product Name Denomination Region
PlayStation Store $10 β€” US $10 US
PlayStation Store $25 β€” US $25 US
PlayStation Store Β£10 β€” UK Β£10 UK
PlayStation Store €20 β€” EU €20 EU
PlayStation Store SAR 100 β€” KSA 100 SAR KSA

Xbox / Microsoft Store

Product Name Denomination Region
Xbox Gift Card $15 β€” US $15 US
Xbox Gift Card $25 β€” US $25 US
Xbox Gift Card Β£15 β€” UK Β£15 UK
Xbox Gift Card €15 β€” EU €15 EU

How to Map Supplier API SKUs to Your Catalog

Your supplier's API returns a catalog with SKU codes. Map them explicitly:

{
  "sku": "steam-20-usd",
  "name": "Steam Gift Card $20",
  "region": "US",
  "currency": "USD",
  "amount": 20.00
}

Your store product listing for this SKU:

  • Title: "Steam Gift Card $20 β€” US"
  • Description: "Adds $20 to a US Steam wallet. For US Steam accounts only."
  • Internal SKU: steam-20-usd (map your store SKU to supplier SKU)

Create one store product per API SKU. Do not merge two supplier SKUs into one store product.


Catalog Organization by Region

For the store navigation/category structure:

Option A: Organize by platform, then show all regions

Gaming Gift Cards
  └── Steam
       β”œβ”€β”€ US ($5, $10, $20, $50, $100)
       β”œβ”€β”€ EU (€5, €10, €20, €50)
       β”œβ”€β”€ UK (Β£5, Β£10, Β£20)
       └── Turkey (50, 100, 200 TRY)

Option B: Organize by region first

US Gaming Gift Cards
  β”œβ”€β”€ Steam US
  β”œβ”€β”€ PSN US
  └── Xbox US

EU Gaming Gift Cards
  β”œβ”€β”€ Steam EU
  β”œβ”€β”€ PSN EU
  └── Xbox EU

Option B is better for stores with a known customer geography. Option A is better for stores serving a global audience.


Geo-Targeting by Customer Region

For advanced stores, use the buyer's IP or billing address to surface the most relevant region first:

  • EU buyers β†’ EU products shown first
  • UK buyers β†’ UK products shown first
  • All other β†’ US products shown first (highest global demand)

This reduces wrong-region selection without hiding other regions.


Checklist

  • One product listing per brand Γ— denomination Γ— region
  • Region explicitly in product title
  • Supplier API SKU mapped 1:1 to store product
  • Category structure allows filtering by region
  • No product labeled "global" without verified country scope
  • Activation instructions region-specific per product
  • Pre-purchase region confirmation on all gift card products

Frequently asked questions

Should I show all regions to all customers?
It depends on your audience. Showing all regions is fine if you label them clearly and customers can identify their own region. Geo-targeting helps but is not required.
Can I have regional variants of one product in my store platform?
Some e-commerce platforms support product variants. If using variants, ensure each variant has the region in its name and its own supplier SKU mapping. Do not share SKU mapping across variants.
How do I handle a supplier catalog that uses ambiguous region codes?
Contact the supplier to clarify what each code means in terms of redeemable countries. Get written confirmation before listing. Do not infer region from product name alone if the supplier's labels are ambiguous.
Get FoxReload API access

Related articles