README

WooCommerce integration plugin for Filament v5. Pulls products + categories, customers, and orders from one or more WooCommerce stores into any Laravel/Filament CRM via configurable model mapping.

Laravel 11 / 12 / 13
Filament v4 / v5
PHP 8.3+
One-way sync: WooCommerce → host app
Multi-store: manage several WooCommerce stores from one Filament panel
Multi-tenant friendly: auto-populate team_id / organization_id / any tenant column on synced records

Installation

composer require madbox-99/filament-woocommerce
php artisan vendor:publish --tag=filament-woocommerce-config
php artisan vendor:publish --tag=filament-woocommerce-migrations
php artisan migrate

// app/Providers/Filament/AdminPanelProvider.php
use Madbox99\FilamentWooCommerce\FilamentWooCommercePlugin;

$panel->plugins([
    FilamentWooCommercePlugin::make(),
]);

Configuration

Edit config/filament-woocommerce.php and point each entity at a host-app model:

'mappings' => [
    'products' => [
        'enabled' => true,
        'model' => \App\Models\Product::class,
        'syncer' => \Madbox99\FilamentWooCommerce\Sync\ProductSyncer::class,
        'field_map' => [
            'name' => 'name',
            'sku' => 'sku',
            'regular_price' => 'unit_price',
            // ...
        ],
    ],
    // product_categories, customers, orders …
],

Add the HasWooMapping trait to each mapped model:

use Madbox99\FilamentWooCommerce\Concerns\HasWooMapping;

final class Product extends Model
{
    use HasWooMapping;
}

HasWooMapping adds a polymorphic relation to the woo_mappings table — no extra columns required on your own models.

Multi-tenant apps

If your host app scopes records by team_id, organization_id, account_id, …, tell the plugin which column to populate and the syncer will fill it on every new record it creates — and skip global scopes when resolving existing mappings, so queue workers can find records without an authenticated tenant context.

// config/filament-woocommerce.php
'tenant' => [
    'column' => 'team_id',              // null disables the feature (default)
    'model' => \App\Models\Team::class, // optional — renders a Select in the store form
    'label_column' => 'name',
    'bypass_global_scopes' => true,
],

Each store then stores its own tenant_id, assigned when you create the store in the UI. The syncer auto-populates team_id = store.tenant_id on newly created Products / Customers / Orders — but never overwrites an existing record's tenant.

Usage

Add a store

Go to WooCommerce → Stores in your Filament panel and create a new store with the site URL, consumer key, and consumer secret from WP Admin → WooCommerce → Settings → Advanced → REST API.

Click Test to verify the connection.

Sync

From the panel: click Sync now on a store row.

From the CLI:

php artisan woo:sync                         # queue all active stores
php artisan woo:sync --store=1               # queue a single store
php artisan woo:sync --store=1 --entity=products
php artisan woo:sync --store=1 --sync        # run inline (no queue)

The scheduler can run sync automatically — enable it in config (on by default, hourly).

Lookups

$product = Product::find(42);
$externalId = $product->wooExternalId(storeId: 1);
$mapping = $product->wooMappingFor(storeId: 1);

How mapping works

Each remote record has a unique external_id from WooCommerce.
When the syncer persists a local record, it creates/updates a row in woo_mappings linking the remote ID ↔ the local model (polymorphic).
Re-syncing re-uses the existing mapping, so records are updated in place rather than duplicated.
Cross-entity links (e.g. order → customer, product → category) resolve via mapping lookups at sync time.

Testing

composer test

License

MIT

madbox-99 / filament-woocommerce

Maintainers

Package info

Statistics

Security