WooCommerce checkout field missing from the order
At handover, the awkward bit is rarely the field itself. The customer entered the purchase-order reference, completed checkout, and fulfilment cannot find it in the order. Someone then emails the customer for information they have already supplied, which makes the operation look less organised than it is.

For WooCommerce stores in Dubai, the UAE, Liverpool or the UK, this is worth tracing properly before changing storage code. A visible checkout field is not proof that the value reached the order, survived validation, or appears in the screen your team actually uses.
Start by defining where the value should end up
Write down the field label, its technical field key, whether it is required, and its expected destination. Be specific: order edit screen, fulfilment export, packing slip, customer email, invoice integration, or an API passed to an ERP.
Illustrative scenario: a trade customer enters a purchase-order reference at checkout. The shop receives payment, but the warehouse team sees no reference in its normal order view. There are at least three possible faults there, and they need different repairs.
| Check | What to confirm | What a failure suggests |
|---|---|---|
| Field registration | The field is registered for the checkout currently in use | The field may be rendered by an old template or incompatible extension |
| Submission | The browser sends the entered value with the order request | JavaScript, field naming or checkout implementation is dropping it |
| Validation | The value passes any sanitising or required-field logic | Custom validation may reject, clear or alter the value |
| Order persistence | The value is attached through WooCommerce order APIs | Legacy storage assumptions may not suit HPOS |
| Admin display | The fulfilment view deliberately retrieves and shows the value | The data may exist but is absent from the screen or export |
1. Identify the checkout implementation before touching anything
First establish whether the store uses the classic shortcode-based checkout, Checkout Blocks, or a bespoke checkout route. A field added through an older PHP checkout hook may appear in classic checkout but not behave as expected in blocks. Equally, a block-compatible field extension may have its own registration and persistence route.
Do not assume the desktop page tells the whole story. Check the live checkout path customers use, including any mobile-specific template, translated checkout, or page builder override. A cached checkout page and a recently updated plugin can leave staff testing a different route from customers.
If the symptom appears when country changes or address fields refresh, keep that issue separate. A field can be present but lost during checkout updates for reasons unrelated to its storage. That is the boundary covered in this guide to WooCommerce postcode validation by selected country.
2. Follow one submitted value through the request
Use a harmless test value that is easy to spot, such as PO-TEST-482. Complete a controlled test order without using a live payment method, then inspect the checkout request in the browser tools or the request logging available to the relevant extension.
The useful question is plain enough: does the submitted request contain the field key and its value? If it does not, there is little point arguing about order storage yet. Check the input name, whether JavaScript rebuilds checkout fields after an address update, and whether the field sits inside the submitted checkout form.
A WooCommerce custom checkout field not saved to an order should be traced as five separate stages: registration, browser submission, validation, persistence and display. Treating these as one job is how a minor checkout fault turns into a week of speculative plugin changes.
3. Inspect the saved order through WooCommerce, not old tables
Once the value is confirmed in the submitted request, inspect the resulting order using WooCommerce’s order layer. This matters on stores using High-Performance Order Storage, commonly called HPOS.
WooCommerce’s HPOS recipe book warns that direct reads and writes to WordPress post tables can return stale or unused order data, and directs extensions towards WooCommerce-specific order APIs. In practical terms, use the order object and its supported metadata methods when checking whether the value persisted. Do not jump straight to legacy postmeta writes or disable HPOS because an old snippet looks familiar.
If the store needs a broader diagnosis across custom checkout code, integrations and order handling, a focused WooCommerce website repair review is more useful than swapping extensions at random.
4. Separate stored data from the fulfilment screen
Yes, the field can be saved correctly but absent from the admin screen. This is common where a developer stores a value against the order but never adds it to the order edit display, order list column, packing workflow or export used by operations.
Check the same test order in three places:
- The WooCommerce order record through the supported order API.
- The admin order edit screen used by staff.
- The actual downstream view, such as a fulfilment export or shipping integration.
The practical fix may be display work rather than storage work. That is a better outcome than changing a data path that was working all along.
5. Test the route your team will actually rely on
Run one controlled order through every checkout path still in use. That can include classic checkout, block checkout, a trade-only payment route, a payment link, or a customer account reorder flow. Check the value after payment, not only before the order is submitted.
Use a written test note with the field key, test value, checkout type, order number, expected destination and observed destination. It sounds dull because it is dull. It also prevents the familiar situation where a developer verifies a value in one admin panel while the warehouse still cannot see it in theirs.
For a safer repeatable process, use a controlled WooCommerce checkout order test that checks the order lifecycle rather than merely confirming that the checkout page loads.
What to hand over after the fix
- The field key and customer-facing label.
- Which checkout implementation supports it.
- Where the value is stored through WooCommerce’s supported order methods.
- Where staff can view it, including exports or integrations.
- A short test procedure for the next WooCommerce or checkout extension update.
A visible field, a stored value and an admin display are three separate checks. Get all three documented and fulfilment staff should not have to chase customers for their own reference number.
If one field is holding up order handling, bring one missing field and its expected order destination for a checkout-data review.