# 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="https://3295576361-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FP4xZUKOSmKW52VquplA7%2Fuploads%2FlcTCoOxi2sF4xS3T6E0b%2FScreenshot%202026-01-16%20at%203.57.38%20AM.png?alt=media&#x26;token=33c434c5-222c-431f-9372-debbe293f996" 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 %}