## TL;DR

Since 3.0, WC_Order properties are protected and need the getter/setter methods: use $order-&gt;get_id(), $order-&gt;get_status(), $order-&gt;get_total() and friends instead of $order-&gt;id style access. Order line items moved to the new classes WC_Order_Item, WC_Order_Item_Product, and WC_Order_Item_Shipping, so iterate $order-&gt;get_items() and read each item with its getters.

## Fix

1. Since 3.0, WC_Order properties are protected and need the getter/setter methods: use $order-&gt;get_id(), $order-&gt;get_status(), $order-&gt;get_total() and friends instead of $order-&gt;id style access.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this WooCommerce 3.0+ feature.
- The symptom matches: how to get order details from a WC_Order object.

## When NOT to use

- Unrelated WooCommerce 3.0+ issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against WooCommerce 3.0+ (mentions 3.0).

## Variant phrasings

### how to get order details from a WC_Order object

## Why it happens

Stack Overflow question (score 144): after the WooCommerce 3.0 update, direct property access on WC_Order objects throws errors, so the old way of reading order details breaks.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- Behavior can change between releases; the linked source reflects the versions above.
- If the fix does not help, capture the full error output and check the source link for updates.