Vault Commerce OS

Run Your Inventory Commerce Business on One Connected Platform

Deploy Vault Commerce OS as a client-branded platform combining your website, rental and sales commerce, CRM, catalogue, inventory, warehouse workflows, fulfilment, portals and reporting.

Operate Commerce OS with your own teams and facilities. Add selected Vault services, Vault marketplaces and supported external systems only where your model requires them.

Request a Commerce OS Demo
Review Engagement Models
Client-branded Commerce OS
Modular implementation
Independent or connected
One connected business platform
Public + operational
01
Website and Commerce
Brand, pages, catalogue, rentals, sales, payments and enquiries.
→
02
Inventory and WMS
QR identity, stock, locations, receiving, movement and availability.
03
CRM and Automations
Leads, accounts, pipelines, tasks, campaigns and follow-ups.
04
Fulfilment and Insight
Reservations, dispatch, returns, portals, connections and reporting.
Begin with the modules your business needs now.
Expand in controlled phases
Choose the appropriate starting scope

Launch Selected Modules, Connect Operations or Deploy the Complete Platform

Commerce OS does not require every capability on day one. Begin with the immediate business requirement and extend the platform as users, locations, channels and operational depth grow.

↔ Swipe through the deployment models
01

Start with Core Modules

Deploy the first platform layer without replacing every existing system immediately.

  • Website and lead capture
  • Catalogue and inventory control
  • CRM and account workflows
  • Rental or sales commerce
02

Connect Commerce and Operations

Bring the client experience, inventory and physical execution into one operating record.

  • Website plus CRM
  • Commerce plus availability
  • WMS plus fulfilment
  • Returns plus condition history
03

Deploy the Complete Commerce OS

Operate the full inventory-led business across public commerce and internal teams.

  • Client-branded website
  • CRM, catalogue and WMS
  • Transactions, fulfilment and returns
  • Portals, reporting and connections
Four connected platform families

From Client Experience to Physical Inventory Execution

Each family can operate independently. When combined, the same records connect the public website, client relationships, inventory, fulfilment and management reporting.

↔ Swipe through the Commerce OS modules
01

Website and Commerce

Operate the client’s brand, catalogue, enquiry, rental, sales and account experience.

WebsiteCMSRentalsSales

View website and commerce

02

Inventory and WMS

Connect catalogue information with stock, QR identity, locations and physical movement.

CatalogueQRLocationsAvailability

View inventory and WMS

03

CRM and Automations

Manage enquiries, clients, pipelines, communications, tasks and approved triggers.

LeadsAccountsPipelinesAutomations

View CRM and automations

04

Portals and Connections

Provide controlled access, connect supported systems and report across the operation.

PortalsRolesConnectionsAnalytics

View portals and connections

See the complete Vault Commerce OS architecture

Follow the Platform across All 10 Connected Commerce OS Modules

Start with the complete architecture, then move through the client-owned website, inventory and WMS, rental commerce, CRM and automations, orders and fulfilment, marketplace connections, data migration, integrations, reporting and analytics, and implementation and support.

Slide 1 of 11

Complete Vault Commerce OS architecture

02
Client-Owned Commerce Website The screen shows a fictional client-branded website configuration with CMS, catalogue, commerce, account and enquiry controls.
Module 1 · Client-Owned Commerce Website

Operate the Public Brand and Commerce Experience from the Client’s Own Platform

The website layer connects public discovery and transactions to the same catalogue and operating platform used internally.

  • Client brand, domain and CMS
  • Catalogue and discovery
  • Cart, checkout and accounts
  • Enquiries and lead capture
What this screen demonstrates The client website is independent of optional Vault marketplace publication.
03
Inventory and Warehouse Management The screen shows fictional inventory, QR identity, warehouse hierarchy, stock state, movement, count and capacity controls.
Module 2 · Inventory and Warehouse Management

Maintain the Physical Truth beneath Every Commercial Workflow

The WMS layer controls where inventory is, what state it is in and what physical work has occurred.

  • Unique or quantity-based inventory
  • Warehouse and location hierarchy
  • Movement, picking and packing
  • Counts, discrepancies and capacity
What this screen demonstrates Physical stock state remains authoritative for availability and warehouse execution.
04
Rental Commerce The screen shows fictional rental rates, date availability, reservation, active rental, extension, return and recovery states.
Module 3 · Rental Commerce

Add Time-Bound Availability and Rental Lifecycle Logic to Physical Inventory

