Extra Product Options - WordPress Plugin

Extra Product Options Guide for Accurate WooCommerce Option Exports

In this guide, Extra Product Options is covered as an add-on for Export Order Items Pro, not as a standalone storefront field builder. Its role here is to take the data customers entered through WooCommerce Extra Product Options, also known as TM Extra Product Options, and turn that data into something usable in order reports. Below, you will find the installation process, the initial validation steps, field selection, a test order workflow, output verification, common issues, and the cases where this add-on genuinely saves time.

The real value of this product appears when a store sells more than a fixed item and instead offers a configurable product: engraving, size, color, extra services, a customer-uploaded file, custom text, gift wrapping, date selection, or another variable. Without separate handling, those values often end up packed into a general order metadata string. You can read that manually, but it is hard to pass along to production, accounting, fulfillment, or an analytics spreadsheet.

This article is written as a practical guide: first, we will review which dependencies need to be active, then walk through the Export Order Items Pro setup, show a working workflow with Extra Product Options fields, explain how to verify the CSV/XLSX file, and finish with troubleshooting. Exact pricing, promises of compatibility with every third-party extension, and unverified hidden settings are intentionally left out. For an add-on like this, it matters far more to carefully validate the chain of "product field - order - export column - output file."

What Problem This Add-On Solves in a WooCommerce Workflow

WooCommerce has a basic order model: an order contains products, and each product in the order contains quantity, price, taxes, discounts, variation data, and a set of internal metadata. When a store adds advanced product options through a separate plugin, that data also has to be stored somewhere. WooCommerce Extra Product Options creates additional fields on the product page, and the values chosen by the buyer are saved with the order item. The problem begins later, when a manager needs to export those values for a recurring report rather than just view them in the admin area.

Export Order Items Pro already knows how to build reports from order lines, select an order range, filter statuses, configure fields, reorder columns, and export the result in multiple formats. Extra Product Options Addon adds a narrow but important layer to that workflow: it breaks WooCommerce Extra Product Options data into separate fields that you can select in Export Fields. It does not change how the product is presented and does not create new customer-facing fields. What it does is make the report easier to read and manage.

The difference is obvious in a simple example. If a customer buys a personalized mug and selects "Color: blue," "Text: Anna," and "Packaging: gift wrap," it is inconvenient for a manager to receive all of that in one long cell. For a production spreadsheet, it is much more useful to see separate columns for color, text, and packaging. That makes it easier to filter rows, verify required values, send the file to a vendor, and quickly spot missing information.

What the Add-On Does and Does Not Do

Setting the right expectations prevents a large share of future errors. Extra Product Options does not replace WooCommerce Extra Product Options, does not add new field types to the product page, does not control storefront price calculations, and does not fix old orders where the required values were never saved. It works at the reporting stage, when the store already has orders containing customer-provided data.

The confirmed workflow is this: after the add-on is installed and activated, additional options appear in the Add Field dropdown on the Export Fields tab in Export Order Items Pro, provided that fields have already been defined in WooCommerce Extra Product Options. The user then adds the required fields to the report, renames the headers if needed, saves a preset, and runs the export. That is why the practical focus of this guide is not "how to build a nice product form," but "how to get a report people can actually work with."

Why Separate Columns Are Better Than One Combined Meta String

A combined meta string may feel sufficient as long as only one person reads the report. In regular operations, though, three limitations show up quickly. First, the table is hard to filter: you cannot quickly isolate only orders with gift wrapping or only products with a certain engraving text. Second, a long string makes it easier to miss an empty required value. Third, external systems often expect stable column headers, not arbitrary text buried inside a single cell.

Individual fields make the report predictable. For production, you can keep only SKU, product name, quantity, and manufacturing options. For accounting, you can include amounts, taxes, status, and selected paid add-ons. For customer support, you can include the customer name, order number, custom comment, and selected configuration. The same order set can be turned into different reports through Export Order Items Pro presets, and the add-on gives you access to values that were previously hidden deeper in the data.

Who Extra Product Options Is For, and When Another Approach Makes More Sense

This product is useful for stores where extra options are already part of day-to-day operations. If additional fields exist only for cosmetic presentation on the product page and do not affect fulfillment, the add-on may be unnecessary. But if someone uses those values to assemble an order, print a layout, verify option availability, prepare delivery, or report on the popularity of paid extras, a separate export is no longer just convenient. It becomes a way to reduce manual errors.

