SaaS Platform
Recurring access to the approved Commerce OS modules and applicable platform support.
- Selected modules
- Users and locations
- Applicable storage or usage limits
- Support level and update scope
Pricing & Engagement Models
Price the Platform, Implementation and Work Your Operation Actually Needs
Commerce OS pricing is built from the selected SaaS modules, implementation scope, users, locations, data, connections and any optional managed operational services.
Assessment comes first. Scope and assumptions are documented next. Billing begins only after the applicable proposal, estimate or recurring plan is approved.
From requirement to approved billing
No automatic commitment
No automatic commitment
01
Assess
Inventory, platform modules, users, facilities, data and operating responsibility.
Assess
Inventory, platform modules, users, facilities, data and operating responsibility.
→
02
Scope
Deliverables, assumptions, quantities, exclusions, dependencies and billing type.
Scope
Deliverables, assumptions, quantities, exclusions, dependencies and billing type.
03
Approve
Proposal, estimate, recurring plan or transaction terms are reviewed before work begins.
Approve
Proposal, estimate, recurring plan or transaction terms are reviewed before work begins.
04
Execute and Reconcile
Approved work, recurring services and usage activity remain traceable.
Execute and Reconcile
Approved work, recurring services and usage activity remain traceable.
The same inventory count can require very different work.
Scope determines price
Scope determines price
Choose the right commercial starting point
Separate the SaaS, Implementation and Optional Operating Work
A clear proposal should show what is recurring platform access, what is one-time implementation and what is additional managed or usage-based work.
↔ Swipe through the engagement models
SaaS plus Implementation
Platform access combined with the work required to configure, migrate, test and launch it.
- Discovery and solution design
- Configuration and data migration
- Testing and training
- Controlled launch and handover
Managed or Hybrid Engagement
Add selected catalogue, storage, fulfilment, care, administration or marketplace work.
- Defined operational responsibilities
- One-time and recurring services
- Usage-based work
- Client approval retained where required
Four commercial families
Understand What Is One-Time, Recurring, Usage-Based or Transaction-Related
The final proposal may contain one or several pricing families. Each should remain separately understandable.
↔ Swipe through the pricing components
SaaS and Implementation
Platform modules, configuration, migration, training, support and technically feasible connections.
SaaSSetupMigrationSupport
Managed Operational Services
Receiving, catalogue, photography, packing, fulfilment, care and special handling.
ReceivingCatalogueFulfilmentCare
Storage and Protection
Recurring capacity, handling profile, access frequency and approved protection services.
CapacityLocationHandlingProtection
Marketplace Activity and Earnings
Channel setup, approved deductions, transaction activity, fulfilment and seller earnings.
ChannelsTransactionsDeductionsEarnings
See pricing and approval in action
Follow a Requirement from Assessment to Approved Billing and Reconciliation
Start with the pricing architecture, then move through scope, Commerce OS and implementation, managed work, recurring capacity, usage activity, earnings, approval and billing history.
↔ Swipe through the pricing walkthrough
01
Price the configured platform
Price the configured platform
SaaS and Implementation
The recurring SaaS scope and the one-time implementation work should be shown separately. The recurring amount reflects the approved ongoing platform configuration; implementation reflects the work required to make it usable.
Connections and custom work are included only where they are technically feasible and expressly scoped.
Recurring SaaS
One-time implementation
Approved custom scope
One-time implementation
Approved custom scope
↔ Swipe through SaaS and implementation factors
Selected Modules
Platform scope begins with the capabilities included in the deployment.
- Website and CMS
- Rental and sales commerce
- CRM, inventory and WMS
- Portals, reporting and connections
Users, Locations and Scale
Operating breadth affects configuration and ongoing platform usage.
- Users and role complexity
- Warehouses and business units
- Catalogue and data volume
- Applicable storage and usage requirements
Implementation Work
One-time setup depends on the starting condition and desired first release.
- Discovery and solution design
- Configuration and branding
- Data preparation and migration
- Testing, training and launch
Connections and Custom Work
Additional technical work requires separate feasibility and scope review.
- External system assessment
- Field and workflow mapping
- Approved custom development
- Testing, monitoring and exception handling
02
Price the work required
Price the work required
Managed Operational Services
Managed-service pricing follows the physical work, handling complexity, required evidence, turnaround, materials and responsibility assigned to Vault.
A seller or client may use selected services without buying every managed workflow.
One-time work
Recurring support
Usage-based activity
Recurring support
Usage-based activity
↔ Swipe through managed-service pricing factors
Receiving and Labour
Price the physical effort required to verify and intake inventory.
- Packages and item quantities
- Counting, scanning and evidence
- Handling type and manpower
- Priority or restricted access
Catalogue and Studio Work
Price the digital preparation required for internal or commercial use.
- Photography and image preparation
- Measurements and attributes
- Category, title and description
- Review and channel readiness
Packing and Fulfilment
Price the activity and materials required to move inventory safely.
- Picking and verification
- Packing and materials
- Documents and dispatch support
- Returns and reconciliation
Care and Special Handling
Price condition-sensitive or specialist work separately.
- Laundry, cleaning and steaming
- Repair and restoration
- Bulky, fragile or luxury handling
- Exception, priority and project work
03
Price recurring capacity and handling
Price recurring capacity and handling
Storage and Protection
Recurring storage pricing depends on the capacity used, facility or location type, inventory profile, movement frequency and selected protection or support services.
Square-foot, cubic-foot, dedicated-zone, rail, shelf, container or specialist arrangements may require different commercial structures.
Capacity
Handling profile
Service level
Handling profile
Service level
↔ Swipe through storage and protection factors
Capacity Used
Price the physical space or dedicated storage arrangement.
- Square-foot or cubic-foot usage
- Rails, shelves, bins or containers
- Dedicated or shared locations
- Minimum capacity commitments where applicable
Inventory and Handling Type
Different assets require different storage and handling conditions.
- Garments, props, furniture or equipment
- Bulky, fragile or high-value inventory
- Hanging, folded or containerised storage
- Condition and care requirements
Access and Movement Frequency
Recurring capacity and frequent handling are separate cost drivers.
- Inbound and outbound frequency
- Internal movements and reorganisation
- Access windows and priority requirements
- Inventory audits and reconciliation
Protection and Additional Services
Optional services are included only when selected and approved.
- Premium protection arrangements
- Condition monitoring
- Care, repair or periodic maintenance
- Dedicated staff or service support
04
Separate preparation from commercial activity
Separate preparation from commercial activity
Marketplaces, Transactions and Seller Earnings
Marketplace participation can involve setup, catalogue preparation, transaction-related deductions, fulfilment activity and third-party costs. These should be shown separately from the seller’s gross transaction value.
Participation does not guarantee income. Seller earnings depend on approved live inventory and completed commercial activity.
Channel readiness
Approved deductions
Net seller earnings
Approved deductions
Net seller earnings
↔ Swipe through marketplace pricing and earnings
Channel Setup and Readiness
Prepare the account and inventory for approved destinations.
- Marketplace access and eligibility
- Category and catalogue requirements
- Destination mapping and setup
- Draft review and publication controls
Commercial Activity
Transaction value and channel-related charges remain distinct.
- Rental or sales value
- Approved marketplace deductions
- Payment and third-party costs
- Refunds, cancellations and adjustments
Fulfilment and Returns
Physical work is priced according to the recorded responsibility.
- Reservation and picking
- Packing and dispatch
- Delivery or collection support
- Return, inspection and restoration
Gross Value to Net Earnings
Seller visibility should explain how the final amount is calculated.
- Gross transaction value
- Approved deductions and adjustments
- Net seller earnings
- Pending, approved and paid status
Quote and approval process
From Initial Requirement to an Approved Billing Structure
The proposal should make scope, assumptions, billing frequency, exclusions and responsibility clear before implementation or operational work begins.
↔ Swipe through the quote process
Submit the Requirement
Describe the platform, inventory, facilities, users, services and desired operating outcome.
Assessment
Review data readiness, quantities, handling profile, modules, responsibilities and dependencies.
Scope and Assumptions
Define deliverables, volumes, billing type, exclusions, acceptance and third-party dependencies.
Estimate or Proposal
Separate SaaS, implementation, recurring, usage-based and optional service components.
Approval and Setup
Record the applicable approval before creating recurring plans or beginning chargeable work.
Execute and Reconcile
Track approved work, recurring services, usage activity, changes, invoices and statements.
One-time charges
Implementation, migration, receiving, catalogue preparation, setup and approved project work.
Recurring and usage charges
SaaS, storage, protection, support and operational activity performed over time.
Commercial responsibility
Keep Scope, Approval, Third-Party Costs and Reconciliation Explicit
The commercial record should make clear who supplies information, who estimates the work, who approves the charge and how changes are handled.
Commercial responsibility
Client or Seller
Vault
External Provider
Provide accurate requirement and data
Responsible
Review and clarify
Not applicable
Define scope and estimate
Review assumptions
Prepare applicable proposal
Provide third-party terms
Approve chargeable work
Approval retained
Record approval
Not applicable
Perform approved Vault work
Provide access and inputs
Responsible by scope
Not applicable
External fees and services
Approve where required
Coordinate where scoped
Responsible for own charges
Changes and reconciliation
Review and approve changes
Document and reconcile
Provide applicable records
↔ Swipe through the commercial responsibility views
Client or Seller
- Requirement and data Provide accurately
- Scope assumptions Review
- Chargeable work Approve
- Changes Review and approve
Vault
- Assessment Review and clarify
- Proposal Prepare by scope
- Approved work Perform and record
- Reconciliation Document
External Provider
- Own fees Responsible
- Terms Provide
- Service delivery Responsible
- Records Provide where applicable
What changes the quote
The Same Item Count Can Require Very Different Work
Quantity matters, but it is only one pricing factor. Condition, complexity, deadlines, data readiness, facilities, handling and desired output can materially change the scope.
↔ Swipe through the pricing factors
Pricing FAQs
Common Questions About Charges, Earnings and Commercial Terms
The final proposal depends on the approved scope. The page explains the structure, not a universal fixed amount.
Why are fixed prices not shown for every service?
The same quantity can involve very different data, condition, handling, photography, storage, urgency and responsibility. A scope review is required before pricing work accurately.
Is SaaS pricing separate from implementation?
Yes. Recurring platform access and one-time implementation should be shown separately unless the applicable proposal expressly combines them.
Can we buy Commerce OS without managed warehouse services?
Yes. Commerce OS can be operated with the client’s own teams and facilities. Vault operational services are optional.
Are receiving, catalogue and fulfilment included in the SaaS fee?
Not automatically. Physical operational work is priced separately unless it is expressly included in the approved engagement scope.
How is storage priced?
Storage depends on capacity, location type, inventory profile, handling, movement frequency and selected service level.
Are marketplace deductions the same as Vault service charges?
No. Marketplace, payment, logistics, fulfilment and managed-service components should remain separately understandable.
Does listing inventory guarantee seller earnings?
No. Earnings depend on approved live inventory and completed rental or sales activity. Marketplace participation does not guarantee income.
Can an estimate change after work begins?
It may change when quantities, condition, data, assumptions, dependencies or requested work differ from the approved scope. Material changes should be documented and approved.
Are taxes and third-party fees included?
The applicable proposal should state taxes, third-party charges and exclusions. These should not be assumed unless expressly shown.
Can the platform and operational services be phased?
Yes. A client can begin with selected modules or services and add further scope through approved phases.
Start with the requirement
Tell Us What You Manage and Which Work You Need Priced
We will help separate the appropriate SaaS, implementation, recurring, usage-based, marketplace and optional managed-service components.