> ## Documentation Index
> Fetch the complete documentation index at: https://docs.satyakod.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Code Studio

> Design your Private Code, test that it reads reliably, and approve it for production.

A [Private Code](https://docs.satyakod.com/private-code/scanning-guide.md) is drawn in your brand's own design. **Code Studio**
is where you make that design, prove it reads on real phones and scanners, and approve it before
any batch uses it. GS1 codes follow the GS1 standard and can't be restyled.

## Create a design

![The design editor: settings, preview and scan reliability](https://docs.satyakod.com/images/screenshot-placeholder.svg)

The design editor: settings, preview and scan reliability

1. **Start from a template** (rings, radial bars, dot grid and others), or ask for a
   [custom design](#custom-designs).
2. Set the **logo** (SVG or PNG, at least 1024 px), the **code** and **background** colours, the
   **layout variant**, the **minimum print size**, the **quiet zone** and the **print method**
   (thermal transfer, inkjet, laser etch, offset, flexo or digital).
3. Watch **Scan reliability** as you go: a score out of 100 from contrast, size and damage
   tolerance, and an estimated decode rate on a low-end Android phone, an iPhone and a rugged
   scanner. One-click fixes suggest changes.

> [!NOTE]
>
> Template designs may look similar to other customers'. Encoding and keys are always unique to you.

Changes save as you go. Each saved change is a new version of the design.

## Test and approve

A design can print only once it is **approved**, which needs, for the current version:

* reliability of **90 or more**;
* a decode rate of **98% or more on every device**, measured with **Run scan test** (12 reads per device);
* sign-off from **an admin and a packaging engineer**.

**Submit for review** asks for those sign-offs; **Approve for production** records yours. A
version in review or approved can't change: **Duplicate as a new version** makes a new draft with
the same settings and the next version number, which needs its own scan test and approval. The
original stays as it is, so batches keep printing it meanwhile. **Version history and approvals**
shows each version, what changed, its reliability and who approved it.

| Action | Roles |
| - | - |
| Create, edit, duplicate and submit designs | Admin, packaging engineer, brand protection |
| Approve for production | Admin, packaging engineer |

## Custom designs

**Request a custom code design** asks Satyakod's design team for a design made for your brand:
your company and brand files (PDF, AI, SVG, PNG or JPG, up to 50 MB each), where the code will be
printed (products, packaging, print methods, smallest size, volume, environment), and your goals
and timing. Its progress shows on the request: received, discovery call, concepts, print trials,
handed over.

| | Standard | Priority (extra fee) |
| - | - | - |
| Discovery call booked | within 2 days | within 2 days |
| Three concepts and a fixed quote | within 10 days | within 10 days |
| Print trials on your lines | within 3 weeks | within 3 weeks |
| Handover to Code Studio as a draft | about 6 weeks | about 4 weeks |

The request page shows the target handover date. Designs already in production keep printing
meanwhile.

Before printing, read the [Private Code scanning guide](https://docs.satyakod.com/private-code/scanning-guide.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.