How to Sell Items With Roblox Developer Products

Choose a repeatable benefit#

Developer products are for repeat purchases, such as consumable items or game currency. A permanent unlock usually belongs in a game pass.

Describe the exact amount, where it appears, and when it can be used. “One trail-marker pack” is easier to evaluate than an unexplained boost. Show what the player receives before asking them to purchase.

Create the product#

Start with a published, accessible experience.

1. Select the experience in Creator Dashboard.
2. Open Monetization → Developer Products and create a developer product.
3. Add its name, description, image, and price, then save.
4. Copy its product ID for the integration.

Deliver through the server#

Use MarketplaceService's ProcessReceipt handler to grant purchases. Validate the player and product, make delivery durable and safe to retry, and acknowledge a receipt only after successful processing.

Track receipt identifiers to avoid duplicate grants. Keep product handling in one coordinated handler so adding an item does not replace another product's logic. Do not grant from the client or from PromptProductPurchaseFinished just because the dialog closed.

Ask PromptBlox to connect your inventory#

Integrate one developer product into my existing game. Product ID: [real product ID]. Benefit: [exact item or currency amount]. Keep game currency separate from Robux in all labels.

Add a compact purchase panel with current product information and an easy close action. Use the real Roblox purchase prompt. Route delivery through one server-side ProcessReceipt handler, with durable duplicate protection and safe retry behavior. Preserve other products already handled by the game.

Show the delivered benefit in the existing inventory. Keep ordinary gameplay available if product information fails to load. Provide a verification checklist for cancellation, reconnects, and repeated receipt delivery.

Test more than the happy path#

Record the inventory before and after each scenario. Include cancellation, reconnecting during delivery, an inventory that is full, and a temporary save failure. Simulate duplicate delivery attempts in a controlled test; do not repeatedly charge real players to exercise failure cases.

Collection effects should celebrate a confirmed reward. They should not make a failed or pending purchase appear complete.

Follow our testing guide, then check the published purchase flow. If the generated integration cannot demonstrate safe delivery, resolve that before offering the product to players.

Official reference#

This independent guide explains the workflow. Roblox's developer product documentation is the reference for current setup, purchase testing, and receipt-processing requirements.