Skip to main content
Version: 1.0.0

What is Data Consumption

Overview​

Data consumption in ARShades subscriptions refers to all traffic and storage generated by the use of ARShades services. It includes both the hosting of 3D models and all data requests made to ARShades servers when services are used by end users.

Examples of data contributing to consumption:

  • Loading and streaming 3D models and imagery in catalogues.
  • Queries to ARShades APIs.
  • Downloading or reading the database documents.
  • Any other server calls required to deliver VTO, 3D AR Viewer, Mirror, or AR PD Meter services.

What Counts as Data Consumption​

  • 3D Model Hosting: The storage and delivery of 3D assets from ARShades servers to client catalogues and applications.
  • Service Requests: All calls made by catalogues or applications to ARShades services, including rendering assets, serving documents, images, and retrieving catalogue data.
  • End-user Interactions: Each user session that loads and interacts with VTO, 3D AR Viewer, or other ARShades features generates data transfer.
  • Asset Management Calls: Any calls performed in ARShades Studio to configure, update, or manage catalogues and 3D assets contribute to data usage.
  • Analytics Calls: The generation and visualisation of analytics reports in ARShades Studio (e.g. usage charts, KPIs) also generate data transfer.

Why GB Instead of Users​

Some competitors measure subscription usage based on the number of users or sessions. ARShades instead calculates consumption in GB of data transfer, which, while less direct, is a more accurate and transparent metric.

The relationship between data usage and user sessions depends on several factors:

  • Number of SKUs in the catalogue: More products require more 3D assets to be loaded.
  • Average weight of 3D models: Heavier models increase data transfer per session.
  • Average sessions per user: Some e-commerce sites generate more sessions per user due to UI design or use of multi-product VTO/3D AR Viewer (where a main model and all its colour variants are accessed in a single session).
  • Catalogue structure: Having multiple catalogues or larger catalogues naturally increases data consumption.

Some of these factors are outside ARShades’ control. For example, the way a client integrates the viewer or how optimised their UI is can significantly change the number of sessions generated per user.

Average Benchmarks​

  • Average 3D model size: 3.5 MB
  • Average sessions per user: 1.8

This means that the same number of users can generate very different data consumption depending on catalogue size, number of variants, or integration design.

Allowances and Extensions​

Each subscription plan includes a data allowance expressed in GB. This allowance can be extended with:

  • Data Pack (Add-on): Prepaid blocks of data available until fully consumed.
  • Overage: Extra data usage beyond the included allowance and Data Packs, billed according to the terms of the subscription.

Consumption Priority​

Data consumption follows a clear priority order:

  1. Data Pack – If one or more Data Packs are active, data will be consumed from these first until they are exhausted.
  2. Plan Allowance – Once all Data Packs are consumed, the subscription uses the data allowance of the plan (monthly or yearly, depending on the contract).
  3. Overage – After both Data Packs and plan allowance are consumed, additional usage is counted as overage. Overage is available only for Enterprise plans and is automatically calculated and made visible in ARShades Studio. For all other plans, once both the Data Pack and plan allowance are consumed, the service will stop until a new Data Pack is purchased or the subscription is renewed.

Visibility in Studio​

  • Data consumption is always displayed in the Subscription details panel.
  • Active Data Packs and their remaining GB are shown alongside the main plan allowance.
  • When overage occurs, it is flagged in red and highlighted in both the details panel and the dashboard notifications.

Key Notes​

  • Data Packs must be linked to an active subscription to be consumed.
  • Overage is billed separately and should be monitored to avoid unexpected costs.
  • Admin users can see full details of allowances, Data Packs, and overage; Member users see only what is linked to their assigned subscriptions; Validators have no access.