[Woo POS][Historical Orders] Order List Search UI and Functionality (Wireframe UI)

[staskus]

WOOMOB-1137

Description

Implemented Order List Search using the same patterns from Products and Coupons:

• Defined a new strategy that calls into separate remote methods that pass a keyword to the orders endpoint, together filtering pos-rest-api
• Reused POSSearchView that is displayed with animation when the search icon is tapped
• Implemented the logic within PointOfSaleOrderListController - not caching search results, showing cached list when the search is cleared, remembering the last selection if the search is closed.

Steps to reproduce

1. Open POS -> Menu -> Orders
2. Confirm the search icon opens the search bar, and the back button returns to the previous state
3. Confirm starting to type shows loading, tapping back or clear button shows cached results
4. Try entering the order number, customer email, or product. Confirm that the appropriate results are shown
5. Confirm pagination works within search
6. Let me know any other observations!

Empty, error states are outside the scope

Testing information

Tested on iPad Air 18.5 Simulator

Screenshots

Simulator.Screen.Recording.-.iPad.Air.11-inch.M3.-.2025-09-05.at.15.25.21.mov

---

• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

[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	pr16089-c07807f
	Version	23.2
	Bundle ID	com.automattic.alpha.woocommerce
	Commit	c07807f
	Installation URL	78o7anq30s2d0

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

[iamgabrielma]

Confirm pagination works within search

I haven't checked the code yet, from testing I found something that I'm not sure if is expected yet: Pagination does not trigger when we close the initial search unless we do a pull to refresh first. Example:

• In my store, I search for supergoop, this shows results up till 18 June
• Close search, scroll to the bottom. Results till 18 june remain and no pagination is triggered.
• It's resolved if we either go back up and pull-to-refresh, then we can navigate to the bottom and pagination triggers again (additional orders till 2 june), or if we exit Orders to the dashboard and go back in

Screen.Recording.2025-09-05.at.15.49.22.mov

I'll check the code now!

[dangermattic]

	1 Warning
⚠️	This PR is larger than 300 lines of changes. Please consider splitting it into smaller PRs for easier and faster reviews.

Generated by 🚫 Danger

[iamgabrielma]

Works as described, LGTM!

[iamgabrielma]

Do we have/want access to totalItems here? I have not tested this much, but consider using the the PagedItems method that parses the responseHeaders as well, ie:

let (orders, responseHeaders) = try await enqueueWithResponseHeaders(request, mapper: mapper)
return createPagedItems(items: orders, responseHeaders: responseHeaders, currentPageNumber: pageNumber) 

[staskus]

Thanks, I'll check it out!

[iamgabrielma]

Just wondering, should we use order-load-all for this test? As is always going to return the 4 orders no matter the searchTerm we pass through. Maybe is there some other file that fits better the test? Or a new response? Not a big deal in any case since we're checking that the function parses the response.

[staskus]

Mm... There's actually not much to test here since our request expects the same type of Order that we already tested in other tests. Search query doesn't produce any special results. Only the second test is meaningful to verify that we're making the request with the expected parameters.

[staskus]

I haven't checked the code yet, from testing I found something that I'm not sure if is expected yet: Pagination does not trigger when we close the initial search unless we do a pull to refresh first. Example:

@iamgabrielma good catch, you're right. AsyncPaginationTracker is in the wrong state after the search is cleared. Maybe need to have two different trackers for search and normal list so they wouldn't interfere with each other.