WP All Export plugin review and common issues

Conditional filtering is a Pro feature. With Pro active, go to the export configuration → Filter section. Add a filter rule: Category → Is → [your category]. If filtering is configured but not working: (1) verify Pro is active (not just the free version); (2) check that the category taxonomy name is correct — for WooCommerce products, the taxonomy is “product_cat,” not “category”; (3) verify products are actually assigned to the specified category (check a few products in WooCommerce to confirm their categories).

Scheduled exports depend on WP-Cron. Check: (1) WP-Cron is functional (use WP Crontrol to verify the export cron job is scheduled); (2) the export destination (FTP, Google Sheets, email) is correctly configured — test a manual export to the same destination to verify credentials work; (3) if using FTP, verify the FTP credentials have write permissions to the destination directory; (4) for email delivery, verify WordPress can send email (test with WP Mail SMTP); (5) increase PHP max_execution_time if large exports time out before completion.

WooCommerce order date filtering in WP All Export uses the order creation date. Check: (1) the date range covers the correct timezone — WooCommerce stores dates in UTC, and date filter interpretation may differ from your local timezone; (2) orders in some statuses (cancelled, failed, pending) may be excluded by default — configure the Order Status filter to include all relevant statuses; (3) if using WooCommerce HPOS (High Performance Order Storage), ensure your WP All Export and WooCommerce add-on versions support HPOS — older versions may not query HPOS tables correctly.

In WP All Export Pro with the WooCommerce add-on, configure the export in “Line Items” mode rather than “Summary” mode. In the export configuration, look for “Export orders with order items” and select to create one row per order item (rather than one row per order with line items in a single cell). Map fields including Order ID, Order Date, Product Name, SKU, Quantity, Item Price, and Total. This format creates a flat table where each product in each order gets its own row — the standard format expected by accounting and fulfillment systems.

With WP All Export Pro and the ACF add-on active, create a new export for your post type. In the field selection step, you see standard WordPress fields alongside an ACF section listing all field groups for that post type. Select specific ACF fields by checking them. In the export preview, configure the column name for each ACF field to match your destination system’s expected column headers. Only selected fields appear in the export — unselected ACF fields are excluded regardless of what data exists in the database.

Yes — this is one of WP All Export’s primary WooCommerce use cases. Configure the order export with fields including: Order Number, Order Date, Customer Name, Email, Billing Address, Payment Method, Subtotal, Tax, Shipping, Total, Payment Status, and Product Line Items. Export to CSV and import into QuickBooks, Xero, FreshBooks, or your accounting software’s import format. For recurring accounting exports, use scheduled exports to automatically deliver the file via email or FTP.

WP All Export actively maintains WooCommerce HPOS (High Performance Order Storage) compatibility. WooCommerce 8.x+ enables HPOS by default, which stores orders in custom database tables rather than WordPress post meta. Ensure both WP All Export and the WooCommerce add-on are updated to their latest versions for HPOS compatibility. Check the plugin changelogs for specific HPOS support version numbers if you encounter issues.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.