Skip to main content

Welcome to ARShades Studio

Last Updated: 15/09/2026

ARShades Studio is where you turn eyewear products into 3D assets, gather them into catalogues, and publish those catalogues for your customers to try on.

This page is the map: what each section of the menu is for, and the order things usually happen in.

The Menu​

SectionWhat it is for
DashboardWhat needs your attention today, and a way into each area. See Dashboard.
ARShades LibraryThe shared repository of every 3D asset available to you. Where you check whether a model exists, and order it when it does not. See Library overview.
My cataloguesYour catalogues: create them, fill them, design their public page, publish them. See Catalogue overview.
AnalyticsHow your published experiences are used. Three areas: VTO services, Gateways and Mirrors.
SubscriptionsThe plans you run on and what you have consumed of them. See Active and Expired Subscriptions.
OrdersEvery request you have made to ARShades, and its status. See Orders.
Frame ValidationThe 3D assets you ordered, shown to you for approval before they go live. See Frame Validation.
ProfileYour account, your teams, your brand identity, your notification preferences and your support tickets.
Orders are requests to ARShades, not sales

The Orders section is not about your customers buying from you. It records what you have asked ARShades to produce — new 3D assets — and tracks the quotation and production of those requests.

How the Work Flows​

Most of what happens in Studio follows this shape:

  1. Check what exists. Search the ARShades Library, or upload a list of codes and let it tell you which models are already available. See Search SKUs from a List.
  2. Order what is missing. The models with no 3D asset are ordered and quoted. See Order Products.
  3. Approve what arrives. Ordered assets come back to you in Frame Validation, where you approve each variant — twice — or send it back with a change request. See Validate Variants.
  4. Build the catalogue. Create it, add the products, and design its public page. See Create a Catalogue.
  5. Publish it. Choose the plan and the address, and it goes live. See Publish a Catalogue.
  6. Integrate and watch. Export the ARShades links for your site or app, and follow how they are used in Analytics. See Download ARShades Links.

Steps 1 to 3 are about having the assets. Steps 4 to 6 are about putting them in front of people. A catalogue can be created and designed at any point — it does not have to wait for the assets.

If You Are New​

  • Open the Dashboard and read the notifications: they say what is already waiting for you.
  • Look at Subscriptions to see the limits you are working within — the number of SKUs your plan allows is the constraint that shapes most decisions.
  • Set up your brand identity and your teams in Profile.
  • Browse the ARShades Library to see what is already available to you.
  • Create your first catalogue in My catalogues.

Roles​

Your role decides what you can do. Client organisations have two account roles — Admin, the organisation's main account, and Member — plus a few ARShades operational accounts, used internally to produce and validate the 3D models, which see Studio differently.

Company Admin and Team Admin, which you will see in the Teams screen, are positions inside a team and are a separate matter from what Studio lets you do.

Where a role makes a real difference, the page that describes the feature says so. For the roles themselves, see Account Roles.

Finding Things in This Guide​

Each section of the menu has its own section in this guide, in the sidebar on the left. The pages that explain a feature are the ones under that feature's own section: when two pages could cover the same ground, the one under the feature is the one kept current.