Rental Commerce manages the commercial lifecycle around inventory that returns to use after each rental.

  • Rental eligibility and rates
  • Date availability and buffers
  • Reservation, active rental and extension
  • Return, care and recovery lifecycle
What this screen demonstrates A returned rental is not available again until the approved recovery workflow completes.
05
CRM and Automations The screen shows fictional leads, accounts, pipelines, tasks, activities, consent and approved automation controls.
Module 4 · CRM and Automations

Connect Relationship Context, Follow-Up and Operational Work

CRM provides accountable ownership from initial enquiry through ongoing account activity and service workflows.

  • Leads, contacts and accounts
  • Pipelines, tasks and activities
  • Service and collections workflows
  • Consent-aware approved automations
What this screen demonstrates A CRM contact does not automatically imply permission for promotional communication.
06
Orders and Fulfilment The screen shows fictional demand validation, stock allocation, source routing, fulfilment ownership, dispatch and completion state.
Module 5 · Orders and Fulfilment

Translate Approved Demand into Accountable Physical Fulfilment

The orchestration layer determines what should be fulfilled, from where and by whom while the WMS performs physical execution.

  • Demand and release validation
  • Stock allocation and split fulfilment
  • Client, managed or hybrid routing
  • Dispatch, delivery and exception control
What this screen demonstrates Orders and Fulfilment is the orchestration layer; the WMS remains the physical execution layer.
07
Marketplace Connections The screen shows fictional marketplace account state, mappings, publication, availability, transaction intake and sync health.
Module 6 · Marketplace Connections

Connect Approved Marketplace Destinations without Creating Separate Inventory Truth

Destination-specific mappings and publication can coexist with one governed internal catalogue and stock relationship.

  • Marketplace account and permissions
  • Category and attribute mapping
  • Publication and availability sync
  • Transaction, status and exception exchange
What this screen demonstrates Connector capability always depends on the destination and approved implementation scope.
08
Data Migration The screen shows fictional source assessment, mapping, cleaning, staged import, reconciliation, cutover and rollback evidence.
Module 7 · Data Migration

Establish a Trusted Opening Data State before Production Use

Migration is a controlled implementation programme rather than a one-click import.

  • Source assessment and data profiling
  • Mapping, cleansing and lineage
  • Dry runs and reconciliation
  • Cutover, rollback and archive
What this screen demonstrates Migration success is measured by reconciliation and usability, not merely imported row count.
09
Integrations The screen shows fictional system ownership, connection methods, sync, reconciliation, retries and integration health.
Module 8 · Integrations

Maintain Ongoing Exchange with the Client’s Wider Technology Stack

Integrations connect live systems after go-live while retaining explicit source-of-truth ownership.

  • APIs, webhooks and scheduled sync
  • Finance, payments, logistics and ERP
  • Idempotency and reconciliation
  • Failures, retries and provider changes
What this screen demonstrates Integrations is ongoing exchange; Data Migration establishes the opening state.
10
Reporting and Analytics The screen shows fictional operational dashboards, KPI definitions, trends, drill-down, scheduled reports, exports and freshness state.
Module 9 · Reporting and Analytics

Measure the Business without Disconnecting the Number from Its Operational Evidence

Reporting connects defined metrics to the source records and exceptions that explain performance.

  • Operational dashboards
  • KPI definitions and trends
  • Drill-down, saved views and schedules
  • Exports, BI and freshness governance
What this screen demonstrates Reporting measures operational truth but does not replace the module that owns the underlying record.
11
Implementation and Support The screen shows fictional configuration readiness, UAT, go-live, support cases, service health, changes and releases.
Module 10 · Implementation and Support

Keep the Platform Testable, Supportable and Controlled after Go-Live

The software lifecycle continues through support, service health and controlled platform change.

  • Configuration and readiness
  • UAT, training, cutover and hypercare
  • Incidents, requests and support history
  • Change, testing and release governance
What this screen demonstrates Support commitments follow the applicable agreement rather than universal public SLA promises.
↔ Swipe through all 10 Commerce OS modules
01
Own the client experience

Website and Commerce

Operate the client’s public brand, content, catalogue and commercial journeys from the same platform used by the internal teams.

The commercial model can support rental, sale, subscription or approved combinations without forcing one marketplace structure onto every client.

Client brand
Own domain
Rental and sales
↔ Swipe through website and commerce capabilities

Website, CMS and Navigation

Manage the approved public structure and content.

  • Pages, landing pages and menus
  • Brand presentation and content blocks
  • Service, category and campaign pages
  • Controlled publishing and revision

