> For the complete documentation index, see [llms.txt](https://docs.atomyx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.atomyx.io/atomyx-submit/implementation/portal-configuration/preflight-configuration.md).

# Preflight Configuration

If you're using Atomyx Submit as a standalone product, you can ignore this as it's built-in, for more flexibility subscribing to Atomyx Prepare too alows you to choose the right profile strategy for implementation or routing in your workflow and is one of the most important parts of a successful Submit implementation.

### Recommended model: two-stage preflight

A typical Atomyx Submit setup uses two stages.

#### Quick check

This runs during upload and should be lightweight and fast.

Typical checks include:

* page dimensions
* image resolution
* font embedding
* spot colour presence
* page count

The quick check should usually **check only**, not correct.

Its purpose is to give the customer immediate, understandable feedback.

#### Production preflight

This runs after submission and can be more comprehensive.

Typical processing includes:

* PDF standard conversion
* colour space correction
* font outlining
* bleed creation
* cut contour correction or addition
* template line removal
* finishing mark placement

This stage can be asynchronous because it is no longer sitting directly in the customer upload interaction.

### Using variables

Where possible, avoid creating many separate profiles for each product.

Instead, use variables to parameterise one or a small number of profiles with product-specific values such as:

* dimensions
* bleed
* safety zone
* finishing parameters

This reduces maintenance while still allowing product-specific behaviour.

### Practical advice

* keep upload-stage checks fast
* move expensive operations into the production stage
* test profiles with representative real-world files
* review profile complexity if preflight becomes slow or hard to maintain

### Next steps

* Go to **Manage Plug-in Configuration**
* Go to **Submit Troubleshooting** if quick checks are too slow or production checks are failing unexpectedly


---

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

```
GET https://docs.atomyx.io/atomyx-submit/implementation/portal-configuration/preflight-configuration.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.