Search Bar
SearchBarComponent (placeholder, matched fields list, chips: array, popover_fields: slot). Replaces the legacy pattern of a tall sidebar of individually-labeled fields (Order #, External Order #, Email, First/Last name, ...) with one prominent fuzzy-matching search plus a collapsed "More filters" popover for rarely-used fields, and compact toggle chips for boolean filters.
Full pattern: search + chips + more-filters popover
State Tabs: the OTHER quick-scope control, for exclusive views
Not every listing page needs Chips. Some need State Tabs instead. Use whichever fits the data: Chips are independent boolean toggles, and any combination can be on at once (e.g. Orders' "Hide freebies" AND "Used coupon" can both be checked). State Tabs are mutually exclusive: a sale is Live OR Upcoming OR Expired, never several at once, so a single-select pill row is the honest affordance. Pick by asking: "can more than one of these be true simultaneously?" Yes → Chips. No → State Tabs. Never mix the two metaphors for the same control.
Listing-page layout convention
To keep every listing page consistent: State Tabs (if the page has one) always sit directly above the Search Bar; Chips (if the page has any) always sit directly below it. Neither control is ever separated from the search bar by other content (stat tiles, headers, etc.); they read top-to-bottom as one continuous "scope, then search, then narrow" unit. A page uses State Tabs, Chips, both, or neither, depending on what its underlying filters actually are, but whichever it uses must sit in this fixed position, not wherever felt convenient on that page.
Why an "uber-search" here (and where it stops)
The identifier-ish fields (order #, external order #, email, first/last name) are all "look up one record by an ID-like value." A single fuzzy-matching search box genuinely simplifies that without losing precision, since any of those values is unambiguous on its own. The remaining fields are different in kind: publisher and sale ID# are attribute filters (narrow a result set, not identify a record) and belong in the popover, not the search string. The four checkboxes are boolean toggles, never search terms, so they render as chips, not text. This mirrors search bars in Linear/Stripe/GitHub: one primary input for "find the thing," a secondary affordance for "narrow what I'm looking at."