Physical stock and system stock were drifting apart
Scattered inventory and unreliable availability made it harder to know what could confidently be allocated to orders.
Case Study 04 · Inventory · Warehouse · Operations
Inventory Management & Warehouse Optimization
Reconciling approximately 20,000 SKUs and about $200K of warehouse stock through barcode-driven workflows, SQL Server inventory control, vendor-status rules and automatic routing into in-house, clearance or donation inventory.
SQL Server
.NET
Barcode API
Warehouse Operations
01 · Executive overview
The inventory existed. The business needed to know exactly where it was and whether it could be trusted.
Pulse Uniform’s Atlanta warehouse held approximately 20,000 SKUs with an inventory value of about $200,000. Stock had become scattered across storage, making physical reconciliation difficult and reducing confidence in the quantities the business could rely on for order fulfilment.
I designed a barcode-driven reconciliation workflow that connected physical products and boxes back to SQL Server inventory records. The application had to identify a scanned item immediately, show the correct product and image with minimal delay, record every scan in history, and decide which inventory path the item should follow.
The system routed merchandise into three operational destinations: in-house inventory for future orders, clearance inventory for discontinued vendor items, and donation inventory for products with minor defects that could not be sold directly to customers. Vendor status and barcode data were therefore part of the warehouse decision, not just reference information.
Scan, identify, decide and route
Barcode lookup, product verification, vendor-status rules, box assignment and scan history created a controlled warehouse decision flow.
Every reconciled item gained a clear destination
Sellable stock returned to in-house availability, discontinued items moved to clearance, and minor-defect items were separated for donation.
02 · Business challenge
Inventory accuracy is operational only when the warehouse can physically find the product.
The issue was not simply an incorrect quantity in a database. Inventory was physically distributed in ways that made counting, locating and committing products difficult. A useful solution therefore had to connect the database record to the real warehouse location and make product identification practical for the people performing the reconciliation.
Products were distributed across warehouse storage without enough reliable location context.
System quantities could not always be trusted as a direct representation of what was physically available.
The catalog was too large for a manual spreadsheet-based cleanup to remain practical or reliable.
The scan was only useful if the barcode resolved to the correct SKU. Barcode data across 20K+ SKUs had to be cleaned and maintained from multiple sources.
The lookup had to be fast enough to display the matching product and image immediately so warehouse scanning did not become a bottleneck.
The system had to decide whether a reconciled item belonged in in-house stock, clearance, or donation based on business and vendor conditions.
03 · My role
Connect the physical warehouse, the inventory database and the fulfilment decision.
Analyze the warehouse problem
Understand why physical stock, locations and system availability were no longer aligned.
Design the reconciliation process
Create a repeatable scan → verify → count → assign → update workflow that warehouse users could follow.
Build the scanning experience
Surface product details and images so scanned inventory could be verified before reconciliation.
Update SQL Server inventory
Connect physical counting and box assignments to the operational inventory records used by the business.
Build & maintain barcode intelligence
Clean and enrich barcode data for 20K+ SKUs from multiple sources so scans consistently resolved to the correct product.
Design routing & audit history
Apply vendor/product rules to determine inventory destination and retain a history of every scan, item and box assignment.
04 · Warehouse architecture
Turn every barcode scan into an inventory decision with a complete audit trail.
Physical warehouse
OperatorBarcode Scan
Scan the physical item during reconciliation
PerformanceInstant Product Lookup
Resolve the correct item and display product details + image immediately
→
Data & decision layer
Master dataSQL Server + Barcode Database
20K+ SKUs · maintained barcode mappings · product data
Business rulesVendor Status + Item Condition
Check discontinued status and reconciliation condition
→
Disposition & traceability
RouteIn-House · Clearance · Donation
Automatically choose the correct inventory destination
AuditScan History + Box Assignment
Record which item was scanned into which box and when
Barcode quality is foundational
A fast scan means little if the barcode points to the wrong SKU. Maintaining the barcode master became part of the solution.
Vendor data drives warehouse action
A discontinued item could automatically enter the clearance path rather than returning to normal sellable inventory.
Every scan is traceable
Scan history preserved the relationship between the item, the destination box and the warehouse action taken.
05 · Reconciliation workflow
Scan fast, identify correctly, apply the rule, then record exactly where the item went.
01Start
Scan
Read the physical barcode.
02Identify
Resolve
Find the correct SKU in the maintained barcode master.
03Confirm
Verify
Display the matching product details and image immediately.
04Rules
Evaluate
Check vendor status and the physical condition of the item.
05Decision
Route
Send the item to in-house inventory, clearance or donation.
06Trace
Audit
Save the item, destination box and complete scan history.
06 · Barcode intelligence & product verification
The warehouse experience depended on resolving the right product immediately.
Barcode lookup became one of the harder engineering parts of the project. With more than 20,000 SKUs, missing, stale or inconsistent barcode data could cause the scanner to return the wrong product or nothing at all. I worked across multiple data sources to make the barcode database more complete and reliable.
The operator experience also had a performance requirement: after scanning, the correct product information and image needed to appear immediately so the person working through boxes could continue scanning without waiting on the application.
Maintain barcode coverage
Clean and update barcode mappings across the 20K+ SKU catalog using multiple available sources.
Resolve the correct product
Use the scanned barcode to find the matching operational product record reliably.
Show product + image immediately
Keep the scan-to-display path fast enough for high-throughput warehouse reconciliation.
07 · Box assignment & scan history
Every warehouse action remained traceable after the scan.
The system retained the history of each reconciliation scan, including the product and the box to which it was assigned. This created an operational audit trail instead of treating scanning as a temporary screen action.
01Event
Barcode Scan
The physical warehouse action begins with the scanned item.
02Identity
Product / SKU
The barcode resolves to the correct product record in the maintained SKU master.
03Disposition
Inventory Path
The system records whether the item belongs to in-house, clearance or donation inventory.
04Location
Box Number
The selected warehouse box becomes the physical storage reference for that item.
05History
Persisted Audit Record
The complete scan, product, disposition and box assignment is retained for later traceability.
08 · Inventory disposition
Three destinations turned reconciliation into a real warehouse decision.
Reconciled inventory was separated into three operational paths. The system used item condition and vendor status to help determine where merchandise should go instead of returning every scanned unit to one generic stock pool.
Available for future orders
Sellable merchandise that remained part of the active assortment could return to local stock and become available for upcoming order allocation.
Discontinued vendor items
If the vendor database marked an item as discontinued, the system could automatically route it to the clearance box. This inventory could be sold at a lower price without applying the normal vendor MAP-price check used for active merchandise.
Minor-defect inventory
Products with minor defects that were not suitable for direct customer sale were separated into the donation path instead of being mixed with sellable stock.
ScanIdentify Product
→
CheckVendor Status + Condition
→
DecisionChoose Inventory PathIn-house · clearance · donation
09 · From reconciliation to fulfilment
The end goal was not a cleaner database. It was inventory with a known condition, location and business purpose.
Reconciled stock could be treated with greater confidence because each item now had a known product identity, destination path and box history. Active sellable inventory could return to in-house availability, discontinued stock could enter clearance, and minor-defect merchandise could be separated for donation.
BeforeScattered / uncertain stock
→
Inventory exists but does not yet have enough trusted operational context.
ControlIdentify · evaluate · route
→
Barcode, vendor status, condition and box assignment determine the warehouse action.
AfterPurpose-driven inventory
Each unit belongs to in-house fulfilment, clearance or donation with traceable scan history.
10 · Engineering decisions
Where the project connected software design with warehouse economics.
Use physical activity as the reconciliation trigger
Inventory changes were grounded in warehouse scanning rather than another disconnected manual spreadsheet.
Scanning cannot become the bottleneck
Barcode resolution and product-image display had to feel immediate so warehouse operators could keep moving through inventory.
Reliable scanning depends on reliable barcodes
Maintaining barcode coverage across 20K+ SKUs was necessary before the warehouse workflow itself could be trusted.
Improve the operational data already used by the business
The warehouse workflow strengthened the existing inventory system rather than creating another disconnected source of truth.
Inventory disposition should be automatic where rules are known
Vendor discontinuation status could automatically move qualifying merchandise into the clearance workflow.
Every scan should be auditable
The system retained which item was scanned, which box received it and how the inventory was classified.
11 · Technology & platforms
A focused operational stack built around warehouse execution.
| Inventory data | SQL Server |
|---|---|
| Application layer | .NET |
| Warehouse input | Barcode scanning |
| Identification | Barcode master · multi-source barcode maintenance · barcode API · box numbers |
| Operator experience | Product details · product images · scan verification |
| Operational model | Physical reconciliation · vendor-status checks · 3-way disposition · box assignment · scan history |
| Decision inputs | Vendor discontinued status · item condition · inventory eligibility |
| Primary outcomes | Stock visibility · reliable barcode lookup · in-house availability · clearance routing · donation separation · auditability |
12 · Business impact
Turn uncertain warehouse stock into classified, traceable inventory.
Barcode reliability improved
Barcode data across 20K+ SKUs was cleaned and enriched so warehouse scans could resolve the correct product more consistently.
Scanning stayed operationally fast
The scan-to-product experience was designed to show product details and images immediately rather than slowing warehouse throughput.
Sellable stock returned to availability
Eligible merchandise could be placed into local in-house inventory for future order allocation.
Discontinued stock gained a clearance path
Vendor status could automatically route discontinued items into clearance rather than mixing them with normal active inventory.
Minor-defect merchandise was separated
Donation inventory was kept distinct from customer-sellable stock.
Every scan became traceable
History preserved which product was scanned, the box it entered and the inventory action taken.
13 · Product experience
The production workspace connected box operations, item search and inventory routing.
This production screen shows the operational side of the warehouse system. Users can work with a box number, find an item, add or remove inventory, merge boxes and review the products already assigned to warehouse destinations. The interface was designed for the repetitive, high-volume work of physical reconciliation rather than as a reporting-only screen.
01
Production box-management & inventory workspace
01
Box operations
Users can open a box, merge boxes, add inventory or empty a box as physical stock is reorganized.
02
Find item
A dedicated lookup area supports identifying products when warehouse users need to locate or verify an item.
03
Multiple inventory destinations
The workspace presents box/destination inventories side by side, including the clearance workflow and numbered warehouse boxes.
04
Operational controls
Item rows expose quantity, box reference and actions such as print or delete so warehouse changes can be executed directly.
The production screenshot has already been sanitized for public use. It demonstrates the real operational application behind the reconciliation, routing and box-management workflow described above.