Good Use Cases

Extra Product Options works especially well for personalization-focused stores: custom apparel printing, named gifts, engraved products, paid upgrade bundles, products with ingredient selection, services with scheduled dates, or accessories with material choices. In those projects, the manager needs more than just visibility inside WooCommerce. They need a compact file they can hand to the person doing the work.

Another strong use case is reporting on add-on services. If the store sells a base product with several paid options, the owner needs to understand which options customers actually choose. Separate columns make it possible to analyze selection frequency, build simple pivot tables, and see where customers are most willing to pay for an upgraded product.

A third use case is support and disputed orders. When a customer says they picked one color but received another, a manager can verify the report with a separate color column much faster than by opening the order, expanding the item metadata, and hunting through it manually. The report does not replace the WooCommerce order as the source of truth, but it does speed up repeated checks.

When the Add-On May Not Be the Right Fit

If the store uses a different extra fields plugin rather than WooCommerce Extra Product Options/TM Extra Product Options, this add-on should not be treated as a universal converter for all metadata. Export Order Items Pro can add custom fields on its own, but the specific ability to parse data into separate fields applies to WooCommerce Extra Product Options data. Other plugins may require standard custom meta fields, a dedicated integration, or a different export tool.

If you need to import orders, sync them across sites, send files to a remote server, build advanced scheduled jobs, or move all store data, it makes sense to compare this product with broader solutions. Extra Product Options Addon is best understood as a small specialized module for an existing reporting stack, not as a replacement for full WooCommerce import-export tooling.

It also does not solve problems with the quality of the fields on the product page itself. If fields are named inconsistently, some required parameters are not actually required, values were changed after checkout, or old orders were created before the options were configured, the report will only show what was saved. That is why you should clean up the Extra Product Options structure and place test orders before using it in production.

What to Check Before Installation

Installing the add-on is simple, but the preparation matters more than the Activate button itself. The product depends on three layers: WooCommerce stores the orders, WooCommerce Extra Product Options creates and saves the extra field values, Export Order Items Pro builds the report, and Extra Product Options Addon adds readable report columns for those fields. If any layer is missing or configured incorrectly, the final file will be incomplete.

Plugins and Admin Access

Make sure WooCommerce is active on the site and that you are working in a self-hosted WordPress installation, not an unsupported environment. For the base Export Order Items Pro plugin, the documentation specifically lists compatibility with self-hosted WordPress, WooCommerce, and a single WordPress site, while WordPress Multisite is marked as incompatible for this product. If your store runs in a multisite network, that is not a reason to invent a workaround. It is a reason to confirm support with the developer first.

Next, verify Export Order Items Pro. It should be installed, activated, and available in the WooCommerce menu. Inside the plugin, the report settings area should open with tabs for filtering, field selection, and output. If you have never run the base export before, create a simple report without the add-on first: a short order range, a few standard columns, and CSV or XLSX format. That separates a core export problem from an extra field problem.

The third required component is WooCommerce Extra Product Options, referred to in the sources as TM Extra Product Options. It should already have fields created either on a specific product or through global forms. The add-on can only expose extra fields in Export Order Items Pro if those fields actually exist. If the store does not yet have a single configured Extra Product Options field, it is too early to expect new report columns.

Test Data Before the First Real Export

An empty store will not show you the real picture. Create or choose a product with several option types: a simple text field, a list or radio field, and a checkbox with an extra charge. Place a test order as a normal customer. After that, open the order in WooCommerce and confirm that the values appear in the product line. If they are not visible in the order itself, the add-on will not magically recover them in the export.

For testing, use values that are easy to spot in a table: "Blue box," "Engraving Test-21188," "Gift wrap." Do not use real customer personal data in tests. A sample name, a test email address, and an internal product are enough for reporting purposes. You can later delete that order or exclude it from production ranges.

HPOS, Caching, and Order Storage Format

WooCommerce is moving toward High-Performance Order Storage, where order data lives in dedicated tables. The Export Order Items Pro changelog includes fixes related to HPOS and order meta field lists, so compatibility should be checked on the current site rather than from memory. Open the WooCommerce settings, check the active order storage mode, and confirm that the base Export Order Items Pro plugin can see the required orders and fields.

