SARACHONG
Epic Systems

OCR Packing slip Verification scanner

  • Mobile Design
  • AI Native

Summary

Due to an NDA with Epic Systems, I can't share my actual designs — the visuals shown are recreations I built independently.

I designed the OCR-driven packing slip verification feature on Epic's Rover app, letting procurement teams reconcile thousands of hospital shipments against POs and catch discrepancies in real time — boosting both speed and accuracy for loading dock workers.

I led user research and owned end-to-end design for the feature's workflow, then shaped receiving-workflow standards across Epic's Supply Chain suite — with this project adopted as the reference model going forward.

My Role
Lead Product Designer
Timeline
June 2026 - Aug 2026
Tools
Figma + Figma AIClaudeGoogle ML Kit
Skills
User researchWireframingPrototypingCross-functional collaboration

Background

Hospital loading docks & packing slips

Accurate, efficient shipment logging is critical to hospital inventory management and vendor discrepancy resolution. Central to this process is the packing slip — a physical document itemizing package contents, which workers must manually compare against the corresponding Purchase Order (PO) to confirm the correct items were received.

Today, that means manually reading the packing slip, entering its contents into a computer, and tracking down the matching PO — a tedious, error-prone process that causes receiving delays and inventory discrepancies.

Example packing slip from a hospital medical supplier

Target users

Loading dock receiving staff
Primary user
Prioritizes speed. Scans the packing slip but doesn't always verify shipment contents against it.
Inventory manager
Secondary user
Prioritizes accuracy and item quality. Cross-checks both the packing slip and the actual contents.

Research

Understanding the receiving flow

To understand the current receiving process, I mapped a sample workflow using notes from previous loading dock visits.

Sample receiving-process workflow mapped from prior loading dock visit notes

I then analyzed dozens of packing slips, annotating what counted as "important" information versus what could be ignored.

Since formats varied widely across vendors — no two followed the same structure — I focused on identifying common patterns and categorizing data by importance.

Packing slip annotated to mark important versus ignorable fields

Internal field studies

I also conducted two field studies on Epic's campus — at the Facilities Dock and Culinary Receiving Dock — each revealing a very different process.

Venn diagram comparing the two loading docks. Facilities Dock: manually checks each item in a shipment, crosses off each item on the packing slip with a highlighter, 1-2 hour process. Culinary Dock: doesn't look at the package contents, glances at the packing slip to verify against the invoice, 10-15 minute process. Shared by both: 1. uses the packing slip as verification, 2. stores the physical packing slip in a filing cabinet.

User Interview

Lastly, I led a scenario-based interview with the Director of Receiving at SUNY Upstate Hospital to understand the receiving flow specifically within a hospital setting.

“Unit of measure is a MONSTER between vendors”

“Person-to-person inconsistency is a common occurrence”

“Packing slips can contain information not detailed in the PO”

Design process

Previous design

My developer partner built an MVP prototype to experiment with the backend OCR processes.

Screens from the developer's MVP prototype: shipment list, camera capture, packing slip scan, and PO reconciliation views

This helped me understand how the backend functioned, but the workflow still needed to be redesigned around what users actually needed.

Design Iterations

Using insights from research, I sketched and iterated through each screen and interaction, grounding every design decision in a specific research finding I could point back to.

Before and after of the shipment list screen: the scan entry point moves from a hidden 3-dot menu to a visible one-step camera button
Before and after of the capture screen: single-scan capture gains a toggle to choose between single or batch images
Before and after of the reconciliation screen: a sparse item form becomes a detailed item list that surfaces key shipment information and flags errors

Solution

A rundown of the Packing Slip OCR Scanner

Scan the packing slip

Open the scan feature, align the image, and capture the packing slip.

This creates a new shipment and displays an itemized list of the shipment contents.

View the packing slip

Access the saved image anytime, eliminating the need to physically store the paper copy.

Review the packing slip

OCR errors are indicated with a warning symbol and stored as null values.

Item-level issues are flagged with a comment, signaling a need for further procurement action.

Impact

What resulted from this project

Shaping Epic’s receiving process.

Epic's Supply Chain features are still being standardized ahead of a 2029 release. My research is informing that standardization effort, and my designs are serving as the bridge between procurement and payment flows.

Faster, more accurate receiving

The packing slip tool is projected to cut loading dock receiving time by 25%, with faster discrepancy catching.

Eliminating filing cabinets.

Digital packing slip storage removes the need to file and retrieve hundreds of paper slips by hand.

Key takeaways

Group photo of the summer internship cohort standing and kneeling on a lawn outside an Epic Systems building

Be grounded in design principles.

Between shifting requirements, conflicting feedback, and endless iterations, it was easy to get lost trying to accommodate every edge case.

Returning to a core design principle — "good defaults by design" — helped me stop chasing every "if" and focus on what actually mattered.

Design ownership = fully understanding.

Shipping in 11 weeks meant advocating for design decisions to shape the feature, not just fit around backend functionality.

Leading every field study and interview myself gave me the evidence to explain and defend each design choice with full ownership.

Check out my other projects