PHPackages                             unopim/bagisto-connector - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [API Development](/categories/api)
4. /
5. unopim/bagisto-connector

ActiveLibrary[API Development](/categories/api)

unopim/bagisto-connector
========================

UnoPim Bagisto Connector enables users to link their Bagisto store to the UnoPim platform, allowing for seamless synchronization and management of product information.

1.0.3(6d ago)0852MITPHPCI passing

Since May 9Pushed 2mo ago2 watchersCompare

[ Source](https://github.com/unopim/bagisto-connector)[ Packagist](https://packagist.org/packages/unopim/bagisto-connector)[ Docs](https://www.unopim.com)[ RSS](/packages/unopim-bagisto-connector/feed)WikiDiscussions master Synced today

READMEChangelog (4)DependenciesVersions (5)Used By (0)

UnoPim-Bagisto Connector
========================

[](#unopim-bagisto-connector)

The **UnoPim-Bagisto Connector** enables seamless integration between **UnoPim 2.0** and **Bagisto**, allowing you to synchronize data effortlessly.

✨ Features
----------

[](#-features)

- 🗂 **Export Categories**: Export categories from UnoPim as collections in Bagisto.
- 🛠️ **Attributes Sync**: Transfer attributes from UnoPim to Bagisto with ease.
- 👨‍👩‍👧 **Export Families**: Export families from UnoPim to Bagisto.
- 📦 **Product Export**: Export products, including simple and configurable ones, from UnoPim to Bagisto.
- ⚡ **Bulk API**: Leverage a bulk API for faster product exports.
- 🗄️ **Media Sync**: Sync product images and videos from UnoPim to Bagisto.
- ☁️ **AWS S3 Compatibility**: Fully compatible with AWS S3 for image storage and management.

✅ Requirements
--------------

[](#-requirements)

- **UnoPim**: `2.1.x`
- **PHP**: `8.3+`
- **Bagisto** with REST API installed (`2.x.x`)

---

🛠️ Installation with Composer (recommended)
-------------------------------------------

[](#️-installation-with-composer-recommended)

UnoPim 2.0 ships with Laravel 12-style auto-discovery, so the service provider is registered automatically through `composer.json` (`extra.laravel.providers`). You only need to require the package and run the installer.

1. **Require the package**

    ```
    composer require unopim/bagisto-connector
    ```
2. **Run the package installer**

    The package ships an artisan command that runs the migrations, publishes assets, and clears caches in one step:

    ```
    php artisan bagisto-package:install
    ```

    > Pass `--no-interaction` (e.g. in CI) to accept the default for the migration prompt.
3. **(Optional) Verify the provider is registered**

    Auto-discovery should add the provider for you. If you want to confirm, check that `bootstrap/providers.php` resolves the package via `composer dump-autoload` — there is **no** entry to add by hand in UnoPim 2.0.

---

⚙️ Installation without Composer
--------------------------------

[](#️-installation-without-composer)

Use this path only if you need to load the package from the local `packages/` directory (for example when forking or developing the connector).

1. **Place the package**

    Download and extract the connector. Rename the folder to `Bagisto` and move it into `packages/Webkul/` of your UnoPim 2.0 project, so the final path is:

    ```
    packages/Webkul/Bagisto

    ```
2. **Register the namespace**

    Open the project's root `composer.json` and add the package namespace under `autoload.psr-4`:

    ```
    "autoload": {
        "psr-4": {
            "Webkul\\Bagisto\\": "packages/Webkul/Bagisto/src"
        }
    }
    ```
3. **Register the service provider**

    > UnoPim 2.0 follows the Laravel 12 bootstrap layout — providers live in `bootstrap/providers.php`, **not** in `config/app.php`.

    Open `bootstrap/providers.php` and add the provider to the returned array:

    ```