> For the complete documentation index, see [llms.txt](https://academy.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pakk.io/ecommerce-launch-mega-checklist.md).

# eCommerce Launch Mega Checklist

Whether this is your first e-commerce business, or you're a seasoned pro, you'll end up going through the same mental  checklist of steps before, while and after launching your site.

We've tried to bring all these steps and actions points together into one big (huge) *launch checklist* that you can use whether you're launching a totally new business, a new brand or even just a new site for an existing business. Of course, depending on which of these apply to you, you may already have a lot of this in place - in which case just tick it off an move on.

This list is always going to be incomplete, so if there's something glaringly missing please let us know and we'll add it. It's a living document, so we'll leave a note here of when it was last updated.

This list is **not specific to Pakk**, so can be used as a reference for launching on any platform. However, it's worth noting two things:

1. This list is somewhat opinionated (a bit like Pakk). We have our approach to e-commerce and a lot of that is codified in this list. Feel free to ignore any of it if you feel it's wrong.
2. Pakk specific implementation details appear *in italics after each point*.

> Suggestion: Print this list off and tick off the tasks once they're complete


---

# 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://academy.pakk.io/ecommerce-launch-mega-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.
