> For the complete documentation index, see [llms.txt](https://vu-custom.gitbook.io/vu-custom/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vu-custom.gitbook.io/vu-custom/getting-started/product-matrix.md).

# Product Matrix

The Product Matrix is an essential planning document that helps define your Brands custom product offerings and their options.

The Product Matrix enables you to:

* Define products for customization
* Specify available customization options
* Document customization constraints
* Ensure accurate visualization setup

### **Product Customization List Template**

{% file src="/files/yeRVsD4zYcVfYwKuvmVH" %}

### **Prepare Product Matrix Template**

Preparing a product matrix involves the following:

#### 2D or 3D Visualization

Specify a visualization type required for the product. 

Brands can choose between, **2D** or **3D.**

#### Customization Location

Brands can specify all areas/zones where customization can be applied. \
\
For Example, Hat: "Front panel, Side panel, Back" Polo: "Left chest, Right sleeve, and Upper back".

#### Personalization Options

Details the ways brands can personalize the product. Common options include:

* Text additions (names, numbers, messages)
* Logo placements
* Pre-designed graphics or emblems
* Monogram options
* User-uploaded images

#### Product Color Options

Indicates whether brands can select different color options for this product. A **Yes** means your product will offer color variants, while a **No** indicates the product comes in a single color only. 

This information helps us configure the correct type of color selection interface in the customizer.

#### Site/Domain

List all e-commerce domains where this product's customizer will be deployed.

**Example:**

```
Copygolf.example.com
wholesale.example.com
retail.example.com
```

**Note:** If the same product customizer will appear on multiple domains, list all applicable URLs.

**Product Name Entry** \
Each product name represents a unique item for visualization in the VU Custom platform. Similar products with different variants (like gender-specific versions) require separate entries, as they are considered distinct products for customization purposes.

**Examples of Distinct Products:**

* Men's Polo vs. Women's Polo
* Youth Jersey vs. Adult Jersey
* 20oz Tumbler vs. 30oz Tumbler

**Product Image** 

A reference image that helps identify the product. Links can point to:

* E-commerce product pages
* Catalog listings
* Website URLs
* Internal image libraries

This initial reference image helps identify the product, while the detailed technical assets will be needed later in the process to build the visualization.

Specifying these options helps us understand what offerings Brands wish to power on their custom product. Once completed, we'll review your requirements and begin configuring the necessary visualization methods for each product.

Speaking of visualization, let's explore the key differences between 2D and 3D product visualization to help you choose your products.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://vu-custom.gitbook.io/vu-custom/getting-started/product-matrix.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.