Catalogue and Discovery

Present searchable inventory and commercial information.

  • Categories, filters and search
  • Images, attributes and variants
  • Availability and commercial eligibility
  • Related inventory and recommendations

Rental and Sales Commerce

Configure the transaction types used by the business.

  • Rental duration and availability
  • Sales, subscriptions and deposits
  • Extensions, returns and exceptions
  • Pricing and approval boundaries

Enquiries and Client Accounts

Connect public activity with the client record.

  • Forms and lead capture
  • Account and portal access
  • Quotations and approved transactions
  • Communication and activity history
02
Connect digital and physical inventory

Inventory and Warehouse Management

Keep the catalogue identity, available quantity, condition, warehouse location and movement history connected to the same inventory record.

The client can operate its own facility, use selected Vault services, or divide responsibility by location and workflow.

Client warehouse
Multiple locations
Optional Vault connection
↔ Swipe through inventory and WMS capabilities

Catalogue Identity

Create a structured digital identity for each inventory group or item.

  • Variants, attributes and images
  • SKU, QR or barcode identity
  • Condition and care information
  • Documents and custom fields

Warehouses and Locations

Model the locations used by the client’s physical operation.

  • Warehouses, floors and zones
  • Aisles, racks, shelves and bins
  • Rails, boxes and floor slots
  • Transfers and location history

Inbound and Movement

Record inventory entering and moving through the operation.

  • Arrival and receiving
  • Counts, scans and discrepancies
  • Put-away and internal movement
  • Holds, exceptions and approvals

Availability and Fulfilment

Translate commercial demand into exact physical actions.

  • Availability and reservation checks
  • Pick, pack and dispatch tasks
  • Returns and condition reconciliation
  • Restoration and return to availability
03
Turn enquiries into accountable work

CRM and Automations

Connect website enquiries, clients, opportunities, communications, tasks and transaction activity instead of rebuilding the relationship history across separate tools.

Automations are configured around approved business rules and should support the team without hiding responsibility.

Sales teams
Account management
Operational follow-up
↔ Swipe through CRM and automation capabilities

Leads and Accounts

Maintain a structured relationship record from first enquiry onward.

  • Lead source and qualification
  • Client and organisation records
  • Contacts, notes and documents
  • Complete interaction history

Pipelines and Opportunities

Make the next commercial action and responsible person visible.

  • Configurable pipeline stages
  • Opportunity value and probability
  • Tasks, calls and meetings
  • Handoffs and management review

Campaigns and Follow-Ups

Coordinate approved outreach and repeat activity.

  • Segmented client groups
  • Email, calling and social activity
  • Reminders and scheduled follow-ups
  • Campaign response tracking

Operational Automations

Trigger actions from meaningful platform events.

  • Assignment and task creation
  • Status and exception notifications
  • Approval reminders and escalation
  • Activity logs and ownership visibility
04
Control access and extend the platform

Portals, Connections and Analytics

Give clients, staff, warehouse users, partners and management the correct views and actions without exposing unrestricted administration.

Supported external systems can be connected through defined mappings, permissions, logs and exception handling.

Role-based portals
Supported connections
Management visibility
↔ Swipe through portals, connections and analytics

Client and Account Portals

Provide controlled self-service and relationship visibility.

  • Profile and account information
  • Transactions, requests and documents
  • Inventory and status visibility
  • Support and communication history

Staff and Partner Roles

Configure access around responsibility rather than one generic login.

  • Sales, catalogue and warehouse roles
  • Partner and vendor access
  • Location and module restrictions
  • Approval and override rights

External Connections

Connect approved services and systems where feasible.

  • Payments and logistics
  • Vault and external marketplaces
  • Accounting and business systems
  • Mappings, sync status and exceptions

Reporting and Analytics

Review the business through connected commercial and operational data.

  • Inventory and utilisation
  • Rentals, sales and transactions
  • CRM and team activity
  • Warehouse performance and exceptions
Implementation journey

Move from Requirements to a Controlled Client Launch

The final sequence depends on the selected modules, data quality, brand, roles, facilities, connections and acceptance requirements.

↔ Swipe through the implementation stages
01

Discover

Document the business, catalogue, users, facilities, commercial model and current systems.

02

Design

Confirm modules, roles, workflows, data boundaries, brand structure and acceptance criteria.

03

Configure

Build the tenant, website, fields, permissions, commerce, CRM and warehouse workflows.

04

Migrate and Connect

Clean and import approved data and connect technically feasible external systems.

