# Settings (Codes)

# Overview

The **Codes** section allows administrators to configure the format used for generating unique codes across different modules of the application. These codes help identify records such as **Orders**, **Form Responses**, **Script Responses**, and **TryOn Sessions** in a consistent and organized manner.

Navigate to **Settings → Codes** to configure code generation settings.

---

# Code Configuration

Administrators can configure the following settings:

- **Timezone**
- **Default Prefix**
- **Default Digits**
- **Order Prefix**
- **Order Digits**
- **Form Response Prefix**
- **Form Response Digits**
- **Script Response Prefix**
- **Script Response Digits**
- **TryOn User Prefix**
- **TryOn User Digits**
- **TryOn Session Prefix**
- **TryOn Session Digits**

Each module can have its own unique prefix and digit length to generate easily identifiable codes.

---

# Timezone

Select the appropriate **Timezone** for the application.

The selected timezone is used while generating date and time-based codes.

---

# Default Code

The **Default Code** configuration is used for general-purpose code generation.

Configure:

- **Default Prefix**
- **Pattern**
- **Default Digits**

Example Pattern:

```text
[PREFIX]/[YYYY]/[MM]/[DD]/NNNN
```

Example Output:

```text
DEF/2026/07/23/0001
```

---

# Order Code

Configure the code format for customer orders.

Fields:

- **Order Prefix**
- **Pattern**
- **Order Digits**

Example Output:

```text
ORD/2026/07/23/0001
```

---

# Form Response Code

Used to generate unique identifiers for submitted forms.

Fields:

- **Form Response Prefix**
- **Pattern**
- **Form Response Digits**

Example Output:

```text
FORM/2026/07/23/0001
```

---

# Script Response Code

Used to generate unique codes whenever a script response is recorded.

Fields:

- **Script Response Prefix**
- **Pattern**
- **Script Response Digits**

Example Output:

```text
RESP/2026/07/23/0001
```

---

# TryOn User Code

Generates a unique identifier for each TryOn user.

Fields:

- **TryOn User Prefix**
- **Pattern**
- **TryOn User Digits**

Example Output:

```text
TRYUSER/2026/07/23/0001
```

---

# TryOn Session Code

Generates a unique code for every TryOn session.

Fields:

- **TryOn Session Prefix**
- **Pattern**
- **TryOn Session Digits**

Example Output:

```text
TRYON/2026/07/23/0001
```

---

# Pattern Placeholders

The following placeholders can be used while creating custom code patterns.

| Placeholder | Description | Example |
|-------------|-------------|---------|
| **[PREFIX]** | Uses the configured prefix for the selected module. | ORD |
| **[YYYY]** | Four-digit year. | 2026 |
| **[MM]** | Two-digit month. | 07 |
| **[DD]** | Two-digit day. | 23 |
| **[H]** | Two-digit hour (24-hour format). | 14 |
| **[M]** | Two-digit minute. | 35 |
| **[S]** | Two-digit second. | 48 |

---

# Manage Code Settings

Administrators can:

- Configure prefixes for different modules.
- Define custom code generation patterns.
- Set the number of auto-generated digits.
- Configure timezone for date-based code generation.
- Maintain unique identifiers across the application.

---

# Best Practices

- Use meaningful prefixes for each module.
- Configure different prefixes for different record types.
- Keep digit lengths consistent for better readability.
- Avoid using duplicate prefixes across modules.
- Verify the generated pattern before saving changes.

---

> **Important:**  
> Every module can have its own **Prefix**, **Pattern**, and **Digit Length**. The application automatically generates unique codes based on these settings, ensuring that records such as **Orders**, **Form Responses**, **Script Responses**, and **TryOn Sessions** remain unique and easy to identify.