Back to selected work

ENMOD

A resale workflow turned into
an operational product system.

  • Commerce
  • Internal tool
  • Workflow
  • Automation
  • Product

From a product found in the real world
to a product ready to sell.

ENMOD explores a simple question:

How can a physical sourcing and resale activity be turned into a structured digital workflow?

Instead of treating the storefront, inventory and administration as separate problems, the project connects them into one operating system.

01 / The problem

The store is only
the visible part.

A resale activity does not begin when a product appears online.

Before publication, a product has to be identified, described, categorized, priced, assigned a real quantity, prepared for delivery and integrated into the store.

ENMOD was designed around that complete workflow.

Public storefront
ENMOD public storefront: new arrivals, deals and last units
Public storefront
ENMOD storefront categories and concept section

02 / Two sides of the same product

One product.
Two environments.

ENMOD public storefront: new arrivals, deals and last units

Public storefront

The customer-facing experience.

ENMOD back-office dashboard with navigation and operational counters

Back office

The operating environment behind it.

03 / From discovery to decision

Start with
the product.

The workflow can begin directly from a product found in the field.

The interface provides several entry points visible in the product:

  • Take a photo
  • Import an image
  • Enter a code

The goal is to reduce the distance between discovering a physical product and processing it inside the system.

Scanner
ENMOD AI Buyer scanner: scan a product, take a photo, import an image or enter a code

The interface states it plainly: nothing is bought, created or published at this stage.

04 / Quick Drop

Turn a physical item
into structured data.

Quick Drop brings the information needed to prepare a product for publication into one workflow.

From the screenshots, the interface handles:

  • 01Photos
  • 02Product information
  • 03Brand / reference / EAN
  • 04Category
  • 05Condition
  • 06Price
  • 07Real stock quantity
  • 08Delivery information
  • 09Arrival
  • 10Publication
Quick Drop — 1
ENMOD Quick Drop, upper part: photos, product, brand, reference, EAN, category and condition
Quick Drop — 2
ENMOD Quick Drop, lower part: price, real stock quantity, delivery, arrival and publication

The important part is not the form itself. It is the transformation:

  1. Physical product
  2. Structured information
  3. Managed inventory
  4. Published product

05 / Operations

The system behind
the storefront.

The back office centralizes the operational areas visible in the product:

  • Dashboard
  • Scanner
  • Products
  • Stock
  • Orders
  • Payments
  • Emails
  • Arrivals
  • Categories
  • Delivery
  • Returns
  • SEO audit
  • Compliance

The dashboard provides an operational view of products, drafts, low stock, sold-out products and orders to prepare.

Back office
ENMOD back-office dashboard with navigation and operational counters

06 / Structure the catalog

Structure
before scale.

The administration layer also manages the structure exposed by the storefront.

Categories can be created, organized, activated and prepared with customer-facing introductory content.

This connects internal product organization with the public browsing experience.

Back office
ENMOD categories administration: create, order and activate categories

07 / The workflow

  1. 01Discover
  2. 02Identify
  3. 03Structure
  4. 04Price
  5. 05Stock
  6. 06Publish
  7. 07Sell
  8. 08Operate

The storefront is
what people see.

The real product is
the system behind it.

What this project demonstrates

  • Turning a business process into a digital workflow
  • Designing both customer-facing and internal interfaces
  • Structuring product and inventory operations
  • Connecting physical operations with software
  • Thinking beyond the visible interface
  • Designing tools around real operational constraints
  • Iterating from business need to usable product

My role

  • Product thinking
  • Business workflow definition
  • Functional specification
  • UX / interface direction
  • AI-assisted development
  • Testing and iteration

I didn’t want to build
just an online store.

I wanted to understand
the system required to run it.

Next project →KANAP