Skip to content
Menu

Commerce

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?

A starting point for your project.

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.

In development

Before you plan around it
In development. Production purchase paths and supported provider configurations still require end-to-end verification.

Planned product scope

What it aims to bring together.

Candidate capabilities, subject to release verification.

Storefront & offers

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

Purchases & entitlements

Connect purchase flows to the items, rewards and unlocks a player should receive.

Economy & inventory

Coordinate currencies, inventory and rewards with the rest of your game's commerce systems.

Know the boundaries

Scope & compatibility.

Review the intended installation and the evidence still needed before release.

Platforms, providers & Unity versions

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.

Included scope & dependencies

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.

Current limitations & release gates

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

Demonstrations to come.

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. Help when you need it.

The product and its release scope are in development. Software licensing and project services are separate offers.

Software · In development

Commerce software license

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 product

Separately scoped services

Aether Commerce Integration

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 integration
Compare service options & how we work together

Software 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.

Assisted Setup

Your project fits a supported configuration and you need help getting started.

What you receive

Project preflight, installation, supported provider configuration, a checked reference flow and handoff notes.

Scope & engagement

Custom UI, data migration, unsupported providers and major architecture changes need a separate scope.

Fixed scope once the setup checklist confirms the fit.

Discuss setup

Production Integration

You need a supported product adapted to your existing game and its systems.

What you receive

Discovery, an integration plan, agreed project changes, provider and data integration, testing and handoff.

Scope & engagement

New provider adapters, broad redesigns and unrelated features are scoped separately.

Fixed scope for verified configurations. Uncertain work starts with paid discovery, then agreed milestones or time and materials.

Discuss integration

Custom Engineering

You need custom Unity UI, a new adapter, a migration or behavior beyond an existing product's scope.

What you receive

Agreed project-specific implementation, documentation and tests, with architectural work where needed.

Scope & engagement

The written scope defines what is included. New requirements are agreed before adding work.

Milestones or time and materials, with written change control.

Discuss custom work

How working together works.

  1. Start with a conversation

    Describe the outcome you need. A short free fit call establishes whether the work is a fit; detailed investigation belongs in discovery.

  2. Define the work

    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.

  3. Build, test and hand over

    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

Tell me what you're building.

Ask about Commerce, or describe where your project needs a hand.

Inquiry delivery is loading. See the privacy notice for how submissions are handled.

Inquiry details
Use the name you would like us to use when replying.
We use this only to reply to your inquiry.
A short description of your project and the support you need is enough.