Business search usually begins with incomplete information. A customer remembers part of a reference, a staff member knows a delivery suburb or a caller uses an old trading name. A useful search interface anticipates those clues and explains the results. Filters should narrow the work without making records seem to vanish. Start by observing what people type when they are trying to answer a real question.
Identify the clues that matter
Consider a Launceston supplier looking for an order while a customer is on the phone. Staff might have the order number, customer name, contact email or delivery address. Decide which fields are searchable and how exact identifiers differ from broad text matches. Show enough context to distinguish similar records, such as the customer, date and status. Do not return a row labelled only with a reference that means nothing to the caller. If an old name is retained as an alias, explain which current record it belongs to.
Make filtering visible and reversible
A search can appear broken when an unnoticed status filter excludes the desired record. Display active filters near the result count and offer an obvious way to remove each one or reset the view. Distinguish no matches from no permission and from a loading failure. Where useful, preserve search state in the page address so a colleague can open the same view. MDN documents URLSearchParams for working with URL query strings. Avoid putting sensitive search terms into shared links or addresses without considering their visibility and purpose.
Support comparison before action
Search results are a decision surface. Staff need to determine whether a record is the correct one before editing, merging or contacting someone. Highlight the matched information in a readable way and make inactive records clearly distinguishable. Decide whether search should include archived items by default or through an explicit option. A broad default may overwhelm daily work; an overly narrow default can lead staff to recreate existing records. Use examples from the business to choose the balance, then label the scope of the search clearly.
Build a small search acceptance set
Collect a dozen fictional queries representing exact references, partial names, spelling variation and archived records. Document the expected outcome for each. Include a query that should return nothing and one with several plausible matches. Check:
- The fields searched are explained where staff need that context.
- Active filters and result counts remain visible.
- Opening a record and returning preserves useful search state.
- A person can identify the right record without opening every result in turn.