Full commerce platform

One platform for every part of merchant commerce.

Deploy the engine, console, website, till, payments, and automation together in your environment and under your name.

Choose the platform path most relevant to your institution:

Platform deploymentRun every merchant surface from one foundation→ Embedded componentsPut selected commerce tools inside your existing products→ Engine onlyBuild your own surfaces on the Box domain model→

Full platform deployment

Stop assembling six vendors into one merchant promise.

Install one licensed package set with a shared catalogue, customer, order, payment, and reporting foundation. The console, website, till, and automation layer move through one release path instead of drifting as separate products.

Explore the platform

One deployment

Operate the complete platform in infrastructure and regions you choose, with one observable boundary.

One upgrade path

Move the engine and every installed surface forward together from a tested package manifest.

One operating model

Give merchants consistent products, orders, customers, payments, and reporting across every channel.

Your brand

Keep Box behind the institution experience, domains, support model, and commercial relationship.

A customer paying with a phone at a counter

Embedded components

Bring commerce into the app merchants already open.

Install checkout, invoicing, catalogue, till, or reporting capability without introducing a second merchant identity. Each component reads the same commerce records and follows the institution’s navigation, permissions, and support route.

Explore embedded components

Checkout

Place a secure payment surface inside an existing journey.

Invoicing

Create and settle invoices without leaving the institution product.

Catalogue

Expose product management where merchants already work.

In person

Bring a till to compatible devices and institution-selected rails.

Identity

Use the institution auth guard instead of another merchant account.

Reporting

Return commerce outcomes to one merchant operating view.

Engine only

Build on the commerce model without taking the surfaces.

Use the OpenAPI description generated by the running deployment for catalogue, checkout, orders, customers, payments, and transactions. Your teams own every interface while Box supplies the domain model and upgradeable package boundary.

Explore Engine only

Build your own surfaces

Keep interaction and brand decisions with your product and engineering teams.

Generate against your box

Use the API description produced by the packages actually installed.

Keep providers swappable

Bind external services through explicit ports rather than hard-coded dependencies.

Compare the operating path

Full platform

Scope, deploy, operate.

Choose the complete package set, bind institution services, and launch every merchant surface through one release path.