WooCommerce 11.1 stops showing a shipping address in the admin order summary when an order needs no fulfillment. The Store API still retains billing-derived shipping data for compatibility. Extensions that read the admin screen, order object, REST response, email, export, fulfillment feed, or phone fallback can therefore observe different but intentional shapes.
Use this for stores selling downloads, memberships, bookings, licenses, virtual services, mixed carts, subscriptions, ERP exports, CRM sync, fraud checks, accounting feeds, and custom order screens.
Quick answer
Create virtual-only, physical-only, and mixed synthetic orders with distinct billing and shipping values. Record what appears in the classic and HPOS admin screens, order object, Store API, authenticated REST API, emails, CSV exports, webhooks, and downstream integrations. A virtual-only order should not present a meaningless shipping summary to staff, but compatibility data must not be mistaken for a fulfillment instruction. Update display and export logic to ask whether the order needs shipping before using the address.
Test scenarios to run
Run the same controlled fixture across these branches. Write down the expected result before testing so a surprising response is easy to identify.
| Scenario | Fixture | Expected result |
|---|
| Virtual only | Download plus billing phone | No admin shipping summary |
| Physical only | Distinct shipping address | Shipping summary remains |
| Mixed cart | Virtual plus shippable item | Physical destination remains |
| API consumer | Billing-derived compatibility data | No false fulfillment |
Diagnostic table
Use this table to connect the observed behavior to evidence and a verification step.
| Action | Evidence | Verification |
|---|
| Freeze three address fixtures | Record WooCommerce version, HPOS state, checkout type, product virtual and downloadable flags, address source, phone source, payment method, email template, export plugin, webhook version, and fulfillment consumer. | Admin, API, email, export, webhook, and integration results match the written matrix. |
| Compare every representation | Build virtual-only, physical-only, mixed, refunded, subscription-renewal, guest, and account checkout fixtures with deliberately different billing and shipping values. | Virtual-only orders do not create shipping labels or fulfillment tasks. |
| Find fulfillment assumptions | Compare admin display, order object getters, Store API response, REST response, webhook payload, email, CSV, PDF invoice, CRM row, and fulfillment request. | Physical and mixed orders retain the correct destination and contact data. |
| Gate shipping by order behavior | Search custom code for assumptions that a populated shipping field always means physical fulfillment or that a hidden admin field means the stored value is empty. | Tax, fraud, invoice, support, and refund workflows remain correct. |
What to check first
- Record WooCommerce version, HPOS state, checkout type, product virtual and downloadable flags, address source, phone source, payment method, email template, export plugin, webhook version, and fulfillment consumer.
- Build virtual-only, physical-only, mixed, refunded, subscription-renewal, guest, and account checkout fixtures with deliberately different billing and shipping values.
- Compare admin display, order object getters, Store API response, REST response, webhook payload, email, CSV, PDF invoice, CRM row, and fulfillment request.
- Search custom code for assumptions that a populated shipping field always means physical fulfillment or that a hidden admin field means the stored value is empty.
- Change downstream decisions to use order-needs-shipping logic, then retest address privacy, tax, fraud, email, invoice, and fulfillment behavior.
Field notes
- Write the pass condition before changing anything and keep one repeatable synthetic fixture for the full test window.
- Record exact versions and UTC timestamps because deployments, caches, retries, scheduled actions, and background jobs can change the evidence.
- Test the public path and the stored server-side result, not only an admin preview, isolated command, or API response.
- Repeat verification after the relevant cache, queue, cron, webhook, and observation window has completed.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
wp eval '$o=wc_get_order(<order_id>); echo json_encode(["needs_shipping"=>$o->needs_shipping_address(),"billing_phone"=>$o->get_billing_phone(),"shipping_city"=>$o->get_shipping_city()]);'
curl -sS https://example.com/wp-json/wc/store/v1/order/<order_id>
Why this usually happens
- An integration equates a nonempty shipping object with a package that must be sent.
- A support procedure trusts the admin summary without checking the order object.
- A phone fallback enters an export even though no carrier needs it.
- A mixed-cart test is skipped because virtual and physical products are tested separately.
Decision rule
Approve the update only when virtual-only orders hide irrelevant admin shipping details, physical and mixed orders keep correct destinations, and no downstream consumer creates fulfillment from compatibility-only data.
Production verification checklist
- Admin, API, email, export, webhook, and integration results match the written matrix.
- Virtual-only orders do not create shipping labels or fulfillment tasks.
- Physical and mixed orders retain the correct destination and contact data.
- Tax, fraud, invoice, support, and refund workflows remain correct.
Safe fix order
Use a sequence that makes each result easy to prove. Stop when new evidence changes the scope or owner of the problem.
- Freeze three address fixtures
- Compare every representation
- Find fulfillment assumptions
- Gate shipping by order behavior
- Retest exports and privacy
Mistakes to avoid
- Changing production before recording exact plugin versions, UTC timestamps, a stable fixture, the expected result, and a tested rollback point.
- Treating one successful screen as proof while stored records, logs, queues, caches, emails, APIs, and downstream systems remain unchecked.
- Testing only as an administrator instead of using the role, device, locale, cache state, payment state, and failure branch that customers reach.
- Leaving temporary exclusions, debug output, test accounts, broad permissions, or one-off repair code active after verification.
Questions teams ask during testing
Can I run this directly in production?
Begin with read-only evidence and use staging for package, database, checkout, form, permission, or security changes. If a production canary is necessary, make it identifiable, reversible, monitored, and unable to expose personal data or charge a customer.
How do I avoid a false positive?
Repeat the same fixture with the same versions, role, URL, locale, cache state, and integrations. Compare browser, stored, API, and log evidence instead of relying on one screen.
What should the evidence packet contain?
Keep UTC time, exact versions, synthetic record ID, expected result, actual result, relevant log lines, change made, rollback point, owner, and final verification. Redact secrets and personal data.
When is the test complete?
Close the work when the primary path passes, failure branches are understood, stored and downstream records reconcile, temporary changes are removed, and monitoring covers the next update.
What to tell the client or owner
Give the owner a concise packet with the affected workflow, exact versions, UTC test time, fixture ID, expected result, actual result, key logs, change made, rollback point, final result, unresolved risks, owner, and next review date. Remove credentials and personal data before sharing it.
When HandL WP should help
Bring in help when this affects leads, checkout, search visibility, security, paid media reporting, or a client production site. HandL WP can trace the issue through WordPress, hosting, cache, tracking, and Search Console, then verify the workflow after the technical fix.
If this is active on a production site, have HandL WP test WooCommerce order compatibility.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references