{"id":555415,"date":"2026-09-03T04:25:42","date_gmt":"2026-09-03T04:25:42","guid":{"rendered":"https:\/\/webkul.com\/blog\/?p=555415"},"modified":"2026-09-03T04:39:31","modified_gmt":"2026-09-03T04:39:31","slug":"woocommerce-connector-for-pimcore","status":"publish","type":"post","link":"https:\/\/webkul.com\/blog\/woocommerce-connector-for-pimcore\/","title":{"rendered":"WooCommerce Connector for Pimcore"},"content":{"rendered":"\n

The WooCommerce Connector<\/strong> is a Pimcore bundle that syncs your product catalog between Pimcore<\/a><\/strong> and a WooCommerce<\/a><\/strong> store, in both directions, entirely from inside Pimcore Studio. No custom scripts, no manual CSV exports \u2014 connect a store once, map your fields, and run export or import jobs whenever you need to, with live progress and a full history of everything that ran.<\/p>\n\n\n\n

This guide walks through every feature of the connector, screen by screen.<\/p>\n\n\n\n

Connecting a WooCommerce Store (Accounts)<\/h2>\n\n\n\n

Everything starts with an Account<\/strong> \u2014 a saved connection to one WooCommerce store, holding its URL and REST API credentials. The connector supports multiple accounts, so you can connect as many WooCommerce stores as you like from a single Pimcore install (a staging store, a production store, a store per brand or region \u2014 whatever your setup needs), each with its own credentials, import folder, and batch size.<\/p>\n\n\n\n

When you first open WooCommerce Connector \u2192 Accounts<\/strong>, the list is empty \u2014 click New account<\/strong> to add your first store.<\/p>\n\n\n\n

\"To<\/figure>\n\n\n\n

The account form asks for:<\/strong><\/p>\n\n\n\n

    \n
  1. Name<\/strong> \u2014 a friendly label for this connection.<\/li>\n\n\n\n
  2. Store URL<\/strong> \u2014 your WooCommerce site’s base URL.<\/li>\n\n\n\n
  3. WooCommerce REST API credentials<\/strong> \u2014 the Consumer key<\/strong> and Consumer secret, generated in WooCommerce under Settings \u2192 Advanced \u2192 REST API<\/strong><\/em>.<\/li>\n\n\n\n
  4. Import folder<\/strong> \u2014 the Pimcore asset\/object folder this account’s imports land in.<\/li>\n\n\n\n
  5. Batch size<\/strong> \u2014 how many records are sent per API request during a sync.<\/li>\n\n\n\n
  6. Active<\/strong> \u2014 a toggle to enable\/disable the connection without deleting it.<\/li>\n<\/ol>\n\n\n\n
    \"Creating<\/figure>\n\n\n\n

    Once saved, the account shows up in the list with quick actions:<\/p>\n\n\n\n

      \n
    1. Test<\/strong> \u2014 pings the store live with the saved credentials to confirm the connection actually works, right from the list, before you run a single job.<\/li>\n\n\n\n
    2. Edit<\/strong> \u2014 update the URL, credentials, folder or batch size at any time.<\/li>\n\n\n\n
    3. Delete<\/strong> \u2014 remove the connection entirely.<\/li>\n<\/ol>\n\n\n\n
      \n
      \"After<\/figure>\n<\/figure>\n\n\n\n

      2. Finding Your Way Around (The Connector Menu)<\/h2>\n\n\n\n

      Everything the connector does lives under its own entry in Pimcore’s main menu, so it never gets mixed up with the rest of your Pimcore setup:<\/p>\n\n\n\n

      \"Mapping<\/figure>\n\n\n\n

      From here you can reach:<\/p>\n\n\n\n

        \n
      1. Accounts<\/strong> \u2014 the connections screen covered above.<\/li>\n\n\n\n
      2. Field Mapping<\/strong> \u2014 decide which Pimcore field feeds which WooCommerce field.<\/li>\n\n\n\n
      3. Filters<\/strong> \u2014 decide which records get included in a sync at all.<\/li>\n\n\n\n
      4. Import<\/strong> \u2014 one submenu entry per importable entity.<\/li>\n\n\n\n
      5. Export<\/strong> \u2014 one submenu entry per exportable entity.<\/li>\n\n\n\n
      6. Job History<\/strong> \u2014 every export\/import job you’ve ever run, in one place.<\/li>\n\n\n\n
      7. Sync Mappings<\/strong> \u2014 the cross-system link between a Pimcore object and its WooCommerce counterpart.<\/li>\n<\/ol>\n\n\n\n

        3. Telling the Connector Which Pimcore Class Is Which<\/h2>\n\n\n\n

        Nothing about this connector is hardcoded to a specific class name. Before mapping fields, you tell it which of your<\/em> Pimcore classes plays the role of a WooCommerce Product<\/strong>, Category<\/strong>, and Brand<\/strong> \u2014 click Configure roles<\/strong> on the Field Mapping screen:<\/p>\n\n\n\n

        \"image\"<\/figure>\n\n\n\n

        Whatever class you already use for products, categories or brands in your Pimcore data model \u2014 the connector adapts to it, instead of forcing you into its own schema.<\/p>\n\n\n\n

        4. Field Mapping \u2014 Connecting Individual Fields<\/h2>\n\n\n\n

        For each account and each entity role (Product \/ Category \/ Brand), the Field Mapping<\/strong> screen lets you wire a Pimcore field to a WooCommerce field one at a time. Click Add mapping<\/strong>:<\/p>\n\n\n\n

        \"image\"<\/figure>\n\n\n\n
          \n
        1. The Pimcore field<\/strong> dropdown is populated straight from your class definition \u2014 including its Pimcore data type (`input`, `numeric`, `image`, `manyToManyObjectRelation`, and so on) \u2014 so there’s no guessing what a field actually is.<\/li>\n\n\n\n
        2. The WooCommerce field<\/strong> dropdown offers exactly the fields this connector understands for that entity, which prevents silent typos that would otherwise map to nothing.<\/li>\n\n\n\n
        3. Send as custom meta data<\/strong> \u2014 for anything WooCommerce doesn’t have a native field for. Instead of losing the value, it gets written as WooCommerce product\/term meta, so custom Pimcore data (brand info, SEO fields, dimensions, or anything modeled through Pimcore’s Classification Store<\/strong>) still makes the trip across.<\/li>\n<\/ol>\n\n\n\n

          Once you’ve mapped everything for an entity, the list gives you the full picture \u2014 every Pimcore field, its WooCommerce counterpart, whether it’s a real field or custom meta, and quick Edit\/Delete actions:<\/p>\n\n\n\n

          \"image\"<\/figure>\n\n\n\n

          5. Filters \u2014 Syncing Only What You Want<\/h2>\n\n\n\n

          Not every record needs to leave \u2014 or enter \u2014 your catalog. The Filters<\/strong> screen lets you define per-account, per-direction (export or import) rules that include or exclude records from a sync, so you can, for example, keep draft products out of an export, or skip importing certain WooCommerce categories entirely.<\/p>\n\n\n\n

          6. Exporting From Pimcore to WooCommerce<\/h2>\n\n\n\n

          The Export<\/strong> submenu gives you one screen per entity type \u2014 Category<\/strong>, Brand<\/strong>, Attribute<\/strong>, Product<\/strong>, and Variation<\/strong> Export. Each screen works the same way: pick the account, hit Run<\/strong>.<\/p>\n\n\n\n

          \"image\"<\/figure>\n\n\n\n

          Run order matters for a first full sync: Categories \u2192 Brands \u2192 Attributes<\/strong> before Products<\/strong> (since a product references its category\/brand\/attributes), and Products<\/strong> before Variations<\/strong>.<\/em><\/p>\n\n\n\n

          Every job runs asynchronously<\/strong> in the background, so Studio stays completely responsive \u2014 start a job, keep working, and come back to check on it. Open a job and you get live status:<\/p>\n\n\n\n

            \n
          1. Status<\/strong>, with a Stop<\/strong> button to cancel a run that’s still in progress.<\/li>\n\n\n\n
          2. Started \/ Ended \/ Duration<\/strong>.<\/li>\n\n\n\n
          3. A live Progress<\/strong> bar with percentage.<\/li>\n\n\n\n
          4. Live Statistics<\/strong>: Total, Read, Written, Updated, Skipped, Failed, and Batches \u2014 updating as the job works.<\/li>\n<\/ol>\n\n\n\n
            \"image\"<\/figure>\n\n\n\n

            7. Importing From WooCommerce Into Pimcore<\/h2>\n\n\n\n

            Sync works the other way too. The Import<\/strong> submenu covers every entity the connector can pull in: Category, Brand, Product, Attribute, Variation<\/strong>, and Order<\/strong> Import.<\/p>\n\n\n\n

            \"image\"<\/figure>\n\n\n\n

            Each import screen mirrors the export screens exactly \u2014 pick the account, Run<\/strong>, and watch the job history build up right there:<\/p>\n\n\n\n

            \"image\"<\/figure>\n\n\n\n

            And the same live job detail view \u2014 progress, statistics, and all \u2014 shows you exactly what happened once it’s done:<\/p>\n\n\n\n

            \"image\"<\/figure>\n\n\n\n

            8. Job History \u2014 Everything, In One Place<\/h2>\n\n\n\n

            Rather than hunting through individual export\/import screens, the Job History<\/strong> page lists every job the connector has ever run \u2014 export or import, any entity type, any account \u2014 with filters for Job Type<\/strong> and Status<\/strong>, live progress, failure counts, and a View<\/strong> action into the full detail of any job:<\/p>\n\n\n\n

            \"image\"<\/figure>\n\n\n\n

            10. Seeing the Result \u2014 Live in WooCommerce<\/h2>\n\n\n\n

            And here’s the payoff: after running a Brand Export, the brands created in Pimcore show up in WooCommerce’s own admin \u2014 names, descriptions, slugs, and images, exactly as configured in your field mapping:<\/p>\n\n\n\n

            \"image\"<\/figure>\n\n\n\n

            11. Feature Summary<\/h2>\n\n\n\n

            Multi-account \/ Multi-store<\/strong><\/p>\n\n\n\n