Digital Goods for Marketplaces: Catalog, Stock and Delivery

Short Answer

Marketplaces can add gift cards, game top-ups and digital codes to their product catalog without logistics, warehousing or physical stock. Integration works through a wholesale supplier API: catalog sync imports products automatically, stock checks prevent overselling, and order creation delivers codes to customers instantly at the point of purchase. The main operational requirements are region-accurate product labeling, real-time stock, API-based fulfillment and a code delivery mechanism on the order confirmation page or via email.

Definition: Digital goods on a marketplace are zero-logistics digital products — gift cards, game top-ups, activation codes — fulfilled through a supplier API at the moment of customer purchase, without physical inventory, warehousing or shipping.

Key takeaway: Digital goods add a high-margin, zero-logistics product category to any marketplace. The integration is technical but one-time. The main ongoing risk is region mislabeling and stale stock — both are solved by real-time API integration, not manual processes.

Who This Guide Is For

• Marketplace operators evaluating digital goods as a product category
• Product managers at e-commerce platforms looking to expand into digital
• Tech teams building the integration between a marketplace and a digital goods supplier

Why Marketplaces Add Digital Goods

Digital goods are structurally attractive for marketplace operators:

Digital goods enable a marketplace to expand its catalog to hundreds of new SKUs with a single API integration.

What Digital Goods Marketplaces Can Offer

Integration Model

The API-based marketplace integration works as follows:

Marketplace Backend
  │
  ├── Product import: catalog API → marketplace product database
  ├── Stock check: called before checkout to verify availability
  ├── Order creation: called on payment confirmation
  └── Code delivery: code from API response → order confirmation page or email

Supplier API
  ├── GET /catalog — product list with names, regions, denominations
  ├── GET /stock/:sku — real-time availability
  ├── POST /orders — create order, receive code
  ├── GET /orders/:id — order status
  └── GET /balance — reseller account balance

Catalog Management

Product Naming Conventions

Region-explicit naming is the most important catalog discipline for digital goods:

SKU Organization

Create one SKU per brand × denomination × region combination. Do not combine regions in one listing.

Catalog Sync Frequency

• Full catalog sync: once per day (new products, removed products)
• Stock status: real-time at checkout, or polled every 15–30 minutes for display
• Pricing: once per day (or real-time if using dynamic pricing)

Stock and Pricing Sync

Stock can change rapidly for high-demand products. A marketplace that shows "in stock" from a morning sync may try to sell codes that are no longer available by afternoon.

Best practice:

• Always call stock check before accepting payment
• If stock check returns "out of stock" during checkout, block purchase and show "currently unavailable"
• For product listing pages, show stock status from a polling cache (15–30 min) — real-time is not required for browsing, only for checkout

Code Delivery to Marketplace Buyers

After a successful API order, the marketplace must deliver the code to the buyer. Delivery options:

The order confirmation page delivery is the recommended approach — it is instant and does not rely on email delivery.

Region Considerations for Marketplace Operators

A marketplace selling internationally must match product regions to buyer locations:

• If your buyer base is primarily UK, list UK PSN and UK Xbox cards — not US cards
• If you sell to multiple regions, list each region separately and use geo-targeting to surface the right SKUs
• Do not list a US Steam card as available to Turkish buyers without explicitly stating it won't work in the Turkish Steam store

Common Mistakes

1. No region in product title — buyers select the wrong region product; refunds follow

2. Stock check not called at checkout — out-of-stock orders fail after payment; creates support overhead

3. Not showing activation instructions — digital goods require instructions for first-time buyers

4. Long code delivery delay — digital buyers expect instant delivery; a 10-minute wait feels like a system error

5. One SKU for multiple regions — "Steam Card" with no region listed causes incorrect purchases

6. No expiry/usage instructions — some cards have expiry dates or usage limits; display them

Marketplace Integration Checklist

• Connect supplier API and receive sandbox credentials
• Import product catalog with region and denomination data
• Map product regions to target customer markets
• Create separate product listings per region per denomination
• Implement real-time stock check at checkout
• Implement order creation on payment confirmation
• Build code delivery mechanism (order page, email, or in-account)
• Display activation instructions with each code
• Set up balance monitoring with alerts
• Test full purchase flow for each major SKU before going live
• Submit sitemap update with new digital goods URLs