[POS Orders] Woo version eligibility checker

[iamgabrielma]

Closes WOOMOB-704

Description

This PR adds an eligibility checker that will handle if we should show the POS badge in order list and order details summary. The only requirement is that the minimum WooCommerce version is 9.9.0, as it's where created_via was introduced.

Initially this check was set directly in the cells for simplicity, as we only checked for feature flag, however as soon we introduced checking the WooCommerce version as well, this would trigger an unnecessary trip to disk for each cell render, so I moved the check up to the view models/datasource.

Testing information

• On a site with WooCommerce 9.9.0+, process a POS order.
• Navigate to orders
• You should see the badge both in order list and order details (this takes a bit to load due other async tasks in the task group)

Screen.Recording.2025-07-07.at.12.01.02.mov

• Turning off pointOfSaleOrdersi1 should hide the POS labels:

[wpmobilebot]

📲 You can test the changes from this Pull Request in WooCommerce iOS Prototype by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce iOS Prototype
	Build Number	pr15868-43f17d9
	Version	22.7
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	43f17d9
	Installation URL	7ld25vd9dvav8

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[iamgabrielma]

We can wait until PluginsService refactoring is done to update this, as won't work as soon as requires the string is the plugin path, rather than the plugin name 👍

[iamgabrielma]

@staskus I just realized Jaclyn is AFK, adding you as well as reviewer 🙇

[staskus]

Thanks!

I think the solution could be improved, especially given that the labels don't appear by themselves the first time orders view is loading.

I would seriously consider keeping a previous conclusion and relying on the existence of the created_via field to determine whether to show or not to show POS. It would simplify the implementation and make the user experience faster.

[staskus]

I agree with this comment https://linear.app/a8c/issue/WOOMOB-704/woo-mobilepos-orders-wc-99-version-check#comment-c873cc1e

It seems simpler just to check the existence of salesChannel label, and no need for additional WooCommerce version checks?

[iamgabrielma]

It seems simpler just to check the existence of salesChannel label, and no need for additional WooCommerce version checks?

That's a good point, and I'm definitely leaning back into it.

The intention of adding the eligibility checker now was to remove the badge from the UI in the edge case that they the merchants happen to revert to a non-supported WC version after already having used POS, however, it is true that if they do so the order model in the DB doesn't change, and the order would still have this property (just not for new orders) so there is really no reason to hide pre-existing badges.

This would simplify the design since there is no need for version check in i1, we just check if the property exists in the order and render the badge in consequence 🤔

[iamgabrielma]

I'll discuss with Sam before updating or closing this issue 👍

[staskus]

It could be good to inject it into OrderListViewModel to have a mocked version within OrderListViewModelTests. I remember encountering a couple of examples where using real implementations slowed down or broke existing tests.

[staskus]

....(this takes a bit to load due other async tasks in the task group)

It takes time to load, but also the rows are not updated after loading is done. Since we're in the UIKit world, we need to manually reload the data once the performEligibilityCheck finishes loading.

ScreenRecording_07-08-2025.17-33-26_1.MP4

[iamgabrielma]

Thanks for the review and suggestions @staskus , we've decided at p1752034631867549-slack-C070SJRA8DP that indeed having a WC version check here isn't necessary, and keeping the previous implementation is fine. I'll close this one 🙇

[staskus]

@iamgabrielma nice, thank you!