diff --git a/docs/.vitepress/config.ts b/docs/.vitepress/config.ts
index 40af41e..b58ed44 100644
--- a/docs/.vitepress/config.ts
+++ b/docs/.vitepress/config.ts
@@ -17,30 +17,31 @@ function loadSidebar(project: string): DefaultTheme.SidebarItem[] {
}
const projects = [
- // { slug: 'shopify', label: 'Shopify' },
- // { slug: 'magento2', label: 'Magento 2' },
- // { slug: 'odoo-erp', label: 'Odoo ERP' },
- // { slug: 'bigcommerce', label: 'BigCommerce' },
- // { slug: 'shopware6', label: 'Shopware 6' },
- // { slug: 'woocommerce', label: 'WooCommerce' },
- // { slug: 'bagisto', label: 'Bagisto' },
- // { slug: 'cs-cart', label: 'CS-Cart' },
- // { slug: 'prestashop', label: 'PrestaShop' },
- // { slug: 'icecat', label: 'Icecat' },
- // { slug: 'xml-connector', label: 'XML Connector' },
- // { slug: 'aws-integration', label: 'AWS Integration' },
{ slug: 'ai-product-feed-openai', label: 'AI Product Feed (OpenAI)' },
+ { slug: 'auto-sku-generator', label: 'Auto SKU Generator' },
+ { slug: 'aws-integration', label: 'AWS Integration' },
+ { slug: 'bagisto', label: 'Bagisto' },
+ { slug: 'bigcommerce', label: 'BigCommerce' },
+ { slug: 'azure-integration', label: 'Azure Integration' },
+ { slug: 'cloudflare-r2-integration', label: 'Cloudflare R2 Integration' },
+ { slug: 'cs-cart', label: 'CS-Cart' },
+ { slug: 'dam', label: 'DAM' },
+ // { slug: 'dam-webdav', label: 'DAM NextCloud' },
+ { slug: 'deepl', label: 'DeepL Translator' },
+ // { slug: 'icecat', label: 'Icecat' },
// { slug: 'job-scheduler', label: 'Job Scheduler' },
- { slug: 'supplier-data-portal', label: 'Supplier Data Portal' },
- // { slug: 'public-image-url', label: 'Public Image URL' },
{ slug: 'maker-checker-workflow', label: 'Maker Checker Workflow' },
+ { slug: 'magento2', label: 'Magento 2' },
+ { slug: 'odoo-erp', label: 'Odoo ERP' },
// { slug: 'pdf-generator', label: 'PDF Generator' },
- // { slug: 'dam', label: 'DAM' },
- // { slug: 'dam-webdav', label: 'DAM NextCloud' },
+ // { slug: 'prestashop', label: 'PrestaShop' },
+ // { slug: 'public-image-url', label: 'Public Image URL' },
+ { slug: 'shopify', label: 'Shopify' },
+ // { slug: 'shopware6', label: 'Shopware 6' },
// { slug: 'starter-pack', label: 'Starter Pack' },
- { slug: 'auto-sku-generator', label: 'Auto SKU Generator' },
- { slug: 'deepl', label: 'DeepL Translator' },
- { slug: 'cloudflare-r2-integration', label: 'Cloudflare R2 Integration' }
+ { slug: 'supplier-data-portal', label: 'Supplier Data Portal' },
+ { slug: 'woocommerce', label: 'WooCommerce' },
+ // { slug: 'xml-connector', label: 'XML Connector' },
] as const
export default defineConfig({
@@ -64,6 +65,7 @@ export default defineConfig({
items: projects.map(p => ({ text: p.label, link: `/${p.slug}/` })),
},
{ text: 'User Guide', link: 'https://docs.unopim.com/' },
+ {text: 'Dev Doc', link: 'https://devdocs.unopim.com/'},
{ text: 'Contact Us', link: 'https://unopim.com/en/contacts/' },
],
sidebar: Object.fromEntries(
@@ -82,9 +84,6 @@ export default defineConfig({
message: 'Released under the MIT License.',
copyright: `Copyright © ${new Date().getFullYear()} UnoPim`,
},
- socialLinks: [
- { icon: 'github', link: 'https://github.com/unopim' },
- ],
search: {
provider: 'local',
},
diff --git a/docs/.vitepress/theme/Layout.vue b/docs/.vitepress/theme/Layout.vue
index 37cc75c..9d8d642 100644
--- a/docs/.vitepress/theme/Layout.vue
+++ b/docs/.vitepress/theme/Layout.vue
@@ -52,3 +52,34 @@ onBeforeUnmount(() => {
+
+
diff --git a/docs/aws-integration/assets/amazon-setup/account-create-aws.webp b/docs/aws-integration/assets/amazon-setup/account-create-aws.webp
new file mode 100644
index 0000000..1a46286
Binary files /dev/null and b/docs/aws-integration/assets/amazon-setup/account-create-aws.webp differ
diff --git a/docs/aws-integration/assets/amazon-setup/all-services.webp b/docs/aws-integration/assets/amazon-setup/all-services.webp
new file mode 100644
index 0000000..c95fd8a
Binary files /dev/null and b/docs/aws-integration/assets/amazon-setup/all-services.webp differ
diff --git a/docs/aws-integration/assets/amazon-setup/create-account-aws.webp b/docs/aws-integration/assets/amazon-setup/create-account-aws.webp
new file mode 100644
index 0000000..0e2af50
Binary files /dev/null and b/docs/aws-integration/assets/amazon-setup/create-account-aws.webp differ
diff --git a/docs/aws-integration/assets/amazon-setup/img3.webp b/docs/aws-integration/assets/amazon-setup/img3.webp
new file mode 100644
index 0000000..23cc7ac
Binary files /dev/null and b/docs/aws-integration/assets/amazon-setup/img3.webp differ
diff --git a/docs/aws-integration/assets/amazon-setup/img4.webp b/docs/aws-integration/assets/amazon-setup/img4.webp
new file mode 100644
index 0000000..fe3f1c5
Binary files /dev/null and b/docs/aws-integration/assets/amazon-setup/img4.webp differ
diff --git a/docs/aws-integration/assets/amazon-setup/img5.webp b/docs/aws-integration/assets/amazon-setup/img5.webp
new file mode 100644
index 0000000..199d16e
Binary files /dev/null and b/docs/aws-integration/assets/amazon-setup/img5.webp differ
diff --git a/docs/aws-integration/assets/amazon-setup/img6.webp b/docs/aws-integration/assets/amazon-setup/img6.webp
new file mode 100644
index 0000000..2979393
Binary files /dev/null and b/docs/aws-integration/assets/amazon-setup/img6.webp differ
diff --git a/docs/aws-integration/assets/amazon-setup/img7.webp b/docs/aws-integration/assets/amazon-setup/img7.webp
new file mode 100644
index 0000000..92749dd
Binary files /dev/null and b/docs/aws-integration/assets/amazon-setup/img7.webp differ
diff --git a/docs/aws-integration/assets/installation/aws-s3.png b/docs/aws-integration/assets/installation/aws-s3.png
new file mode 100644
index 0000000..25bc17d
Binary files /dev/null and b/docs/aws-integration/assets/installation/aws-s3.png differ
diff --git a/docs/aws-integration/assets/overview/intro-banner.png b/docs/aws-integration/assets/overview/intro-banner.png
new file mode 100644
index 0000000..50dae36
Binary files /dev/null and b/docs/aws-integration/assets/overview/intro-banner.png differ
diff --git a/docs/aws-integration/assets/unopim-setup/aws-cred.png b/docs/aws-integration/assets/unopim-setup/aws-cred.png
new file mode 100644
index 0000000..975136f
Binary files /dev/null and b/docs/aws-integration/assets/unopim-setup/aws-cred.png differ
diff --git a/docs/aws-integration/assets/unopim-setup/aws-s3-section.png b/docs/aws-integration/assets/unopim-setup/aws-s3-section.png
new file mode 100644
index 0000000..973f70d
Binary files /dev/null and b/docs/aws-integration/assets/unopim-setup/aws-s3-section.png differ
diff --git a/docs/aws-integration/assets/unopim-setup/aws-s3.png b/docs/aws-integration/assets/unopim-setup/aws-s3.png
new file mode 100644
index 0000000..6e1e04e
Binary files /dev/null and b/docs/aws-integration/assets/unopim-setup/aws-s3.png differ
diff --git a/docs/aws-integration/assets/unopim-setup/product-catalog.png b/docs/aws-integration/assets/unopim-setup/product-catalog.png
new file mode 100644
index 0000000..ab20238
Binary files /dev/null and b/docs/aws-integration/assets/unopim-setup/product-catalog.png differ
diff --git a/docs/aws-integration/assets/unopim-setup/save-cred.png b/docs/aws-integration/assets/unopim-setup/save-cred.png
new file mode 100644
index 0000000..f73e69f
Binary files /dev/null and b/docs/aws-integration/assets/unopim-setup/save-cred.png differ
diff --git a/docs/aws-integration/assets/unopim-setup/verify.png b/docs/aws-integration/assets/unopim-setup/verify.png
new file mode 100644
index 0000000..2264247
Binary files /dev/null and b/docs/aws-integration/assets/unopim-setup/verify.png differ
diff --git a/docs/aws-integration/aws-s3-setup-in-unopim.md b/docs/aws-integration/aws-s3-setup-in-unopim.md
new file mode 100644
index 0000000..761f03c
--- /dev/null
+++ b/docs/aws-integration/aws-s3-setup-in-unopim.md
@@ -0,0 +1,87 @@
+# AWS S3 Setup in UnoPim
+
+After installing the **UnoPim AWS Integration** module, users with the required permissions can manage the AWS storage settings from the admin panel.
+
+Go to:
+
+**Left Menu → AWS S3 → Credentials**
+
+
+
+From here, you can enable the module and connect UnoPim to **Amazon S3** so files are stored in your AWS bucket instead of only on the local server.
+
+## What This Configuration Does
+
+Once the setup is saved correctly:
+
+- UnoPim can store supported files on **Amazon S3**.
+- Your media can be served from the configured **bucket URL**.
+- Cached file URLs are refreshed based on the **Environment Update Time** value.
+
+## Fields You Need to Fill
+
+To connect UnoPim with AWS, enter the configuration details created in your Amazon AWS account.
+
+| Field | Description |
+|---|---|
+| **Access Key ID** | The public access key generated for your AWS IAM user. |
+| **Secret Key** | The secret key paired with the Access Key ID. Keep this private. |
+| **Bucket Name** | The exact name of the S3 bucket where UnoPim should store files. |
+| **Region** | The AWS region where your bucket was created, such as `us-east-1` or `ap-south-1`. |
+| **Bucket URL** | The public URL or bucket endpoint used to access files stored in the bucket. |
+
+## How to Configure It
+
+1. Open the **AWS S3 → Credentials** section in UnoPim.
+
+
+
+2. Enable the module if it is currently disabled.
+
+3. Enter the **Access Key ID** and **Secret Key** from your AWS account.
+4. Add the correct **Bucket Name** and **Region**.
+5. Enter the **Bucket URL** that should be used to access uploaded files.
+
+
+
+6. Save the configuration.
+
+
+
+After saving, UnoPim will use these details to connect with Amazon S3 for file storage.
+
+## Understanding Environment Update Time
+
+The **Environment Update Time** field controls how long image URLs stay cached in the browser before they are refreshed.
+
+- The value is entered in **seconds**.
+- During this time, the browser keeps using the existing cached image URL.
+- A new request is made only after the configured time has passed.
+
+If this field is left empty, UnoPim uses the default value:
+
+`86400` seconds = `24 hours`
+
+## Why This Setting Matters
+
+This setting helps:
+
+- reduce repeated file URL requests,
+- avoid unnecessary fetches from AWS,
+- improve loading efficiency for frequently viewed images.
+
+## Recommended Before Saving
+
+Before saving the configuration, make sure:
+
+- your AWS credentials are valid,
+- the S3 bucket name is correct,
+- the selected region matches the bucket region,
+- the bucket URL is accessible,
+- the IAM user has permission to read and write files in the bucket.
+
+If you have not prepared your AWS account yet, follow [Setup Credentials in Amazon S3](./setup-amazon.md) first.
+
+Once your credentials are saved, continue to [Migrate Existing Files to S3](./migrate-existing-files.md) if you want to move older local media into Amazon S3.
+
+If you also use **UnoPim DAM** and want to move DAM asset files from private local storage to S3, follow [DAM Asset Migration to AWS S3](./dam-asset-migration-to-aws-s3.md).
diff --git a/docs/aws-integration/contact.md b/docs/aws-integration/contact.md
new file mode 100644
index 0000000..058272a
--- /dev/null
+++ b/docs/aws-integration/contact.md
@@ -0,0 +1,21 @@
+# Contact & Support
+
+That wraps up the user guide for the **UnoPim AWS Integration** extension. We hope this documentation helps you set up Amazon S3 storage in UnoPim with clarity.
+
+If you have any queries, doubts, or need help with the extension, feel free to contact us.
+
+## Get in Touch
+
+**Email**
+Reach out to us at [support@webkul.com](mailto:support@webkul.com) and our team will get back to you.
+
+**HelpDesk**
+You can also raise a ticket through the [Webkul HelpDesk System](https://webkul.uvdesk.com/en/).
+
+This is useful if you want to:
+
+- report an issue,
+- ask a setup-related question,
+- track the status of your support request.
+
+We are happy to help whenever needed.
diff --git a/docs/aws-integration/dam-asset-migration-to-aws-s3.md b/docs/aws-integration/dam-asset-migration-to-aws-s3.md
new file mode 100644
index 0000000..9cb0857
--- /dev/null
+++ b/docs/aws-integration/dam-asset-migration-to-aws-s3.md
@@ -0,0 +1,121 @@
+# DAM Asset Migration to AWS S3
+
+If you use **UnoPim DAM** together with the **AWS S3 Integration**, you can move DAM asset files from the local private disk to your configured **Amazon S3** bucket.
+
+This is useful when:
+
+- your DAM assets were uploaded before AWS S3 was enabled,
+- you want DAM files to be served from the same S3 storage as the rest of your media,
+- you want to reduce storage usage on the local server after a successful migration.
+
+## Command Signature
+
+Run the following Artisan command from your UnoPim project:
+
+```bash
+php artisan unopim:dam:move-asset-to-s3
+```
+
+## Before You Start
+
+Make sure the following setup is already complete:
+
+1. The **AWS Integration** module is installed and configured.
+2. Your **Amazon S3 bucket** is reachable with valid credentials.
+3. The **UnoPim DAM** module is installed and working correctly.
+4. The DAM assets you want to migrate are still available on the local private disk.
+
+If your AWS setup is not ready yet, complete these guides first:
+
+- [Setup Credentials in Amazon S3](./setup-amazon.md)
+- [AWS S3 Setup in UnoPim](./aws-s3-setup-in-unopim.md)
+
+## Authentication Required
+
+For security, this command requires valid **admin credentials** before the migration begins.
+
+During execution, you will be prompted to enter:
+
+- your **admin email**,
+- your **admin password**.
+
+Access is granted only if those credentials belong to an admin user in UnoPim.
+
+> [!NOTE]
+> Keep the terminal session private while entering credentials, especially on shared servers or staging environments.
+
+## What the Command Prompts For
+
+After authentication, the command asks how you want to handle the migration.
+
+## What You Will See in the Terminal
+
+During execution, the command prompts you in this order:
+
+```bash
+Enter your Email:
+> admin@example.com
+
+Enter your Password:
+>
+
+Want to migrate only new uploaded files from your local to s3 (yes/no):
+>
+
+Migrate New only flag: No
+
+Want to delete files from local once uploaded to s3? (yes/no):
+>
+
+Delete flag: No
+Starting migration to aws
+10/10 [============================] 100%
+Done Moving DAM Assets.
+```
+
+This confirms that the command:
+
+- authenticates the admin user first,
+- asks whether only new files should be migrated,
+- asks whether local files should be deleted after upload,
+- then starts the DAM asset transfer to Amazon S3.
+
+### Migrate Only New Files
+
+The command asks whether you want to migrate only files that are not already present on S3.
+
+- Choose **Yes** when you want to upload only newly added or still-unmigrated DAM assets.
+- Choose **No** when you want the command to process the full DAM asset set again.
+
+This is helpful when you run the migration regularly and want to avoid reprocessing files that already exist in S3.
+
+### Delete Local Files After Upload
+
+The command also asks whether local files should be deleted after a successful upload to S3.
+
+- Choose **Yes** to free local server storage after the migration completes successfully.
+- Choose **No** if you want to keep the local files as a backup copy.
+
+> [!CAUTION]
+> Delete local files only after you confirm the migrated DAM assets are accessible from Amazon S3.
+
+## Recommended Migration Flow
+
+Use this order in production:
+
+1. Run the command.
+2. Authenticate with a valid admin account.
+3. Start with **migrate only new files = Yes** if you are doing an incremental migration.
+4. Keep **delete local files = No** on the first run.
+5. Verify that DAM asset files are opening correctly from S3.
+6. Run the command again with local-file deletion only when you are fully confident in the migration result.
+
+## After Migration
+
+After the command finishes:
+
+- verify a few DAM assets from the admin panel,
+- confirm the files exist in your S3 bucket,
+- check whether old local files should remain for backup or be removed in a follow-up run.
+
+If you also need the DAM-side view of this process, see [DAM Asset Migration to AWS S3](../dam/dam-asset-migration-to-aws-s3.md).
diff --git a/docs/aws-integration/index.md b/docs/aws-integration/index.md
index 12c7f06..de5950e 100644
--- a/docs/aws-integration/index.md
+++ b/docs/aws-integration/index.md
@@ -1,3 +1,58 @@
-# Aws Integration Extension
+# UnoPim AWS S3 Integration
+
+The **UnoPim AWS Integration** connects your UnoPim instance with **Amazon S3** — one of the world's most reliable cloud storage services — to store, manage, and serve your product images and PDFs securely in the cloud.
+
+Instead of storing media files on your local server, everything gets uploaded to Amazon S3 automatically. This means your assets are always available, load quickly for users, and can scale without any storage limitations as your catalog grows.
+
+
+
+
+
+
+
+## How It Works
+
+Once connected, the integration handles your media in two ways:
+
+- **New files** — any image or PDF you add to UnoPim is automatically synced to Amazon S3 without any manual action.
+
+The integration also includes a **cache refresh mechanism** — it refreshes cached images at regular intervals so your storefront and product pages always display the latest version of any updated asset. If no custom refresh time is set, a sensible default kicks in automatically to keep everything current.
+
+
+## Key Features
+
+### Cloud Storage
+- Connect UnoPim with **Amazon S3** to store images and PDFs safely and reliably in the cloud.
+- Enjoy **unlimited, scalable storage** — no capacity limits, no need to manage server disk space.
+
+### Easy Setup
+- Get connected quickly by entering just four details: **Access Key ID**, **Secret Key**, **Region**, and **Bucket Name**.
+
+### Automatic Media Sync
+- All new images and PDFs added to UnoPim are **automatically uploaded to S3** — no manual uploads needed.
+
+### Cache Management
+- Set a custom **environment refresh time** to control how often cached images are updated.
+- Enable **automatic cache refresh** to minimise repeated requests to AWS and ensure faster media loading.
+- If no refresh time is configured, a **default interval** is applied automatically so updates still happen without any manual intervention.
+
+### DAM Integration *(requires UnoPim DAM)*
+If you have the **UnoPim Digital Asset Management (DAM)** extension installed, the AWS integration extends its capabilities further:
+
+- **DAM asset import for products** — when importing products, the system automatically resolves DAM asset file paths to their correct asset IDs, so media links stay accurate without manual correction.
+- **DAM asset import for categories** — the same automatic resolution applies to category fields of type `asset` during import.
+- **Category media in export archives** — when you export a ZIP file, it now includes all files referenced by category fields of type `image`, `file`, and `asset`, alongside your product media — giving you a complete export package every time.
+
+
+## Requirements
+
+| Requirement | Detail |
+|---|---|
+| **Amazon AWS Account** | Required to create an S3 bucket and generate API keys |
+| **S3 Bucket** | A dedicated bucket for storing UnoPim media |
+| **Access Key ID & Secret Key** | Generated from your AWS IAM user settings |
+| **UnoPim DAM** *(optional)* | Required only for DAM-specific asset import and export features |
+
-Placeholder landing page. Real docs are pulled from the project repo at build time.
diff --git a/docs/aws-integration/installation.md b/docs/aws-integration/installation.md
new file mode 100644
index 0000000..bd6769b
--- /dev/null
+++ b/docs/aws-integration/installation.md
@@ -0,0 +1,104 @@
+# Installation
+
+Follow the steps below to install the UnoPim AWS Integration extension. Make sure you have terminal access to your server and know which version of Laravel your UnoPim instance is running before you begin.
+
+
+## Step 1 — Add the Package Files
+
+Download and unzip the extension. Inside, you'll find a folder called `AWSIntegration` — move it into the following directory in your UnoPim project:
+
+```
+packages/Webkul/AWSIntegration
+```
+
+
+## Step 2 — Register the Service Provider
+
+This step depends on which version of Laravel your project uses.
+
+**Laravel 10 — add to `config/app.php` under the `providers` array:**
+
+```php
+Webkul\AWSIntegration\Providers\AWSIntegrationServiceProvider::class,
+```
+
+**Laravel 11 and above — add to `bootstrap/providers.php`:**
+
+```php
+use Webkul\AWSIntegration\Providers\AWSIntegrationServiceProvider;
+
+return [
+ // ...existing providers...
+ AWSIntegrationServiceProvider::class,
+];
+```
+
+
+## Step 3 — Update Composer Autoload
+
+Open `composer.json` and add the following line under the `autoload > psr-4` section:
+
+```json
+"Webkul\\AWSIntegration\\": "packages/Webkul/AWSIntegration/src"
+```
+
+
+## Step 4 — Run the Installer
+
+Run the following commands in order. Each command handles a specific part of the setup:
+
+```bash
+composer dump-autoload
+php artisan aws-s3-package:install
+php artisan optimize:clear
+```
+
+Here's what each command does:
+
+| Command | What it does |
+|---|---|
+| `composer dump-autoload` | Refreshes the Composer autoloader to recognise the new package |
+| `php artisan aws-s3-package:install` | Installs the AWS SDK dependencies, runs database migrations, and publishes package assets |
+| `php artisan optimize:clear` | Clears the application cache |
+
+> **Note:** The installer automatically pulls in the required AWS libraries — `league/flysystem-aws-s3-v3` and `aws/aws-sdk-php` — so you don't need to install them separately.
+
+
+## Step 5 — Publish Config *(Only if using a custom theme)*
+
+If your UnoPim instance uses a custom published theme, run this additional command:
+
+```bash
+php artisan vendor:publish --tag=aws-s3-config --force
+```
+
+You can skip this step if you're using the default UnoPim theme.
+
+
+## Step 6 — Build Frontend Assets *(Only if using a custom theme)*
+
+If you ran Step 5, you also need to build the frontend assets for the extension.
+
+Open your project's `package.json` file and add the following lines inside the `scripts` section:
+
+```json
+"aws:install": "cd packages/Webkul/AWSIntegration && npm install",
+"aws:build": "cd packages/Webkul/AWSIntegration && npm run build"
+```
+
+Then run:
+
+```bash
+npm run aws:install
+npm run aws:build
+```
+
+
+## Verify the Installation
+
+Once all steps are complete, log in to your UnoPim dashboard. If the extension has been installed correctly, you'll be able to access the AWS S3 configuration settings from the admin panel.
+
+
+
+If something doesn't look right, try running `php artisan optimize:clear` again and refreshing the page.
+
diff --git a/docs/aws-integration/media-upload-on-amazon-s3.md b/docs/aws-integration/media-upload-on-amazon-s3.md
new file mode 100644
index 0000000..6d25871
--- /dev/null
+++ b/docs/aws-integration/media-upload-on-amazon-s3.md
@@ -0,0 +1,58 @@
+# Media Upload on Amazon S3
+
+Once the **UnoPim AWS Integration** is configured, users can continue uploading media files in the usual way from the product section.
+
+Go to:
+
+**Catalog → Products**
+
+From there, you can upload:
+
+- product images,
+- PDF documents,
+- other supported product media files.
+
+## How It Works
+
+You do not need to follow any separate upload process for Amazon S3.
+
+When a user uploads media in UnoPim:
+
+1. the file is added through the normal product form,
+2. UnoPim automatically transfers the file to **Amazon S3**,
+3. an **S3 file link** is generated for that media.
+
+
+
+This means users can work inside UnoPim as usual, while the storage is handled in the background through AWS.
+
+
+
+this shows the media file stored in Amazon S3 with the correct bucket URL, confirming that the upload and storage process is working as expected.
+
+## What Users Need to Know
+
+- Uploading files from the product page works the same as before.
+- The system automatically stores uploaded files in the configured **S3 bucket**.
+- Media links are served using the AWS S3 configuration saved in UnoPim.
+
+## Benefits of Uploading Media to S3
+
+Using Amazon S3 for media storage provides several benefits:
+
+- **automatic cloud storage** for newly uploaded files,
+- **reliable access** to images and documents,
+- **better scalability** as your media library grows,
+- **reduced pressure on local server storage**.
+
+Because Amazon S3 offers highly scalable cloud storage, you can continue adding large numbers of media files without worrying about local storage limitations.
+
+## Before Uploading
+
+Before uploading media, make sure:
+
+- the AWS Integration module is enabled,
+- your AWS credentials are configured correctly,
+- the S3 bucket and bucket URL are valid.
+
+If the AWS configuration is not complete, review [AWS S3 Setup in UnoPim](./aws-s3-setup-in-unopim.md).
diff --git a/docs/aws-integration/migrate-existing-files.md b/docs/aws-integration/migrate-existing-files.md
new file mode 100644
index 0000000..f5f6c9b
--- /dev/null
+++ b/docs/aws-integration/migrate-existing-files.md
@@ -0,0 +1,104 @@
+# Migrate Existing Files to S3
+
+After configuring the **UnoPim AWS Integration**, you can move your existing media files from local storage to **Amazon S3**.
+
+This is useful when:
+
+- the module was installed after media already existed in UnoPim,
+- you want old files and new files to be stored in the same S3 bucket,
+- you want to reduce dependency on local server storage.
+
+## Before You Start
+
+Make sure the following steps are already completed:
+
+1. Create an **S3 bucket** in your AWS account.
+2. Generate the **Access Key ID** and **Secret Key** from IAM.
+3. Configure your AWS credentials in UnoPim.
+
+If you have not completed these steps yet, follow:
+
+- [Setup Credentials in Amazon S3](./setup-amazon.md)
+- [AWS S3 Setup in UnoPim](./aws-s3-setup-in-unopim.md)
+
+## Migrate Existing Media to AWS S3
+
+To move existing UnoPim media files to Amazon S3, run:
+
+```bash
+php artisan aws_integration:move_existing_files
+```
+
+This command uploads the existing media from local storage to your configured S3 bucket.
+
+> [!NOTE]
+> Run this command only after your AWS configuration has been saved correctly in UnoPim.
+
+## Remove Local Media After Migration
+
+After confirming that the files are successfully available in Amazon S3, you can remove the local copies by running:
+
+```bash
+php artisan aws_integration:remove_media_files
+```
+
+This helps free up storage space on your server after migration.
+
+> [!CAUTION]
+> Before removing local files, make sure your migration is complete and the files are accessible from S3.
+
+## Update S3 File Visibility (ACL)
+
+You can also update the visibility of files already stored in your S3 bucket.
+
+This command lets you make files:
+
+- `public` so they can be accessed publicly,
+- `private` so access remains restricted.
+
+Run:
+
+```bash
+php artisan aws_integration:update_visibility
+```
+
+## Available Options
+
+You can use the following options with the visibility command:
+
+| Option | Description |
+|---|---|
+| `--visibility=public or private` | Overrides the default visibility stored in the database. |
+| `--path=folder/path` | Applies the visibility update only to a specific folder or prefix. |
+| `--dry-run` | Shows what would change without actually updating any files. |
+
+## Command Examples
+
+Make all matching files public:
+
+```bash
+php artisan aws_integration:update_visibility --visibility=public
+```
+
+Make files inside a specific folder private:
+
+```bash
+php artisan aws_integration:update_visibility --path=products --visibility=private
+```
+
+Preview the changes without applying them:
+
+```bash
+php artisan aws_integration:update_visibility --dry-run
+```
+
+## Recommended Usage
+
+Before running the visibility update in production:
+
+- use `--dry-run` first,
+- check that the selected path is correct,
+- confirm whether files should be `public` or `private`.
+
+> [!CAUTION]
+> The visibility update command can affect all matching files in your S3 bucket. Always review the result with `--dry-run` before applying changes in production.
diff --git a/docs/aws-integration/setup-amazon.md b/docs/aws-integration/setup-amazon.md
new file mode 100644
index 0000000..0142315
--- /dev/null
+++ b/docs/aws-integration/setup-amazon.md
@@ -0,0 +1,116 @@
+# Setting Up Your Amazon S3 Credentials
+
+Before configuring the UnoPim AWS Integration, you need to set up an Amazon S3 bucket and generate your API credentials. Follow the steps below to get everything ready on the AWS side.
+
+
+## Step 1 — Create an AWS Account
+
+Go to [https://aws.amazon.com](https://aws.amazon.com) and click **Create an AWS Account**.
+
+
+
+
+On the sign-in page, you'll see two options:
+
+| Option | Who it's for |
+|---|---|
+| **Create an AWS Account** | First-time users who don't have an AWS account yet |
+| **Sign in to the Console** | Existing users who already have an account |
+
+
+
+Once signed in, you'll land on the AWS Management Console — your central dashboard for all AWS services.
+
+
+
+## Step 2 — Open Amazon S3
+
+From the AWS Console, click on **All Services** and select **S3** under the Storage section. Alternatively, type `S3` in the search bar at the top and click on it from the results.
+
+
+
+This opens the S3 dashboard where you can see all your existing buckets — or create a new one.
+
+
+
+
+## Step 3 — Create a New Bucket
+
+Click the **Create bucket** button. Fill in the required details on the Create bucket page:
+
+| Field | What to enter |
+|---|---|
+| **Bucket name** | A unique name for your bucket (e.g., `mystore-unopim-media`). Names are globally unique — no two buckets on all of AWS can share the same name. |
+| **AWS Region** | Choose the region closest to your server for best performance (e.g., `us-east-1`, `eu-west-1`) |
+
+> **Important:** Make sure to **uncheck "Block all public access"** so that UnoPim can read and write media files to the bucket. Without this, file uploads will fail.
+
+Once all details are filled in, scroll to the bottom and click **Create bucket**.
+
+
+
+
+## Step 4 — Manage Your Bucket
+
+Once the bucket is created, you can:
+
+- **Upload files** directly to the bucket
+- **Create folders** to organise your assets
+- **View and manage** all stored data
+
+This is the same bucket where UnoPim will store your product images and PDFs once the integration is active.
+
+
+## Step 5 — Create an IAM User
+
+Instead of using your main AWS root account for the integration, it's strongly recommended to create a dedicated **IAM user** with limited permissions. This keeps your main account secure.
+
+1. In the AWS Console, search for **IAM** and open it — it's listed under **Security, Identity & Compliance**.
+
+
+
+2. In the IAM dashboard, click **Users** in the left sidebar.
+3. Click **Add users** to create a new IAM user.
+4. Enter a username (e.g., `unopim-s3-user`) and follow the on-screen steps to set permissions.
+
+
+
+> Assign the `AmazonS3FullAccess` policy to give this user full access to your S3 bucket, or create a custom policy limited to your specific bucket for tighter security.
+
+
+
+## Step 6 — Generate Your Access Key ID and Secret Access Key
+
+Once your IAM user is created:
+
+1. Click on the user's name to open their profile.
+2. Go to the **Security credentials** tab.
+3. Scroll to **Access keys** and click **Create access key**.
+4. Your **Access Key ID** and **Secret Access Key** will be generated and displayed.
+
+
+
+> **Important:** AWS will only show your Secret Access Key **once**. Copy both keys immediately and store them in a safe place. If you lose the Secret Key, you'll need to delete this key pair and generate a new one.
+
+
+## What You Now Have
+
+You should now have the four values needed to connect UnoPim to your S3 bucket:
+
+| Credential | Where to find it |
+|---|---|
+| **Access Key ID** | Generated in Step 6 |
+| **Secret Access Key** | Generated in Step 6 — save immediately |
+| **Region** | The region selected when creating the bucket in Step 3 |
+| **Bucket Name** | The name you gave your bucket in Step 3 |
+
+
+## Module Configuration in UnoPim
+
+After installing the UnoPim AWS Integration, navigate to the left sidebar in your UnoPim dashboard and go to:
+
+**AWS S3 → Credentials**
+
+Here, users with the required permissions can enter the credentials collected above and manage all AWS configuration settings.
+
+Head over to [AWS S3 Setup in UnoPim](./aws-s3-setup-in-unopim.md) to complete the setup.
diff --git a/docs/aws-integration/sidebar.json b/docs/aws-integration/sidebar.json
index d665e86..0b76036 100644
--- a/docs/aws-integration/sidebar.json
+++ b/docs/aws-integration/sidebar.json
@@ -2,7 +2,28 @@
{
"text": "Aws Integration",
"items": [
- { "text": "Overview", "link": "/aws-integration/" }
+ { "text": "Overview", "link": "/aws-integration/" },
+ {"text" : "Installation", "link": "/aws-integration/installation" },
+ {"text" : "Setup Credentials in Amazon S3", "link": "/aws-integration/setup-amazon" }
+ ]
+ },
+
+ {
+ "text": "Configuration",
+ "items": [
+ {"text" : "AWS S3 Setup in UnoPim", "link": "/aws-integration/aws-s3-setup-in-unopim" },
+ {"text" : "Migrate Existing Files to S3", "link": "/aws-integration/migrate-existing-files" },
+ {"text" : "Media Upload on Amazon S3", "link": "/aws-integration/media-upload-on-amazon-s3" },
+ {"text" : "DAM Asset Migration to AWS S3", "link": "/aws-integration/dam-asset-migration-to-aws-s3" }
+
+
+ ]
+ },
+
+ {
+ "text":"Support",
+ "items":[
+ {"text" : "Contact & Support", "link": "/aws-integration/contact" }
]
}
]
diff --git a/docs/azure-integration/assets/overview/intro-banner.png b/docs/azure-integration/assets/overview/intro-banner.png
new file mode 100644
index 0000000..fe541ed
Binary files /dev/null and b/docs/azure-integration/assets/overview/intro-banner.png differ
diff --git a/docs/azure-integration/assets/setup/azure-cred.png b/docs/azure-integration/assets/setup/azure-cred.png
new file mode 100644
index 0000000..b2afa22
Binary files /dev/null and b/docs/azure-integration/assets/setup/azure-cred.png differ
diff --git a/docs/azure-integration/assets/setup/azure.png b/docs/azure-integration/assets/setup/azure.png
new file mode 100644
index 0000000..f9cc26f
Binary files /dev/null and b/docs/azure-integration/assets/setup/azure.png differ
diff --git a/docs/azure-integration/assets/verify/133-img-8.webp b/docs/azure-integration/assets/verify/133-img-8.webp
new file mode 100644
index 0000000..05eab0c
Binary files /dev/null and b/docs/azure-integration/assets/verify/133-img-8.webp differ
diff --git a/docs/azure-integration/assets/verify/img-1.webp b/docs/azure-integration/assets/verify/img-1.webp
new file mode 100644
index 0000000..ec287fa
Binary files /dev/null and b/docs/azure-integration/assets/verify/img-1.webp differ
diff --git a/docs/azure-integration/assets/verify/img-2.webp b/docs/azure-integration/assets/verify/img-2.webp
new file mode 100644
index 0000000..2a79d6c
Binary files /dev/null and b/docs/azure-integration/assets/verify/img-2.webp differ
diff --git a/docs/azure-integration/assets/verify/img-3.webp b/docs/azure-integration/assets/verify/img-3.webp
new file mode 100644
index 0000000..40201ee
Binary files /dev/null and b/docs/azure-integration/assets/verify/img-3.webp differ
diff --git a/docs/azure-integration/assets/verify/img-4.webp b/docs/azure-integration/assets/verify/img-4.webp
new file mode 100644
index 0000000..2d69cd7
Binary files /dev/null and b/docs/azure-integration/assets/verify/img-4.webp differ
diff --git a/docs/azure-integration/assets/verify/img-5.webp b/docs/azure-integration/assets/verify/img-5.webp
new file mode 100644
index 0000000..a1855aa
Binary files /dev/null and b/docs/azure-integration/assets/verify/img-5.webp differ
diff --git a/docs/azure-integration/assets/verify/img-6.webp b/docs/azure-integration/assets/verify/img-6.webp
new file mode 100644
index 0000000..cde48e0
Binary files /dev/null and b/docs/azure-integration/assets/verify/img-6.webp differ
diff --git a/docs/azure-integration/assets/verify/img-7.webp b/docs/azure-integration/assets/verify/img-7.webp
new file mode 100644
index 0000000..b388fc0
Binary files /dev/null and b/docs/azure-integration/assets/verify/img-7.webp differ
diff --git a/docs/azure-integration/assets/verify/img-9.webp b/docs/azure-integration/assets/verify/img-9.webp
new file mode 100644
index 0000000..29dabd4
Binary files /dev/null and b/docs/azure-integration/assets/verify/img-9.webp differ
diff --git a/docs/azure-integration/contact.md b/docs/azure-integration/contact.md
new file mode 100644
index 0000000..4f57f9a
--- /dev/null
+++ b/docs/azure-integration/contact.md
@@ -0,0 +1,21 @@
+# Contact & Support
+
+That wraps up the user guide for the **UnoPim Azure Integration** extension. We hope this documentation helps you set up and use Azure Blob Storage in UnoPim with confidence.
+
+If you have any questions, run into issues, or need help with the extension, the Webkul support team is available to assist.
+
+## Get in Touch
+
+**Email**
+Reach out to us at [support@webkul.com](mailto:support@webkul.com) and our team will get back to you as soon as possible.
+
+**HelpDesk**
+You can also raise a ticket through the [Webkul HelpDesk System](https://webkul.uvdesk.com/en/).
+
+This is useful if you want to:
+
+- report an issue,
+- ask a setup or migration question,
+- track the status of your support request.
+
+We are happy to help whenever needed.
diff --git a/docs/azure-integration/index.md b/docs/azure-integration/index.md
new file mode 100644
index 0000000..bcd6135
--- /dev/null
+++ b/docs/azure-integration/index.md
@@ -0,0 +1,48 @@
+# UnoPim Azure Integration
+
+## What Is the UnoPim Azure Integration?
+
+The **UnoPim Azure Integration** connects your UnoPim product catalog with **Microsoft Azure Blob Storage** — Microsoft's cloud-based storage service designed to handle large volumes of media like images, videos, and documents.
+
+
+
+
+Instead of storing your product images and PDFs on your local server, this integration lets you move everything to the cloud — keeping your assets secure, accessible, and easy to manage no matter how large your catalog grows.
+
+
+
+## What Can It Do?
+
+- Upload product images and PDFs **directly to Azure Blob Storage** from UnoPim.
+- **Migrate existing local media files** to Azure Blob Storage in one go.
+- Optionally **remove local copies** of files after a successful migration to free up server space.
+- **View Azure Blob URLs** directly on the product page — no need to download assets locally to access them.
+- **Export product data** with public image URLs included, in CSV, XLS, and XLSX formats.
+
+
+## Features
+
+| Feature | Description |
+|---|---|
+| **Azure Blob Integration** | Connects your UnoPim catalog directly to Microsoft Azure Blob Storage |
+| **Secure Cloud Storage** | Store and manage all product assets safely in the cloud |
+| **Direct Media Upload** | Upload product images and PDFs to Azure without leaving UnoPim |
+| **Local Media Migration** | Easily migrate existing local files to Azure Blob Storage |
+| **Remove Local Files** | Option to delete local media after successful migration to save server space |
+| **Azure Blob URLs on Product Page** | View and access asset URLs directly from the product page |
+| **Export with Public URLs** | Export product data with image URLs in CSV, XLS, or XLSX format |
+| **UnoPim Compatible** | Fully compatible with the latest version of UnoPim |
+
+
+## Prerequisites
+
+Before you begin, make sure the following are in place:
+
+| Requirement | Detail |
+|---|---|
+| **UnoPim** | Installed and running on your system |
+| **Microsoft Azure Account** | An active Azure account with Blob Storage enabled |
+| **Azure Storage Credentials** | Your Azure **Storage Account Name** and **Access Key** — available from your Azure portal |
+
+
diff --git a/docs/azure-integration/installation.md b/docs/azure-integration/installation.md
new file mode 100644
index 0000000..8803b87
--- /dev/null
+++ b/docs/azure-integration/installation.md
@@ -0,0 +1,74 @@
+# Installation
+
+Follow the steps below to install the UnoPim Azure Blob Integration. Make sure you have terminal access to your server before getting started.
+
+---
+
+## Step 1 — Extract the Extension
+
+Unzip the extension package you downloaded. Inside, you'll find a `packages` folder — merge it into the **root directory** of your UnoPim project. Your project structure should look like this:
+
+```
+/your-unopim-project
+└── packages/
+ └── Webkul/
+ └── AzureBlob/
+```
+
+---
+
+## Step 2 — Register the Service Provider
+
+Open the `bootstrap/providers.php` file and add the following:
+
+```php
+use Webkul\AzureBlob\Providers\AzureBlobServiceProvider;
+
+return [
+ // ...existing providers...
+ AzureBlobServiceProvider::class,
+];
+```
+
+---
+
+## Step 3 — Update Composer Autoload
+
+Open `composer.json` and add the following line under the `autoload > psr-4` section:
+
+```json
+"Webkul\\AzureBlob\\": "packages/Webkul/AzureBlob/src"
+```
+
+---
+
+## Step 4 — Run the Setup Commands
+
+Run the following commands one by one from your project root directory. Wait for each one to complete before running the next.
+
+**Refresh the Composer autoloader**
+```bash
+composer dump-autoload
+```
+
+**Install the Azure Blob package**
+```bash
+php artisan azure-blob-package:install
+```
+
+**Clear the application cache**
+```bash
+php artisan optimize:clear
+```
+
+---
+
+## Verify the Installation
+
+Once all commands have completed successfully, log in to your UnoPim dashboard. If the integration is installed correctly, you'll find the Azure Blob configuration options available in the admin settings.
+
+If something doesn't look right, run `php artisan optimize:clear` again and refresh the page.
+
+---
+
+Next, you'll need to set up your Azure Blob Storage account and retrieve your credentials. Head over to [Azure Blob Storage Setup](./setup.md) to continue.
\ No newline at end of file
diff --git a/docs/azure-integration/move-existing-files.md b/docs/azure-integration/move-existing-files.md
new file mode 100644
index 0000000..2138916
--- /dev/null
+++ b/docs/azure-integration/move-existing-files.md
@@ -0,0 +1,39 @@
+# Migrating Existing Media Files to Azure
+
+If you already have product media stored locally in UnoPim, you don't need to re-upload everything manually. The integration includes a built-in command that automatically moves all your existing local media files to Azure Blob Storage in one go.
+
+---
+
+## Before You Begin
+
+Make sure the following is in place before running the migration command:
+
+- Your **Azure credentials are saved and enabled** in UnoPim (see [Setting Up Azure Credentials in UnoPim](./setup.md)).
+
+> **Important:** If your Azure credential is disabled, the migration command will fail. Double-check that the toggle is turned **on** before proceeding.
+
+---
+
+## Run the Migration Command
+
+Open your terminal, navigate to your UnoPim project root, and run:
+
+```bash
+php artisan azure_integration:move_existing_files
+```
+
+This command will scan all existing media files in your UnoPim local storage and transfer them to the Azure Blob container you configured in your credentials.
+
+---
+
+## What Happens After the Migration
+
+Once the command completes:
+
+- All transferred media files will be stored in your **Azure Blob container**.
+- Product pages in UnoPim will serve media via **Azure Blob URLs** instead of local paths.
+- Any **new media** uploaded going forward will also go directly to Azure — no additional commands needed.
+
+---
+
+> **Tip:** Run this command during off-peak hours if you have a large media library, as migrating a high volume of files may take some time to complete.
diff --git a/docs/azure-integration/remove-local-media-after-migration.md b/docs/azure-integration/remove-local-media-after-migration.md
new file mode 100644
index 0000000..428f05c
--- /dev/null
+++ b/docs/azure-integration/remove-local-media-after-migration.md
@@ -0,0 +1,56 @@
+# Remove Local Media After Migration
+
+After your media files have been successfully moved to **Azure Blob Storage**, you may want to remove the duplicate files from your local server to free up disk space.
+
+UnoPim provides a command for that:
+
+```bash
+php artisan azure_integration:remove_media_files
+```
+
+## What This Command Does
+
+This command removes the local copies of media files that have already been migrated to Azure.
+
+Use it when:
+
+- your migration to Azure has finished successfully,
+- you have confirmed that product media is loading correctly from Azure,
+- you no longer need to keep duplicate files on the local server.
+
+## Before You Run It
+
+Make sure you verify the migration first:
+
+- check that the expected files are present in your Azure Blob container,
+- open a few product pages in UnoPim and confirm the images or PDFs are working,
+- make sure your Azure integration is still enabled and serving files correctly.
+
+> [!CAUTION]
+> Do not remove local files immediately after migration without checking Azure first. Once local duplicates are deleted, the local backup copy is no longer available.
+
+## When to Use This Command
+
+This command is useful if you want to:
+
+- free up storage space on your server,
+- avoid keeping the same media in two places,
+- fully switch your product media storage from local disk to Azure Blob Storage.
+
+## Recommended Usage
+
+Follow this order:
+
+1. Run the migration command to move your media to Azure.
+2. Verify that the files are available and working from Azure.
+3. Run the local cleanup command only after verification is complete.
+
+## Result
+
+After running the command:
+
+- the duplicate local media files are removed,
+- your product assets continue to be served from **Azure Blob Storage**,
+- your local server keeps less unused media data.
+
+If you want to confirm everything before cleanup, continue to [Verify Migration](./verify-migration.md).
diff --git a/docs/azure-integration/setup.md b/docs/azure-integration/setup.md
new file mode 100644
index 0000000..de2551c
--- /dev/null
+++ b/docs/azure-integration/setup.md
@@ -0,0 +1,53 @@
+# Setting Up Azure Credentials in UnoPim
+
+Once the module is installed, the next step is to connect your Azure Blob Storage account to UnoPim by entering your credentials.
+
+---
+
+## Step 1 — Open Azure Integration
+
+Log in to your UnoPim dashboard. You'll notice a new **Azure Integration** option in the left navigation panel. Click on it to expand the menu.
+
+
+
+---
+
+## Step 2 — View the Documentation *(Optional)*
+
+Go to **Azure Integration → Documentation** to access the official Azure Blob Storage documentation directly from UnoPim. This is helpful if you need to look something up while configuring the integration.
+
+---
+
+## Step 3 — Enter Your Credentials
+
+Navigate to **Azure Integration → Credential**. Fill in the following fields with your Azure Blob Storage details:
+
+| Field | What to enter |
+|---|---|
+| **Account Name** | The name of your Azure Storage Account |
+| **Account Key** | The access key for your Azure Storage Account — found in your Azure portal under **Access keys** |
+| **Container Name** | The name of the Blob container where media files will be stored |
+| **Endpoint Suffix** | The endpoint suffix for your Azure storage service (e.g., `core.windows.net`) |
+
+
+
+Once all fields are filled in, click **Save Credential**.
+
+---
+
+## Step 4 — Enable or Disable the Credential
+
+After saving, you'll see a **toggle switch** next to your credential. Use this to enable or disable the Azure integration at any time.
+
+Here's what each state means:
+
+| State | What happens |
+|---|---|
+| **Enabled** | All media files (images and PDFs) uploaded in UnoPim are stored directly in Azure Blob Storage and served via an Azure Blob URL |
+| **Disabled** | Media files are stored in your local server storage instead, and no files are sent to Azure |
+
+> **Note:** If you switch from enabled to disabled, any files already uploaded to Azure Blob Storage will remain there — only new uploads will go to local storage going forward.
+
+---
+
+Once your credential is saved and enabled, your UnoPim instance is fully connected to Azure Blob Storage. Any product media you upload from this point will be stored securely in the cloud.
\ No newline at end of file
diff --git a/docs/azure-integration/sidebar.json b/docs/azure-integration/sidebar.json
new file mode 100644
index 0000000..5de6343
--- /dev/null
+++ b/docs/azure-integration/sidebar.json
@@ -0,0 +1,26 @@
+[
+ {
+ "text": "Azure Integration",
+ "items": [
+ { "text": "Overview", "link": "/azure-integration/" },
+ {"text" : "Installation", "link": "/azure-integration/installation" },
+ {"text" : "Azure Blob Storage Setup", "link": "/azure-integration/setup" }
+ ]
+ },
+
+ {
+ "text" : "Migrating Existing Files to Azure",
+ "items" : [
+ {"text" : "Move Existing Files to Azure", "link": "/azure-integration/move-existing-files" },
+ {"text" : "Remove Local Media after Migration", "link": "/azure-integration/remove-local-media-after-migration" },
+ {"text" : "Verify Migration", "link": "/azure-integration/verify-migration" }
+ ]
+ },
+
+ {
+ "text" : "Support",
+ "items" : [
+ {"text" : "Contact & Support", "link": "/azure-integration/contact" }
+ ]
+ }
+]
diff --git a/docs/azure-integration/verify-migration.md b/docs/azure-integration/verify-migration.md
new file mode 100644
index 0000000..b771460
--- /dev/null
+++ b/docs/azure-integration/verify-migration.md
@@ -0,0 +1,96 @@
+# Creating Products with Azure Media
+
+Once your Azure integration is set up and enabled, any media you attach to a product — images or PDFs — will automatically be uploaded to Azure Blob Storage. Here's how to create a product and attach media to it.
+
+---
+
+## Step 1 — Create a New Product
+
+Go to **Catalog → Products** and click the **Create Product** button.
+
+
+
+Fill in the following fields:
+
+| Field | What to enter |
+|---|---|
+| **Product Type** | Select **Simple** for a standard product, or **Configurable** for a product with variants |
+| **Family** | A family named `Default` is already available — select it or choose another if you've created custom families |
+| **SKU** | Enter a unique identifier for the product |
+
+> **Note:** The SKU must be unique across all products. No two products can share the same SKU.
+
+
+
+Click **Save Product** to continue.
+
+---
+
+## Step 2 — Fill in the Product Details
+
+After saving, you'll be taken to the product edit page. Complete the following fields:
+
+| Field | Notes |
+|---|---|
+| **SKU** | Auto-filled from the previous step |
+| **Name** | Enter the product name manually |
+| **URL Key** | Auto-filled based on the product name |
+| **Short Description** | Enter a brief summary of the product |
+| **Description** | Enter the full product description |
+| **Price** | Enter the product price manually |
+
+
+
+
+---
+
+## Step 3 — Add an Image
+
+In the **Image attribute field**, click to select and upload a product image. Once uploaded, the image will be stored directly in your Azure Blob container and the product page will display its Azure Blob URL.
+
+
+
+---
+
+## Step 4 — Add a PDF File
+
+In the **File attribute field**, select a PDF file to attach to the product.
+
+
+
+> **Note:** Before you can attach a PDF, you need to first create a **File type attribute**. See the section below for how to do this.
+
+---
+
+## Creating a File Type Attribute
+
+If you haven't already created a file attribute, follow these steps:
+
+1. Go to **Catalog → Attributes** and click **Create Attribute**.
+2. Fill in the following:
+ - **Code** — enter a unique code for the attribute (e.g., `product_pdf`)
+ - **Type** — select **File** from the dropdown
+ - **Label / Name** — enter a display name for the attribute (e.g., `Product PDF`)
+3. Click **Save Attribute**.
+
+
+
+
+> **Note:** The File type attribute in UnoPim currently supports **PDF files only**.
+
+Once created, this attribute will appear on the product edit page under the file attribute section, ready for you to attach PDFs to your products.
+
+---
+
+## Step 5 — Save the Product
+
+Once all fields are filled in and your media is attached, click **Save Product** at the top of the page.
+
+
+
+
+After saving, both the image and the PDF file will show an **Azure Blob Storage URL** — confirming they have been successfully uploaded to Azure and are being served from the cloud.
+
+
+
+
\ No newline at end of file
diff --git a/docs/bagisto/assets/Data-Transfer/attribute-family-export.png b/docs/bagisto/assets/Data-Transfer/attribute-family-export.png
new file mode 100644
index 0000000..3695aa0
Binary files /dev/null and b/docs/bagisto/assets/Data-Transfer/attribute-family-export.png differ
diff --git a/docs/bagisto/assets/Data-Transfer/bagisto-attribute-export.png b/docs/bagisto/assets/Data-Transfer/bagisto-attribute-export.png
new file mode 100644
index 0000000..41d91fb
Binary files /dev/null and b/docs/bagisto/assets/Data-Transfer/bagisto-attribute-export.png differ
diff --git a/docs/bagisto/assets/Data-Transfer/bagisto-category-export.png b/docs/bagisto/assets/Data-Transfer/bagisto-category-export.png
new file mode 100644
index 0000000..318d14e
Binary files /dev/null and b/docs/bagisto/assets/Data-Transfer/bagisto-category-export.png differ
diff --git a/docs/bagisto/assets/Data-Transfer/create-export-job.png b/docs/bagisto/assets/Data-Transfer/create-export-job.png
new file mode 100644
index 0000000..7da5676
Binary files /dev/null and b/docs/bagisto/assets/Data-Transfer/create-export-job.png differ
diff --git a/docs/bagisto/assets/Data-Transfer/data-transfer.png b/docs/bagisto/assets/Data-Transfer/data-transfer.png
new file mode 100644
index 0000000..1d1f901
Binary files /dev/null and b/docs/bagisto/assets/Data-Transfer/data-transfer.png differ
diff --git a/docs/bagisto/assets/Data-Transfer/export-fields.png b/docs/bagisto/assets/Data-Transfer/export-fields.png
new file mode 100644
index 0000000..cfff723
Binary files /dev/null and b/docs/bagisto/assets/Data-Transfer/export-fields.png differ
diff --git a/docs/bagisto/assets/Data-Transfer/export-now.png b/docs/bagisto/assets/Data-Transfer/export-now.png
new file mode 100644
index 0000000..808e6a7
Binary files /dev/null and b/docs/bagisto/assets/Data-Transfer/export-now.png differ
diff --git a/docs/bagisto/assets/Data-Transfer/filters.png b/docs/bagisto/assets/Data-Transfer/filters.png
new file mode 100644
index 0000000..5e94a34
Binary files /dev/null and b/docs/bagisto/assets/Data-Transfer/filters.png differ
diff --git a/docs/bagisto/assets/Data-Transfer/monitor-jobs.png b/docs/bagisto/assets/Data-Transfer/monitor-jobs.png
new file mode 100644
index 0000000..4c98a22
Binary files /dev/null and b/docs/bagisto/assets/Data-Transfer/monitor-jobs.png differ
diff --git a/docs/bagisto/assets/Data-Transfer/save-export.png b/docs/bagisto/assets/Data-Transfer/save-export.png
new file mode 100644
index 0000000..e4caf08
Binary files /dev/null and b/docs/bagisto/assets/Data-Transfer/save-export.png differ
diff --git a/docs/bagisto/assets/mapping/additional-fields.png b/docs/bagisto/assets/mapping/additional-fields.png
new file mode 100644
index 0000000..29209da
Binary files /dev/null and b/docs/bagisto/assets/mapping/additional-fields.png differ
diff --git a/docs/bagisto/assets/mapping/category-fields.png b/docs/bagisto/assets/mapping/category-fields.png
new file mode 100644
index 0000000..2ae4dad
Binary files /dev/null and b/docs/bagisto/assets/mapping/category-fields.png differ
diff --git a/docs/bagisto/assets/mapping/category-mapping.png b/docs/bagisto/assets/mapping/category-mapping.png
new file mode 100644
index 0000000..a0a4933
Binary files /dev/null and b/docs/bagisto/assets/mapping/category-mapping.png differ
diff --git a/docs/bagisto/assets/mapping/configurable-attribute.png b/docs/bagisto/assets/mapping/configurable-attribute.png
new file mode 100644
index 0000000..a3b1bfa
Binary files /dev/null and b/docs/bagisto/assets/mapping/configurable-attribute.png differ
diff --git a/docs/bagisto/assets/mapping/fields.png b/docs/bagisto/assets/mapping/fields.png
new file mode 100644
index 0000000..e551d46
Binary files /dev/null and b/docs/bagisto/assets/mapping/fields.png differ
diff --git a/docs/bagisto/assets/mapping/mapping-template.png b/docs/bagisto/assets/mapping/mapping-template.png
new file mode 100644
index 0000000..9915b94
Binary files /dev/null and b/docs/bagisto/assets/mapping/mapping-template.png differ
diff --git a/docs/bagisto/assets/mapping/save.png b/docs/bagisto/assets/mapping/save.png
new file mode 100644
index 0000000..bc78e22
Binary files /dev/null and b/docs/bagisto/assets/mapping/save.png differ
diff --git a/docs/bagisto/assets/overview/intro-banner.png b/docs/bagisto/assets/overview/intro-banner.png
new file mode 100644
index 0000000..0c6abbb
Binary files /dev/null and b/docs/bagisto/assets/overview/intro-banner.png differ
diff --git a/docs/bagisto/assets/setup/bagisto.png b/docs/bagisto/assets/setup/bagisto.png
new file mode 100644
index 0000000..5a0e694
Binary files /dev/null and b/docs/bagisto/assets/setup/bagisto.png differ
diff --git a/docs/bagisto/assets/setup/create-cred.png b/docs/bagisto/assets/setup/create-cred.png
new file mode 100644
index 0000000..983c5ca
Binary files /dev/null and b/docs/bagisto/assets/setup/create-cred.png differ
diff --git a/docs/bagisto/assets/setup/cred.png b/docs/bagisto/assets/setup/cred.png
new file mode 100644
index 0000000..7cdbd3a
Binary files /dev/null and b/docs/bagisto/assets/setup/cred.png differ
diff --git a/docs/bagisto/attribute-mapping-template.md b/docs/bagisto/attribute-mapping-template.md
new file mode 100644
index 0000000..4dbb632
--- /dev/null
+++ b/docs/bagisto/attribute-mapping-template.md
@@ -0,0 +1,32 @@
+# Mapping Templates
+
+Users can create multiple mapping templates in this connector. They can then edit these templates to set specific attribute mappings as needed. For this, they tap on **Attribute Mapping**.
+
+
+
+
+
+## Attribute Template Page
+
+To view and edit an attribute template, users click on the template name. This redirects them to the **Attribute Template** page where they can manage the following:
+
+### Attribute Fields
+
+Map the Bagisto Fields with UnoPim Attributes. Users can also set a **Fixed Value** for the mappings.
+
+
+
+### Additional Attribute Mappings
+
+Users can perform **Additional Attribute Mappings** by writing and selecting the Bagisto attribute code to add and map an additional attribute.
+
+
+
+### Configurable Attribute Mappings
+
+Users can also perform **Configurable Attribute Mappings** by selecting and mapping the Bagisto configurable attributes.
+
+
+
+
+To save the Attribute Template, they tap on the **Save** button and it will be added into the list of templates. Users can further proceed to edit the templates to perform the attribute mapping or delete templates.
diff --git a/docs/bagisto/category-mapping-template.md b/docs/bagisto/category-mapping-template.md
new file mode 100644
index 0000000..b6b82a0
--- /dev/null
+++ b/docs/bagisto/category-mapping-template.md
@@ -0,0 +1,33 @@
+# Category Field Mapping
+
+The Category Field Mapping feature enables users to establish mappings between Bagisto category fields and UnoPim category attributes. This allows for seamless synchronization of category data between the two systems.
+
+## Overview
+
+By selecting **Category Field Mapping**, users can link Bagisto category fields to their corresponding UnoPim category fields. This mapping ensures that category information is properly transferred and synchronized.
+
+
+
+## Mappable Fields
+
+The following Bagisto category fields can be mapped to UnoPim:
+
+- **Name** - Category name
+- **Description** - Category description
+- **Display Mode** - How the category is displayed
+- **Position** - Category ordering position
+- **Visible in Menu** - Menu visibility setting
+- **Slug** - URL-friendly category identifier
+- **Meta Title** - SEO meta title
+- **Meta Keywords** - SEO meta keywords
+- **Meta Description** - SEO meta description
+- **Logo** - Category logo image
+- **Banner** - Category banner image
+
+
+
+## Saving the Mapping
+
+After configuring the category field mappings, users can click the **Save** button to store the mapping configuration. This ensures that the defined mappings are applied during category synchronization between Bagisto and UnoPim.
+
+
diff --git a/docs/bagisto/contact-support.md b/docs/bagisto/contact-support.md
new file mode 100644
index 0000000..b8f9759
--- /dev/null
+++ b/docs/bagisto/contact-support.md
@@ -0,0 +1,21 @@
+# Contact & Support
+
+That wraps up the user guide for the **UnoPim Bagisto Connector** extension. We hope this documentation helps you set up and use the connector in UnoPim with confidence.
+
+If you have any questions, run into issues, or need help with the extension, the Webkul support team is available to assist.
+
+## Get in Touch
+
+**Email**
+Reach out to us at [support@webkul.com](mailto:support@webkul.com) and our team will get back to you as soon as possible.
+
+**HelpDesk**
+You can also raise a ticket through the [Webkul HelpDesk System](https://webkul.uvdesk.com/en/).
+
+This is useful if you want to:
+
+- report an issue,
+- ask a setup or migration question,
+- track the status of your support request.
+
+We are happy to help whenever needed.
diff --git a/docs/bagisto/credentials-setup.md b/docs/bagisto/credentials-setup.md
new file mode 100644
index 0000000..df36bda
--- /dev/null
+++ b/docs/bagisto/credentials-setup.md
@@ -0,0 +1,86 @@
+# Configuration & Credentials Setup
+
+After installing the UnoPim Bagisto Connector, you need to configure it with your Bagisto store credentials. This guide walks you through setting up and managing connector credentials, attribute mappings, and channel/locale configurations.
+
+
+## Accessing the Bagisto Connector
+
+Once the UnoPim Bagisto Connector is installed, it appears in the left sidebar of your UnoPim dashboard.
+
+### Step 1 — Open the Connector
+
+1. Log in to your UnoPim dashboard
+2. Navigate to the left sidebar
+3. Click on **Bagisto** to access the connector
+
+
+
+
+## Setting Up Store Credentials
+
+### Step 1 — Navigate to Credentials
+
+From the Bagisto section, navigate to:
+
+**Bagisto > Credentials > Create Credentials**
+
+
+
+### Step 2 — Enter Bagisto Store Details
+
+Fill in the following information to connect your Bagisto store:
+
+| Field | Description | Example |
+|---|---|---|
+| **Bagisto Shop URL** | The base URL of your Bagisto store | `https://shop.example.com` |
+| **Email Address** | Administrator email for authentication | `admin@example.com` |
+| **Password** | Administrator password for authentication | `••••••••` |
+
+
+
+### Step 3 — Save Credentials
+
+Click the **Save** button to add the credential to UnoPim.
+
+### Multiple Store Support
+
+The UnoPim Bagisto Connector supports managing multiple Bagisto stores. You can:
+- Add credentials for different Bagisto store instances
+- Manage separate product catalogs per store
+- Maintain independent export configurations for each store
+
+Simply repeat the steps above to add additional store credentials as needed.
+
+
+## Managing Credentials
+
+### View All Credentials
+
+Once credentials are saved successfully, they appear in the **Credentials** section. Here you can see:
+- List of all connected Bagisto stores
+- Connection status
+- Quick actions (Edit, Delete)
+
+### Edit Credentials
+
+To modify existing credentials:
+
+1. Click the **Edit** button next to the credential you want to update
+2. You'll be redirected to the credential edit page
+3. Update any of the following:
+ - Bagisto Shop URL
+ - Email Address
+ - Password
+4. Click **Save** to apply changes
+
+### Delete Credentials
+
+To remove a credential:
+
+1. Click the **Delete** button next to the credential
+2. Confirm the deletion
+3. The credential and all associated mappings will be removed
+
+> **Note:** Deleting credentials will stop all product exports to that Bagisto store. Proceed with caution.
+
+---
diff --git a/docs/bagisto/index.md b/docs/bagisto/index.md
index 3ca76cc..4898ee2 100644
--- a/docs/bagisto/index.md
+++ b/docs/bagisto/index.md
@@ -1,3 +1,40 @@
-# Bagisto Extension
+# UnoPim Bagisto Connector
+
+## Overview
+
+The UnoPim Bagisto Connector seamlessly integrates your UnoPim product information management system with your Bagisto e-commerce store. This powerful extension enables you to efficiently manage and synchronize product data, categories, attributes, and media files all from a centralized location.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+## What Can It Do?
+
+The connector works in two directions:
+
+- **Export** — push your product data from UnoPim into Odoo
+- **Import** — pull existing data from Odoo back into UnoPim
+
+
+## Features
+
+### Export
+
+Everything you build in UnoPim can be exported to Odoo:
+
+- **Categories** — export all categories, or only the ones linked to a specific channel. Categories can also be exported directly to **Odoo eCommerce categories**.
+- **Attributes and Options** — export product attributes along with all their selectable options.
+- **Product Models and Products** — export your full product catalog, including product models and individual products.
+- **Product Images** — export multiple images per product.
+- **Targeted Export** — need to export just one product? Use its **SKU**, **internal reference**, or **barcode** to export a specific item without running a full catalog export.
+- **Update Existing Products** — re-run an export job at any time to push the latest changes to products already in Odoo.
+
+### Mapping & Configuration
+
+Before exporting, you can set up mappings to make sure data lands in the right fields in Odoo:
+
+- Map UnoPim categories to their corresponding Odoo categories.
+- Map both standard and custom attributes to Odoo fields.
+- Set **default values** for attribute mappings — useful when a field is required in Odoo but not always filled in UnoPim.
+- Map additional standard attributes as needed.
+
+### Import
+
+You can also bring data from Odoo into UnoPim using the following import job types:
+
+- Categories
+- Attributes
+- Product Models
+- Products
+
+### Advanced Filtering
+
+When running a product export, you can filter exactly what gets exported using:
+
+| Filter | What it does |
+|---|---|
+| **Odoo Credentials** | Select which Odoo store to export to |
+| **Channel** | Export only products from a specific channel |
+| **Locale** | Export product data in a specific language |
+| **Code** | Target a specific export job profile |
+| **Media** | Choose whether to include or exclude product images |
+
+
+## Compatibility
+
+| Requirement | Version |
+|---|---|
+| **Odoo** | Version 19.x |
+| **UnoPim** | Version 1.0.0 or later |
+
+
+> **Please Note:**
+> - The UnoPim Odoo Connector is compatible with **Odoo version 17, 18, and 19**.
+> - Currently, only **select-type attributes** from UnoPim are supported for export to Odoo as variation attributes.
-Placeholder landing page. Real docs are pulled from [`unopim/unopim-odoo-erp`](https://github.com/unopim/unopim-odoo-erp) at build time.
diff --git a/docs/odoo-erp/installation.md b/docs/odoo-erp/installation.md
new file mode 100644
index 0000000..76f4a03
--- /dev/null
+++ b/docs/odoo-erp/installation.md
@@ -0,0 +1,71 @@
+# Installation
+
+Follow the steps below to install the UnoPim Odoo Connector on your UnoPim instance. Make sure you have terminal access to your server before getting started.
+
+
+## Step 1 — Add the Package Files
+
+Unzip the extension ZIP file you downloaded. Inside, you'll find a `packages` folder — merge this into the **root directory** of your UnoPim project.
+
+
+## Step 2 — Register the Service Provider
+
+Open the `bootstrap/providers.php` file and add the following:
+
+```php
+use Webkul\Odoo\Providers\OdooServiceProvider;
+
+return [
+ // ...existing providers...
+ OdooServiceProvider::class,
+];
+```
+
+
+## Step 3 — Update Composer Autoload
+
+Open `composer.json` and add the following line under the `autoload > psr-4` section:
+
+```json
+"Webkul\\Odoo\\": "packages/Webkul/Odoo/src"
+```
+
+
+## Step 4 — Run the Setup Commands
+
+Run the following commands one by one in your terminal. Wait for each one to finish before running the next.
+
+**Dump Composer autoload**
+```bash
+composer dump-autoload
+```
+
+**Run database migrations**
+```bash
+php artisan migrate
+```
+
+**Publish the connector assets**
+```bash
+php artisan vendor:publish --tag=unopim-odoo-connector
+```
+
+**Install the Odoo XML-RPC client package**
+```bash
+composer require alazzi-az/odoo-xmlrpc
+```
+
+**Clear the application cache**
+```bash
+php artisan optimize:clear
+```
+
+
+## Verify the Installation
+
+Once all commands have run successfully, log in to your UnoPim dashboard. You should see an **Odoo icon** in the left sidebar — this confirms the connector has been installed correctly.
+
+
+
+If the icon doesn't appear, try running `php artisan optimize:clear` again and refresh the page.
+
diff --git a/docs/odoo-erp/odoo-setup.md b/docs/odoo-erp/odoo-setup.md
new file mode 100644
index 0000000..39fc91b
--- /dev/null
+++ b/docs/odoo-erp/odoo-setup.md
@@ -0,0 +1,44 @@
+# Setting Up Odoo Before You Begin
+
+Before you start importing or exporting data between UnoPim and Odoo, you need to make sure your Odoo instance has the right apps installed. Without these, the connector won't be able to communicate with Odoo properly.
+
+This is a one-time setup step — once done, you won't need to repeat it.
+
+
+## Step 1 — Open the Odoo Dashboard
+
+Log in to your Odoo account. Once you're on the dashboard, click the **grid icon** (⊞) in the **top-left corner** of the screen. This opens the main app menu where all available Odoo apps are listed.
+
+
+
+
+## Step 2 — Go to Apps
+
+Click on **Apps** from the menu. This takes you to the Odoo App Store, where you can browse and install modules for your Odoo instance.
+
+
+
+Use the search bar to find each app you need.
+
+
+## Step 3 — Install the Required Apps
+
+The following Odoo apps **must be installed** for the UnoPim Odoo Connector to work correctly:
+
+
+
+| App | Why it's needed |
+|---|---|
+| **Sales** | Required for managing products and pricelists in Odoo |
+| **eCommerce** | Enables product publishing and eCommerce category management |
+| **Inventory** | Handles stock and product variant management |
+| **Website** | Required for eCommerce functionality to work in Odoo |
+
+
+
+For each app, click **Install** if it isn't already installed. Wait for each installation to complete before moving on to the next one.
+
+
+> **Tip:** If an app is already installed, it will show an **Installed** badge — you can skip it and move on to the next one.
+
+Once all four apps are installed, your Odoo store is ready to connect with UnoPim. Head over to [Installation](./installation.md) to continue.
\ No newline at end of file
diff --git a/docs/odoo-erp/product-import.md b/docs/odoo-erp/product-import.md
new file mode 100644
index 0000000..75b70ee
--- /dev/null
+++ b/docs/odoo-erp/product-import.md
@@ -0,0 +1,105 @@
+# UnoPim - Odoo Import Product
+
+Importing Products from Odoo
+
+
+## Overview
+
+This import job will import all the products from Odoo to UnoPim.
+
+
+## Prerequisites
+
+Before importing products from Odoo, ensure that you have configured your Odoo credentials in UnoPim. It is also recommended to first import attributes and categories from Odoo.
+
+
+## Step 1: Go to Data Transfer
+
+Navigate to the **Data Transfer** section from the main menu in UnoPim.
+
+
+
+
+## Step 2: Go to Imports
+
+Click on **Imports** to view the available import options.
+
+
+
+
+## Step 3: Create Import
+
+Click on **Create Import** to create a new import profile.
+
+
+
+
+## Step 4: Enter Code and Select Type
+
+In the **General** section, configure the following:
+
+### Code
+
+Enter a unique code for your import profile. This code will help you identify the import profile.
+
+**Example:** odoo_product_import_001
+
+### Type
+
+In the **Type** field, select **Odoo Product** from the dropdown menu.
+
+
+
+
+## Step 5: Configure Settings
+
+In the **Settings** section, configure the following required fields:
+
+### Odoo Credentials
+
+Click on the **Odoo credentials** dropdown and select the specific Odoo credentials or connection you want to import from. This is a required field.
+
+### Channel
+
+Click on the **Channel** dropdown and select the appropriate channel or store view from your Odoo setup. This is a required field.
+
+### Locale
+
+Click on the **Locale** dropdown and select the language or regional settings for importing product data. This is a required field.
+
+### Family
+Click on the Family dropdown and select the product family you want to import products into. This is a required field.
+
+### With Media
+
+Toggle the With Media option to include or exclude product images and other media assets in the import.
+
+#### ON - Import products with all associated images and media files
+#### OFF - Import products without media files
+
+
+
+
+
+
+
+## Step 6: Save Import
+
+Click the **Save Import** button to save your import profile configuration.
+
+
+
+
+## Step 7: Import Now
+
+Once the import profile is saved, click the **Import Now** button to start the import process and import all Odoo products to UnoPim.
+
+
+
+
+## Step 8: Monitor Progress
+
+In the execution process, you can check the progress of the import job and view any errors in the log.
+
+
+
diff --git a/docs/odoo-erp/product-model-import.md b/docs/odoo-erp/product-model-import.md
new file mode 100644
index 0000000..8e18ed4
--- /dev/null
+++ b/docs/odoo-erp/product-model-import.md
@@ -0,0 +1,112 @@
+# UnoPim - Odoo Import Product Model
+
+Importing Product Models from Odoo
+
+
+## Overview
+
+This import job will import all the product models from Odoo to UnoPim.
+
+
+## Prerequisites
+
+Before importing product models from Odoo, ensure that you have configured your Odoo credentials in UnoPim.
+
+
+## Step 1: Go to Data Transfer
+
+Navigate to the **Data Transfer** section from the main menu in UnoPim.
+
+
+
+
+## Step 2: Go to Imports
+
+Click on **Imports** to view the available import options.
+
+
+
+
+## Step 3: Create Import
+
+Click on **Create Import** to create a new import profile.
+
+
+
+
+## Step 4: Enter Code and Select Type
+
+In the **General** section, configure the following:
+
+### Code
+
+Enter a unique code for your import profile. This code will help you identify the import profile.
+
+**Example:** odoo_product_model_import
+
+### Type
+
+In the **Type** field, select **Odoo Product Model** from the dropdown menu.
+
+
+
+## Step 5: Configure Settings
+
+In the **Settings** section, select the appropriate channel, locale, and currency for importing Odoo products to UnoPim.
+
+### Odoo Credentials
+
+Click on the **Odoo credentials** dropdown and select the specific Odoo credentials or connection you want to import from. This is a required field.
+
+### Channel
+
+Click on the **Channel** dropdown and select the appropriate channel or store view from your Odoo setup. This is a required field.
+
+### Locale
+
+Click on the **Locale** dropdown and select the language or regional settings for imported product data (e.g., English, Spanish). This is a required field.
+
+### Family
+
+Click on the **Family** dropdown and select the product family where you want to import product models. This is a required field.
+
+### With Media
+
+Toggle the **With Media** option to choose whether to import product models along with their images and media files.
+
+- **ON** - Import product models with all associated images and media files
+- **OFF** - Import product models without media files
+
+
+
+
+## Step 6: Save Import
+
+Click the **Save Import** button to save your import profile configuration.
+
+
+
+
+## Step 7: Import Now
+
+Once the import profile is saved, click the **Import Now** button to execute the import process and import all product models from Odoo to UnoPim.
+
+
+
+
+## Step 8: Monitor Progress
+
+In the execution process, you can check the progress of the import job and view any errors in the log.
+
+
+
+
+## Benefits of Using Filters
+
+These filters give you fine-grained control over your imports, making it easier to:
+
+- Manage localized catalogs
+- Handle multi-channel data
+- Organize media-rich content
+- Avoid overloading your UnoPim workspace
+
diff --git a/docs/odoo-erp/setup-credentials.md b/docs/odoo-erp/setup-credentials.md
new file mode 100644
index 0000000..8c858ab
--- /dev/null
+++ b/docs/odoo-erp/setup-credentials.md
@@ -0,0 +1,66 @@
+# Setting Up Odoo Credentials
+
+Once the connector is installed, the next step is to connect your Odoo store to UnoPim. This is done by entering your Odoo server details inside the UnoPim dashboard.
+
+
+## Step 1 — Open the Credentials Page
+
+Log in to your UnoPim dashboard and navigate to **Odoo → Credentials → Create Credentials**.
+
+
+
+
+## Step 2 — Enter Your Odoo Server Details
+
+Fill in the following fields to establish the connection:
+
+| Field | What to enter |
+|---|---|
+| **URL** | The full URL of your Odoo server (e.g., `https://mystore.odoo.com`) |
+| **Database Name** | The name of your Odoo database |
+| **Login Username** | Your Odoo admin username |
+| **Login Password** | Your Odoo admin password |
+
+
+
+> **Note:** Each set of credentials must have a unique database name. If you enter a database name that's already in use, UnoPim will show an error and the credentials won't be saved.
+
+
+## Step 3 — Configure Export Settings
+
+After entering the server details, you'll need to define how products should be exported. Fill in the following settings:
+
+### Odoo Allowed Company ID
+Select the **Company ID** for which you want to export products. If your Odoo instance has multiple companies and you want to export to all of them, leave this field blank.
+
+### Default Locale
+Choose the locale that matches your Odoo store's language. For example:
+- `English (United States)`
+- `Spanish (Brazil)`
+
+### Currency
+Select the default currency used in your Odoo store. For example:
+- `US Dollar`
+- `Euro`
+- `British Pound`
+
+### Default Product Identifier
+This tells the connector how exported products will be identified in Odoo. Choose one of the following:
+
+| Option | When to use |
+|---|---|
+| **Internal Reference** (`default_code`) | Use this if your products are identified by an internal reference code in Odoo |
+| **Barcode** (`barcode`) | Use this if your products are identified by their barcode |
+
+
+### Category Export as eCommerce Categories
+Toggle this **on** if you want your UnoPim categories to be exported directly as **Odoo eCommerce categories** rather than standard internal categories.
+
+
+
+## Step 4 — Save Your Credentials
+
+Once all fields are filled in, click **Save**. Your Odoo store is now connected to UnoPim and ready for export and import jobs.
+
+
+> **Tip:** You can connect more than one Odoo store by repeating these steps and creating a separate set of credentials for each store.
\ No newline at end of file
diff --git a/docs/odoo-erp/sidebar.json b/docs/odoo-erp/sidebar.json
index bc20f55..3b8b86b 100644
--- a/docs/odoo-erp/sidebar.json
+++ b/docs/odoo-erp/sidebar.json
@@ -2,7 +2,46 @@
{
"text": "Odoo ERP",
"items": [
- { "text": "Overview", "link": "/odoo-erp/" }
+ { "text": "Overview", "link": "/odoo-erp/" },
+ {"text" : "Odoo Setup", "link": "/odoo-erp/odoo-setup" },
+ {"text" : "Installation", "link": "/odoo-erp/installation" },
+ {"text" : "Setup Odoo Credentials in Unopim", "link": "/odoo-erp/setup-credentials" }
+ ]
+ },
+
+ {
+ "text": "Configuration",
+ "items": [
+ {"text" : "Attribute Mapping", "link": "/odoo-erp/attribute-mapping" },
+ {"text" : "Additional Mapping", "link" : "/odoo-erp/additional-mapping" },
+ {"text" : "Category Mapping", "link" : "/odoo-erp/category-mapping" }
+
+]
+ },
+
+ {
+ "text":"Export Jobs",
+ "items":[
+ {"text" : "Export Attributes", "link": "/odoo-erp/export-attributes" },
+ {"text" : "Export Categories", "link": "/odoo-erp/export-categories" },
+ {"text" : "Export Products", "link": "/odoo-erp/export-products" }
+ ]
+ },
+
+ {
+ "text":"Import Jobs",
+ "items":[
+ {"text" : "Attribute import", "link": "/odoo-erp/attribute-import" },
+ {"text" : "Category Import", "link": "/odoo-erp/category-import" },
+ {"text" : "Product Import", "link": "/odoo-erp/product-import" },
+ {"text" : "Product Model", "link": "/odoo-erp/product-model-import" }
+ ]
+ },
+
+ {
+ "text":"Support",
+ "items":[
+ {"text" : "Contact & Support", "link": "/odoo-erp/contact" }
]
}
]
diff --git a/docs/shopify/index.md b/docs/shopify/index.md
index a055a16..ea833e5 100644
--- a/docs/shopify/index.md
+++ b/docs/shopify/index.md
@@ -52,9 +52,12 @@ Shopify supports **metafields** — custom data fields that go beyond standard p
- Rating
- URL
- JSON
-- Unit Weight
-- Unit Volume
-- Unit Dimension
+- Weight
+- Volume
+- Dimension
+- boolean
+- Date
+- Number
These are exported without needing any additional mapping setup.
diff --git a/docs/woocommerce/api-credentials.md b/docs/woocommerce/api-credentials.md
new file mode 100644
index 0000000..b31224d
--- /dev/null
+++ b/docs/woocommerce/api-credentials.md
@@ -0,0 +1,64 @@
+# Generating WooCommerce API Credentials
+
+Before connecting WooCommerce to UnoPim, you need to generate an API key from your WooCommerce store. This key allows UnoPim to securely communicate with WooCommerce on your behalf.
+
+The whole process takes just a couple of minutes. Follow the steps below.
+
+
+## Step 1 Open WooCommerce Settings
+
+Log in to your WordPress admin panel and go to **WooCommerce → Settings**.
+
+
+
+
+## Step 2 Go to the REST API Section
+
+From the Settings page, click the **Advanced** tab in the top navigation bar. Then click on **REST API** from the sub-menu.
+
+
+
+This page lists all existing API keys for your store. You'll create a new one here.
+
+
+## Step 3 Add a New Key
+
+Click the **Add Key / Create API Key** button.
+
+Fill in the following details on the form that appears:
+
+| Field | What to enter |
+|---|---|
+| **Description** | A label to identify this key e.g., `UnoPim Integration` |
+| **User** | Select the WordPress user this key belongs to Admin is selected by default |
+| **Permissions** | Select **Read/Write** |
+
+
+
+> **Important:** UnoPim requires **Read/Write** permission to export and import data between the two platforms. Selecting **Read Only** will cause exports to fail.
+
+---
+
+## Step 4 Generate the API Key
+
+Once all fields are filled in, click **Generate API Key**.
+
+WooCommerce will generate and display three items:
+
+| Item | What it's used for |
+|---|---|
+| **Consumer Key** | Used to authenticate UnoPim with your WooCommerce store |
+| **Consumer Secret** | Used alongside the Consumer Key for secure authentication |
+| **Barcode** | A visual reference for the key not used in UnoPim |
+
+> **Important:** This is the **only time** WooCommerce will display the Consumer Secret in full. Copy both the **Consumer Key** and **Consumer Secret** immediately and store them somewhere safe. If you lose the secret, you'll need to delete this key and generate a new one.
+
+---
+
+## What You Now Have
+
+You'll need the following two values to set up credentials in UnoPim:
+
+- **Consumer Key**
+- **Consumer Secret**
+
diff --git a/docs/woocommerce/assets/api-key/generate-key.png b/docs/woocommerce/assets/api-key/generate-key.png
new file mode 100644
index 0000000..43ae2e7
Binary files /dev/null and b/docs/woocommerce/assets/api-key/generate-key.png differ
diff --git a/docs/woocommerce/assets/api-key/rest-api.png b/docs/woocommerce/assets/api-key/rest-api.png
new file mode 100644
index 0000000..6bff37d
Binary files /dev/null and b/docs/woocommerce/assets/api-key/rest-api.png differ
diff --git a/docs/woocommerce/assets/api-key/settings.png b/docs/woocommerce/assets/api-key/settings.png
new file mode 100644
index 0000000..dbb76ab
Binary files /dev/null and b/docs/woocommerce/assets/api-key/settings.png differ
diff --git a/docs/woocommerce/assets/api-key/woo-cred.png b/docs/woocommerce/assets/api-key/woo-cred.png
new file mode 100644
index 0000000..14ced21
Binary files /dev/null and b/docs/woocommerce/assets/api-key/woo-cred.png differ
diff --git a/docs/woocommerce/assets/api-key/woocommerce-settings.png b/docs/woocommerce/assets/api-key/woocommerce-settings.png
new file mode 100644
index 0000000..18f9241
Binary files /dev/null and b/docs/woocommerce/assets/api-key/woocommerce-settings.png differ
diff --git a/docs/woocommerce/assets/api-key/woocommerce.png b/docs/woocommerce/assets/api-key/woocommerce.png
new file mode 100644
index 0000000..2431efc
Binary files /dev/null and b/docs/woocommerce/assets/api-key/woocommerce.png differ
diff --git a/docs/woocommerce/assets/jobs/Data-trnsfer.png b/docs/woocommerce/assets/jobs/Data-trnsfer.png
new file mode 100644
index 0000000..16d03a7
Binary files /dev/null and b/docs/woocommerce/assets/jobs/Data-trnsfer.png differ
diff --git a/docs/woocommerce/assets/jobs/attribute-complete.png b/docs/woocommerce/assets/jobs/attribute-complete.png
new file mode 100644
index 0000000..8ce75d9
Binary files /dev/null and b/docs/woocommerce/assets/jobs/attribute-complete.png differ
diff --git a/docs/woocommerce/assets/jobs/attribute-export.png b/docs/woocommerce/assets/jobs/attribute-export.png
new file mode 100644
index 0000000..b815c24
Binary files /dev/null and b/docs/woocommerce/assets/jobs/attribute-export.png differ
diff --git a/docs/woocommerce/assets/jobs/attribute-fields.png b/docs/woocommerce/assets/jobs/attribute-fields.png
new file mode 100644
index 0000000..3327d96
Binary files /dev/null and b/docs/woocommerce/assets/jobs/attribute-fields.png differ
diff --git a/docs/woocommerce/assets/jobs/attribute-import-complete.png b/docs/woocommerce/assets/jobs/attribute-import-complete.png
new file mode 100644
index 0000000..e83384c
Binary files /dev/null and b/docs/woocommerce/assets/jobs/attribute-import-complete.png differ
diff --git a/docs/woocommerce/assets/jobs/attribute-import.png b/docs/woocommerce/assets/jobs/attribute-import.png
new file mode 100644
index 0000000..5eda6d7
Binary files /dev/null and b/docs/woocommerce/assets/jobs/attribute-import.png differ
diff --git a/docs/woocommerce/assets/jobs/attribute-settings.png b/docs/woocommerce/assets/jobs/attribute-settings.png
new file mode 100644
index 0000000..33f8a6d
Binary files /dev/null and b/docs/woocommerce/assets/jobs/attribute-settings.png differ
diff --git a/docs/woocommerce/assets/jobs/category-complete.png b/docs/woocommerce/assets/jobs/category-complete.png
new file mode 100644
index 0000000..96b8b3a
Binary files /dev/null and b/docs/woocommerce/assets/jobs/category-complete.png differ
diff --git a/docs/woocommerce/assets/jobs/category-export.png b/docs/woocommerce/assets/jobs/category-export.png
new file mode 100644
index 0000000..3570c53
Binary files /dev/null and b/docs/woocommerce/assets/jobs/category-export.png differ
diff --git a/docs/woocommerce/assets/jobs/category-fields.png b/docs/woocommerce/assets/jobs/category-fields.png
new file mode 100644
index 0000000..f6f067d
Binary files /dev/null and b/docs/woocommerce/assets/jobs/category-fields.png differ
diff --git a/docs/woocommerce/assets/jobs/category-filter.png b/docs/woocommerce/assets/jobs/category-filter.png
new file mode 100644
index 0000000..710dc07
Binary files /dev/null and b/docs/woocommerce/assets/jobs/category-filter.png differ
diff --git a/docs/woocommerce/assets/jobs/category-import-complete.png b/docs/woocommerce/assets/jobs/category-import-complete.png
new file mode 100644
index 0000000..4d79b75
Binary files /dev/null and b/docs/woocommerce/assets/jobs/category-import-complete.png differ
diff --git a/docs/woocommerce/assets/jobs/category-import.png b/docs/woocommerce/assets/jobs/category-import.png
new file mode 100644
index 0000000..a506189
Binary files /dev/null and b/docs/woocommerce/assets/jobs/category-import.png differ
diff --git a/docs/woocommerce/assets/jobs/create-export.png b/docs/woocommerce/assets/jobs/create-export.png
new file mode 100644
index 0000000..28a0867
Binary files /dev/null and b/docs/woocommerce/assets/jobs/create-export.png differ
diff --git a/docs/woocommerce/assets/jobs/create-import.png b/docs/woocommerce/assets/jobs/create-import.png
new file mode 100644
index 0000000..a7e770a
Binary files /dev/null and b/docs/woocommerce/assets/jobs/create-import.png differ
diff --git a/docs/woocommerce/assets/jobs/data-transfer-import.png b/docs/woocommerce/assets/jobs/data-transfer-import.png
new file mode 100644
index 0000000..988a8c7
Binary files /dev/null and b/docs/woocommerce/assets/jobs/data-transfer-import.png differ
diff --git a/docs/woocommerce/assets/jobs/product-complete.png b/docs/woocommerce/assets/jobs/product-complete.png
new file mode 100644
index 0000000..1093366
Binary files /dev/null and b/docs/woocommerce/assets/jobs/product-complete.png differ
diff --git a/docs/woocommerce/assets/jobs/product-export.png b/docs/woocommerce/assets/jobs/product-export.png
new file mode 100644
index 0000000..00cc6ff
Binary files /dev/null and b/docs/woocommerce/assets/jobs/product-export.png differ
diff --git a/docs/woocommerce/assets/jobs/product-fields-import.png b/docs/woocommerce/assets/jobs/product-fields-import.png
new file mode 100644
index 0000000..7d28b43
Binary files /dev/null and b/docs/woocommerce/assets/jobs/product-fields-import.png differ
diff --git a/docs/woocommerce/assets/jobs/product-fields.png b/docs/woocommerce/assets/jobs/product-fields.png
new file mode 100644
index 0000000..3846389
Binary files /dev/null and b/docs/woocommerce/assets/jobs/product-fields.png differ
diff --git a/docs/woocommerce/assets/jobs/product-import-complete.png b/docs/woocommerce/assets/jobs/product-import-complete.png
new file mode 100644
index 0000000..239d025
Binary files /dev/null and b/docs/woocommerce/assets/jobs/product-import-complete.png differ
diff --git a/docs/woocommerce/assets/jobs/product-import.png b/docs/woocommerce/assets/jobs/product-import.png
new file mode 100644
index 0000000..77ad958
Binary files /dev/null and b/docs/woocommerce/assets/jobs/product-import.png differ
diff --git a/docs/woocommerce/assets/mapping/additional-attribute.png b/docs/woocommerce/assets/mapping/additional-attribute.png
new file mode 100644
index 0000000..b26af77
Binary files /dev/null and b/docs/woocommerce/assets/mapping/additional-attribute.png differ
diff --git a/docs/woocommerce/assets/mapping/attribute-mapping.png b/docs/woocommerce/assets/mapping/attribute-mapping.png
new file mode 100644
index 0000000..52eeb30
Binary files /dev/null and b/docs/woocommerce/assets/mapping/attribute-mapping.png differ
diff --git a/docs/woocommerce/assets/mapping/fields.png b/docs/woocommerce/assets/mapping/fields.png
new file mode 100644
index 0000000..24f53b7
Binary files /dev/null and b/docs/woocommerce/assets/mapping/fields.png differ
diff --git a/docs/woocommerce/assets/mapping/other-mapping.png b/docs/woocommerce/assets/mapping/other-mapping.png
new file mode 100644
index 0000000..90e9c04
Binary files /dev/null and b/docs/woocommerce/assets/mapping/other-mapping.png differ
diff --git a/docs/woocommerce/assets/mapping/quick-export.png b/docs/woocommerce/assets/mapping/quick-export.png
new file mode 100644
index 0000000..2409bb4
Binary files /dev/null and b/docs/woocommerce/assets/mapping/quick-export.png differ
diff --git a/docs/woocommerce/assets/overview/hero-banner.png b/docs/woocommerce/assets/overview/hero-banner.png
new file mode 100644
index 0000000..e202147
Binary files /dev/null and b/docs/woocommerce/assets/overview/hero-banner.png differ
diff --git a/docs/woocommerce/attribute-export.md b/docs/woocommerce/attribute-export.md
new file mode 100644
index 0000000..1b66cec
--- /dev/null
+++ b/docs/woocommerce/attribute-export.md
@@ -0,0 +1,45 @@
+# Attribute Export
+
+The UnoPim WooCommerce Connector allows users to export attribute data from UnoPim to WooCommerce through dedicated export jobs.
+
+## Open the Export Jobs Section
+
+To create an attribute export job, go to:
+
+`Data Transfer > Exports`
+
+
+
+From the Exports page, click **Create Export** in the top-right corner.
+
+
+
+## Create an Attribute Export Job
+
+While creating the export job, the user needs to:
+
+- Enter the **Export Job Code**.
+- Select **WooCommerce Attribute Export** as the export job type.
+
+
+
+## Attribute Export Filters
+
+After selecting the attribute export job type, configure the following filters as needed:
+
+- **WooCommerce Store URL**: Select the required WooCommerce store credentials.
+- **Channel**: Select the channel to use for the export.
+- **Locale**: Select the required locale.
+- **Additional Attribute for Mapping**: Select the additional attribute that should be used for mapping during export.
+
+
+
+## Save and Run the Export Job
+
+After completing the required fields, click **Save Export** to create and save the export job.
+
+Once the job is run, the export progress can be tracked from the **Job Tracker**.
+
+
+
+After the export completes successfully, the selected attributes will be available in the connected WooCommerce store.
diff --git a/docs/woocommerce/attribute-import.md b/docs/woocommerce/attribute-import.md
new file mode 100644
index 0000000..666f70f
--- /dev/null
+++ b/docs/woocommerce/attribute-import.md
@@ -0,0 +1,39 @@
+# Attribute Import
+
+The UnoPim WooCommerce Connector allows users to import WooCommerce attributes into UnoPim by creating an import profile.
+
+## Open the Import Section
+
+To create an import job, go to:
+
+`Import > Create Import Profile`
+
+
+
+From there, click **Create Import** to open the import setup form.
+
+
+
+## Create an Attribute Import Job
+
+While creating the import job, the user needs to:
+
+- Enter the **Code**.
+- Select **WooCommerce Attribute Import** as the import type.
+
+
+
+## Attribute Import Settings
+
+Under **Settings**, configure the following:
+
+- **WooCommerce Store URL**: Select the required WooCommerce store credentials.
+- **Locale**: Select the locale to be used during import.
+
+
+
+After entering the required values, click **Save Import** to save the import profile.
+
+Once the job is executed, the imported attributes will be available in UnoPim.
+
+
diff --git a/docs/woocommerce/attribute-mapping.md b/docs/woocommerce/attribute-mapping.md
new file mode 100644
index 0000000..b43dac2
--- /dev/null
+++ b/docs/woocommerce/attribute-mapping.md
@@ -0,0 +1,66 @@
+# Attribute Mapping in UnoPim
+
+Attribute mapping allows users to connect WooCommerce product fields with the correct UnoPim attributes. This ensures that product data is transferred into the right fields during synchronization.
+
+
+
+While setting up the mapping, users need to select the UnoPim attribute that matches each WooCommerce product information field.
+
+## Default WooCommerce Fields Available for Mapping
+
+By default, the following WooCommerce fields can be mapped with UnoPim attributes:
+
+- **SKU `[sku]`**: Unique identifier for each product, used for inventory and tracking.
+- **Slug `[slug]`**: URL-friendly version of the product name used in permalinks.
+- **Product Name `[name]`**: The title of the product displayed to customers.
+- **Price `[regular_price]`**: Standard selling price of the product.
+- **Description `[description]`**: Full product description shown on the product page.
+- **Short Description `[short_description]`**: Brief product summary typically shown near the top of the product page.
+- **Weight `[weight]`**: Physical weight of the product, commonly used for shipping calculations.
+- **Length `[length]`**: Product length dimension used for shipping or display.
+- **Width `[width]`**: Product width dimension used for packaging or logistics.
+- **Height `[height]`**: Product height dimension used in physical handling.
+- **Quantity `[stock_quantity]`**: Available stock quantity for the product.
+- **Is Featured? `[featured]`**: Indicates whether the product is marked as featured in the store.
+- **Purchase Notes `[purchase_note]`**: Message sent to customers after purchase, usually for instructions or follow-up information.
+- **Reviews Allowed `[reviews_allowed]`**: Defines whether customers can leave reviews for the product.
+- **Backorders Allowed `[backorders_allowed]`**: Defines whether the product can be ordered when it is out of stock.
+
+
+
+> **Note:** For the WooCommerce **Quantity `[stock_quantity]`** field, map a UnoPim **text-type attribute**.
+
+## Add Additional Meta Keys
+
+The connector also allows users to add custom WooCommerce fields through **Additional Meta Keys**.
+
+
+
+In this section, users can enter a WooCommerce field code and press **Enter** to add it as a new mapping field. After that, they can assign the appropriate UnoPim attribute to the newly added field.
+
+## Other Mappings
+
+Under **Other Mappings**, the admin can configure the following options:
+
+- **Non-Select attribute sent as Select attribute (recommended)**: Use this option when a WooCommerce field should be handled as a select-type value during synchronization.
+- **Attribute to be used as a custom attribute**: Use this option to define which UnoPim attributes should be treated as custom attributes in WooCommerce. Variant attributes must also be added here.
+- **Attribute to be used as Images**: Use this option to select the UnoPim attribute that should be used for product images.
+
+
+
+This section is also used to add additional keywords required for mapping behavior.
+
+## Quick Export Settings
+
+Under **Quick Export Settings**, the admin needs to configure the following default values:
+
+- Select the default **channel** for quick export.
+- Select the default **locale**.
+- Select the default **currency**.
+- Enable **Auto Sync Products** if products should be synced automatically from UnoPim to WooCommerce when they are created, updated, or deleted.
+
+For **Quick Export**, enabling auto sync is not required. The admin only needs to assign the default values for **channel**, **locale**, and **currency** in the attribute mapping, and then enable **Quick Export** in the credential settings.
+
+
+
+After completing the mapping configuration, click **Save** to store the settings.
diff --git a/docs/woocommerce/category-export.md b/docs/woocommerce/category-export.md
new file mode 100644
index 0000000..b06ea56
--- /dev/null
+++ b/docs/woocommerce/category-export.md
@@ -0,0 +1,46 @@
+# Category Export
+
+The UnoPim WooCommerce Connector allows users to export category data from UnoPim to WooCommerce through dedicated export jobs.
+
+## Open the Export Jobs Section
+
+To create a category export job, go to:
+
+`Data Transfer > Exports`
+
+
+
+From the Exports page, click **Create Export** in the top-right corner.
+
+
+
+## Create a Category Export Job
+
+While creating the export job, the user needs to:
+
+- Enter the **Export Job Code**.
+- Select **WooCommerce Category Export** as the export job type.
+
+
+
+## Category Export Filters
+
+After selecting the category export job type, configure the available filters as required for your store and catalog data.
+
+Typically, the user needs to select:
+
+- **WooCommerce Store URL**: Select the required WooCommerce store credentials.
+- **Channel**: Select the channel to use for the export.
+- **Locale**: Select the required locale.
+
+
+
+## Save and Run the Export Job
+
+After filling in the required details, click **Save Export** to create and save the export job.
+
+Once the job is run, the export progress can be viewed from the **Job Tracker**.
+
+
+
+After the export completes successfully, the categories will be available in the connected WooCommerce store.
diff --git a/docs/woocommerce/category-import.md b/docs/woocommerce/category-import.md
new file mode 100644
index 0000000..f6af67b
--- /dev/null
+++ b/docs/woocommerce/category-import.md
@@ -0,0 +1,39 @@
+# Category Import
+
+The UnoPim WooCommerce Connector allows users to import WooCommerce categories into UnoPim by creating an import profile.
+
+## Open the Import Section
+
+To create an import job, go to:
+
+`Import > Create Import Profile`
+
+
+
+From there, click **Create Import** to open the import setup form.
+
+
+
+## Create a Category Import Job
+
+While creating the import job, the user needs to:
+
+- Enter the **Code**.
+- Select **WooCommerce Category Import** as the import type.
+
+
+
+## Category Import Settings
+
+Under **Settings**, configure the following:
+
+- **WooCommerce Store URL**: Select the required WooCommerce store credentials.
+- **Locale**: Select the locale to be used during import.
+
+
+
+After entering the required values, click **Save Import** to save the import profile.
+
+Once the job is executed, the imported categories will be available in UnoPim.
+
+
diff --git a/docs/woocommerce/contact-support.md b/docs/woocommerce/contact-support.md
new file mode 100644
index 0000000..78677d3
--- /dev/null
+++ b/docs/woocommerce/contact-support.md
@@ -0,0 +1,7 @@
+# Support
+
+That wraps up the User Guide for the UnoPim WooCommerce Connector. We hope this documentation helps you get started smoothly and manage your catalog integration with ease.
+
+For any queries or doubts, feel free to reach out to us at support@webkul.com.
+
+You can also raise a ticket through our HelpDesk System.
\ No newline at end of file
diff --git a/docs/woocommerce/index.md b/docs/woocommerce/index.md
index 085f2e7..3fb2f8d 100644
--- a/docs/woocommerce/index.md
+++ b/docs/woocommerce/index.md
@@ -1,3 +1,43 @@
-# Woocommerce Extension
+# UnoPim WooCommerce Connector
+
+The **UnoPim WooCommerce Connector** links your **WooCommerce store** with **UnoPim** a powerful Product Information Management (PIM) system so you can manage all your product data from one place and keep both platforms in sync automatically.
+
+
+
+
+
+
+
+If you're tired of updating product information in WooCommerce and UnoPim separately, this connector solves that. Make your changes once in UnoPim and let the connector handle the rest categories, attributes, products, and variations all stay consistent across both platforms without manual effort.
+
+
+## How It Works
+
+The connector works in **both directions**:
+
+- **Export (UnoPim → WooCommerce)** push your product catalog from UnoPim to your WooCommerce store.
+- **Import (WooCommerce → UnoPim)** pull existing WooCommerce data into UnoPim to centralise your catalog management.
+- **Auto Sync** any product you create, update, or delete in UnoPim is automatically reflected in WooCommerce in real time no manual export needed.
+
+## Features
+
+### Export (UnoPim → WooCommerce)
+- Export **categories** from UnoPim to WooCommerce.
+- Export **attributes** and **attribute terms** from UnoPim to WooCommerce.
+- Export **products** including variations and attribute values.
+- **Quick Export** run a fast product export job for selected products without a full catalog run.
+
+### Import (WooCommerce → UnoPim)
+- Import **categories** from WooCommerce into UnoPim.
+- Import **attributes** and **attribute terms** from WooCommerce into UnoPim.
+- Import **products** from WooCommerce into UnoPim.
+
+### Sync & Credentials
+- **Auto Sync** product creates, updates, and deletes in UnoPim are automatically pushed to WooCommerce.
+- **Multiple credentials** connect more than one WooCommerce store to the same UnoPim instance.
+
+
+
-Placeholder landing page. Real docs are pulled from the project repo at build time.
diff --git a/docs/woocommerce/installation.md b/docs/woocommerce/installation.md
new file mode 100644
index 0000000..3ac02fc
--- /dev/null
+++ b/docs/woocommerce/installation.md
@@ -0,0 +1,75 @@
+# Installation
+
+Follow the steps below to install the UnoPim WooCommerce Connector. You'll need terminal access to your server before getting started.
+
+> **Note:** UnoPim 2.0.0 uses the **Laravel 12 bootstrap architecture** (`bootstrap/app.php` fluent API).
+
+## Step 1 Add the Package Files
+
+Unzip the extension ZIP file. Inside, you'll find a `packages` folder merge it into the **root directory** of your UnoPim project.
+
+
+## Step 2 Register the Service Provider
+
+Open `bootstrap/providers.php` and add the following:
+
+```php
+use Webkul\WooCommerce\Providers\WooCommerceServiceProvider;
+
+return [
+ // ...existing providers...
+ WooCommerceServiceProvider::class,
+];
+```
+
+
+## Step 3 Update Composer Autoload
+
+Open `composer.json` and add the following line under the `autoload > psr-4` section:
+
+```json
+"Webkul\\WooCommerce\\": "packages/Webkul/WooCommerce/src"
+```
+
+
+## Step 4 Run the Setup Commands
+
+Run the following commands one by one. Wait for each to complete before moving to the next.
+
+**Refresh the Composer autoloader**
+```bash
+composer dump-autoload
+```
+
+**Install the package**
+```bash
+php artisan woocommerce-package:install
+```
+This runs the database migrations and publishes the package assets automatically.
+
+**Build the frontend assets**
+```bash
+cd packages/Webkul/WooCommerce
+npm install
+npm run build
+cd ../../..
+```
+
+**Clear the application cache**
+```bash
+php artisan optimize:clear
+```
+
+**Restart the queue worker**
+```bash
+php artisan queue:restart
+```
+> The queue worker must be restarted whenever application code changes. This command sends a safe restart signal it waits for the current job to finish before restarting, so no jobs are lost.
+
+
+## Verify the Installation
+
+Once all commands have completed, log in to your UnoPim dashboard. You should see the **WooCommerce** option appear in the left sidebar this confirms the connector is installed and ready to configure.
+
+If it doesn't appear, run `php artisan optimize:clear` again and refresh the page.
+
diff --git a/docs/woocommerce/product-export.md b/docs/woocommerce/product-export.md
new file mode 100644
index 0000000..574ee29
--- /dev/null
+++ b/docs/woocommerce/product-export.md
@@ -0,0 +1,47 @@
+# Product Export
+
+The UnoPim WooCommerce Connector allows users to export product data from UnoPim to WooCommerce through dedicated export jobs.
+
+## Open the Export Jobs Section
+
+To create a product export job, go to:
+
+`Data Transfer > Exports`
+
+
+
+From the Exports page, click **Create Export** in the top-right corner.
+
+
+
+## Create a Product Export Job
+
+While creating the export job, the user needs to:
+
+- Enter the **Export Job Code**.
+- Select **WooCommerce Product Export** as the export job type.
+
+
+
+## Product Export Filters
+
+After selecting the product export job type, configure the following filters as needed:
+
+- **WooCommerce Store URL**: Select the required WooCommerce store credentials.
+- **Channel**: Select the channel for exporting.
+- **Locale**: Select the required locale.
+- **Currency**: Select the required currency.
+- **UnoPim Product SKU**: Enter the SKU of the specific product that needs to be exported.
+- **With Media**: Enable this option if product images should also be exported to WooCommerce.
+
+
+
+## Save and Run the Export Job
+
+After filling in the required details, click **Save Export** to create and save the export job.
+
+Once the export job is run, the user can monitor its progress from the **Job Tracker**.
+
+
+
+After the export completes successfully, the products will be visible in the connected WooCommerce store.
diff --git a/docs/woocommerce/product-import.md b/docs/woocommerce/product-import.md
new file mode 100644
index 0000000..6b06f27
--- /dev/null
+++ b/docs/woocommerce/product-import.md
@@ -0,0 +1,43 @@
+# Product Import
+
+The UnoPim WooCommerce Connector allows users to import WooCommerce products into UnoPim by creating an import profile.
+
+## Open the Import Section
+
+To create an import job, go to:
+
+`Import > Create Import Profile`
+
+
+
+From there, click **Create Import** to open the import setup form.
+
+
+
+## Create a Product Import Job
+
+While creating the import job, the user needs to:
+
+- Enter the **Code**.
+- Select **WooCommerce Product Import** as the import type.
+
+
+
+## Product Import Settings
+
+Under **Settings**, configure the following:
+
+- **WooCommerce Store URL**: Select the required WooCommerce store credentials.
+- **Locale**: Select the locale to be used during import.
+- **Channel**: Select the channel for importing products.
+- **Currency**: Select the currency to be used during import.
+- **Family**: Select the family to which the imported products should belong.
+- **With Media**: Enable this option if product media should also be imported.
+
+
+
+After entering the required values, click **Save Import** to save the import profile.
+
+Once the job is executed, the imported products will be available in UnoPim.
+
+
diff --git a/docs/woocommerce/setup-credentials.md b/docs/woocommerce/setup-credentials.md
new file mode 100644
index 0000000..58f7b0e
--- /dev/null
+++ b/docs/woocommerce/setup-credentials.md
@@ -0,0 +1,39 @@
+# Setup Credentials in UnoPim
+
+Once the UnoPim WooCommerce Connector is installed, it becomes available in the left-side menu of the UnoPim admin panel.
+
+From there, go to **WooCommerce > Credentials > Create** to add a new WooCommerce account and connect it with UnoPim.
+
+
+
+This credential setup allows UnoPim to communicate securely with your WooCommerce store for product, category, attribute, and variation synchronization.
+
+## Create a New Credential
+
+While creating a new credential, the admin needs to enter the following details:
+
+### General Details
+
+- **WooCommerce URL**: Enter the full URL of your WooCommerce store.
+- **Consumer Key**: Enter the Consumer Key generated from WooCommerce.
+- **Consumer Secret**: Enter the Consumer Secret generated from WooCommerce.
+
+
+
+## Settings
+
+The connector also provides the following configuration options:
+
+- **Is Active**: This option is enabled by default when a new credential is created. You can enable or disable the credential at any time by toggling this option.
+- **Default for Quick Export**: Enable this option if you want to use the credential for WooCommerce quick export jobs.
+
+
+
+> **Note:** Only one credential can be set as the default for quick export at a time.
+
+## Navigation Flow
+
+Follow this path in the UnoPim admin panel:
+
+`WooCommerce > Credentials > Create`
+
diff --git a/docs/woocommerce/sidebar.json b/docs/woocommerce/sidebar.json
index d5c5b37..2788bc6 100644
--- a/docs/woocommerce/sidebar.json
+++ b/docs/woocommerce/sidebar.json
@@ -2,7 +2,42 @@
{
"text": "Woocommerce",
"items": [
- { "text": "Overview", "link": "/woocommerce/" }
+ { "text": "Overview", "link": "/woocommerce/" },
+ {"text" : "Installation", "link": "/woocommerce/installation" },
+ {"text" : "Generate WooCommerce API Credentials", "link": "/woocommerce/api-credentials" },
+ {"text" : "Setup Credentials in UnoPim", "link": "/woocommerce/setup-credentials" }
+ ]
+ },
+
+ {
+ "text" : "Mapping",
+ "items" : [
+ {"text" : "Attribute Mapping Template", "link": "/woocommerce/attribute-mapping" }
+ ]
+ },
+
+ {
+ "text" : "Export Jobs",
+ "items" : [
+ {"text": "Attribute Export", "link": "/woocommerce/attribute-export" },
+ {"text": "Category Export", "link": "/woocommerce/category-export" },
+ {"text" : "Products Export", "link": "/woocommerce/product-export" }
+ ]
+ },
+
+ {
+ "text" : "Import Jobs",
+ "items" : [
+ {"text": "Attribute Import", "link": "/woocommerce/attribute-import" },
+ {"text": "Category Import", "link": "/woocommerce/category-import" },
+ {"text": "Product Import", "link": "/woocommerce/product-import" }
+ ]
+ },
+
+ {
+ "text" : "Support",
+ "items" : [
+ {"text" : "Contact Support", "link": "/woocommerce/contact-support" }
]
}
]