Product page caching usually does not affect an export that has already been saved, but it can interfere with test checkout if the customer sees an outdated version of the form. After changing Extra Product Options, clear the site and browser cache, then place a fresh test order. If the store uses object caching or optimization plugins, verify not just the storefront but the actual order in the admin area as well.

Quick pre-installation check: the Extra Product Options field is visible on the product page, the value is saved in the order, Export Order Items Pro can generate a simple report, and the admin user has access to the WooCommerce menu and plugin installation.

Installation and the First Check in the Admin Area

The add-on does not require its own separate page full of advanced settings. According to the official description, it integrates into the WordPress interface and, after activation, adds extra choices to Add Field inside Export Fields for Export Order Items Pro. But that does not mean you should skip validation. A proper initial check shows whether the add-on can see your field structure and whether the base report is working without conflicts.

A Low-Risk Installation Order

1. Create a site backup, or at least a database backup, before installing a new add-on on a live store.
2. Make sure WooCommerce, Export Order Items Pro, and WooCommerce Extra Product Options are already active.
3. Upload the ZIP file through Plugins - Add New - Upload Plugin.
4. Click Install Now, then Activate Plugin.
5. If the product requires license activation for updates and pro features, use legitimate purchase details on the appropriate BerryPress or WP Zone page without sharing them with third parties or placing them in reports.
6. Open WooCommerce - Export Order Items and go to the report settings.

If you have a staging copy of the site, start there. The add-on changes report field availability, not the storefront, so it is convenient to test on a copy with a few orders. The main thing is not to send test files to external teams as if they were real production reports.

Where to Look for the New Fields

Open the Export Fields tab in Export Order Items Pro. In the base workflow of this tab, you can select fields with checkboxes, reorder them by drag and drop, edit headers, and add a custom field through a dropdown. After activating Extra Product Options Addon, the Add Field list should include fields that correspond to WooCommerce Extra Product Options data, as long as those fields are defined in the store.

If the new entries are missing, do not rush to reinstall the add-on. First, verify that actual fields exist in WooCommerce Extra Product Options and that there is a recent order where those fields were filled in. There is no reason for the add-on to expose an empty structure if the source system provided no data or if the field was created but never used in an order. Also make sure you are looking at the Export Fields tab, not order filters or output settings.

The First Report After Activation

For the first test, there is no need to build a large report across the entire store. Pick a short range, include statuses where the test order definitely exists, add standard fields such as Order ID, Product Name, Quantity, and one or two Extra Product Options fields. Choose CSV or HTML for a quick check. HTML is useful for diagnostics, CSV works well in a spreadsheet, and XLSX is helpful for production files, but the Export Order Items Pro documentation warns that it can be corrupted if debug mode is enabled.

After exporting, open the file and verify not just that the columns exist, but that the row mapping is correct. If an order contains multiple products, make sure the option value belongs to the correct product row. If the "one line per order" mode is selected, the extra values may be less useful for production because an order with multiple items gets compressed into one row. For manufacturing reports, line-item-based rows are usually clearer.

How to Configure Export Fields for Real Product Options

The most important part of working with this add-on is not the installation, but the column setup. This is where you decide whether the report becomes a working tool or just another file people still have to clean up manually. Build the configuration around the task: who reads the file, which values they need, in what order, which fields are required, and which ones belong only in a full administrative report.

Choosing Columns Based on the Report's Purpose

A production report usually needs the order number, date, SKU, product name, quantity, selected options, customer comment, and status. An add-on revenue report needs the product, option, amount, coupon, tax, and total. Support usually needs the customer, email, order number, product, selected values, and completion status. Do not force every role into one file if Export Order Items Pro lets you save multiple presets.

Inside Export Fields, add Extra Product Options fields only after the basic order and product identifiers. That makes the report easier to read: first it is clear which row you are looking at, then you can see what the customer selected. If you have three personalization fields, it is better to use human-readable column names such as "Engraving Text," "Packaging Color," and "Card Type" rather than leaving technical internal labels in place, if the interface allows you to edit the header.

Order, Headers, and File Stability

Any table that another department or external system opens later needs to be stable. If "Engraving Text" is in column G today and column K tomorrow, people start making mistakes. Export Order Items Pro lets you reorder fields by drag and drop and save presets. Use that as a contract: one preset, one stable format.

