> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/magento-2-api-connector/magento2_en_us/getting-started/go-live-checklist.md).

# Go-Live Checklist

Check off each item in sandbox and production.

### Technology and Security

* [ ] Expected app version installed
* [ ] Technical Magento user configured
* [ ] HTTPS and certificate valid
* [ ] Connection test successful
* [ ] Permissions restricted
* [ ] Developer logging disabled by default

### Setup

* [ ] Correct shop active
* [ ] Initial data downloaded
* [ ] Payment, shipping, and taxes verified
* [ ] Websites and Store Views mapped
* [ ] MSI sources mapped
* [ ] Number series sufficient

### Catalog and Inventory

* [ ] Simple item successful
* [ ] Price, tax, texts, and visibility correct
* [ ] Categories and images correct
* [ ] Configurable product tested
* [ ] Inventory per source verified
* [ ] Negative quantities clarified

### Orders and Documents

* [ ] Guest and registered customer tested
* [ ] Payment, shipping charges, and tax correct
* [ ] Options correct
* [ ] Shipment, tracking, and invoice successful
* [ ] Repetition without duplicates
* [ ] Credit memo process accepted separately

### Operations

* [ ] Cockpit preflight without blockers
* [ ] Batch size appropriate
* [ ] Only validated jobs active
* [ ] Log monitoring and support path defined
* [ ] Data privacy/deletion concept in place

{% hint style="danger" %}
Do not go live while tax posting, customer creation, or credit memos are unresolved.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.solutioo.de/magento-2-api-connector/magento2_en_us/getting-started/go-live-checklist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
