{"id":393637,"date":"2026-11-07T13:24:26","date_gmt":"2026-11-07T13:24:26","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/api-connector-for-woocommerce\/"},"modified":"2026-11-07T14:05:25","modified_gmt":"2026-11-07T14:05:25","slug":"storedispatcher-outbound-integration-for-woocommerce","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/storedispatcher-outbound-integration-for-woocommerce\/","author":8935584,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"0.1.1","stable_tag":"0.1.1","tested":"7.1.4","requires":"6.4","requires_php":"8.1","requires_plugins":null,"header_name":"StoreDispatcher - Outbound Integration for WooCommerce","header_author":"Mary Glo De La Pedra","header_description":"Send WooCommerce order data to external REST APIs with configurable authentication, field mapping, retries, and request logs.","assets_banners_color":"","last_updated":"2026-11-07 14:05:25","external_support_url":"","external_repository_url":"","donate_link":"https:\/\/paypal.me\/mgdelapedra","header_plugin_uri":"https:\/\/github.com\/maryglo\/api-connector-for-woocommerce","header_author_uri":"","rating":0,"author_block_rating":0,"active_installs":0,"downloads":162,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","faq","changelog"],"tags":{"0.1.1":{"tag":"0.1.1","author":"glowkazaf","date":"2026-11-07 14:05:25","revision":3789703}},"upgrade_notice":{"0.1.1":"

