Mobile adaptation — Work Ticket Inventory Lookup

The storyboard is explicit that material usage on the ticket needs a clear source path. This screen therefore separates what was already planned for the job from what is being searched now, and keeps the request item path separate when stock is unavailable.

Story flow covered here

• Planned items first. The technician should be able to add detail items from work-order materials or estimate-backed inventory lines.
• Search when needed. If the needed item was not already planned, the technician can search truck stock first, then all inventory.
• Barcode before typing. If the technician already has the item in hand, barcode or shelf-label scan is the fastest add path.
• Request when unavailable. If the item is not available, the technician can request it from the back office without confusing that request with actual ticket usage.

What this screen clarifies

• The planned state is not a search result. It is the list of items already associated with the job.
• The search state is where truck inventory and full inventory lookup results appear.
• The barcode state is a direct add path when the item is physically present.
• The request state is for missing items and should not read like actual usage already added to the ticket.

Voice examples