Renaming headers helps, but it should not hide meaning. If a field in Extra Product Options is called "Name" and you rename it to "Text on Product" in the report, make sure it is really used only for that purpose. If one field is reused across different products with different meanings, it is better to revisit the structure of the option forms themselves. Otherwise, the report may look clean while remaining operationally risky.

Order Filters and Product Rows

Field configuration cannot be separated from filters. If the report is for production, it usually makes sense to include only statuses where the order is actually ready to be fulfilled, such as processing, on-hold, or completed, depending on the store's workflow. Do not include failed and cancelled orders in a manufacturing file unless there is a specific reason. WooCommerce documents order statuses separately, and their meaning directly affects which rows belong in the report.

Filtering by products or categories is useful when only some products use Extra Product Options. For example, personalized gifts can be exported separately from regular products. Export Order Items Pro supports line item filtering by categories, product IDs, tags, and fields. That kind of filter does not replace Extra Product Options fields, but it helps narrow the report to the orders where those fields should exist in the first place.

Output Format and Encoding

CSV is universal, but it is sensitive to delimiters and encoding, especially when options include Cyrillic text, quotation marks, line breaks, or emoji. XLSX is convenient for Excel, but it can be more demanding when it comes to clean output. HTML Enhanced is useful for review, but it is not always the right format for sending into an external system. For the first production workflow, pick one format, test it in the application where people will actually open it, and make that part of the staff instructions.

Practical rule: if people will edit the report, use readable headers and a stable column order. If the file goes into a system, prioritize stable column names, a fixed format, and as few unnecessary fields as possible.

How the Data Moves from the Product Field to the Report Column

Understanding the mechanics makes troubleshooting much less stressful. Extra Product Options Addon has a clear responsibility boundary: it does not render the storefront form and it does not calculate the product price on the product page. It comes into play later, when Export Order Items Pro gathers the available report fields. Because of that, every issue can be broken down into stages: the field was created, the field was shown to the buyer, the value was saved in the order, Export Order Items Pro can see the order, the add-on exposes separate fields, and the export file contains the values.

Step 1: The Field Is Created in WooCommerce Extra Product Options

In ThemeComplete Extra Product Options, fields can be created locally on the product page or through global forms. The documentation covers builder mode, sections, fields, labels, price, checkbox/radio/select/text settings, and conditional logic. For export purposes, not every presentation setting matters. What matters is what produces a clear saved value: the label, field type, option set, and whether the field is required.

Try to name fields in a way that will not need decoding later in the report. "Text 1" or "Option A" may feel like temporary labels during setup, but they can later become the basis for an export column. A good field name reduces support overhead before it starts: "Name for Engraving," "Gift Box Size," "Ribbon Color."

Step 2: The Customer Fills the Field and Places an Order

Until a customer places an order using the new field, you do not have a real order item value. If the field was added today, older orders may not contain that value. If the field was optional, some orders may legitimately have an empty column. If conditional logic hides the field for some choices, an empty value may also be normal.

That is why validation requires a controlled order. Choose the product, go through the public side of the site, fill in all required options, and complete checkout with a test method. Then open the order in the admin area and inspect the product line. If the value is not visible in the order, the problem belongs in WooCommerce Extra Product Options or the checkout flow, not in Export Fields.

Step 3: Export Order Items Pro Builds the Report

Export Order Items Pro builds the report using the selected range, statuses, line item filters, and chosen fields. It can show one row per product line or one row per order, include or exclude shipping/refunds/free items, add custom fields, change the output format, and use presets. The add-on extends that set specifically at the field selection stage.

If the base report is empty, first check the date range, order statuses, time zone, end date/time, and product filters. The Export Order Items Pro documentation specifically notes that an incorrect time format and exclusive end date behavior can cause incomplete ranges. That is not an Extra Product Options Addon issue, but it can look like "no values found" if the test order never made it into the report at all.

Step 4: The Add-On Turns Saved Data into Separate Fields

According to the official description, base Export Order Items Pro may already be able to find custom fields in the WooCommerce database, but WooCommerce Extra Product Options data may be stored inside one of those fields. The add-on improves the report by parsing that data into individual report fields. That is where its value comes from: not just "export meta," but expose separate fields that match the options you created.

The limitation follows from the same logic: if a field was deleted, renamed, or never used, the report structure may not match what you expect. When you change Extra Product Options forms, place a new test order and verify the preset. Do not change the names and purpose of live production fields in the middle of a working day without checking them separately.

