PHPackages                             serkanalgur/woocommerce-custom-order-export - 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. serkanalgur/woocommerce-custom-order-export

ActiveWordpress-plugin

serkanalgur/woocommerce-custom-order-export
===========================================

Export WooCommerce orders to CSV/XLSX with product-level custom codes

v1.8.2(2mo ago)401GPL-2.0-or-laterPHPPHP >=7.4CI passing

Since Nov 29Pushed 2mo ago1 watchersCompare

[ Source](https://github.com/serkanalgur/woocommerce-custom-order-export)[ Packagist](https://packagist.org/packages/serkanalgur/woocommerce-custom-order-export)[ RSS](/packages/serkanalgur-woocommerce-custom-order-export/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (7)Dependencies (5)Versions (9)Used By (0)

WooCommerce Custom Order Export
===============================

[](#woocommerce-custom-order-export)

[![WordPress](https://camo.githubusercontent.com/eae94c78f0fe73447ab8c809af7de8a09ee5152666245c37417e6bc2df9d8a8f/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f576f726450726573732d3231373539623f7374796c653d666f722d7468652d6261646765266c6f676f3d576f72645072657373266c6f676f436f6c6f723d25323346464646464626636f6c6f723d253233323137353962)](https://camo.githubusercontent.com/eae94c78f0fe73447ab8c809af7de8a09ee5152666245c37417e6bc2df9d8a8f/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f576f726450726573732d3231373539623f7374796c653d666f722d7468652d6261646765266c6f676f3d576f72645072657373266c6f676f436f6c6f723d25323346464646464626636f6c6f723d253233323137353962) [![WooCommerce](https://camo.githubusercontent.com/acbe3276aa0c5c8ef5046806dcad74c6951f6e97d9bc25abac8d0ca5a342ffce/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f576f6f436f6d6d657263652d3936353838613f7374796c653d666f722d7468652d6261646765266c6f676f3d576f6f266c6f676f436f6c6f723d25323346464646464626636f6c6f723d253233393635383861266c6f676f53697a653d3330)](https://camo.githubusercontent.com/acbe3276aa0c5c8ef5046806dcad74c6951f6e97d9bc25abac8d0ca5a342ffce/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f576f6f436f6d6d657263652d3936353838613f7374796c653d666f722d7468652d6261646765266c6f676f3d576f6f266c6f676f436f6c6f723d25323346464646464626636f6c6f723d253233393635383861266c6f676f53697a653d3330)

A production-ready WordPress plugin for exporting WooCommerce orders to CSV/XLSX with support for product-level custom codes and metadata.

Features
--------

[](#features)

- **Flexible Export Formats**: CSV (default) and XLSX output
- **Custom Column Selection**: Choose which order, item, and product fields to include
- **Product Custom Codes**: Map product meta keys or taxonomy terms to custom columns
- **Export Modes**: Export as one row per line item or one row per order
- **Advanced Filtering**: Filter orders by date range and status
- **Performance Optimized**: Stream output for large datasets (3,000+ orders)
- **Export Logging**: Track all export operations with filters applied
- **Extensible**: Hooks and filters for custom development
- **Security**: Proper nonces, capability checks, and sanitization

Requirements
------------

[](#requirements)

- WordPress 6.0+
- WooCommerce 6.0+
- PHP 7.4+

Supported Plugins
-----------------

[](#supported-plugins)

This plugin integrates with and supports the following plugins:

### Product Input Fields for WooCommerce

[](#product-input-fields-for-woocommerce)

- [Product Input Fields for WooCommerce](https://wordpress.org/plugins/product-input-fields-for-woocommerce/)
- **Feature**: Line Item Metadata Mapping
- **Description**: Export custom product input field metadata to your CSV/XLSX exports
- **Status**: Optional (feature is only available when this plugin is installed and activated)
- **Use Case**: Extract custom metadata collected via Product Input Fields and include it in order exports

Installation
------------

[](#installation)

1. Download the plugin or clone into your `wp-content/plugins/` directory
2. Navigate to the plugin in WordPress admin and activate
3. Go to **WooCommerce → Custom Order Export**

Configuration
-------------

[](#configuration)

### Basic Setup

[](#basic-setup)

1. **Select Filters**

    - Choose date range (optional)
    - Select order statuses to include
2. **Choose Export Format**

    - CSV or XLSX
    - Set CSV delimiter (comma, semicolon, tab, pipe)
    - Configure column headers inclusion
3. **Select Columns**

    - Order fields (ID, date, customer info, totals)
    - Line item fields (product name, SKU, quantity, price)
    - Product fields (categories)
4. **Add Custom Code Mappings**

    - Map product meta keys or taxonomies to export columns
    - Supports multiple terms per product

Custom Code Mapping Examples
----------------------------

[](#custom-code-mapping-examples)

### Example 1: Product Meta Key

[](#example-1-product-meta-key)

Export a product custom field stored as post meta:

```
Column Name: product_code
Source Type: Product Meta
Meta Key: _product_code

```

This exports the value of `get_post_meta( $product_id, '_product_code', true )`

### Example 2: Product Taxonomy

[](#example-2-product-taxonomy)

Export a product taxonomy (like a custom "Collection" taxonomy):

```
Column Name: product_collection
Source Type: Taxonomy
Taxonomy Name: product_collection

```

This exports `wp_get_post_terms( $product_id, 'product_collection', array('fields' => 'names') )`

### Example 3: Product Attribute

[](#example-3-product-attribute)

For WooCommerce attributes (stored as taxonomy `pa_*`):

```
Column Name: metal_type
Source Type: Taxonomy
Taxonomy Name: pa_metal

```

Default Export Columns
----------------------

[](#default-export-columns)

By default, the export includes:

```
order_id, order_date, customer_name, customer_email, billing_phone,
shipping_address, payment_method, order_total, product_id, sku,
product_name, quantity, line_total, product_code, product_categories

```

Database Schema
---------------

[](#database-schema)

The plugin creates a logging table (`wp_wexport_logs`) with the following columns:

- `id`: Auto-increment ID
- `export_date`: Timestamp of export
- `filters`: JSON of filters applied
- `file_path`: Path to exported file
- `rows_exported`: Number of rows in export
- `export_format`: csv or xlsx
- `user_id`: ID of user who triggered export
- `status`: success or error
- `error_message`: Error details if applicable

Available Hooks
---------------

[](#available-hooks)

### Filters

[](#filters)

```
// Add or modify order query arguments
apply_filters( 'wexport_order_query_args', $args );

// Modify custom code mappings
apply_filters( 'wexport_custom_code_mappings', $mappings );
```

### Actions

[](#actions)

```
// Before export starts
do_action( 'wexport_before_export', $manager );

// After export completes
do_action( 'wexport_after_export', $manager, $file_path, $rows_exported );
```

Example: Custom Code Implementation
-----------------------------------

[](#example-custom-code-implementation)

### Adding a Product Meta Code

[](#adding-a-product-meta-code)

1. In your product edit screen or via code, save product meta:

```
update_post_meta( $product_id, '_product_code', 'PROD-12345' );
```

2. In WExport, add a custom code mapping:
    - Column Name: `product_code`
    - Source Type: `Product Meta`
    - Meta Key: `_product_code`

### Adding a Product Taxonomy

[](#adding-a-product-taxonomy)

1. Register a custom product taxonomy:

```
register_taxonomy(
    'product_code',
    'product',
    array(
        'label' => 'Product Code',
        'rewrite' => array( 'slug' => 'product-code' ),
    )
);
```

2. Assign terms to products via admin or code:

```
wp_set_post_terms( $product_id, array( 'PROD-12345' ), 'product_code' );
```

3. In WExport, add a custom code mapping:
    - Column Name: `product_code`
    - Source Type: `Taxonomy`
    - Taxonomy Name: `product_code`

File Structure
--------------

[](#file-structure)

```
woocommerce-custom-order-export/
├── woocommerce-custom-order-export.php   # Main plugin file
├── composer.json                         # Composer dependencies
├── composer.lock                         # Locked dependency versions
├── phpunit.xml                           # PHPUnit configuration
├── README.md                             # This file
├── CHANGELOG.md                          # Version history
├── LICENSE                               # GPL v2 license
├── .gitignore                            # Git ignore rules
│
├── includes/                             # Core plugin classes
│   ├── class-export-manager.php          # Main export orchestration
│   ├── class-export-formatter.php        # CSV/XLSX data formatting
│   ├── class-export-logger.php           # Export logging and tracking
│   ├── class-xlsx-exporter.php           # XLSX file generation
│   ├── class-ajax-handler.php            # AJAX request handling
│   ├── class-template-manager.php        # Template CRUD operations
│   ├── class-template-ajax-handler.php   # Template AJAX operations
│   └── class-import-manager.php          # Template import/export
│
├── admin/                                # WordPress admin interface
│   ├── class-admin-page.php              # Admin page controller
│   ├── admin-page.php                    # Admin UI HTML template
│   ├── css/
│   │   ├── admin-styles.css              # Main admin styling
│   │   ├── notifications.css             # Notification system styling
│   │   └── template-styles.css           # Template UI styling
│   └── js/
│       ├── admin-ui.js                   # Main admin interface logic
│       ├── notifications.js              # Notification system
│       └── template-manager.js           # Template frontend logic
│
├── tests/                                # PHPUnit tests
│   ├── bootstrap.php                     # Test bootstrap configuration
│   └── test-export-manager.php           # Export manager tests
│
└── vendor/                               # Composer dependencies
    ├── phpoffice/phpspreadsheet/         # XLSX generation library
    ├── phpunit/phpunit/                  # PHPUnit testing framework
    ├── wp-coding-standards/wpcs/         # WordPress coding standards
    └── [other dependencies...]

```

Testing
-------

[](#testing)

### Unit Tests

[](#unit-tests)

Run PHPUnit tests using Composer:

```
# Run all tests
composer test

# Run with coverage report
composer test -- --coverage-html coverage/
```

Tests are located in the `tests/` directory and configured via `phpunit.xml`.

### Manual QA Steps

[](#manual-qa-steps)

1. **Verify Product Meta Export**

    - Create a product with custom meta key `_test_code` = "TEST123"
    - Add custom code mapping in WExport (Meta type)
    - Export and verify column contains "TEST123"
2. **Verify Taxonomy Export**

    - Assign a product to a custom taxonomy term
    - Add custom code mapping in WExport (Taxonomy type)
    - Export and verify column contains term name
3. **Large Dataset Test**

    - With 3,000+ orders, verify export completes without memory errors
    - Check that file is created and downloaded correctly
4. **Multi-Item Order Test**

    - Create order with 3 line items
    - Export in "line\_item" mode: should see 3 rows
    - Export in "order" mode: should see 1 row with products joined
5. **Special Characters Test**

    - Create product with quotes, commas, newlines in name
    - Verify CSV escaping works correctly in exported file
6. **Date Range Filtering Test**

    - Export with both from and to dates: verify complete range is applied
    - Export with only from date: verify all orders after that date
    - Export with only to date: verify all orders before that date
7. **Template System Test**

    - Save a template with custom columns
    - Load the template and verify all settings are restored
    - Set as default and reload page to verify auto-loading
    - Duplicate and edit templates

Performance Considerations
--------------------------

[](#performance-considerations)

### Memory Usage

[](#memory-usage)

- Orders are fetched in batches (default 100 per batch)
- CSV is streamed to disk via `fputcsv()`
- No order or item data stored in memory simultaneously

### Large Exports (3,000+ orders)

[](#large-exports-3000-orders)

- Processing time depends on server speed and data size
- Recommend increasing PHP timeout for very large exports
- Consider exporting by date ranges for large organizations

Troubleshooting
---------------

[](#troubleshooting)

### "Export directory is not writable"

[](#export-directory-is-not-writable)

Ensure `/wp-content/uploads/wexport/` directory exists and is writable:

```
chmod 755 wp-content/uploads/wexport/
```

### Missing custom code columns in export

[](#missing-custom-code-columns-in-export)

1. Verify the meta key exists on products:

    ```
    get_post_meta( $product_id, '_your_meta_key', true )
    ```
2. Verify the taxonomy exists and is assigned to product:

    ```
    wp_get_post_terms( $product_id, 'your_taxonomy' )
    ```
3. Check that custom code mapping is configured in WExport settings

### CSV not opening correctly in Excel

[](#csv-not-opening-correctly-in-excel)

Ensure "Include column headers" and "Use UTF-8 BOM" are both checked for Excel compatibility.

For Developers
--------------

[](#for-developers)

### Project Structure

[](#project-structure)

- **includes/** - Core plugin classes (Export\_Manager, Export\_Logger, Exporters, Template\_Manager)
- **admin/** - WordPress admin interface (class-admin-page.php, templates, styles, JavaScript)
- **tests/** - PHPUnit unit and integration tests
- **vendor/** - Composer dependencies (PhpSpreadsheet, WordPress Coding Standards)

### Code Standards

[](#code-standards)

The project follows WordPress Coding Standards. Run checks with:

```
# Check code style
composer phpcs

# Auto-fix style issues
composer phpcbf
```

### Key Classes

[](#key-classes)

- **Export\_Manager** (`includes/class-export-manager.php`)

    - Orchestrates the export process
    - Queries orders in batches
    - Applies filters and custom code mappings
    - Delegates formatting to exporter classes
- **CSV\_Exporter** / **XLSX\_Exporter** (`includes/class-*-exporter.php`)

    - Format-specific export logic
    - Stream data to files
    - Handle styling and encoding
- **Export\_Logger** (`includes/class-export-logger.php`)

    - Tracks export operations in database
    - Logs filters applied, file paths, status
- **Template\_Manager** (`includes/class-template-manager.php`)

    - User-scoped template persistence
    - CRUD operations for templates
    - Default template handling
- **Admin\_Page** (`admin/class-admin-page.php`)

    - Generates admin UI
    - Handles form data validation
    - Provides preview functionality

### Adding Features

[](#adding-features)

#### Add a new export column

[](#add-a-new-export-column)

1. Update column selection UI in `admin/admin-page.php`
2. Add column to available columns list in `Export_Manager::get_available_columns()`
3. Implement column data retrieval in `Export_Formatter::format_item()`
4. Update default export columns if needed

#### Add a new filter type

[](#add-a-new-filter-type)

1. Create filter UI in `admin/admin-page.php`
2. Modify `Export_Manager::get_orders_batch()` to apply new filter
3. Update `Export_Logger` to track new filter type
4. Add validation in `Admin_Page::validate_filters()`

#### Add a new export format

[](#add-a-new-export-format)

1. Create new exporter class extending base logic
2. Implement file writing in `export()` method
3. Register in `Export_Manager::get_exporter()`
4. Add format option to admin UI

### Hooks and Filters

[](#hooks-and-filters)

**Filters:**

```
// Modify order query arguments
apply_filters( 'wexport_order_query_args', $args );

// Modify custom code mappings
apply_filters( 'wexport_custom_code_mappings', $mappings );

// Modify export columns
apply_filters( 'wexport_export_columns', $columns );
```

**Actions:**

```
// Before export starts
do_action( 'wexport_before_export', $manager );

// After export completes
do_action( 'wexport_after_export', $manager, $file_path, $rows_exported );
```

### Debugging

[](#debugging)

Enable debug logging by adding to `wp-config.php`:

```
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
```

Check logs in `wp-content/debug.log`. The plugin uses `error_log()` for server-side debugging.

For frontend debugging, check browser console (`F12`) for detailed logging during export operations.

### Running Tests Locally

[](#running-tests-locally)

```
# Install dependencies
composer install

# Run tests
composer test

# Run with verbose output
composer test -- --verbose
```

Test files use WordPress test utilities if bootstrapped properly. See `tests/bootstrap.php` for configuration.

Development Notes
-----------------

[](#development-notes)

### Adding Custom Columns

[](#adding-custom-columns)

Extend export columns via filter:

```
add_filter( 'wexport_order_query_args', function( $args ) {
    $args['meta_query'] = array(
        array(
            'key'   => '_custom_order_field',
            'value' => 'value',
        )
    );
    return $args;
});
```

### Creating a Scheduled Export

[](#creating-a-scheduled-export)

Use WP-Cron:

```
wp_schedule_event( time(), 'daily', 'wexport_scheduled_export' );

add_action( 'wexport_scheduled_export', function() {
    $manager = new WExport\Export_Manager( array(
        'format'       => 'csv',
        'columns'      => get_option( 'wexport_default_columns' ),
        'order_status' => array( 'wc-completed' ),
    ));

    $file = $manager->export();

    // Email result
    wp_mail(
        get_option( 'admin_email' ),
        'Daily Order Export',
        'Export completed: ' . $file
    );
});
```

Performance Benchmark
---------------------

[](#performance-benchmark)

Typical performance on standard hosting:

- 100 orders: < 1 second
- 1,000 orders: 5-10 seconds
- 10,000 orders: 1-2 minutes
- 100,000 orders: 15-30 minutes

Security
--------

[](#security)

- All admin actions require `manage_woocommerce` capability
- Nonces on all forms
- User ID and timestamp logged for all exports
- Meta keys and taxonomy names sanitized before database queries
- CSV output escaped for safe Excel import

Support & Issues
--------------------

[](#support--issues)

For issues or feature requests, please contact support or submit via the plugin support channel.

Contributors
------------

[](#contributors)

This plugin is developed with contributions from the community:

[ ![](https://camo.githubusercontent.com/b5d667a785d1130256a5ca74e17c12dca8b318bbb1c22f2f07401be101331c5f/68747470733a2f2f636f6e747269622e726f636b732f696d6167653f7265706f3d7365726b616e616c6775722f776f6f636f6d6d657263652d637573746f6d2d6f726465722d6578706f7274)](https://github.com/serkanalgur/woocommerce-custom-order-export/graphs/contributors)Special thanks to:

- **[@BrianHenryIE](https://github.com/BrianHenryIE)** - Line Item Metadata Mapping feature

Changelog
---------

[](#changelog)

### 1.8.2 (2026-03-08)

[](#182-2026-03-08)

- **Fixed**: XLSX exports now properly populate all row data (previously returned empty rows)
- **Fixed**: Removed unnecessary row data type conversion that broke column-to-value mapping
- **Improved**: XLSX row data structure maintains associative array format for proper exporter compatibility

### 1.8.1 (2026-03-08)

[](#181-2026-03-08)

- **Fixed**: Preview/export mismatch where preview displayed data but export returned empty file
- **Fixed**: Date filter inconsistency between preview and export functions
- **Fixed**: Unreachable code in AJAX handler preventing option persistence
- **Changed**: Preview now applies same date filters as export for consistent results

### 1.8.0 (2026-03-08)

[](#180-2026-03-08)

- **Added**: Line Item Metadata Mapping feature to export custom metadata from Product Input Fields products
- **Added**: Support for nested JSON query paths in metadata extraction
- **Added**: Conditional UI that shows/hides metadata feature based on plugin installation
- **Added**: Unit tests for metadata configuration and export functionality
- **Fixed**: Enhanced AJAX and form handlers with plugin presence verification
- **Contributors**: [@BrianHenryIE](https://github.com/BrianHenryIE) for initial metadata feature implementation

### 1.7.3 (2026-03-06)

[](#173-2026-03-06)

- **Fix**: Re-registered autoloader via `spl_autoload_register` which was lost after `WExport` class refactor.
- **Fix**: Corrected autoloader directory mapping for `WExport\Admin` namespace to fix admin area disappearance.

### 1.7.2 (2026-03-06)

[](#172-2026-03-06)

- **Changed**: Decoupled bootstrap initialization by moving `WExport` class to `includes/class-wexport.php`.
- **Fixed**: Multiple WordPress Coding Standards issues.
- **Improved**: Hardened security with better nonce validation and input sanitization.
- **Optimized**: Preview generation for small datasets is now faster.

### 1.7.2 - 2026-03-06

[](#172---2026-03-06)

**Changed**

- **Refactoring**: Moved `WExport` core class to [includes/class-wexport.php](includes/class-wexport.php) to separate bootstrap logic from core architecture and improve PSR autoloading.

**Fixed**

- **WP Coding Standards**: Resolved numerous violations across the codebase, including inline comment punctuation, docblock @throws tags, for better compliance with WordPress standards.
- **Security**: Strengthened security by adding missing nonce verification and proper `$_POST` sanitization in the admin module.
- **File System**: Improved directory handling by integrating `WP_Filesystem` for path and permission checks.
- **Preview Optimization**: Refactored the preview generation logic to avoid redundant file system writes/reads, keeping processing in-memory where possible.

### 1.7.1 - 2025-12-01

[](#171---2025-12-01)

**Fixed**

- **Critical**: Taxonomy custom columns now correctly show only the variation-specific attribute value for variation products, instead of showing all taxonomy terms from the parent product. When exporting a variation with a selected attribute (e.g., "50g" for `pa_gramaj`), only that specific value is now exported, not all available values.
- Product variation taxonomy extraction now prioritizes `get_attribute()` to retrieve the variation-specific value before falling back to `wp_get_post_terms()`.
- Preview and export now have consistent behavior for variation taxonomy values.
- Persist `remove_variation_from_product_name` admin setting: Store the checkbox state persistently using `update_option` from both AJAX and non-AJAX flows (preview and export), so the checkbox is remembered for subsequent sessions.

**Changed**

- Taxonomy handling: Reordered variation attribute extraction logic to check `product->get_attribute()` FIRST for variations, ensuring only the selected attribute value is returned, then falling back to taxonomy term queries only if needed.
- Simplified taxonomy extraction logic by removing redundant attribute fallback from the else block.

### 1.6.0 - 2025-11-29

[](#160---2025-11-29)

**Added**

- Checkbox in admin UI to remove variation details from product names on export and preview. The exporter now uses parent product name for variations if this option is enabled.

**Changed**

- Taxonomy-based custom code mappings now prefer terms assigned to the variation (if the exported item is a variation) and fall back to the parent product if none are present. This makes per-variation attributes (e.g., `pa_gramaj`) export the correct variation value (like "50g").

### 1.5.0 - 2025-11-16

[](#150---2025-11-16)

**Fixed**

- Date Range Filtering: Fixed critical bug where date range filters were not working correctly
    - Previously, when both `date_from` and `date_to` were specified, the second filter would overwrite the first
    - Now uses proper WooCommerce query approach with post-filtering for combined date ranges
    - Single date filters (from OR to) use native WooCommerce date\_created parameter
    - Combined date range filters use PHP-level post-filtering to avoid WooCommerce HPOS incompatibility
    - Orders are now correctly filtered by the complete date range
- Export now respects both start and end dates when filtering orders
- Fixed TypeError from incompatible date query format with WooCommerce HPOS

**Changed**

- Improved `get_orders_batch()` method with hybrid approach: native query for single conditions, post-filtering for ranges
- Date filtering now uses time boundaries (00:00:00 for start, 23:59:59 for end) for accurate daily filtering
- Added custom parameter handling (\_wexport\_date\_from, \_wexport\_date\_to) for post-filtering logic

### 1.4.8 - 2025-11-16

[](#148---2025-11-16)

**Changed**

- UX Improvement: Replaced browser alerts with user-friendly flyout notifications
- Alerts in template loading logic now display as non-intrusive notification popups
- Notifications support multiple types: success, error, warning, and info
- Auto-dismiss notifications after 3-5 seconds with manual close option
- Improved visual feedback with color-coded notification types

**Added**

- New notification system with dedicated CSS styling (`admin/css/notifications.css`)
- Notification JavaScript utility (`admin/js/notifications.js`) with `WExportNotifications` API
- Smooth animations for notification appearance and dismissal
- Responsive design for mobile and tablet devices
- Notification types: success (green), error (red), warning (orange), info (blue)
- Template Management Improvements:
    - Display currently loaded template in Template section with visual indicator
    - "Edit" button for templates to rename and update their configurations
    - Visual highlighting of currently loaded template in manage modal
    - Track currently loaded template state across sessions

### 1.4.7 - 2025-11-16

[](#147---2025-11-16)

**Fixed**

- Simplified: Removed unnecessary `plugin_version` and `operation_type` columns from logging table
- Cleaned up database schema to only store essential export information
- Removed complex migration logic that was causing database issues

**Changed**

- Export logger now only tracks: filters, file\_path, rows\_exported, export\_format, user\_id, status, error\_message
- Removed `log_export()` parameters: `operation_type`, `plugin_version`
- Removed `migrate_table()` method and all related migration logic
- Simplified table schema to reduce complexity

### 1.4.6 - 2025-11-16

[](#146---2025-11-16)

**Fixed**

- Critical: Database migration now properly adds missing `plugin_version` and `operation_type` columns on export
- Simplified migration logic to use direct ALTER TABLE statements instead of dbDelta
- Migration now runs automatically before every export to ensure columns exist
- Added error logging for migration failures

**Changed**

- Migration function now checks column existence with `INFORMATION_SCHEMA` before attempting to add
- Export AJAX handler now calls `migrate_table()` before processing exports
- Transient-based migration caching on page load to avoid performance issues

### 1.4.5 - 2025-11-16

[](#145---2025-11-16)

**Added**

- Auto-load default template - When a user sets a template as default, it now automatically loads on page visit
- Default template ID is passed to frontend and loaded on admin page initialization

**Changed**

- Template initialization now checks for and loads the default template if one is set
- Updated frontend data localization to include `defaultTemplateId`
- `loadDefaultTemplateIfSet()` method added to template manager for automatic loading

### 1.4.4 - 2025-11-16

[](#144---2025-11-16)

**Fixed**

- Critical: Database table migration not running on existing installations
- Added automatic database migration on every plugin load to ensure missing columns are created
- Fixed `plugin_version` and `operation_type` columns missing on tables created with older versions

**Changed**

- Plugin now runs `migrate_table()` on `plugins_loaded` hook in addition to activation
- Ensures backward compatibility with all existing installations without manual SQL intervention

### 1.4.3 - 2025-11-16

[](#143---2025-11-16)

**Fixed**

- Critical: Custom code mappings source field was always empty when saving templates
- Fixed form data collection to properly read from the correct input element (text vs select)
- For taxonomy types, now correctly reads from `.custom-code-source-select` instead of generic `.custom-code-source`
- For meta types, correctly reads from `.custom-code-source-text`

### 1.4.2 - 2025-11-16

[](#142---2025-11-16)

**Fixed**

- Fixed custom code mappings not being properly serialized when saving templates
- Improved template save AJAX request to use FormData API for proper nested array handling
- Added comprehensive debug logging to track data flow during template save operations

**Changed**

- Template save now uses FormData API instead of plain object spread
- Enhanced error reporting in browser console and server logs
- Added detailed logging for custom codes array processing

### 1.4.1 - 2025-11-16

[](#141---2025-11-16)

**Fixed**

- Critical: Template system now correctly loads custom column mappings when loading saved templates
- Custom code mappings were not being restored when loading templates due to form data mismatch
- Form now properly clears existing custom code rows before loading template rows
- Added null/undefined checks for safely handling template data

### 1.4.0 - 2025-11-16

[](#140---2025-11-16)

**Added**

- Template Management System - Save, load, duplicate, and manage export templates
- New `Template_Manager` class for handling template CRUD operations
- New `Template_Ajax_Handler` class for AJAX template operations
- Template dropdown selector for quick template loading
- "Manage Templates" modal with table view of all saved templates
- Set default template functionality for automatic loading on page load
- Template duplication and deletion capabilities
- Template import/export as JSON for backup and sharing

**Changed**

- Updated admin page to include template management interface
- Added template JavaScript handler for frontend operations
- Plugin version bumped from 1.3.8 to 1.4.0

### 1.3.8 - 2025-11-16

[](#138---2025-11-16)

**Fixed**

- Critical: XLSX export styling methods now compatible with PhpSpreadsheet 1.29+
- Fixed `getFont()` method - now uses `getStyle()->getFont()`
- Fixed `getFill()` method - now uses `getStyle()->getFill()`
- Fixed `getDataType()` method - now uses `getStyle()->getNumberFormat()`
- XLSX header styling (bold, gray background) now works correctly
- Number formatting for decimal values in XLSX files now works

### 1.3.7 - 2025-11-16

[](#137---2025-11-16)

**Fixed**

- Important: Product variations now correctly export parent product taxonomy terms
- Variation products now inherit category and taxonomy assignments from their parent product
- Product categories now properly resolve for all product variation types

**Added**

- Automatic parent product detection for variation products
- Proper handling of WooCommerce product variation inheritance in taxonomy extraction

### 1.3.6 - 2025-11-16

[](#136---2025-11-16)

**Fixed**

- Critical: Taxonomy form data not being properly captured during AJAX form submission
- Fixed FormData construction to correctly extract values from taxonomy select dropdowns
- Improved input visibility toggle to use CSS display properties instead of jQuery show/hide
- Taxonomy terms now properly export when selected from the custom code mapping dropdown

### 1.3.5 - 2025-11-16

[](#135---2025-11-16)

**Fixed**

- Critical: Custom taxonomy term mappings showing no values in export
- Improved form validation to properly capture taxonomy select values
- Fixed visibility toggle detection in form data collection
- Added taxonomy validation to prevent silent failures on invalid taxonomy names

### 1.3.4 - 2025-11-16

[](#134---2025-11-16)

**Fixed**

- Critical: Product taxonomy term data not being exported to CSV despite appearing in preview
- Custom taxonomy term extraction now retrieves full term objects instead of only term names
- Both export and preview now access complete term data with proper separators

### 1.3.3 - 2025-11-16

[](#133---2025-11-16)

**Fixed**

- Critical: Custom code mappings not being included in export/preview
- Form data submission now uses FormData API instead of jQuery serialize()
- Properly handles nested array structure for custom codes (`custom_codes[index][field]`)
- Custom code columns and product data now correctly appear in exports

### 1.3.2 - 2025-11-16

[](#132---2025-11-16)

**Added**

- Debug logging for custom code mapping issues
- Browser console logging to show custom codes before AJAX submission
- Server-side error logging for custom code processing (wp-content/debug.log)

### 1.3.1 - 2025-11-16

[](#131---2025-11-16)

**Fixed**

- Bug: Validation error when using taxonomy dropdown selector
- Form validation now checks only the visible input field (text for meta, dropdown for taxonomy)
- Fixed "Please fill in both Column Name and Source" error during preview/export

### 1.3.0 - 2025-11-16

[](#130---2025-11-16)

**Added**

- New Feature: Dynamic taxonomy dropdown selector for custom product code mappings
- `get_available_product_taxonomies()` method to fetch all public product taxonomies
- Smart input type switching in custom codes UI - text input for meta, select dropdown for taxonomies
- Taxonomy labels displayed with technical names for better user clarity (e.g., "Color (pa\_color)")

### 1.2.9 - 2025-11-16

[](#129---2025-11-16)

**Fixed**

- Bug: Product custom metas not included in preview generation
- Custom code mappings now correctly show in preview data
- Preview now matches final export output

### 1.2.8 - 2025-11-16

[](#128---2025-11-16)

**Features**

- CSV and XLSX export support
- Product custom codes mapping (meta and taxonomy)
- Order filtering by date range and status
- Export logging and recent exports display
- Flexible column selection
- Template system foundation

### 1.0.0 - 2025-11-16

[](#100---2025-11-16)

**Initial Release**

- Basic CSV and XLSX export functionality
- WooCommerce order export with customizable columns
- Support for product metadata and custom fields
- Date range and order status filtering
- Export logging to track operations
- Full WordPress and WooCommerce integration
- Security features: nonce verification, capability checks, input sanitization

License
-------

[](#license)

This plugin is licensed under the [GPL v2 License](LICENSE).

---

Made with 💙 by the WooCommerce Custom Order Export community

###  Health Score

36

—

LowBetter than 82% of packages

Maintenance87

Actively maintained with recent releases

Popularity5

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity40

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~16 days

Recently: every ~0 days

Total

7

Last Release

64d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/4c0bdaace73a06876c30b91f86f99e206c4a8fe5bb7a1a1e91f159a5e2c98088?d=identicon)[serkanalgur](/maintainers/serkanalgur)

---

Top Contributors

[![serkanalgur](https://avatars.githubusercontent.com/u/353690?v=4)](https://github.com/serkanalgur "serkanalgur (21 commits)")

---

Tags

woocommerce-pluginwoocoommercewordpresswordpress-plugin

###  Code Quality

TestsPHPUnit

Code StylePHP\_CodeSniffer

### Embed Badge

![Health badge](/badges/serkanalgur-woocommerce-custom-order-export/health.svg)

```
[![Health](https://phpackages.com/badges/serkanalgur-woocommerce-custom-order-export/health.svg)](https://phpackages.com/packages/serkanalgur-woocommerce-custom-order-export)
```

###  Alternatives

[prestashop/prestashop

PrestaShop is an Open Source e-commerce platform, committed to providing the best shopping cart experience for both merchants and customers.

9.0k15.4k](/packages/prestashop-prestashop)[elgg/elgg

Elgg is an award-winning social networking engine, delivering the building blocks that enable businesses, schools, universities and associations to create their own fully-featured social networks and applications.

1.7k15.7k5](/packages/elgg-elgg)[pressbooks/pressbooks

Pressbooks is an open source book publishing tool built on a WordPress multisite platform. Pressbooks outputs books in multiple formats, including PDF, EPUB, web, and a variety of XML flavours, using a theming/templating system, driven by CSS.

44643.1k1](/packages/pressbooks-pressbooks)[rainlab/blog-plugin

Blog plugin for October CMS

17257.7k](/packages/rainlab-blog-plugin)[abydahana/aksara

Aksara is a CodeIgniter based CRUD Toolkit you can use to build complex applications become shorter, secure and more reliable just in a few lines of code. Serving both CMS or Framework, produce both HEADLESS (RESTful API) or TRADITIONAL (Browser Based), just by writing single controller. Yet it's reusable, scalable and ready to use!

1121.2k](/packages/abydahana-aksara)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)