> 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/implementation-patterns/integration-pattern-summary.md).

# Integration Pattern Summary

### Main implementation patterns

#### Standalone portal

A dedicated submission portal with its own URL and branding.

**Best for:**

* B2B print providers
* large-format workflows
* submission journeys that happen separately from ordering

#### API-created sessions with portal redirect

The external ordering platform creates a submission session and redirects the user into the Atomyx Submit experience.

**Best for:**

* label and packaging workflows
* multiple storefronts sharing one submission backend
* businesses that want the storefront to remain in control of the wider order journey

#### API-heavy custom integration

A more customised implementation where the surrounding application controls more of the user experience and Atomyx Submit is used more selectively within the broader flow.

**Best for:**

* teams with strong development capacity
* highly specific user experience requirements
* environments where the ordering platform must tightly control the full journey

### How to choose

When choosing an implementation pattern, consider:

* where the customer journey should begin and end
* whether the ERP or storefront needs to create sessions directly
* how much of the user experience should be owned externally
* whether one portal instance needs to support multiple brands or storefronts
* how much custom development effort is acceptable

### General recommendation

For many implementations, the most practical approach is:

* let the ordering or ERP system remain the system of record
* use Atomyx Submit for the artwork submission experience
* use Atomyx Prepare for processing and proof generation
* keep the systems connected through APIs and callbacks

This provides a good balance between control, speed of delivery, and long-term maintainability.


---

# 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/implementation-patterns/integration-pattern-summary.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.