runthings.dev

Order Departments for WooCommerce enables large organizations to automatically route orders to the appropriate departments based on the products or the categories of the products in each order.
For each department, a quick access menu is created below the WooCommerce.
The built in WooCommerce order emails can be re-routed so that only the relevant dept gets the order notification thats relevant to them.
The AutomateWoo integration then allows for further workflow automation based on department assignments.
<h4>Features</h4>
<ul>
<li>Automatic Department Assignment: Orders are automatically assigned to departments based on products/categories</li>
<li>Email Routing: Route order emails to department-specific email addresses</li>
<li>Admin Filtering: Filter orders by department in WooCommerce admin</li>
<li>Quick Access Menus: Direct links to orders for each department</li>
<li>AutomateWoo Integration: Complete set of actions, triggers, rules, and variables for workflow automation</li>
<li>Department Variables: Access department data in AutomateWoo workflows (names, emails, counts)</li>
<li>HPOS Compatible: Full support for WooCommerce High-Performance Order Storage</li>
</ul>
<h4>AutomateWoo Integration</h4>
This plugin provides complete AutomateWoo integration, allowing you to create sophisticated workflows based on department assignments. The integration includes custom actions, triggers, rules, and variables specifically designed for department-based automation.
Department Assignment Timing Tip: This plugin assigns departments immediately during order processing using the product/category rules you configure in the taxonomy screens. This happens early enough to affect WooCommerce’s core systems like email sending. AutomateWoo workflows run later in the process, so relying solely on AutomateWoo actions for department assignment would be too late to override WooCommerce’s built-in emails and other core functionality.
Using AutomateWoo for Email Handling: If you prefer to handle all emails through AutomateWoo workflows instead of the built-in email routing:
<ol>
<li>Disable WooCommerce’s default admin emails</li>
<li>Use AutomateWoo’s email actions with department triggers for full control</li>
</ol>
This approach gives you the flexibility to use AutomateWoo’s advanced email features (templates, conditions, delays, etc.) while still benefiting from automatic department assignment.
<h4>Actions</h4>
<ul>
<li>Set Order Department: Replace all existing departments with one department</li>
<li>Add Order Department: Add a department while keeping existing ones</li>
<li>Remove Order Department: Remove a specific department from an order</li>
<li>Clear Order Departments: Remove all departments from an order</li>
</ul>
<h4>Triggers</h4>
<ul>
<li>Order Department Added: Fires when a department is added to an order</li>
<li>Order Department Removed: Fires when a department is removed from an order</li>
<li>Order Department Changed: Fires when departments are modified in any way</li>
</ul>
<h4>Rules</h4>
<ul>
<li>Order Has Department: Check if order has specific department(s)</li>
<li>Order Department Count: Check the number of departments assigned</li>
<li>Order Department Is: Check if order’s departments exactly match a set</li>
</ul>
<h4>Variables</h4>
Collection Variables (all departments): 
* <code>{{ order.departments_names }}</code>: List of all department names assigned to the order 
* <code>{{ order.departments_emails }}</code>: List of all department email addresses (automatically deduplicated)
Per-Department Variables (flexible access): 
* <code>{{ order.department_names }}</code>: Department names with index/all/count options 
* <code>{{ order.department_emails }}</code>: Department emails with index/all/count options 
* <code>{{ order.department_count }}</code>: Number of departments assigned to the order
<h4>Variable Parameters</h4>
Collection Variables support <code>separator</code>, <code>prefix</code>, and <code>suffix</code> parameters: 
* <code>{{ order.departments_names | separator: ';' }}</code> → “Sales;Technical;Support” 
* <code>{{ order.departments_names | prefix: 'Dept: ', suffix: ' Team' }}</code> → “Dept: Sales Team, Dept: Technical Team” 
* <code>{{ order.departments_emails | separator: '; ' }}</code> → “sales@example.com; tech@example.com”
Per-Department Variables support <code>mode</code>, <code>index</code>, <code>separator</code>, <code>prefix</code>, and <code>suffix</code> parameters:
Mode Options: 
* <code>{{ order.department_names }}</code> → First department name (default mode: index) 
* <code>{{ order.department_names | mode: 'all' }}</code> → All department names 
* <code>{{ order.department_names | mode: 'count' }}</code> → Number of departments
Index Access: 
* <code>{{ order.department_names | index: '1' }}</code> → First department name 
* <code>{{ order.department_names | index: '2' }}</code> → Second department name 
* <code>{{ order.department_emails | index: '1' }}</code> → All emails from first department
Formatting: 
* <code>{{ order.department_names | prefix: 'Team: ', suffix: ' Dept' }}</code> → “Team: Sales Dept” 
* <code>{{ order.department_emails | separator: '; ' }}</code> → Multiple emails separated by semicolon
<h4>Variable Use Cases</h4>
<ul>
<li>
Sales & Technical Support: Route orders containing software to Technical, hardware to Sales
<ul>
<li>Use <code>{{ order.departments_emails }}</code> to automatically send order notifications to the right team</li>
<li>Create conditional workflows based on <code>{{ order.department_count }}</code> for mixed orders</li>
</ul>
</li>
<li>
Multi-location Fulfillment: Route orders to appropriate warehouses/locations
<ul>
<li>Include <code>{{ order.departments_names }}</code> in fulfillment emails to specify handling location</li>
<li>Use department variables in webhook payloads to external fulfillment systems</li>
</ul>
</li>
<li>
Specialized Teams: Route complex products to specialist departments
<ul>
<li>Send detailed instructions using <code>{{ order.department_names }}</code> for single-department orders</li>
<li>Create escalation workflows when <code>{{ order.department_names | mode: 'count' }}</code> exceeds normal thresholds</li>
</ul>
</li>
<li>
CRM Integration: Trigger department-specific workflows in external systems
<ul>
<li>Pass <code>{{ order.departments_names }}</code> to CRM systems for proper lead assignment</li>
<li>Use <code>{{ order.departments_emails }}</code> for automated follow-up sequences</li>
</ul>
</li>
</ul>
<h3>Developer Filters</h3>
The plugin provides filters to customize email handling behavior:
<h4>Email ID Filters</h4>
runthings_wc_order_departments_customer_email_ids
Customize which customer-facing email IDs have their reply-to headers modified by department emails.
<pre><code>add_filter('runthings_wc_order_departments_customer_email_ids', function($email_ids) { // Add custom customer email ID $email_ids[] = 'custom_customer_email'; // Remove an email ID if you don't want it modified $key = array_search('customer_new_account', $email_ids); if ($key !== false) { unset($email_ids[$key]); } return $email_ids; });
</code></pre>
Default customer email IDs: <code>customer_completed_order</code>, <code>customer_cancelled_order</code>, <code>customer_failed_order</code>, <code>customer_on_hold_order</code>, <code>customer_invoice</code>, <code>customer_note</code>, <code>customer_refunded_order</code>, <code>customer_processing_order</code>, <code>customer_new_account</code>, <code>customer_reset_password</code>
runthings_wc_order_departments_admin_email_ids
Customize which admin-facing email IDs have their recipients modified to use department emails.
<pre><code>add_filter('runthings_wc_order_departments_admin_email_ids', function($email_ids) { // Add custom admin email ID $email_ids[] = 'custom_admin_notification'; // Remove an email ID if you don't want it modified $key = array_search('backorder', $email_ids); if ($key !== false) { unset($email_ids[$key]); } return $email_ids; });
</code></pre>
Default admin email IDs: <code>new_order</code>, <code>cancelled_order</code>, <code>failed_order</code>, <code>backorder</code>
<h4>Use Cases for Email Filters</h4>
<ul>
<li>Custom Email Types: Add support for emails from other plugins or custom implementations</li>
<li>Selective Email Routing: Exclude specific email types from department-based routing</li>
<li>Third-party Integration: Ensure compatibility with other email-related plugins</li>
</ul>
<h3>Configuration</h3>
<h4>Setting Up Departments</h4>
<ol>
<li>Navigate to WooCommerce > Order Departments</li>
<li>Add new departments with:
<ul>
<li>Department name</li>
<li>Email addresses (semicolon-separated)</li>
<li>Associated product categories</li>
<li>Specific products</li>
</ul>
</li>
</ol>
<h4>Email Routing</h4>
The plugin provides two types of email routing:
<h4>Admin Email Routing</h4>
Admin emails (new order notifications, etc.) are automatically routed to department email addresses when departments are assigned to orders.
<h4>Customer Email Reply-To Override</h4>
Customer emails can have their reply-to headers modified based on department assignments. Configure this at Settings > Order Departments:
<ul>
<li>Override reply-to with department emails: Enable/disable the reply-to override feature</li>
<li>For multi-department orders: Choose behavior when multiple unique email addresses are involved:
<ul>
<li>Use all department emails: Add all unique department emails to reply-to header</li>
<li>Skip override – fall back to WooCommerce default: Use WooCommerce’s default reply-to setting</li>
</ul>
</li>
</ul>
Email routing behavior:
<ul>
<li>Single department orders: Always use that department’s email for reply-to (when override enabled)</li>
<li>Multi-department orders with same email: Treated as single department</li>
<li>Multi-department orders with different emails: Behavior depends on settings choice</li>
<li>If the order’s assigned departments have NO email addresses: The plugin does not attempt to override emails and WooCommerce emails work normally</li>
<li>If WooCommerce emails are disabled: No emails will be sent regardless of department email configuration</li>
</ul>
Notes:
<ul>
<li>Each department can have multiple email addresses (semicolon-separated)</li>
<li>You can simply set the default WooCommerce admin email address in each department to maintain the same recipient while enabling department-based routing</li>
<li>Email routing is determined per-order based on that order’s specific department assignments</li>
<li>If the same email address is listed in multiple departments assigned to an order, only one email will be sent to that address (duplicates are automatically removed)</li>
</ul>
<h4>AutomateWoo Workflows</h4>
Create workflows using the department triggers, rules, and variables to:
<ul>
<li>Send notifications to external systems using department email variables</li>
<li>Create tickets in support systems with department information</li>
<li>Update CRM records with department assignments</li>
<li>Trigger fulfillment processes based on department rules</li>
<li>Route emails to department-specific addresses using <code>{{ order.departments_emails }}</code></li>
<li>Include department context in communications using <code>{{ order.departments_names }}</code></li>
</ul>
<h3>Requirements</h3>
<ul>
<li>WordPress 6.3+</li>
<li>WooCommerce 8.2+</li>
<li>PHP 7.4+</li>
<li>AutomateWoo (optional, for workflow automation)</li>
</ul>
<h3>Additional Notes</h3>
Built by Matthew Harris of runthings.dev, copyright 2025.
Visit <a href="https://runthings.dev/" rel="nofollow ugc">runthings.dev</a> for more WordPress plugins and resources.
Contribute or report issues at <a href="https://github.com/runthings-dev/runthings-wc-order-departments" rel="nofollow ugc">GitHub repository</a>.
<h3>License</h3>
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, see <a href="http://www.gnu.org/licenses/gpl-3.0.html" rel="nofollow ugc">http://www.gnu.org/licenses/gpl-3.0.html</a>.
Icon – SEO by pictohaven from [https://thenounproject.com/browse/icons/term/seo/](Noun Project) (CC BY 3.0)

Order Departments for WooCommerce

Automatically assign WooCommerce orders to departments based on products/categories with email routing and AutomateWoo integration.

jrswordpress

Let visitors choose who receives their message. Add recipient dropdowns to your Contact Form 7 forms without exposing email addresses. No more manually forwarding submissions—emails reach the right person or department automatically.
Extend CF7 with dynamic recipient routing. Fast, lightweight, and easy to configure.
<h4>Features</h4>
<ul>
<li>Add a dynamic recipient dropdown to your Contact Form 7 forms</li>
<li>Manage recipient email addresses through an easy-to-use admin interface</li>
<li>Seamless integration into the Contact Form 7 admin page</li>
<li>Light-weight, clean, and secure code that’s less than 60kb in size</li>
</ul>
<h4>Pro Features</h4>
<ul>
<li>Advanced Recipient Management – Create unlimited recipients with custom labels and email addresses</li>
<li>Unlimited Shortcode Groups – Generate unlimited shortcode groups for different forms</li>
<li>Unlimited Email Groups – Put email groups inside drop downs for form entries that need to go to multiple locations</li>
<li>CF7 Tag Generator Integration – Built-in tag generators for easy form building inside Contact Form 7 forms</li>
</ul>
Get the <a href="https://onlyplugins.com/product/dynamic-recipients-pro/" rel="nofollow ugc">Pro Version</a> and access all of the features above.
<h4>Requirements</h4>
<ul>
<li>WordPress 5.8 or higher</li>
<li>PHP 7.4 or higher</li>
<li>Contact Form 7 plugin</li>
</ul>

Dynamic Recipients for Contact Form 7

Add recipient dropdowns to Contact Form 7. Let visitors route their messages to the right person or department without exposing email addresses.

Order Departments for WooCommerce vs Dynamic Recipients for Contact Form 7