Own the commerce platform your merchants use.

Deploy Box in the environment you choose, keep control of merchant relationships and data, and grow without giving away a share of every sale.

A studio team standing together in their workplace

Box Enterprise helps you own your platform and protect merchant relationships so growth stays in your control.

Box merchant dashboard

Own the platform

Run the engine and console in your environment against your database. The merchant relationship, operating model, and records remain yours.

Review the architecture
Account and commerce activity shown together

Keep the economics

Box is licensed per deployment. It does not take a percentage of merchant sales, so growth in the estate belongs to the institution.

See the commercial model
Merchant sales and operating context

See the business

Orders, products, customers, locations, and settlement outcomes create operating context that a transaction feed alone cannot provide.

Explore Insights

One programme, from migration to ongoing operation.

Plan the migration, agree the operating boundary, and keep the deployment current through one coordinated programme.

  1. Migration planning

    Map source systems, test critical workflows, reconcile records, and move merchants in controlled cohorts.

    Explore migration
  2. Deployment control

    Agree the region, infrastructure, identity boundary, provider connections, domains, and approval responsibilities.

    Review deployment security
  3. Ongoing access

    Keep the deployment current with package releases, upgrade guidance, documentation, and support.

    Review responsibilities

Built for every stage of an institution rollout.

A team operating a growing merchant business

Basic licence 30 packages

For an institution launching its first merchant platform with catalogue, orders, payments, websites, tills, invoicing, bookings, and analytics.

Growth licence 48 packages

Add subscriptions, memberships, loyalty, customer segmentation, campaigns, content, and locations without removing anything merchants already use.

Enterprise licence 51 packages

Add staff roles, cross-tenant analytics, device tracking, deployment-level data residency, and named support commitments.

“A licence should make the platform yours, not place your logo on somebody else’s estate.”

Box runs its own deployment internationally and licenses deployments by market. A licensed institution controls its merchant relationship, commercial terms, payment providers, access policy, and deployment data.

See the first licensed deployment

Pricing to meet your needs

A merchant team working together in a busy market

Annual access

30–50%of the original licence fee each year

Contact sales

Have questions?

Is the licence priced as a percentage of merchant sales?

No. Box separates the deployment licence, annual access, and merchant-level Connect usage.

Where does the deployment run?

The operating model and region are agreed during scoping. The institution operates the deployment by default, with Box Cloud available when a managed model is selected.

Can an institution change tiers later?

Yes. The tiers are nested, so moving upward adds capability without removing what merchants already use.

Who controls payment providers and merchant pricing?

The institution does. Box records commerce and provider outcomes but does not replace the institution, processor, acquirer, or settlement system.

How are existing merchants moved?

Migration uses data mapping, representative testing, controlled cutover, reconciliation, and cohort rollout.

What is needed for a proposal?

The merchant estate, initial tier, deployment region, integrations, migration scope, support expectations, and target rollout shape.