Practical Workflow: Reporting for a Personalized Product

Let us walk through a concrete example that shows exactly what this product is for. The store sells gift sets. The customer can choose a box color, add a short note for the card, and select gift wrapping. Production needs a file for each product where SKU and quantity are followed by three separate columns: color, text, and packaging. Without the add-on, that data may end up in one combined string, forcing a staff member to copy values manually.

Goal and Preparation

The goal is to get a production-ready report that can be opened in a spreadsheet without manually decoding metadata. Preparation includes active WooCommerce, Export Order Items Pro, WooCommerce Extra Product Options, and Extra Product Options Addon. The product should have these fields configured: a select or radio field for box color, a text field for the note, and a checkbox for gift wrapping.

Before exporting, create a test order. Choose easy-to-spot values: color "Blue," text "Test Gift 21188," and gift wrap enabled. After payment or manual order creation, check the order status. For this example, processing or on-hold works if those are the statuses included in the future production report.

Report Setup Steps

1. Open WooCommerce - Export Order Items.
2. On the filtering tab, set a short date range that definitely includes the test order.
3. Enable only the required order statuses so the report does not include cancelled or failed orders.
4. In line item filtering, keep all products or select the personalized products category.
5. Go to Export Fields and add the base fields: Order ID, Order Date, Product SKU, Product Name, Quantity.
6. Use Add Field to add the WooCommerce Extra Product Options fields made available by the add-on.
7. Rename the column headers so they make sense to the production team.
8. Set the order as follows: order identifiers, product, quantity, then the production option columns.
9. On the Output tab, choose CSV or XLSX, disable unnecessary rows, and keep the header row enabled if people will read the file.
10. Run the export and open the file in the application where it will actually be used.

Verifying the Output

The correct result should be simple: one product row includes the order identifier, SKU, product name, quantity, and three separate option columns. The color column shows the selected color, the text column shows the customer note, and the packaging column shows the selected packaging value. If the order contains two personalized products, each row should keep its own values.

Make sure empty values are explainable. If the field is optional, a blank cell may be normal. If the field is required and it is blank, open the order in WooCommerce. If the value exists in the order but is missing in the report, return to Export Fields and confirm that the correct field was added. If the value is missing from the order, fix the product form or the checkout flow.

A Common Issue When the Form Changes After Orders Exist

Suppose the field was originally called "Card text" and later renamed to "Gift message." Older orders may have saved data in a structure that differs from the new one. That will not always break the export, but it can create confusion around headers and expectations. For stores that generate recurring production files, it is better to change field structures in a controlled way: create a new test order, verify the preset, notify the team, and only then use the new form in live operations.

Workflow checkpoint: four places must match - the field on the product page, the value in the WooCommerce order, the selected column in Export Fields, and the value in the exported file.

Report Quality Settings: Range, Statuses, Format, and Presets

Once the separate fields are showing up, report quality becomes a normal but important part of working with Export Order Items Pro. The add-on handles extra fields, but export accuracy still depends on filters, date range, statuses, row mode, column order, and file format. Errors at this level are often mistaken for an Extra Product Options issue when the real problem is the wrong range or an unsuitable output mode.

Date Range and End Time

The Export Order Items Pro documentation explicitly explains that a custom date range requires the time to be set correctly. An incorrect combination of 24-hour time and AM/PM can produce the wrong range, and the end time in reports may behave as an exclusive boundary. The practical takeaway is simple: for a daily report, it is safer to use clear preset ranges or a time template that has already been validated.

If the report does not include the last order of the day, do not start with the Extra Product Options field. Check the range boundaries first. Open the order, note its date and time, then temporarily widen the range for testing. If the row appears, the problem was the time filter. After that, update the preset so the manager does not have to enter the range manually every time.

Order Statuses

WooCommerce order statuses carry operational meaning. Pending payment is not the same as processing, cancelled is not the same as refunded, and completed does not always mean the product no longer needs attention. For a report that includes Extra Product Options, choose statuses based on the business workflow. Production usually does not need failed orders, while option analytics may benefit from comparing completed and cancelled if that helps explain customer drop-off.

Create separate presets such as "Production - Active Orders," "Option Analytics," and "Return Review." Each preset can have its own status set and column list. That is better than one oversized file where each employee has to decide for themselves which rows to ignore.

Row Mode: Line Item or One Order Per Row

