> For the complete documentation index, see [llms.txt](https://vu-custom.gitbook.io/vu-custom/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vu-custom.gitbook.io/vu-custom/integrations-connections/external-platform-connections.md).

# External Platform Connections

The **Connections** module allows Vu to integrate with external platforms other than your e-commerce storefront. While "Stores" handle the front-end transactions, "Connections" handle the backend logistics, data transfer, and reconciliation.

You can use pre-built integrations or use Vu Platform APIs to build custom connections if a specific platform is not listed.

<figure><img src="/files/i9QNYCXUzo4OAlxpP3WQ" alt=""><figcaption></figcaption></figure>

## **Connection Categories**

We group connections into four primary categories:

<details>

<summary><strong>1. File Share &#x26; Authentication (Artwork Transfer)</strong></summary>

These connections are primarily used to transfer artwork files from Vu to the factory's "Hot Folders," servers, or processing queues.

* **Supported Platforms:** Dropbox, Google Drive, FTP/sFTP, various server configurations.
* **Use Case:** A machine or operator on the production floor monitors a folder for incoming print-ready artwork files generated by VU.

</details>

<details>

<summary><strong>2. Systems (Accounting &#x26; Reconciliation)</strong></summary>

These connections link Vu to financial software for invoicing and order reconciliation.

* **Supported Platforms:** QuickBooks, Zoho Books.

</details>

<details>

<summary><strong>3. Order Management &#x26; Fulfillment (OMS)</strong></summary>

These integrations route order data to third-party logistics (3PL) providers or external Order Management Systems.

* **Supported Platforms:** NetSuite, ShipStation, ShipHero.
* **Use Case:** ensuring orders flow from Vu into the merchant's fulfillment engine to generate shipping labels and track delivery

</details>

<details>

<summary><strong>4. Custom Authentication Protocols</strong></summary>

For bespoke integrations where a specific branded connector does not exist, standard authentication protocols can be configured to link with proprietary APIs.

* Basic Auth&#x20;
  * Name: Display name.\
    Connection url: Endpoint URL.\
    Username / Password: Basic authentication credentials.\
    Request method: POST, GET, PUT, or DELETE.\
    Custom headers: (Optional) JSON format.\
    Additional attributes: (Optional) JSON format.
* OAuth
  * Name: Display name.\
    Connection url: Primary endpoint.\
    Token url: URL for token retrieval.\
    Key / Secret: Consumer Key and Secret.\
    Request method: POST, GET, PUT, or DELETE.\
    Headers for connection: (Optional) JSON format.\
    Attributes for token retrieval: (Optional) JSON format.

</details>

{% hint style="info" %}
Only users with Administrator permissions can add, edit, and delete the connections.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://vu-custom.gitbook.io/vu-custom/integrations-connections/external-platform-connections.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.