# Launch Checklist

* [x] Embed Code is present on the production version of the PDP **(**[<mark style="color:$danger;">**Brand/Agency**</mark>](#user-content-fn-1)[^1]**)**
* [x] Embed Tag configuration: **(**[<mark style="color:$danger;">**Brand/Agency**</mark>](#user-content-fn-2)[^2]**)**

- debugging should be disabled,&#x20;
- Env should be production or not listed,&#x20;
- Draft Mode needs to be disabled/removed&#x20;

* [x] Production Theme needs to be published **(**[<mark style="color:$danger;">**Brand/Agency**</mark>](#user-content-fn-3)[^3]**)**
* [x] Production SKUs are linked to the templates **(**[<mark style="color:$success;">**VU**</mark>](#user-content-fn-4)[^4]**)**
* [x] If Color and Size *(anything that would translate to a new variant by selection)* occurs in the customizer, ensure the Add-To-Cart array has the production SKUs configured **(**[<mark style="color:$success;">**VU**</mark>](#user-content-fn-4)[^4]**)**
* [x] Ensure Upcharges are included in variant array (if used) **(**[<mark style="color:$success;">**VU**</mark>](#user-content-fn-5)[^5]**)**
* [x] Ensure Cart is populating with all desired customization information **(**[<mark style="color:$success;">**VU**</mark> **/&#x20;**<mark style="color:$danger;">**Brand/Agency**</mark>](#user-content-fn-6)[^6]**)**

- *custom thumbnail*
- *upcharge pricing*
- *recipeID*
- *custom order-line attribute*

* [x] Ensure quantity management in the cart has finalized *(relationship between SKU and variants+upcharges)* **(**[<mark style="color:$danger;">**Brand/Agency**</mark>](#user-content-fn-7)[^7]**)**
* [x] Ensure test orders can be placed and retrieved into VU **(**[<mark style="color:$success;">**VU**</mark> **/&#x20;**<mark style="color:$danger;">**Brand/Agency**</mark>](#user-content-fn-8)[^8]**)**
* [x] Ensure current version of the template is set to active **(**[<mark style="color:$success;">**VU**</mark>](#user-content-fn-9)[^9]**)**
* [x] Ensure travelers populate correctly with custom order data + thumbnails and can be retrieved by the desired method **(**[<mark style="color:$success;">**VU**</mark> **/&#x20;**<mark style="color:$danger;">**Brand/Agency**</mark>](#user-content-fn-10)[^10]**)**
* [x] Ensure all products are active and not in DRAFT **(**[<mark style="color:$danger;">**Brand/Agency**</mark>](#user-content-fn-10)[^10]**)**
* [x] Ensure all products have inventory **(**[<mark style="color:$danger;">**Brand/Agency**</mark>](#user-content-fn-10)[^10]**)**
* [x] Ensure validation is setup for all required fields needed for order import into VU **(**[<mark style="color:$danger;">**Brand/Agency**</mark>](#user-content-fn-10)[^10]**)**
* [x] Ensure artwork for products VU is producing for has been signed off on by the production facility **(**[<mark style="color:$danger;">**Brand/Agency**</mark>](#user-content-fn-10)[^10]**)**

[^1]: <sub>Ensure the customizer is actually embedded on the live product page</sub>

[^2]: Prevents debug/test behavior from appearing on live site

[^3]: Make sure you're not using a draft version

[^4]: Ensures correct SKU-to-template relationships for the customizer

[^5]: If a customization costs extra, ensure it's accounted for in pricing

[^6]: Key for backend order fulfillment & customer clarity

[^7]: Needs to correctly reflect SKU + variant + upcharge relationships

[^8]: Verifies end-to-end functionality, including order ingestion

[^9]: Avoids accidental use of an outdated or draft version

[^10]: Ensures downstream production sees correct customization info


---

# Agent Instructions: 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:

```
GET https://vu-custom.gitbook.io/vu-custom/onboarding/launch-checklist.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.