WooCommerce orders contain standard information such as customer details, products, payment and shipping data. Operational teams often need additional information that does not fit naturally into those standard fields: a controlled fulfillment attribute, an internal assignment, a delivery-related date or a support classification. When that information is stored consistently, staff can review orders more quickly and use it in the administration workflow.
WooCommerce custom order fields provide a way to keep this additional information at order level. The documented WooCommerce Admin Custom Order Fields extension can display values in the Orders dashboard and configure them for searching, filtering or sorting. This article explains how to plan and create fields, choose suitable types, distinguish structured metadata from order notes, and test the resulting workflow. The documented behavior applies to that extension; other plugins that store order metadata may work differently.
What WooCommerce Custom Order Fields Are—and How They Differ from Order Notes
Custom order fields store structured information that is not covered by standard WooCommerce order fields. The documented extension adds fields for order details, notes, dates and other values, with the aim of centralizing order information in the administration area. The values are stored as order metadata. For this extension, the documentation identifies the meta-key pattern as _wc_acof_{id}, which is specific to the documented extension rather than a universal WooCommerce pattern.
WooCommerce’s single order page also includes a Custom Fields panel for information outside the standard order fields. However, Admin Custom Order Fields is an extension and should not be presented as part of WooCommerce core. Core order-management screens and other plugins may expose different controls.
Structured values versus chronological notes
A custom field is most useful when the store needs a repeatable value that staff can review, search or filter. An order note serves a different purpose: it records events, internal references and free-form communication. For example, a controlled support classification can belong in a field, while a dated explanation of a customer-service event may belong in order notes.
Keeping these functions separate makes the workflow easier to understand. Do not use a custom field as a replacement for an order status, payment record, shipping record or customer-facing order note unless the workflow has been deliberately designed and tested.
Common Use Cases for Structured Order Data
Custom fields can support practical fulfillment, support and administration workflows when the information is truly order-specific. Possible examples include a controlled fulfillment attribute, an internal assignment, a delivery-related date or a support classification. These are practical examples, not a universal WooCommerce schema. The documentation does not define one field list for every store or industry.
The main benefit is visibility. Selected values can be displayed in the WooCommerce Orders dashboard, allowing staff to see operational information while reviewing orders. A field can also provide a consistent value for a decision that would otherwise be hidden in free-form notes or recorded with different spellings by different team members.
From operational need to field definition
Start with the decision the field must support. Ask what staff need to know, who maintains the value and where it must be visible. Then check whether the information already belongs to standard WooCommerce order data. If it does, avoid creating a duplicate custom field.
Give each field one clear operational purpose. A small set of well-defined fields is easier to maintain than a large collection of overlapping values. Also decide whether the information is administrator-facing only or whether it may be shown on the customer’s order details page, in order emails or in exports. Internal fulfillment labels, fraud-review information and staff-only instructions should not be exposed unintentionally.
How to Create a Custom Order Field in WooCommerce
For the documented WooCommerce Admin Custom Order Fields extension, begin by installing and activating the extension. Then open WooCommerce > Custom Order Fields and choose Add Field. Define a clear label and description so staff can understand the value without consulting separate instructions. Next, select the field type and configure the available attributes for dashboard visibility, filtering, sorting and customer or email display.
After saving the field, update a test order and verify the complete result. Check that the value can be entered as intended, appears in the expected administration area and behaves correctly in the Orders screen. If the field is meant to be searched or filtered, test those actions with a known value. If it is intended only for administrators, review customer order details and email settings before using it on live orders.
The exact interface depends on the solution being used. The extension provides a field-creation workflow, while the WooCommerce single order page separately provides a Custom Fields panel for data not included in standard order fields. Do not assume that every plugin creating order metadata offers the same field types, search behavior or visibility controls.
Configuration decisions to make before saving
Make the operational decisions before the field becomes part of daily order handling. The label should communicate the stored value, and the description should clarify its purpose. Dashboard visibility should be enabled when staff need the value during order review, but not every field must occupy the main workflow.
Filtering and sorting should be selected only when they support a meaningful task and the field type allows it. Decide separately whether customers should see the value on their order details page or in emails. Administrator-facing data should remain internal unless there is a deliberate reason to expose it.
Use test orders or a staging site to check the configuration before applying it to live operational processes. This is especially important when search, filtering, exports or connected automation depend on the value being saved in a particular way.
Choosing the Right Field Type
The documented extension supports Text, Text Area, Radio, Select, Checkbox, Multiselect and Date fields. Choose the type according to the information being stored and the way staff will use it. Text is suitable for a short value that does not fit a predefined list. Text Area is intended for longer content that is less naturally represented as a controlled option.
Radio and Select are useful when one controlled value is required. Checkbox and Multiselect allow multiple values when more than one option may apply. Date is intended for date-based operational information. Controlled choices can reduce inconsistent spellings and make filtering more useful; this is practical workflow guidance, not a universal WooCommerce requirement.
Controlled fields and the sorting limitation
Field types do not provide identical dashboard behavior. In the documented extension, Checkbox and Multiselect fields can be used for filtering but cannot be used for sorting. That limitation matters when designing a workflow that needs a predictable order in the dashboard.
If staff need one controlled value, Select or Radio may be a better fit for the intended process. If they need a date-based value, Date may be appropriate. These choices should still be verified in the actual configuration because behavior belongs to the selected extension and field settings, not to all plugins that store order metadata.
How Search, Filtering and Dashboard Columns Work
The WooCommerce Orders screen supports searching, filtering and sorting available order information. Extensions may add order data beyond the core columns. In the documented Admin Custom Order Fields extension, a custom field can be displayed in the Orders dashboard and configured for filtering or sorting where supported.
Search is also available for saved custom-field values in the documented extension. After a custom field is added to an order and the order is updated, its value is included in order search and can return that order as a result. This means the field can support a practical lookup workflow, provided staff save the value consistently.
Filtering and sorting depend on field configuration and type. Checkbox and Multiselect can be filtered but cannot be sorted in the documented extension. Other plugins that create order metadata may not provide the same behavior. The presence of metadata alone does not prove that it is searchable or filterable in the Orders screen.
Available columns are not identical in every installation. WooCommerce documentation describes Screen Options for controlling visible columns, while extensions, themes or customizations may add additional order data. If a field is not visible where expected, review the extension configuration and Screen Options rather than assuming the value was not saved.
What to verify in the Orders screen
Use a test order to validate the workflow in a fixed sequence:
- Confirm that the field is visible in the location where staff expect to find it.
- Enter a known value, update the order and check that the value remains saved.
- Search for the saved value and confirm that the test order is returned when the documented extension is in use.
- Verify that the selected field type supports the intended filtering or sorting behavior.
- Check Screen Options and extension settings if the expected column is not visible.
Repeat the test after changing visibility or field-type settings. Search and filtering should be treated as workflow features that require verification, not as automatic properties of every WooCommerce order metadata solution.
A Practical Metadata Structure and Testing Checklist
A maintainable structure starts with a small, documented set of fields. Each field should have one clear purpose, an identified owner and a defined point in the workflow when its value is created or updated. Record the allowed values for controlled fields so that staff use the same options over time.
Prefer predefined values for statuses, teams, priorities or categories when the workflow depends on consistent filtering. Use Date fields for dates and reserve Text or Text Area for information that genuinely cannot be represented by predefined choices. Keep structured metadata separate from chronological communication stored in order notes.
Display only the fields staff need during order review. Review the field list periodically and remove or retire values that no longer support a real decision, subject to the capabilities of the solution being used. Do not store sensitive personal, payment or authentication data in custom fields unless the store has a documented lawful and secure reason to do so.
Before deployment, test not only data entry but also the full operational path. Check search, filtering, sorting, exports, customer visibility, email display and any connected automation that depends on the value. Use staging or test orders where relevant, and do not move an untested field structure directly into a live fulfillment process.
Deployment checklist for live stores
- Confirm each field’s purpose, owner and allowed values.
- Verify that the chosen field type matches the information and the intended dashboard behavior.
- Review dashboard visibility so staff see the values needed for order handling.
- Check customer order details and email settings before storing internal information.
- Update test orders and verify search, filtering and sorting behavior.
- Confirm that chronological events and free-form internal references remain in order notes.
- Test exports and connected workflows before relying on them for live operations.
- Document any extension-specific behavior rather than assuming it applies to other metadata solutions.
WooCommerce custom order fields are most useful when they capture consistent, order-level information that staff need to find, filter or review. The documented Admin Custom Order Fields extension supports structured values, dashboard visibility, search and configured filtering, while core WooCommerce separately distinguishes custom fields from order notes. Choose the field type deliberately, keep internal data private, and test the workflow before deployment. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.