Blog · Oct 12, 2026

Virtual Try-On Total Cost of Ownership: Budget Beyond the Demo

/ 9 min read /
Retail colleagues reviewing a laptop and planning sheet beside jackets and a freestanding display in a fashion store

In short

Budget virtual try-on beyond the software quote: deployment, usage, catalog work, internal time and exit costs, with a worked pilot example.

iKawn
Share:

The demo works. The merchandising lead has a collection in mind. Then finance asks a deceptively simple question: what will it cost to keep this experience useful once the launch team leaves?

A software quote cannot answer that on its own. Someone must approve garments, introduce the experience, handle interruptions and decide whether more usage deserves more budget. For a fashion retailer evaluating virtual try-on, those responsibilities belong in the investment decision.

Build the virtual try-on total cost of ownership around a defined shopper journey, a fixed evaluation period and an explicit usage range. This guide is for founders, finance partners, ecommerce and retail operations leaders budgeting a Mirror pilot. It provides a planning framework and a worked example, not an industry price benchmark or an iKawn quotation.

Why the operating budget matters now

The Business of Fashion–McKinsey State of Fashion 2026, published November 17, 2025, reported that 46% of surveyed fashion executives expected industry conditions to worsen in 2026. Its efficiency theme calls for productivity improvements that free resources for differentiation. That is evidence of executive pressure, not evidence that any particular virtual try-on investment will pay back.

Our interpretation: a proposal needs to show both the customer problem worth funding and the recurring work required to solve it. If the budget covers the launch but assumes free merchandising and store support thereafter, it has not answered the commercial question.

Inditex provides a useful example of the broader operating context. Its 2025 annual report CEO statement, accessed October 12, 2026, describes investment in stores and ecommerce platforms alongside technology intended to help employees and improve shopping. This is a company-level investment account, not a virtual try-on cost disclosure. The budgeting lesson we draw is to connect the customer experience with the people and channels that must operate it.

Specify what the quote is buying

Before comparing prices, write a short scope statement. For example: “Help shoppers shortlist jackets in one store, using an approved collection, during normal trading hours, with an associate available for the handoff.” For ecommerce, the equivalent might be helping an eligible shopper compare selected looks before returning to the product page.

These are proposed use cases, not promises that every configuration includes every channel or integration. Confirm the intended workflow in a live demonstration. A visual preview also does not establish physical fit; do not budget on the assumption that it replaces size advice or physical fitting.

Give every supplier the same baseline: location or channel, collection scope, evaluation period, customer-facing devices, expected sessions, likely session duration, support hours and required next action. Ask for exclusions in writing. A lower quote for an unattended screen is not directly comparable with one that includes installation and staffed launch support.

Scope can be deliberately narrow. In an April 24, 2023 announcement, Zalando described a virtual fitting-room pilot covering 22 jeans items. This historical avatar-and-size experience differs from Mirror and provides no cost benchmark. It is a concrete example of testing a defined assortment rather than assuming whole-catalog coverage. For your budget, record what happens when the first collection changes.

Build one cost ledger with named owners

Use the following categories as a request-for-quote worksheet. For each line, record the amount, payer, timing, inclusion or exclusion, and the condition that changes the cost. Where a category does not apply, mark it explicitly rather than leaving an unexplained blank.

  • Initial deployment: hardware purchase or rental, transport, installation, configuration and acceptance. Check ownership and removal responsibilities. Do not count purchased equipment and rental of that same equipment twice.
  • Software and usage: committed access fees, included allowances, the billable unit, top-ups or overages, and additional device or location charges. Confirm whether unused allowance expires and what happens when it is exhausted.
  • Catalog operation: first assortment approval, replacement collections, product withdrawal and checks after changes. Assign the merchandising hours even when the vendor does the upload.
  • Customer and store operation: introductions, assistance, session reset, shift handover and training. Separate work absorbed into an existing role from additional paid coverage.
  • Support and change: incident response, equipment replacement, connectivity, software changes and any integration maintenance. Define who pays when an issue sits between two suppliers.
  • Measurement and closure: collecting agreed evidence, reviewing results, exporting permitted records, removing equipment and ending the service. Include minimum commitments and notice periods.

Keep two totals: cash leaving the business and the wider cost including internal time. Existing salaries are not necessarily incremental cash expense, but assigning work to an already busy team has a capacity cost. Conversely, do not claim cash savings from minutes saved unless that time actually changes staffing expense or creates measurable productive capacity.

