developer-products.md

title	description
Developer Products	Developer Products are items or abilities that users can purchase more than once.

A Developer Product is an item or ability that a user can purchase more than once, such as in-experience currency, ammo, or potions.

For items or abilities that a user should only purchase **once**, such as a special weapon or a permanent power-up, see [Passes](../../production/monetization/game-passes.md).

Creating Developer Products

When you're creating an image to use for your Developer Product, consider the following requirements:

• Use a template of 512×512 pixels.
• Save the image in either .jpg, .png, or .bmp format.
• Don't include important details outside of the circular boundaries because the upload process trims and crops the final Developer Product into a circular image.

To create a new Developer Product:

1. Navigate to your Creations page on Creator Dashboard and select your experience.

2. In the Monetization menu, select Developer Products. All developer products for that experience display.

   

3. Click the Create a Developer Product button.

4. Click the Upload Image button. A file browser displays.

5. Select the image you want to display as the icon, then click the Open button.

6. Fill in the following fields:

   • Name: A title for your Developer Product.
   • Description: A description what a user should expect when they purchase the Developer Product.
   • Price in Robux: The amount of Robux you want to charge users for the Developer Product.

7. Click the Create Developer Product button.

If you are creating a randomized Developer Product, review the Randomized Virtual Item Policy.

Locating Developer Product IDs

A Developer Product ID is the unique identifier of a Developer Product.

To locate a Developer Product ID:

1. Navigate to the Developer Product section of an experience's Monetization menu.

2. Hover over a Pass thumbnail and click the ⋯ button. A contextual menu displays.

3. Select Copy Asset ID. The Pass ID copies to your clipboard.

   

Scripting Developer Products

You must use scripting to implement Developer Product effects in your experiences.

Common Developer Product scripting use cases include:

• Prompting purchases.

• Handling purchases.

• Getting information.

Prompting Purchases

You can prompt a user to purchase one of your developer products with the Class.MarketplaceService:PromptProductPurchase()|PromptProductPurchase() method of Class.MarketplaceService. Depending on the needs of your experience, you can call the promptPurchase() function in situations such as when the user presses a button or when their character talks to a vendor NPC.

local MarketplaceService = game:GetService("MarketplaceService")
local Players = game:GetService("Players")

local player = Players.LocalPlayer

local productId = 0000000  -- Change this to your developer product ID

-- Function to prompt purchase of the developer product
local function promptPurchase()
	MarketplaceService:PromptProductPurchase(player, productId)
end

Handling Purchases

After a user purchases a developer product, it's your responsibility to handle and record the transaction. You can do this through a Class.Script within Class.ServerScriptService using the Class.MarketplaceService.ProcessReceipt callback.

local MarketplaceService = game:GetService("MarketplaceService")
local Players = game:GetService("Players")

local productFunctions = {}

-- Product ID 123123 brings the user back to full health
productFunctions[123123] = function(receipt, player)
	local character = player.Character
	local humanoid = character and character:FindFirstChildWhichIsA("Humanoid")

	if humanoid then
		humanoid.Health = humanoid.MaxHealth
		-- Indicate a successful purchase
		return true
	end
end

-- Product ID 456456 awards 100 gold to the user
productFunctions[456456] = function(receipt, player)
	local leaderstats = player:FindFirstChild("leaderstats")
	local gold = leaderstats and leaderstats:FindFirstChild("Gold")

	if gold then
		gold.Value += 100
		return true
	end
end

local function processReceipt(receiptInfo)
	local userId = receiptInfo.PlayerId
	local productId = receiptInfo.ProductId

	local player = Players:GetPlayerByUserId(userId)
	if player then
		-- Get the handler function associated with the developer product ID and attempt to run it
		local handler = productFunctions[productId]
		local success, result = pcall(handler, receiptInfo, player)
		if success then
			-- The user has received their benefits
			-- Return "PurchaseGranted" to confirm the transaction
			return Enum.ProductPurchaseDecision.PurchaseGranted
		else
			warn("Failed to process receipt:", receiptInfo, result)
		end
	end

	-- The user's benefits couldn't be awarded
	-- Return "NotProcessedYet" to try again next time the user joins
	return Enum.ProductPurchaseDecision.NotProcessedYet
end

-- Set the callback; this can only be done once by one server-side script
MarketplaceService.ProcessReceipt = processReceipt

The `receiptInfo` table passed to the `processReceipt()` callback function contains detailed information on the purchase. For a list of keys and descriptions, as well as guarantees related to the callback, see the `Class.MarketplaceService.ProcessReceipt|ProcessReceipt` reference. The functions for handling each product ID **must** return `true` for it to successfully process the transaction. If not, the product will not be awarded. Roblox itself does **not** record the purchase history of Developer Products by specific users, although you can request to [download sales data](../../production/analytics/analytics-dashboard.md#sales-data). If you want to track user-specific purchase history, it's your responsibility to [store the data](../../cloud-services/datastores.md).

Getting Information

To get information about a specific Developer Product, such as its price, name, or image, use the Class.MarketplaceService:GetProductInfo() function with a second argument of Enum.InfoType.Product. For example:

local MarketplaceService = game:GetService("MarketplaceService")

local productId = 000000  -- Change this to your developer product ID

local productInfo = MarketplaceService:GetProductInfo(productId, Enum.InfoType.Product)

local success, productInfo = pcall(function()
	return MarketplaceService:GetProductInfo(productId, Enum.InfoType.Product)
end)

if success then
	-- Use "productInfo" here
end

You can also get the data for all of the developer products in an experience by using the Class.MarketplaceService:GetDeveloperProductsAsync()|GetDeveloperProductsAsync() method. This returns a Class.Pages object that you can inspect and filter to build things like an in-experience store or product list GUI.

For example, the following script prints the name, price, ID, description, and AssetID for all Developer Products in an experience:

local MarketplaceService = game:GetService("MarketplaceService")

local success, developerProducts = pcall(function()
	return MarketplaceService:GetDeveloperProductsAsync():GetCurrentPage()
end)

if developerProducts then
	for _, developerProduct in developerProducts do
		for field, value in developerProduct do
			print(field .. ": " .. value)
		end
	end
end

Developer Product Analytics

Developer Product analytics help you gauge the success of individual Developer Products, identify trends, and forecast potential future earnings.

To access Developer Product analytics:

1. Navigate to your Creations page on Creator Dashboard and select your experience.

2. Navigate to Monetization > Developer Products and select the Analytics tab.

The Analytics tab enables you to:

• View top performing items: See your top selling and top grossing Developer Products over a selected time period.
• Analyze overall sales and net revenue: Showcase up to eight top items on a time-series graph.
• Monitor your catalog: Examine a table with up to 400 items, sortable by sales and net revenue.