We ran the same WooCommerce 9.8.0 → 11.3.0 jump again, this time on the classic checkout shortcode. The order, the totals and the stored order were all unchanged. The checkout page changed by only 3.1%, and every other page by 0%. The most interesting change didn't show up in the screenshots at all: the checkout gained a new field.
Our first report tested the block checkout, which new stores get by default. A reader here asked whether we'd test the classic [woocommerce_checkout] shortcode next, since that's where custom CSS and checkout-field plugins tend to live. Older stores are much more likely to still use it.
The test setup
Same sandbox as last time, with one difference: the checkout page uses the classic shortcode instead of the Checkout block.
| Setting | Value |
|---|---|
| WooCommerce | 9.8.0 → 11.3.0 |
| Theme | Storefront 4.6.0 → 4.6.2, default sidebar |
| Checkout | Classic [woocommerce_checkout] shortcode |
| Products | 1 simple product, 150,000 VND |
| Shipping | Flat rate, 30,000 VND |
| Payment | Cash on delivery |
Since the first report, the test checks a few more things, most of them suggested by readers. After each test order it reads the order back from WooCommerce and compares its status, total and shipping with what checkout showed. It also saves the list of checkout fields before and after the update, and compares the two lists.
Results
The run ended as a WARN. Nothing broke, but there were two things a person should look at.
| Check | Before (9.8.0) | After (11.3.0) | Verdict |
|---|---|---|---|
| Test order placed | Yes | Yes | ✅ PASS |
| Order total | 180,000 VND | 180,000 VND | ✅ PASS |
| Shipping | 30,000 VND | 30,000 VND | ✅ PASS |
| Stored order (status, total, shipping) | Processing, matches | Processing, matches | ✅ PASS |
| Home, shop, product, cart pixels changed | — | 0% | ✅ PASS |
| Checkout page pixels changed | — | 3.1% | ⚠️ WARN |
| Checkout fields | 19 | 20 | ⚠️ WARN |
The whole run took 97 seconds. About 40 of those went on WooCommerce's database update, more on that below.
What changed on checkout
The layout stayed in two columns. The block checkout stacked into one column in our first test, but that came from a breakpoint change inside the Checkout block, which the classic shortcode doesn't use. Two small things changed on screen:
- A new heading. "Additional information" now sits above the order notes field. That pushed the notes down and made the page 55 pixels taller, which accounts for most of the 3.1%.
- A renamed label. In the order summary, "Shipping" now reads "Shipment".

Classic checkout before (9.8.0), after (11.3.0), and the changed pixels in red: the new "Additional information" heading and the "Shipment" label.
If a store has custom CSS for the order notes area, or a translation that expects the word "Shipping", those are the two places to check.
The field a screenshot can't see
The field comparison found one new checkout field after the update: shipping_phone, a phone number for the shipping address.
| Field list | Before (9.8.0) | After (11.3.0) |
|---|---|---|
| Billing fields | 9 | 9 |
| Shipping fields | 7 | 8 (new: shipping_phone) |
| Other (ship-to checkbox, order notes, payment method) | 3 | 3 |
You won't find it in the screenshots. The shipping fields only appear when the shopper ticks "Ship to a different address?", and the test order ships to the billing address. So a pixel comparison can't catch this change, however low the threshold.
This is why we added the field comparison. A reader made the point on our first post: a missing field, like a VAT number or a delivery date added by another plugin, can change only a few percent of the page, or nothing at all if it's hidden. Comparing the list of fields catches it exactly. A missing field is now a FAIL and a new one is a WARN.
If you manage checkout fields with a plugin, check whether it knows about the new shipping phone field, and whether you want shoppers to see it.
Block vs classic, side by side
| Same jump, 9.8.0 → 11.3.0 | Block checkout | Classic checkout |
|---|---|---|
| Order, totals, shipping | Unchanged | Unchanged |
| Checkout pixels changed | 12.1% | 3.1% |
| Checkout layout | Two columns → one (next to the sidebar) | Still two columns |
| Empty cart pixels changed | 6.8% | 0% |
| New checkout fields | Not compared yet in that run | shipping_phone |
The classic checkout looked calmer on screen, but it wasn't untouched. If you only compared screenshots, you'd have missed the one change that adds something to the form.
Wait for the database update to finish
Another reader suggestion: after a big version jump, look at WooCommerce → Status → Scheduled Actions. After this update, WooCommerce queued 45 database update jobs. They normally run in the background through WP-Cron. Our staging copy turns WP-Cron off, so background jobs can't send emails or fire webhooks, which means these jobs would never have run either. The test now runs them before checking the updated store. Here they took 39 seconds, and none failed.
On your own staging site, check that this queue is empty before you test checkout. Otherwise you may be testing a store that is only partly migrated.
Two more steps for the checklist
The checklist from the first report still applies. These two steps go between running the database update and placing the second test order:
- Wait until WooCommerce → Status → Scheduled Actions shows no pending database update jobs.
- Compare the list of checkout fields before and after, including the hidden shipping fields, not just the screenshots.
About UpdateDrill
UpdateDrill rehearses WooCommerce updates on staging. It places a real test order before and after, reads the order back from the store, compares fields and screenshots, and rolls staging back on a failure. I'm building it, and it's in early access. If you look after WooCommerce stores, request a free check and we'll run one update rehearsal on a store of your choice.
Originally published at updatedrill.com.