For store equipment, distinguish the cash needed to buy it from how finance allocates its cost over its useful life. Do not mix a full purchase price in one proposal with a single month's rental in another and call the result a like-for-like comparison. Agree treatment of taxes, recoverable taxes and currency with finance.

Price usage without confusing sessions, minutes and outcomes

A shopper session, a garment preview and a billable minute can represent different things. Ask the provider to demonstrate the usage record for a normal session, a repeated preview, a failed attempt and an interrupted session. Record what is billed, rounded, credited or excluded under the proposed agreement.

If the offer is billed by minutes, a useful starting estimate is expected sessions multiplied by average billable minutes per session. Then apply the actual pack sizes, minimum commitments and overage rules. Do not substitute that formula for the contract. If the offer is billed by completed try-ons, use that unit instead.

Estimate a low-use, expected-use and high-use case. Low use may leave the invoice almost unchanged while increasing cost per useful interaction. High use may justify additional spend, but can also require more assistance or capacity. Ask whether alerts and spending limits are available; do not assume they are included.

Define a useful interaction before launch. For a jacket-shortlisting pilot, it could mean an eligible shopper completes a preview and selects an item for the next shopping step. Track technical completion separately from that commercial action. Cost per interaction is a diagnostic, not evidence of incremental sales.

A worked pilot budget: why the cheapest quote can mislead

The following twelve-week, single-store example is entirely illustrative. Every amount and volume below is an editorial assumption chosen to show the calculation. These are not iKawn prices, observed customer results or market averages.

  • Deployment and equipment: INR 120,000.
  • Committed software access and support for the evaluation period: INR 60,000.
  • Expected variable usage: INR 40,000.
  • Catalog changes and closure work: INR 25,000.
  • Allocated internal labor: INR 55,000.

The total is INR 300,000, of which INR 245,000 is external cash expenditure in this example. If the pilot produces 600 useful interactions, the fully allocated cost is INR 500 per interaction. If it produces only 300 while costs remain unchanged, that becomes INR 1,000. If usage expenditure doubles while the other lines stay fixed, the total becomes INR 340,000. Replace all these assumptions with your quote and pilot observations.

This reveals two different risks: paying for unused capacity and paying more because demand increases. A sensible approval specifies the initial commitment, a maximum additional spend and the person who can release it. It also defines what the team should do when the allowance runs out; an unapproved interruption should not become the default shopper experience.

For a later business-case review, compare cost with incremental contribution after relevant variable costs and returns, using a credible comparison group. The separate guide to measuring virtual try-on sales lift explains that measurement decision. Do not count every order from a user of the experience as an additional order caused by it.

Choose a commitment you can learn from

A short rental may limit initial commitment but cost more over a longer deployment. Purchased equipment may have a lower ongoing expense but leave you with installation, replacement and exit responsibilities. Existing equipment can reduce upfront spend only if it passes the agreed experience and reliability checks. Evaluate those choices over the same period and service scope.

“We can keep the catalog small” is a reasonable cost-control proposal. It also limits what you learn about future collection changes. Include at least one representative refresh exercise in the agreed scope if frequent launches are central to the intended deployment. This is an evaluation recommendation, not a universal minimum.

“Our associates can absorb the work” should become an observed operating assumption. Record assistance and recovery time on ordinary shifts. A pilot that relies on unusually enthusiastic staff or continuous vendor presence needs a separate budget for routine operation.

Before approval, ask the sponsor to sign off three things: the cost through the next decision date, the downside if adoption is low, and the conditions for buying more capacity. If a major recurring line remains unpriced, request a bounded learning engagement rather than approving an open-ended rollout.

Bring a cost brief to your Mirror demo

Use iKawn Mirror to evaluate a specific visual discovery and garment-preselection journey. Bring your collection, channel, device plan, expected usage range and operational owners. Ask the team to demonstrate the proposed journey and explain the commercial scope needed to run it.

Consult the current Mirror pricing page as a starting point, then obtain a dated proposal for your fashion use case. Confirm allowances, hardware, catalog work, installation, support and exclusions for that configuration. A public plan should not silently become a quote for a different deployment.

The useful outcome is a budget with owners and decision points: what you commit now, what changes with usage, and what evidence would justify the next investment. Book a live Mirror demo to discuss that scope before you commit to a pilot.

Research checked October 12, 2026. Framework and budget example are original editorial analysis. Hero image is an AI-generated editorial illustration of retail planning, not a photograph of an iKawn customer installation.

Bring live virtual try-on into focus

Map the priority category, customer journey, channel, and commercial objective with iKawn Mirror.

WhatsApp iKawn Mirror