
Catalogue
One catalogue
Products, prices, and availability come from the same records used at the counter.
Commerce
Intelligence
Infrastructure
Why institutions choose Box
Keep the brand, records, rails, and merchant relationship.
Start here
By merchant activity
By deployment
See it running
OlivePay licensed Box. The tills are already in the field.
One integrated system

Catalogue
Products, prices, and availability come from the same records used at the counter.

Customers
Online and in person purchases belong to the same customer relationship.

Inventory
A sale on either channel changes the same inventory, so nothing waits to synchronise.






Give merchants a head start with adaptable commerce layouts built for selling online without giving up their own identity.
Explore templatesTheir brand
Branding, content, catalogue, and domain belong to the merchant. The institution can provide the complete experience without adding another marketplace name to the relationship.
Explore online commerce





A complete shopping journey
Products, services, bookings, and collections receive the right path rather than one generic template.
Customers can browse and complete an order from a phone without losing the context that brought them there.
Merchants highlight new items and collections while stock continues to come from one source.
Checkout reaches the payment implementation selected by the institution, not a separate account opened for the website.
Licence fit
Every merchant plan includes a website. The plans differ in how the merchant creates, extends, and operates the wider business.
Run the business and publish a website on a free Box address.
Describe the website and let Box build and refine it.
Build custom website experiences directly on Box.
No. Website is the online commerce surface on the Box engine. It reads the same catalogue as the till and writes orders into the same history.
Yes. The institution registers the host against the merchant, and the shared render resolves each request to the correct deployment and tenant.
Inside the deployment operated by the institution. The shared render fetches public data for each request and holds no merchant database of its own.
The website reads the same inventory the till changes, so the last unit sold at the counter is no longer available online.
Through the payment port and provider selected by the institution, using the same payment path as every other channel.
Yes. Products, services, and bookings can each use the purchasing and fulfilment path appropriate to what the merchant sells.