Back to work

Project story / Product-expiry platform

ShelfIQ

A .NET 8 product-expiry platform for capturing shelf-life data, monitoring product status, verifying barcodes, and keeping product media behind a separate image boundary.

In developmentPrivate sourceNot publicly launched
  • C#
  • .NET 8
  • ASP.NET Core MVC
  • Razor
  • SQL
  • Entity Framework Core
  • Azure Blob Storage

Interactive product path

Follow one product through the current system.

The explorer reflects implemented source boundaries. It does not represent a publicly running product.

Product portal

Register identity and shelf-life data together.

A product combines name, category, production date and time, expiry date and time, barcode, and detected barcode type.

BoundaryValidation keeps production time tied to a production date and prevents production from following expiry.

Capture stage selected.

01 / Product problem

Expiry awareness starts with a trustworthy product record.

A product record is useful only when identity, production date, expiry date, status, and media stay connected. ShelfIQ brings those decisions into one workflow instead of leaving expiry awareness to manual checks.

02 / Current system

Layered around product, verification, and media boundaries.

Built the layered ASP.NET Core application across portal, domain, application, SQL, configuration, integration, and image-serving projects, including product workflows, expiry dashboards, barcode verification, and image handling.

01

Portal

Razor and MVC workflows for account access, dashboard views, product capture, search, editing, and verification.

02

Domain and application

Product, expiry, barcode, image, route, and security behavior separated from the presentation layer.

03

SQL data

Repositories and migrations for users, products, verification results, image metadata, and references.

04

Image boundary

A dedicated image-serving path with resizing, content-type handling, caching metadata, and Azure Blob integration.

03 / Implemented today

The story starts with what the source can already prove.

  • User-scoped product capture and search
  • Expired, expiring-soon, and fresh status
  • Barcode lookup with persisted verification results
  • Dashboard summaries by status and category
  • Separate image references, processing, and blob data

04 / Before public release

Four engineering gates remain before public release.

No launch, customer usage, or production outcome is claimed. These are the next engineering gates.

01

Protect the core rules with automated tests

Add focused coverage for expiry boundaries, product ownership, barcode normalization, verification caching, and image reference behavior.

02

Finish production configuration and security review

Validate authentication, anonymous verification, secret handling, data protection, upload limits, error responses, and environment-specific settings.

03

Remove time-bound assumptions

Make dashboard reporting windows derive from current data and complete the remaining image delivery behavior before launch.

04

Prove the deployed experience

Add deployment automation, observability, accessibility checks, performance evidence, and a controlled release path before calling the product public.

05 / Current position

Implemented product boundaries, with release work still open.

ShelfIQ demonstrates product modelling and full-stack system boundaries today. The page will evolve with the product, and public-delivery evidence will replace the in-development status only after release.

Discuss ShelfIQ