Configure WCAC_ENCRYPTION_KEY<\/code> before saving API credentials.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.jpg":{"filename":"icon-128x128.jpg","revision":3789624,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.jpg":{"filename":"icon-256x256.jpg","revision":3789624,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.1.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3789578,"resolution":"1","location":"assets","locale":"","width":752,"height":652},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3789578,"resolution":"2","location":"assets","locale":"","width":1370,"height":690},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3789578,"resolution":"3","location":"assets","locale":"","width":1430,"height":666},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3789578,"resolution":"4","location":"assets","locale":"","width":942,"height":650},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3789578,"resolution":"5","location":"assets","locale":"","width":1357,"height":515}},"screenshots":{"1":"Configure the API connection, authentication method, and order event settings.","2":"Map order fields to nested API fields and line-item arrays.","3":"Review the full order mapping table and save the field mappings.","4":"Preview the JSON payload generated from the saved mapping.","5":"Review integration logs, request statuses, and attempt counts."}},"plugin_section":[],"plugin_tags":[1556,597,16281,23853,286],"plugin_category":[45],"plugin_contributors":[291365],"plugin_business_model":[],"class_list":["post-393637","plugin","type-plugin","status-publish","hentry","plugin_tags-api","plugin_tags-integration","plugin_tags-orders","plugin_tags-rest-api","plugin_tags-woocommerce","plugin_category-ecommerce","plugin_contributors-glowkazaf","plugin_committers-glowkazaf"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/storedispatcher-outbound-integration-for-woocommerce\/assets\/icon-128x128.jpg?rev=3789624","icon_2x":"https:\/\/ps.w.org\/storedispatcher-outbound-integration-for-woocommerce\/assets\/icon-256x256.jpg?rev=3789624","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/storedispatcher-outbound-integration-for-woocommerce\/assets\/screenshot-1.png?rev=3789578","caption":"Configure the API connection, authentication method, and order event settings."},{"src":"https:\/\/ps.w.org\/storedispatcher-outbound-integration-for-woocommerce\/assets\/screenshot-2.png?rev=3789578","caption":"Map order fields to nested API fields and line-item arrays."},{"src":"https:\/\/ps.w.org\/storedispatcher-outbound-integration-for-woocommerce\/assets\/screenshot-3.png?rev=3789578","caption":"Review the full order mapping table and save the field mappings."},{"src":"https:\/\/ps.w.org\/storedispatcher-outbound-integration-for-woocommerce\/assets\/screenshot-4.png?rev=3789578","caption":"Preview the JSON payload generated from the saved mapping."},{"src":"https:\/\/ps.w.org\/storedispatcher-outbound-integration-for-woocommerce\/assets\/screenshot-5.png?rev=3789578","caption":"Review integration logs, request statuses, and attempt counts."}],"raw_content":"\n

A lightweight, configurable plugin for connecting WooCommerce stores to external REST APIs.<\/p>\n\n

The plugin sends order data when an order is created or completed. Store owners can configure the API connection, authentication, event triggers, and order field mappings in WordPress admin.<\/p>\n\n

Configure the API connection, authentication, events, and field mappings directly from the WordPress admin.<\/p>\n\n\n\n

Features<\/h3>\n\n

WooCommerce Integration<\/h3>\n\n
    \n
  • Connect WooCommerce to any REST API endpoint<\/li>\n
  • Support configurable API base URLs<\/li>\n
  • Bearer token authentication<\/li>\n
  • API key authentication<\/li>\n
  • Test API connectivity from the WordPress admin<\/li>\n<\/ul>\n\n

    Order Events<\/h3>\n\n
      \n
    • Detect newly created WooCommerce orders<\/li>\n
    • Detect completed orders<\/li>\n
    • Process integration requests asynchronously<\/li>\n
    • Queue requests using Action Scheduler<\/li>\n
    • Automatic retry handling for failed requests<\/li>\n<\/ul>\n\n

      Flexible Field Mapping<\/h3>\n\n

      Map WooCommerce order data to the structure required by your external API.<\/p>\n\n

      Example:<\/p>\n\n

      WooCommerce Field              API Field\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\nOrder ID                       order_id\nOrder Number                   order.reference\nOrder Status                   order.status\nCurrency                       order.currency\nOrder Total                    order.total\nBilling Email                  customer.email\nBilling First Name             customer.first_name\nBilling Last Name              customer.last_name\n<\/code><\/pre>\n\n
      The mapping engine supports nested destination structures such as customer.email<\/code>, customer.address.city<\/code>, and order.shipping.postcode<\/code>.<\/p>\n\n
      Line items can also be mapped into arrays. For example, map items[].sku<\/code>, items[].name<\/code>, items[].quantity<\/code>, and items[].price<\/code>.<\/p>\n\n
      Integration Logging<\/h3>\n\n
      Track integration requests and their results, including:<\/p>\n\n
        \n
      • Request status<\/li>\n
      • HTTP response status<\/li>\n
      • Attempt count<\/li>\n
      • Error information<\/li>\n
      • Processing timestamps<\/li>\n<\/ul>\n\n
        Sensitive authentication credentials are not included in integration logs.<\/p>\n\n
        Testing Tools<\/h3>\n\n
        Test the integration before sending real order data.<\/p>\n\n
          \n
        • Test API connection<\/li>\n
        • Generate a payload from an existing WooCommerce order<\/li>\n
        • Inspect the generated JSON<\/li>\n
        • Send test requests<\/li>\n
        • Review API responses<\/li>\n<\/ul>\n\n
          High-Performance Order Storage<\/h3>\n\n
          The plugin is designed to work with WooCommerce High-Performance Order Storage (HPOS).<\/p>\n\n
          Orders are accessed through WooCommerce's order APIs rather than directly querying WordPress post tables.<\/p>\n\n\n\n
          Architecture<\/h3>\n\n
          The plugin follows a simple integration pipeline:<\/p>\n\n
                            WooCommerce\n                       \u2502\n                       \u25bc\n                 Order Event\n                       \u2502\n                       \u25bc\n              Integration Job\n                       \u2502\n                       \u25bc\n                Mapping Engine\n                       \u2502\n             \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2534\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510\n             \u2502                   \u2502\n       Field Resolver       Transformer\n             \u2502                   \u2502\n             \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u252c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\n                       \u25bc\n                 JSON Payload\n                       \u2502\n                       \u25bc\n                  API Client\n                       \u2502\n                       \u25bc\n              External REST API\n                       \u2502\n                       \u25bc\n               Integration Log\n<\/code><\/pre>\n\n
          The integration is intentionally separated into independent components so the API client, mapping engine, event handling, and logging can evolve independently.<\/p>\n\n\n\n
          From GitHub<\/h3>\n\n
          Clone the repository:<\/p>\n\n
          git clone https:\/\/github.com\/maryglo\/api-connector-for-woocommerce.git\n<\/code><\/pre>\n\n
          The installable ZIP includes Composer's generated runtime autoloader; Composer is not required on the WordPress server. To build the ZIP from source, use PHP 8.1 or newer, run this from the repository root in PowerShell, then upload the ZIP under Plugins \u2192 Add Plugin \u2192 Upload Plugin<\/strong>:<\/p>\n\n
          .\\scripts\\build-plugin.ps1\n<\/code><\/pre>\n\n
          The ZIP is written to build\/storedispatcher-outbound-integration-for-woocommerce.zip<\/code>. It includes composer.json<\/code>, composer.lock<\/code>, and the generated vendor\/<\/code> autoloader. The icon and screenshots remain in the source assets\/<\/code> folder and are excluded from the ZIP; the admin CSS and JavaScript are included.<\/p>\n\n
          After installing the ZIP, activate StoreDispatcher - Outbound Integration for WooCommerce<\/strong> under WordPress Admin \u2192 Plugins \u2192 Installed Plugins<\/strong>.<\/p>\n\n
          Requirements<\/h3>\n\n
            \n
          • WordPress 6.4 or newer<\/li>\n
          • WooCommerce 11.1.0<\/li>\n
          • PHP 8.1 or newer<\/li>\n
          • PHP Sodium extension<\/li>\n
          • HTTPS recommended for production API communication<\/li>\n<\/ul>\n\n
            Compatibility<\/h3>\n\n
            This plugin is currently developed and tested with:<\/p>\n\n
              \n
            • WordPress:<\/strong> 7.1<\/li>\n
            • WooCommerce:<\/strong> 11.1.0<\/li>\n
            • PHP:<\/strong> 8.1+<\/li>\n
            • WooCommerce HPOS:<\/strong> Supported<\/li>\n<\/ul>\n\n
              Test the plugin in a staging environment before deploying it to a production store.<\/p>\n\n
              Configuration<\/h3>\n\n
              After activating the plugin, open:<\/p>\n\n
              WordPress Admin\n\u2192 WooCommerce\n\u2192 API Connector\n<\/code><\/pre>\n\n
              Configure:<\/p>\n\n
              API Connection\n\u251c\u2500\u2500 API Name\n\u251c\u2500\u2500 API Base URL\n\u251c\u2500\u2500 Health Path\n\u251c\u2500\u2500 Authentication method\n\u251c\u2500\u2500 API credentials\n\u2514\u2500\u2500 Connection test\n\nOrder Events\n\u251c\u2500\u2500 Order created\n\u2514\u2500\u2500 Order completed\n\nEndpoints\n\u2514\u2500\u2500 Order endpoint\n\nField Mapping\n\u251c\u2500\u2500 Order fields\n\u2514\u2500\u2500 Line-item fields\n<\/code><\/pre>\n\n
              Save the configuration and use the built-in connection test to verify communication with the external API.<\/p>\n\n
              Required encryption key<\/h3>\n\n
              Before saving API credentials, configure a dedicated encryption key in wp-config.php<\/code>.<\/p>\n\n
              The plugin uses this key to encrypt API credentials before storing them in the WordPress database.<\/p>\n\n
              Add:<\/p>\n\n
              define('WCAC_ENCRYPTION_KEY', 'YOUR_BASE64_ENCODED_32_BYTE_KEY');\n<\/code><\/pre>\n\n
              Generate a secure 32-byte key with PHP:<\/p>\n\n
              php -r \"echo base64_encode(random_bytes(32)), PHP_EOL;\"\n<\/code><\/pre>\n\n
              Copy the generated value into wp-config.php<\/code>:<\/p>\n\n
              define('WCAC_ENCRYPTION_KEY', 'your-generated-base64-key');\n<\/code><\/pre>\n\n
              Place the constant before \/* That's all, stop editing! Happy publishing. *\/<\/code> in wp-config.php<\/code>.<\/p>\n\n
              Docker environments<\/h3>\n\n
              If WordPress is running in Docker, the key can be generated inside the WordPress container:<\/p>\n\n
              docker compose exec wordpress php -r \"echo base64_encode(random_bytes(32)), PHP_EOL;\"\n<\/code><\/pre>\n\n
              The key can also be provided through the container environment.<\/p>\n\n
              For example, in .env<\/code>:<\/p>\n\n
              WCAC_ENCRYPTION_KEY=your-generated-base64-key\n<\/code><\/pre>\n\n
              Then expose it to the WordPress container and load it from wp-config.php<\/code>:<\/p>\n\n
              if (getenv('WCAC_ENCRYPTION_KEY')) {\n    define('WCAC_ENCRYPTION_KEY', getenv('WCAC_ENCRYPTION_KEY'));\n}\n<\/code><\/pre>\n\n
              Do not commit .env<\/code> files containing the encryption key to source control.<\/p>\n\n
              Encryption key requirements<\/h3>\n\n
                \n
              • The key must be a valid Base64-encoded 32-byte value.<\/li>\n
              • Keep the encryption key secret.<\/li>\n
              • Do not commit the encryption key to Git.<\/li>\n
              • Do not place the key in plugin source code.<\/li>\n
              • Do not use the external API credential as the encryption key.<\/li>\n
              • Keep the same encryption key for the lifetime of the encrypted credentials.<\/li>\n
              • Changing the encryption key will prevent previously encrypted credentials from being decrypted.<\/li>\n
              • Back up the encryption key securely when backing up a production WordPress installation.<\/li>\n<\/ul>\n\n
                After configuring the encryption key, enter the API credential in the API Connector settings and save the configuration.<\/p>\n\n\n\n
                Authentication<\/h3>\n\n
                The connector supports configurable API authentication.<\/p>\n\n
                Bearer Token<\/h3>\n\n
                Send the header Authorization: Bearer YOUR_TOKEN<\/code>.<\/p>\n\n
                API Key<\/h3>\n\n
                Send the header X-API-Key: YOUR_API_KEY<\/code>.<\/p>\n\n
                The API credential is encrypted before being stored in the WordPress database.<\/p>\n\n
                Credentials are not rendered back into the settings form after being saved. The credential field remains empty and displays a saved-credential indicator when a credential is configured.<\/p>\n\n
                When testing a connection, an administrator can enter a new credential and test it without first saving it.<\/p>\n\n
                Server-managed API credential<\/h3>\n\n
                For high-security deployments, an API credential can also be provided through the WCAC_API_KEY<\/code> constant in wp-config.php<\/code>.<\/p>\n\n
                Example:<\/p>\n\n
                define('WCAC_API_KEY', 'YOUR_API_CREDENTIAL');\n<\/code><\/pre>\n\n
                When configured, this server-managed credential takes precedence over the credential stored by the plugin.<\/p>\n\n
                Keep the value outside source control and never commit production credentials to Git.<\/p>\n\n
                Encryption key vs API credential<\/h3>\n\n
                These are two different secrets:<\/p>\n\n
                WCAC_API_KEY\n    \u2502\n    \u2514\u2500\u2500 External API credential\n\nWCAC_ENCRYPTION_KEY\n    \u2502\n    \u2514\u2500\u2500 Local encryption key used to protect\n        credentials stored by the plugin\n<\/code><\/pre>\n\n
                The encryption key does not authenticate requests to the external API.<\/p>\n\n
                Never place production API credentials or encryption keys in GitHub, screenshots, example configuration files, support requests, or issue reports.<\/strong><\/p>\n\n\n\n
                Order Processing<\/h3>\n\n
                When a configured WooCommerce event occurs, the plugin creates an asynchronous integration job.<\/p>\n\n
                Order Event\n    \u2502\n    \u25bc\nCreate Integration Job\n    \u2502\n    \u25bc\nAction Scheduler\n    \u2502\n    \u25bc\nLoad WooCommerce Order\n    \u2502\n    \u25bc\nApply Field Mapping\n    \u2502\n    \u25bc\nGenerate JSON Payload\n    \u2502\n    \u25bc\nSend REST API Request\n    \u2502\n    \u251c\u2500\u2500 Success\n    \u2502      \u2193\n    \u2502   Log success\n    \u2502\n    \u2514\u2500\u2500 Failure\n           \u2193\n        Retry\n           \u2193\n        Log failure\n<\/code><\/pre>\n\n
                Using asynchronous processing prevents the external API request from unnecessarily blocking the WooCommerce order lifecycle.<\/p>\n\n\n\n
                Retry Handling<\/h3>\n\n
                Temporary API failures can occur because of:<\/p>\n\n
                  \n
                • Network problems<\/li>\n
                • API timeouts<\/li>\n
                • Temporary server errors<\/li>\n
                • Rate limiting<\/li>\n
                • External service outages<\/li>\n<\/ul>\n\n
                  The connector can retry failed integration jobs according to its configured retry strategy.<\/p>\n\n
                  A typical flow is:<\/p>\n\n
                  Attempt 1\n   \u2502\n   \u2514\u2500\u2500 Failed\n         \u2193\n       Retry\n         \u2193\nAttempt 2\n   \u2502\n   \u2514\u2500\u2500 Failed\n         \u2193\n       Retry\n         \u2193\nAttempt 3\n   \u2502\n   \u251c\u2500\u2500 Success\n   \u2502\n   \u2514\u2500\u2500 Failed \u2192 Mark as failed\n<\/code><\/pre>\n\n\n\n
                  Field Mapping<\/h3>\n\n
                  The mapping system separates WooCommerce data from the external API's payload structure.<\/p>\n\n
                  For example, a WooCommerce order might contain:<\/p>\n\n
                  Order ID\nBilling Email\nBilling First Name\nBilling Last Name\nOrder Total\nCurrency\nLine Items\n<\/code><\/pre>\n\n
                  The external API may expect:<\/p>\n\n
                  {\n  \"externalOrderId\": 12345,\n  \"customer\": {\n    \"email\": \"customer@example.com\",\n    \"firstName\": \"John\",\n    \"lastName\": \"Doe\"\n  },\n  \"amount\": 199.99,\n  \"currency\": \"USD\",\n  \"items\": []\n}\n<\/code><\/pre>\n\n
                  The mapping configuration determines how the WooCommerce data is transformed into the destination structure.<\/p>\n\n
                  This means the plugin can support different API payload structures without requiring custom PHP code for every integration.<\/p>\n\n\n\n
                  Testing<\/h3>\n\n
                  The project includes automated tests for core components.<\/p>\n\n
                  Run the test suite:<\/p>\n\n
                  composer test\n<\/code><\/pre>\n\n
                  Before deploying a new version, test the plugin against a real WooCommerce installation with:<\/p>\n\n
                    \n
                  • HPOS enabled<\/li>\n
                  • HPOS disabled\/legacy storage where applicable<\/li>\n
                  • New orders<\/li>\n
                  • Completed orders<\/li>\n
                  • Successful API requests<\/li>\n
                  • Authentication failures<\/li>\n
                  • API validation errors<\/li>\n
                  • Server errors<\/li>\n
                  • Request timeouts<\/li>\n
                  • Retry scenarios<\/li>\n
                  • Encrypted credential storage and retrieval<\/li>\n
                  • Connection testing with a newly entered credential<\/li>\n
                  • Connection testing with a previously saved credential<\/li>\n<\/ul>\n\n\n\n
                    Security<\/h3>\n\n
                    Security is an important part of the plugin architecture.<\/p>\n\n
                    The project follows WordPress security practices including:<\/p>\n\n
                      \n
                    • Capability checks for administrative actions<\/li>\n
                    • Nonce verification<\/li>\n
                    • Input sanitization<\/li>\n
                    • Output escaping<\/li>\n
                    • WordPress HTTP APIs<\/li>\n
                    • Authenticated encryption for stored API credentials<\/li>\n
                    • Dedicated encryption key configuration<\/li>\n
                    • Secure handling of API credentials<\/li>\n
                    • Avoiding direct database access for WooCommerce orders<\/li>\n
                    • Avoiding credentials in logs<\/li>\n
                    • Validation of API configuration<\/li>\n
                    • TLS certificate verification for outbound HTTP requests<\/li>\n<\/ul>\n\n
                      API credentials stored by the plugin are encrypted before being persisted to the WordPress options table.<\/p>\n\n
                      The plugin uses PHP Sodium authenticated encryption for credential protection.<\/p>\n\n
                      The plugin does not require access to the external API's source code or server infrastructure.<\/p>\n\n\n\n
                      Project Structure<\/h3>\n\n
                      api-connector-for-woocommerce\/\n\u2502\n\u251c\u2500\u2500 src\/\n\u2502   \u251c\u2500\u2500 Admin\/\n\u2502   \u251c\u2500\u2500 Api\/\n\u2502   \u251c\u2500\u2500 Mapping\/\n\u2502   \u251c\u2500\u2500 Orders\/\n\u2502   \u251c\u2500\u2500 Jobs\/\n\u2502   \u251c\u2500\u2500 Logging\/\n\u2502   \u251c\u2500\u2500 Settings\/\n\u2502   \u2514\u2500\u2500 Install\/\n\u2502\n\u251c\u2500\u2500 assets\/ (admin CSS and JavaScript, icon, and directory screenshots)\n\u2502\n\u251c\u2500\u2500 tests\/\n\u2502\n\u251c\u2500\u2500 languages\/\n\u2502\n\u251c\u2500\u2500 composer.json\n\u251c\u2500\u2500 composer.lock\n\u251c\u2500\u2500 readme.txt\n\u251c\u2500\u2500 uninstall.php\n\u2514\u2500\u2500 storedispatcher-outbound-integration-for-woocommerce.php\n<\/code><\/pre>\n\n
                      The project uses a modular architecture to keep WordPress-specific functionality separate from API communication and mapping logic.<\/p>\n\n\n\n
                      Current Scope<\/h3>\n\n
                      The current version focuses on the core WooCommerce \u2192 REST API integration workflow.<\/p>\n\n
                      Currently supported<\/h3>\n\n
                        \n
                      • WooCommerce order events<\/li>\n
                      • Configurable API connection<\/li>\n
                      • API authentication<\/li>\n
                      • Encrypted API credential storage<\/li>\n
                      • Order field mapping<\/li>\n
                      • Customer information mapping<\/li>\n
                      • Line-item mapping<\/li>\n
                      • Nested JSON structures<\/li>\n
                      • Asynchronous processing<\/li>\n
                      • Retry handling<\/li>\n
                      • Integration logging<\/li>\n
                      • Test connection<\/li>\n
                      • Test payload generation<\/li>\n
                      • HPOS compatibility<\/li>\n<\/ul>\n\n
                        Not implemented in this release<\/h3>\n\n
                        The current release sends order events only. Customer names, email addresses, and line items are available as fields within an order payload; standalone customer and product event delivery are not implemented.<\/p>\n\n
                        Other possible future improvements include:<\/p>\n\n
                          \n
                        • Custom WooCommerce metadata mapping<\/li>\n
                        • Additional authentication methods<\/li>\n
                        • Advanced field transformations<\/li>\n
                        • Conditional mappings<\/li>\n
                        • Multiple API integrations<\/li>\n
                        • Scheduled synchronization<\/li>\n
                        • Bidirectional synchronization<\/li>\n
                        • Response mapping<\/li>\n
                        • Import\/export of integration configurations<\/li>\n
                        • AI-assisted field mapping<\/li>\n<\/ul>\n\n\n\n
                          Future AI Integration<\/h3>\n\n
                          AI is intentionally not required for the core integration process.<\/p>\n\n
                          The planned AI functionality will assist administrators during configuration rather than running inside the production order-processing pipeline.<\/p>\n\n
                          For example:<\/p>\n\n
                          External API Schema\n        \u2502\n        \u25bc\nAI Mapping Assistant\n        \u2502\n        \u25bc\nSuggested WooCommerce Mappings\n        \u2502\n        \u25bc\nAdministrator Review\n        \u2502\n        \u25bc\nSaved Mapping\n        \u2502\n        \u25bc\nDeterministic Production Integration\n<\/code><\/pre>\n\n
                          This approach keeps production integrations predictable while using AI to reduce the time required to configure complex API mappings.<\/p>\n\n\n\n
                          Roadmap<\/h3>\n\n
                          V1<\/h3>\n\n
                            \n
                          • [x] WooCommerce integration<\/li>\n
                          • [x] REST API client<\/li>\n
                          • [x] API authentication<\/li>\n
                          • [x] Encrypted API credential storage<\/li>\n
                          • [x] Order events<\/li>\n
                          • [x] Field mapping<\/li>\n
                          • [x] Nested payloads<\/li>\n
                          • [x] Line-item mapping<\/li>\n
                          • [x] Action Scheduler processing<\/li>\n
                          • [x] Retry handling<\/li>\n
                          • [x] Integration logging<\/li>\n
                          • [x] Test connection<\/li>\n
                          • [x] Test payload<\/li>\n<\/ul>\n\n
                            V1.x<\/h3>\n\n
                              \n
                            • [ ] Improved mapping UI<\/li>\n
                            • [ ] Idempotency protection<\/li>\n
                            • [ ] Additional API authentication methods<\/li>\n
                            • [ ] Custom order metadata<\/li>\n
                            • [ ] Improved integration monitoring<\/li>\n
                            • [ ] Additional automated tests<\/li>\n<\/ul>\n\n
                              V2+<\/h3>\n\n
                                \n
                              • [ ] Multiple integrations<\/li>\n
                              • [ ] Advanced transformations<\/li>\n
                              • [ ] Conditional mappings<\/li>\n
                              • [ ] Scheduled synchronization<\/li>\n
                              • [ ] Bidirectional synchronization<\/li>\n
                              • [ ] Configuration import\/export<\/li>\n
                              • [ ] AI-assisted mapping<\/li>\n<\/ul>\n\n\n\n
                                Contributing<\/h3>\n\n
                                Contributions, bug reports, feature requests, and improvements are welcome.<\/p>\n\n
                                Before submitting a pull request:<\/p>\n\n
                                  \n
                                1. Follow the existing project structure.<\/li>\n
                                2. Add or update tests where appropriate.<\/li>\n
                                3. Run the test suite.<\/li>\n
                                4. Run static analysis\/linting where configured.<\/li>\n
                                5. Ensure WordPress and WooCommerce compatibility is maintained.<\/li>\n
                                6. Do not include API credentials or customer data.<\/li>\n
                                7. Do not include encryption keys or other deployment secrets.<\/li>\n<\/ol>\n\n\n\n
                                  Bug Reports<\/h3>\n\n
                                  When reporting a problem, please include:<\/p>\n\n
                                    \n
                                  • WordPress version<\/li>\n
                                  • WooCommerce version<\/li>\n
                                  • PHP version<\/li>\n
                                  • Whether HPOS is enabled<\/li>\n
                                  • Plugin version<\/li>\n
                                  • Relevant error\/log information<\/li>\n
                                  • Steps to reproduce the issue<\/li>\n<\/ul>\n\n
                                    Never include API keys, encryption keys, passwords, customer information, or other sensitive data in an issue.<\/strong><\/p>\n\n\n\n
                                    License<\/h3>\n\n
                                    This project is licensed under the GPL-2.0-or-later license.<\/p>\n\n
                                    See LICENSE<\/code> for details.<\/p>\n\n\n\n
                                    Disclaimer<\/h3>\n\n
                                    This plugin is provided as an integration framework for connecting WooCommerce stores with external REST APIs.<\/p>\n\n
                                    External API availability, authentication requirements, rate limits, payload requirements, and data processing are controlled by the destination service.<\/p>\n\n
                                    Always test an integration in a staging environment before using it with production orders.<\/p>\n\n\n\n
                                    Project<\/h3>\n\n
                                    If this project is useful to you, consider giving it a star on GitHub.<\/p>\n\n
                                    Issues and feature requests are welcome.<\/p>\n\n\n
                                    \n
                                    Does this send customer or product events?<\/h3><\/dt>\n
                                    No. This release sends order-created and order-completed events. Customer details and products in an order can be included in its mapped payload, but separate customer and product synchronization are not implemented.<\/p><\/dd>\n
                                    Can this connect to any REST API?<\/h3><\/dt>\n
                                    The plugin can send order data to REST APIs that accept JSON requests. Configure the API URL, authentication, order endpoint, and field mappings to match the destination API.<\/p><\/dd>\n
                                    Can I create nested objects and line-item arrays?<\/h3><\/dt>\n
                                    Yes. Use dot paths such as customer.email<\/code> for nested objects and items[].sku<\/code> for line-item arrays.<\/p><\/dd>\n
                                    Does the mapping preview use unsaved edits?<\/h3><\/dt>\n
                                    No. Preview and test send use the saved mapping. Save the mapping table before previewing if you want to test recent changes.<\/p><\/dd>\n
                                    How are API credentials stored?<\/h3><\/dt>\n
                                    Credentials are encrypted in the WordPress database using PHP Sodium. Configure WCAC_ENCRYPTION_KEY<\/code> before saving credentials, and keep a secure backup of that key.<\/p><\/dd>\n\n<\/dl>\n\n\n
                                    0.1.1<\/h4>\n\n
                                      \n
                                    • Added configurable REST API connections and authentication.<\/li>\n
                                    • Added order events, field mapping, asynchronous delivery, retries, and integration logs.<\/li>\n
                                    • Added connection and payload testing tools.<\/li>\n<\/ul>","raw_excerpt":"Connect WooCommerce orders to external REST APIs with configurable authentication, field mapping, retries, and request logs.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/393637","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=393637"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/glowkazaf"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=393637"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=393637"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=393637"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=393637"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=393637"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=393637"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}