05

Test and Train

Complete acceptance testing, operational simulation, user training and launch preparation.

06

Launch and Improve

Release the first operating scope, support users and expand the platform through a controlled roadmap.

First operating release

Prioritise the modules and workflows required to run the first stable client operation.

Controlled expansion

Add advanced reporting, automation and optional ecosystem connections after the foundation is stable.

Who manages what

Operate the Platform Yourself, Share Selected Work or Add Managed Support

Responsibilities should be defined by module and workflow. Commercial approval remains with the client unless an agreement expressly states otherwise.

Responsibility
Client-Operated
Shared Support
Vault-Managed Support
Platform administration
Client
Shared by scope
Vault platform team
Website and content
Client team
Divided by content type
Agreed managed team
Catalogue and inventory data
Client team
Divided by workflow
Agreed managed team
Warehouse and fulfilment
Client team
By site or transaction
Vault where contracted
Commercial approvals
Client
Client
Client approval retained
Platform support and updates
Included by plan
Included by plan
Included by plan
↔ Swipe through the operating responsibility models
01

Client-Operated

  • Administration Client
  • Content and catalogue Client team
  • Warehouse and fulfilment Client team
  • Commercial approval Client
  • Platform support Included by plan
02

Shared Support

  • Administration Shared by scope
  • Content and catalogue Divided by workflow
  • Warehouse and fulfilment By site or transaction
  • Commercial approval Client
  • Platform support Included by plan
03

Vault-Managed Support

  • Administration Vault platform team
  • Content and catalogue Agreed managed team
  • Warehouse and fulfilment Vault where contracted
  • Commercial approval Client approval retained
  • Platform support Included by plan
Inventory-led business models

Configure Commerce OS Around the Assets and Operating Model

The platform foundation can support different catalogue, rental, sales, warehouse, fulfilment and governance requirements.

↔ Swipe through the business use cases
Rental and SubscriptionAvailability, reservations, deposits, dispatch, return and repeated use.
Retail and Direct CommerceCatalogue, stock, transactions, fulfilment, returns and CRM.
Warehouses and 3PLClient inventory, locations, inbound, outbound, services and portals.
Fashion and CostumesVariants, measurements, imagery, rental, sale and care history.
Furniture, Props and EventsBulky assets, visual catalogue, condition, dispatch and returns.
Screen and Media WardrobesAccountable movement, collections, projects, reuse and condition control.
Luxury and Specialist AssetsHigher-control access, condition, approvals and movement history.
Multi-Site OperationsControlled users, locations, transfers, documents and reporting.
Commerce OS FAQs

Common Questions Before Choosing the Platform Scope

The final deployment is configured around the business, selected modules, data, users, facilities and operating responsibilities.

Request a Commerce OS Demo

Is Commerce OS the same as Seller Central?

No. Seller Central is the portal for businesses participating in the wider Vault services and marketplace ecosystem. Vault Commerce OS is a configurable platform for the client’s own operation.

Can Commerce OS operate without Vault storage or fulfilment?

Yes. The client can operate the platform with its own teams and facilities. Vault services are optional connections.

Can the platform use our brand and domain?

Yes, subject to the agreed implementation and technical scope. The tenant can be configured around the approved client brand and domain arrangement.

Do we need every module at launch?

No. The recommended approach is to launch the first useful operating scope and add further capability through a controlled roadmap.

Can Commerce OS support rentals and sales together?

Yes, where the client’s inventory, commercial rules and selected configuration allow both modes.

Can we use our own warehouse and fulfilment team?

Yes. Locations, roles, tasks and fulfilment ownership can be configured around the client’s facilities and operating model.

Can it connect with marketplaces and other systems?

Potentially. Feasibility depends on the external system, supported interfaces, credentials, data quality and approved technical scope.

Who controls content, pricing and commercial approvals?

Responsibility is defined in the engagement scope. Commercial approval remains with the client unless the applicable agreement expressly states otherwise.

How is Commerce OS priced?

The proposal can separate the recurring Commerce OS subscription, implementation and optional managed or operating services. Final pricing depends on the selected scope.

How long does implementation take?

Timing depends on modules, data readiness, connections, workflow complexity, content, testing and acceptance requirements. Broader deployments should be phased.

Start with the business requirement

Show Us the Business You Want Commerce OS to Run

We will map the appropriate website, commerce, CRM, catalogue, WMS, fulfilment, portal, connection and reporting scope for the first operating release.

Request a Commerce OS Demo
Review Engagement Models