Frame Validation
Last Updated: 15/09/2026
Frame Validation is where the 3D assets you ordered are shown to you before they go live. Nothing reaches your catalogues without passing through here: you look at each variant, and you either approve it or send it back with a change request.
Where the Assets Come From
Everything in Frame Validation starts as an order. When you order 3D assets and the quote is accepted, the order becomes a batch in production. The models are built, checked internally, and only then presented to you for approval.
How It Is Organised
Frame Validation is four levels deep. You start from the list and drill down to the single variant.
| Level | What you see |
|---|---|
| Ordered Batches | The landing page. One card per order, with the client information and the order details. |
| Products | The models inside that batch, with Image, Name, Progress, Variant Status and Last Update. |
| Variants | The variants of a product, with Image, Glasses Name, Size, Frame Color, Lenses Color, Batch, Status, Note and the variant type. |
| Variant Details | The single variant: its 3D model, its technical information, and the approve and decline controls. |
The Download Summary button on the Ordered Batches page exports a summary of the batch.
The Validation Flow
A variant moves through six states. They are shown by name wherever a status appears:
| State | What it means |
|---|---|
| Incomplete | The variant exists but the model is not finished. |
| Modelist Rev. | Under review by the modeller who built it. |
| Spaarkly Rev. | Under internal ARShades review. |
| Client Rev. | Waiting for you. This is where your approval is required. |
| In Publication | You approved it; it is being prepared for publication. |
| Published | Live, and usable in your catalogues, Virtual Try-On and AR viewers. |
The first three states are internal production. You can follow them from the progress indicators, but there is nothing for you to do there — you can only open a variant that has reached Client Rev., In Publication or Published.
What you approve, and when
You have two approval points, not one:
- In Client Rev., approving moves the variant to In Publication.
- In In Publication, approving again moves it to Published.
Declining is possible only in Client Rev. — once a variant is In Publication it can no longer be sent back from here. A declined variant goes back to Modelist Rev., straight to the modeller who built it.
Declining a variant
Declining is not a single click: the Decline Variant form asks for enough detail to let the modeller act on it. These fields are required:
- Issue Title — a concise title for the problem.
- Reason(s) for Decline — one or more reasons; choosing other requires you to write it out.
- Detailed Change Request — precise instructions on what to change in the 3D model.
- Severity — Minor (cosmetic), Major (functional) or Critical (blocking).
- Correct Reference Image(s) — at least one image showing how the frame should look.
You can also attach up to four screenshots, which are optional.
It is read by the person who will rebuild the model. «The temple hinge is too thick, see reference» gets a fix; «doesn't look right» gets another round.
Notes
Notes are attached to variants and carry the history of what was asked and answered. You can read the notes on a variant in any state, including the internal ones you cannot open — so if a model is taking longer than expected, the notes usually say why.
What Is Not Yours to Do
Some of what Frame Validation shows belongs to production, not to you. The list of raw 3D asset files, the assignment of variants to modellers, the modelling coefficients and the tag and badge editing are reserved for the ARShades production roles. You will see those areas either absent or inactive; this is by design, and does not mean something is broken.
Next steps: