Decision summary
A marketplace SKU taxonomy for PSN gift cards and PS Plus codes covering product type, region, denomination, duration, and support labels.
Build marketplace SKU IDs from stable product attributes: product family, PlayStation Store region, currency, denomination or duration, and delivery type. Price and stock can change; those attributes should not, or old orders become difficult to reconcile.
Decision fields
Separate wallet-credit PSN gift cards from PS Plus subscription codes.
Make PlayStation Store region a required attribute, not optional description text.
Use denomination for gift cards and duration or tier for subscription products.
Mirror the customer-facing compatibility language inside internal support tooling.
Marketplace SKU workflow
Before upload, define product type, region, currency, value, duration, batch ID, and owner as required fields.
Map each delivered batch to SKUs before any seller or listing team receives inventory.
Reject listing titles that omit region, currency, or product type.
Use claim patterns to refine taxonomy labels and prevent repeat confusion.
Stable SKU key and parent/variant map
Keep the SKU key tied to product identity rather than commercial conditions. Price, stock status, supplier batch, and campaign labels belong in linked records because they can change while the sellable product remains the same.
Build the key from controlled tokens for product family, PlayStation Store region, and denomination or subscription tier and duration. An illustrative pattern is [family]-[region]-[value-or-tier]-[duration]; use only the fields that apply to that product family.
Use the parent to group one product family for navigation and reporting. A parent is not sellable and must not hide region, currency, denomination, tier, or duration differences.
Create one leaf variant for each distinct combination a buyer can receive. Map every supplier line, listing, checkout item, delivery batch, and claim back to that variant key.
Do not recycle a retired key for a different product. Create a new variant when an identity field changes, then preserve the previous key on historical orders.
Controlled vocabulary record
- Product family: keep wallet-credit gift cards separate from PS Plus subscription products.
- Region label: use the approved catalog label and map aliases to it; do not silently convert a regional label into "global."
- Value: store currency and denomination separately for gift cards; store tier and duration separately for subscriptions.
- Vocabulary version: record the version, approval owner, effective date, retired tokens, and replacement tokens so feeds and support tools can be reconciled.
SKU taxonomy mistakes
- Do not publish a generic "PSN code" SKU without region and product type.
- Do not let sellers rename a Turkey, UAE, EU, UK, or US code as global unless explicitly confirmed.
- Do not mix PS Plus tier, duration, and wallet denomination in one value field.
FAQ
Why does taxonomy matter for PSN codes?
Region-specific digital codes create support risk when the catalog cannot show product type and account compatibility clearly.
Should region be in the title?
Yes. Region should appear in the title or primary attributes and repeat in checkout or delivery notes.
Can multiple regions share a parent SKU?
They can share a category, but each sellable SKU should keep region-specific fields separate.
What field helps support most?
Batch ID is often the most useful internal field because it connects customer claims to supplier delivery records.
Related pages
Trust context
PSN Wholesale is operated by PSN NETWORK LTD, company number 16191822. PlayStation, PSN, and PS Plus are trademarks of Sony Interactive Entertainment Inc. PSN Wholesale is independent and is not affiliated with, endorsed by, or sponsored by Sony Interactive Entertainment Inc.
Last updated: 2026-09-01