Storefront & offers
Bring product presentation, an in-game storefront and offers into a connected purchasing experience.

Connect your game's store, purchases and player entitlements.
A connected Commerce Solution for Unity, bringing the storefront and the systems behind a purchase into one planned workflow.
Is it a fit?
For Unity teams building an in-game store and connecting what players buy to what they own. Start with your target platforms, providers and game economy to establish the right scope.
Before you plan around it
In development. Production purchase paths and supported provider configurations still require end-to-end verification.
Planned product scope
Candidate capabilities, subject to release verification.
Bring product presentation, an in-game storefront and offers into a connected purchasing experience.
Connect purchase flows to the items, rewards and unlocks a player should receive.
Coordinate currencies, inventory and rewards with the rest of your game's commerce systems.
Know the boundaries
Review the intended installation and the evidence still needed before release.
A supported configuration must identify its platform, providers and package versions, then pass installation and purchase-flow tests together. No production compatibility matrix is published here yet. Provider adapters are selected for a configuration; their presence in a catalog is not proof of support.
The proposed Solution brings together Storefront, IAP, Offers, Economy, Inventory, Rewards, Unlocks and Analytics. Required shared dependencies belong within the Solution's licensed scope. Final inclusion and optional provider adapters will be defined against verified release evidence.
A local development purchase provider does not establish a real-money transaction path. Commerce integration requires the relevant modules to reach 1.0 and selected configurations to work together. A later self-service release has its own installation, documentation, licensing and support gates.
Product evidence
Basic Storefront UI and LiveOps Offer Rotation are identified as candidate demonstrations in the product plan. Verified footage and supported configurations are not published on this page yet.
Availability & working together
The product and its release scope are in development. Software licensing and project services are separate offers.
Software · In development
The planned license covers the Commerce Solution and its required dependencies. Product licensing is separate from project implementation. Release scope, terms and a purchase destination are not published yet.
Ask about the productSeparately scoped services
Discuss the work needed to fit Commerce to your project: configuration, storefront adaptation, provider integration, testing and handoff. Delivery scope depends on a verified configuration; new adapters or migrations require separate scoping.
Discuss Commerce integrationSoftware licensing and project implementation are separate offers. Product-based setup and integration depend on a verified release and supported configuration; a concept page does not establish availability.
Describe the outcome you need. A short free fit call establishes whether the work is a fit; detailed investigation belongs in discovery.
Where the requirements are uncertain, paid discovery produces findings, risks and a recommended path. Before delivery, we agree on inputs, deliverables, exclusions and acceptance checks.
I deliver against the agreed scope and hand over documentation, test results and known limitations. Ongoing support is a separate agreement.
A direct line to the developer
Ask about Commerce, or describe where your project needs a hand.