For product options, a line-item row is usually more useful. If one order contains two different products with different Extra Product Options values, separate rows make the report obvious. The "one line per order" mode works better for order-level summaries, but it may hide product-specific details. Use it only when you truly need the order as the reporting unit rather than the individual product line.

Format and Debugging

On the Output tab, do not enable debug mode for live XLSX files. The documentation warns that debug mode is intended for HTML and may corrupt XLSX output. For troubleshooting, run a separate HTML export and inspect which fields and values appear in the report. Then disable debug mode and generate the production file.

Handling Personal Data and External Files Safely

Option exports may seem harmless, but product fields can contain personal data entered by the customer: a name for engraving, an event date, a delivery phone number, a comment, a file, or a greeting message. If the report is sent to production, a print shop, support, or a third-party system, you need to decide in advance which columns are truly necessary. Extra Product Options Addon helps structure the data, but the store administrator still decides what goes into the file.

Keep Only the Columns You Need

Do not include the billing address, phone number, email address, or full order totals in a production file if the person doing the work only needs SKU, quantity, and production parameters. Separate presets in Export Order Items Pro make it possible to build narrow reports for specific roles. That reduces unnecessary data exposure and makes the table easier to read.

If a personalized text field is needed for production, keep only that field and the order number. For an external contractor, you can replace the customer name with the Order ID and route communication through the store manager. This matters especially for gifts, medical products, children's products, and any case where the field content could be sensitive.

Testing Without Real Customer Data

Use test orders to validate the add-on. Do not grab a random real order with customer text and send it to a shared team chat. Build a short controlled test case with sample values. If you need to verify Cyrillic support, use a neutral phrase. If you need to test special characters, add them in a test field and make sure the CSV or XLSX opens correctly.

Rolling Back a Questionable Configuration

If a new preset starts generating confusing files, do not change the product form, field list, and output format all at once. First, roll the preset back to the previous column set, or create a separate preset for testing. Then validate a single test order. A step-by-step rollback is much faster than trying to diagnose several changes at the same time.

This guide does not recommend code-level customizations for this add-on. Public official sources provide enough confirmation for user-facing Export Fields settings, filters, formats, and the general custom field workflow, but they do not expose a stable public hook specifically for Extra Product Options Addon parsing changes. Because of that, it is safer not to invent a PHP snippet and instead work with the built-in fields, presets, and a verifiable export flow.

If Extra Product Options Fields Are Missing from the Report

Troubleshooting should follow the data path, not begin with reinstalling every plugin. The add-on works in a narrow part of the workflow, so the key is to identify the exact point where the value disappears. Below are the most common symptoms in this setup: new fields do not appear, columns are blank, data is collapsed into one cell, the wrong order falls into the range, the XLSX file is corrupted, numeric values show extra decimal tails, or the site is using HPOS.

New Fields Do Not Appear in Add Field

Symptom: the add-on is active, but no additional WooCommerce Extra Product Options fields appear in Export Fields. Possible causes: the required Extra Product Options plugin is not active, no fields have been created, there are no orders with filled values, the wrong screen is open, or a different product options plugin is being used.

Check the product in WooCommerce Extra Product Options, then place a fresh test order and make sure the values are visible in the order item. After that, reopen Export Order Items Pro and check Add Field again. If you are not using ThemeComplete/TM Extra Product Options but another plugin, look for its custom meta through the base Export Order Items Pro features or choose another solution.

The Column Exists, but the Values Are Blank

Symptom: the column header is present, but the rows are empty. The cause may be normal: the field is optional, conditional logic hid it, the order was created before the field existed, or the selected product does not use those options. But it can also be a configuration issue: the wrong range, statuses, preset, or row mode was selected.

Open the specific order and check the product line. If the value exists in the order, temporarily run a short report just for that order or a very narrow date range. Add the minimum set of columns and one Extra Product Options field. If the value appears, the problem was the filters or an overloaded preset. If it still does not appear, check whether the field was renamed or deleted after the order was created.

All Options Stay in One Long String

Symptom: Export Order Items Pro shows a general custom field, but the add-on is not providing separate columns, or those columns were not selected. In many cases, the user added a base custom field from the database instead of the special fields exposed by the add-on. Go back to Export Fields, remove the generic technical meta field from the test preset, and add the individual fields through Add Field.

