> 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/platform-setup-discovery.md).

# Platform Setup Discovery

While the Product Matrix handles the SKU-level data, the below discovery questions define the **integration,  order flow and logic, and production workflow.**

### Why this is important

Capturing these details early ensures that the VU Customizer is configured to fit within your existing e-commerce stack and that the output files are compatible with your manufacturing process.

***

### Discovery Template

To streamline this process, please locate the **"Prospect Profile Q/A"** tab (the second sheet) in the Product Matrix linked below and complete the profile.

{% file src="/files/7g2NGqwzG8HlbJB9eIXF" %}

***

## 1. Platform & Order Integration

We need to understand how VU will sit within your existing ecosystem to ensure orders flow seamlessly from the cart to the factory.

| Item                                      | Specifics to Capture                                 | Sample Answer                                  |
| ----------------------------------------- | ---------------------------------------------------- | ---------------------------------------------- |
| **Ecomm Platform**                        | Exact platform and version (Shopify Plus, B2B, etc.) | Shopify Plus                                   |
| **Additional Platforms Involving Orders** | Other systems involved (ERP, WMS, 3PL)               | NetSuite (ERP) and Shipstation (3PL)           |
| **Order Flow Logic**                      | The step-by-step path the order takes                | Shopify → NetSuite → Shipstation               |
| **Order Export**                          | How the factory/fulfillment center accesses data     | Orders grabbed via API with decoration details |

## 2. The Customizer Experience (UX)

These questions define how the user interacts with VU and navigates through the customizer

| Item                | Specifics to Capture                                     | Sample Answer                                    |
| ------------------- | -------------------------------------------------------- | ------------------------------------------------ |
| **Pricing Logic**   | Nuances like tiered pricing, upcharges, or MOQs          | Price breaks are volume and customer-type driven |
| **Live Wireframes** | Desired user flow or links to an existing customizer     | "We want to re-orient our current flow to XYZ"   |
| **2D or 3D**        | Are we using photography, 3D models, or CADs?            | 2D photography                                   |
| **Business Logic**  | Conditions that dictate the customization process occurs | "Must have a Minimum Order Quantity (MOQ) of 24" |

## 3. Personalization & Configuration

This section defines the selections within a product.

| Item                 | Specifics to Capture                                  | Sample Answer                                         |
| -------------------- | ----------------------------------------------------- | ----------------------------------------------------- |
| **Zoning**           | Defined sizes, locations, and behavior of print areas | Image wraps around the entire product; fixed text box |
| **Personalizations** | Details on Image, Text, and Monogram capabilities     | Users can move/rotate images; specific font lists     |
| **Customizations**   | Options selected outside the customizer               | Color and Size are selected on the product page       |
| **Decorations**      | Available stock icons, patches, or offerings          | No stock offerings; user-uploaded content only        |
| **Stock Graphics**   | Static branding that must appear in the render        | Unchangeable logo present on the product base         |

## 4. Production & Fulfillment

This ensures that the "Print Ready" files generated by VU are actually ready for your specific machinery.

| Item                   | Specifics to Capture                            | Sample Answer                         |
| ---------------------- | ----------------------------------------------- | ------------------------------------- |
| **Production Methods** | The physical application (Engraving, DTG, etc.) | Logos are printed, text is engraved   |
| **Print Files**        | Required file formats, dimensions, and layers   | Layered Adobe Illustrator (.AI) files |
| **Delivery Method**    | How the print files reach the factory           | TBD (API, SFTP, etc.)                 |


---

# 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/platform-setup-discovery.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.