> 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/onboarding/setup-e-commerce-store.md).
# Setup E-Commerce Store
**VU OS** offers pre-configured "One-Click" integrations with many E-Commrce platforms such as Shopify, Salesforce, Oracle, and others. VU OS also is built on an **Open Integration Architecture**. This means \***any platform** can be connected to VU OS to power a customized product experience.
\*Platforms must have an accessible catalog and cart API
## **Integration Types: OOTB vs. Custom**
When setting up your store in the VU Admin Panel (**Settings > Stores**), you can choose between two primary paths:
### **1. Out-of-the-Box (OOTB) Configurations**
These are pre-built templates where VU OS already understands the API language of the platform. You need to provide the credentials.
| Platform | Required Fields (per VU OS UI) |
| --------------- | ------------------------------------------------------------------- |
| **BigCommerce** | Name\*, URL\*, Access Token\*, Token Secret\* |
| **EMUN** | Name\*, EMUN URL\* |
| **Magento** | Name\*, Magento URL\*, Access Token\* |
| **Odoo** | Name\*, URL\*, Db Name\*, Username\*, API Key\* |
| **Oracle ATG** | Name\*, ATG URL\*, Username\*, Password\* |
| **Salesforce** | Name\*, Salesforce URL\*, Client Hash\*, Site ID\*, Version ID |
| **Shopify** | Name\*, Shopify URL\*, Shopify Token\*, Fulfillment/Webhook Toggles |
| **WooCommerce** | Name\*, Woo URL\*, Consumer Key\*, Secret\* |
### **2. Custom & Unlisted Platforms (Standalone Path)**
If your platform is not listed above (e.g., a custom React/Vue build, or an unlisted ERP-driven store), select **Standalone Store**.
* **The Standalone Advantage:** This allows you to use the **VU OrderAPI**. Your development team can "push" order data (including the vital RecipeID) directly to VU OS using our standardized API endpoints.
* **Field Requirements:** Only **Name**\* and **Standalone Store URL**\* are required in the initial configuration.
***
## **Global Configuration Standards**
Regardless of the platform you choose (OOTB or Standalone), you will always configure the following global settings as shown in your VU OS dashboard:
1. **Store Key:** A unique internal ID that connects your storefront calls to this specific store instance in VU OS.
2. **Currency:** Supports global currencies including
* Major: USD, EUR, GBP, CAD, AUD.
* Regional: AED, SAR, JPY, CNY, etc. (Full list available in the selection menu).
3. **Locale:** Defines the default language/regional context for order data.
4. **Store Domain:** Your customer-facing web address (e.g., [www.yourbrand.com](http://www.yourbrand.com)).
***
## **How the Integration Works (Universal Logic)**
VU OS creates a relationship between your e-commerce catalog and your custom product templates. No matter which platform you use, the "handshake" follows this standard process:
* **Order Ingestion:** When an order is placed on your storefront, the store notifies VU OS via **Webhook** (Pull) or **API Call** (Push).
* **The RecipeID:** This is a mandatory piece of information for all custom orders. It is the "digital blueprint" of the customer's design. Your store sends this ID to VU OS to ensure the factory produces exactly what the customer saw.
* **Two-Way Fulfillment:** Once an order is processed in VU OS, the system can push a "Shipped" status back to your store, automatically updating your customer's tracking information.
***
## **Next Steps**
1. **Select Your Store Type:** Go to VU OS Settings and click "Create Store."
2. **Gather Credentials:** Use the platform-specific guides to find your API keys or Access Tokens.
3. **Link your Products:** After the store is created, proceed to Product Linking to map your SKUs to their respective VU templates.
> **Need help with a Custom Platform?**\
> If you are using the **Standalone** path, our team will assist you with your integration
---
# 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/onboarding/setup-e-commerce-store.md?ask=&goal=
```
`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.