If the individual fields are missing, verify the dependencies. The add-on does not parse arbitrary data from any plugin. Its confirmed role is to work with fields created by WooCommerce Extra Product Options/TM Extra Product Options. Other sources may require custom field mapping, a different export plugin, or a custom integration.

The Test Order Does Not Appear in the File

Symptom: the values exist in the order, but the export does not even include a row for that order. Check the date range, end time, order status, product filter, category, and whether refund/free/shipping line items are included. In Export Order Items Pro, the end date/time and time format can be a source of unexpectedly incomplete reports. For troubleshooting, widen the range by one day on both sides, then set a precise rule once the cause is clear.

XLSX Opens with an Error or the File Is Corrupted

Symptom: CSV or HTML looks fine, but XLSX will not open. Check debug mode on the Output tab. The Export Order Items Pro documentation warns that debug mode is intended for HTML and can corrupt XLSX. Use HTML for troubleshooting, then disable debug and regenerate the XLSX file for production.

Amounts Show Strange Long Decimal Tails

Symptom: monetary values appear with an excessive number of decimal places. This is not directly related to Extra Product Options Addon. The Export Order Items Pro documentation explains that these tails can appear because of limited floating-point precision in PHP and recommends rounding the output. Check the Output settings and the number format.

Some Fields Behave Differently After Enabling HPOS

Symptom: after changing the order storage mode, Export Order Items Pro no longer sees all order meta, or filters do not behave the same way they did before. WooCommerce HPOS changes the order storage tables, and the Export Order Items Pro release history includes HPOS-related fixes. Check that the base plugin is up to date, review the WooCommerce compatibility mode, and run a simple report without extra fields. If the base order meta is missing, solve the Export Order Items Pro and WooCommerce compatibility issue first, then come back to the add-on.

Do not skip the order check in the admin area. If the value was never saved in the line item, the export add-on is neither required nor able to create it in the report.

How to Maintain the Report After Product Options Change

A working setup does not end with the first successful CSV export. Stores change products, add variants, remove outdated fields, rename labels, enable new categories, and update the order fulfillment process. Any of those changes can affect the export. If the report is used regularly, treat it as a small internal integration rather than a one-time data pull.

Simple Preset Versioning

You do not need complicated documentation. Clear preset names are enough: "Production gift boxes," "Support personalization check," "Monthly add-ons analysis." When the form changes significantly, create a new preset or copy the old one. The name can reflect the purpose, but there is no need to put a date into the article or on a public page. Internally, make sure the team agrees on which preset is the live one.

If Extra Product Options fields change often, add a short checklist before publishing product changes: create a test order, check line item values, update the preset, export the CSV, open the file in a spreadsheet, and verify the columns. That takes less time than fixing dozens of orders after the form structure changes.

Validation After Plugin Updates

After updating WooCommerce, Export Order Items Pro, WooCommerce Extra Product Options, or the add-on itself, run a control export. You do not need to retest the whole store every time. One product with several option types and one test order is enough. If the store moved to HPOS or changed compatibility mode, expand the check: base report, custom fields, Extra Product Options fields, and XLSX/CSV output.

When It Makes Sense to Contact Support

It makes sense to contact support once you have gathered the minimum useful evidence: a list of active dependencies, a screenshot or description of the field in WooCommerce Extra Product Options, the test order number, which fields are selected in Export Fields, which output format was used, whether the value exists in the order admin screen, and exactly what is blank in the file. Do not send the developer real secrets, license keys, or a full file containing customer personal data if a test case will do.

When Extra Product Options Is the Right Choice

Extra Product Options is worth using when the store already relies on WooCommerce Extra Product Options, Export Order Items Pro, and has a real need to see customer-selected options in separate columns. It is especially useful for personalization workflows, production, paid add-on reporting, support, and sending a minimal working file to a contractor. The add-on does not do everything an export system can do, but it solves one narrow problem well: it turns complex option values into a more readable report structure.

Before using it in production, verify the dependencies, create a test order, add the necessary fields in Export Fields, save the preset, open the file in the actual spreadsheet tool, and make sure each column matches the correct product row. If that chain works without manual decoding, you can move to regular use and download Extra Product Options to test it on your own site.

If you need universal import-export tooling, advanced automated file delivery, support for another product options plugin, or order migration between sites, compare alternatives before rollout. Within its niche, Extra Product Options works well precisely because it keeps the scope focused: it adds the missing bridge between product fields and the order line report.