EPOS Stock Verification Tool
Internal web application that turns stock-controller submissions into classified, trackable work instead of inbox attachments.
Overview
Stock controllers produce verification reports. The operational need is not another place to store PDFs — it is a way to know which outlets have been checked, which variances need a person, and what is still outstanding.
The Problem
If verification lives in inboxes, nothing is classified. Outlet names drift, product variances are scanned by eye, and 'done' means someone thinks they looked at it. That does not scale across an estate.
Requirements
- Accept a pasted stock verification report
- Extract outlet information automatically
- Match the outlet to a known location
- Analyse product-level variances
- Classify the submission
- Send variances that need attention into a review path
- Track completed and outstanding submissions
- Export results
My Role
Designed and built the internal tool around the real submission workflow, including matching, classification and the outstanding-work view. No live stock or employee data is shown here.
Approach
- Start from the controller's actual artefact (the pasted report), not from an ideal API that does not exist
- Make outlet matching a first-class step with a fallback when confidence is low
- Classify automatically where the rule is clear; queue for review where it is not
- Give operations a dashboard, not only a successful-parse message
System / Architecture
The application is a workflow: ingest → extract → match → analyse → classify → review → dashboard → export. Each step has a pass/fail that can be inspected. It is an internal operations tool, not a public product.
- 01Paste report
- 02Extract outlet
- 03Match outlet
- 04Analyse variances
- 05Classify submission
- 06Review if needed
- 07Dashboard
- 08Export
Implementation
- Paste-based ingest of verification reports
- Outlet extraction and matching
- Product variance analysis
- Automatic classification with review triggers
- Dashboard of completed and outstanding submissions
- Exportable reporting
Challenges
- Inconsistent report layout and outlet naming
- Deciding which variances are noise vs review
- Keeping the UI fast enough for people who are already mid-count
- Not turning classification into a black box
Outcome
Verification became a tracked process. Submissions can be completed, outstanding or in review — and exported — without reconstructing the week from email.
- Submissions classified instead of parked in email
- Outlet matching done once, consistently
- A dashboard of completed and outstanding verification work
Technologies
What I Learned
- Internal tools should match the artefact people already produce
- Matching is a product problem, not a nice-to-have
- Dashboards for outstanding work change behaviour more than pretty charts
Future Improvements
- Richer audit of classification decisions
- Tighter feed into the stock system of record
- Better handling of unknown or temporary outlets