From Stockroom to Success

Internship Project @ Tecovas

Project Area

UX, Tech Operations, Training, & Merchandise

Role

Retail Operations Intern

Tools

Figma, Claude Code, Shopify

Scope

May 2026 - August 2026

Replacing Walkie Chatter With An In-House Request Tool

Product requests were called by walkies, an outdated tool. A customer asks for a product,t and an associate radios over for a runner to bring it out from the stockroom. It worked but sometimes didn’t. Walkies created three distinct problems:

Walkies increased noise on the sales floor and reduced time with the customer. Multiple requests coming at once left the stockroom runner confused and helpless.

Walkies are customer-facing, hearing repeated requests and unrelated chatter, and can see firsthand when there is an issue in the stockroom. A tool that was thought of as internal was actually part of the customer experience.

Because requests were verbally made, there was no way of tracking how many requests were coming in, what fulfillment time looks like, and what products are asked for but not available.

Walkies became not just an inconvenience but also a problem that needed to be addressed to better support employees and create a hospitable environment for customers.

Build v.s. buy

Adopting a different company’s tool meant adopting the workflow. This would cap our capabilities and dilute our radical hospitality mission.

The expense behind it wasn’t worth it for us. Our Tech team managed to build this in-house without a price per store, per year.

The flow at its simplest

Floor:
→ Associate submits request
- E.g. Item + Style + Size & Destination

→Waits for delivery and builds a connection with the customer

Stockroom:
→Request appears in queue
→Picks the product
→Delivers product

Status Updates and Delivery

Explicit states - submitted, picked, delivered, mispicked

Allowing for customers to know what is happening when necessary.

MY IMPAct

Pilot Leader Meetings:
- Led numerous pilot store meetings to drive adoption and test new features

QA:
- Working with pilot leaders to identify current issues before a fleetwide launch
- Collaborating with the tech team to publish user feedback
- Testing published user feedback independently and with pilot leaders

Training Materials:
- Created how-to one-pagers for store support and employee onboarding

Current Outcomes - July 2026

From Stockroom to Success

Internship Project @ Tecovas

Project Area

UX, Tech Operations, Training, & Merchandise

Role

Retail Operations Intern

Tools

Figma, Claude Code, Shopify

Scope

May 2026- August 2026

Replacing Walkie Chatter With An In-House Request Tool

Replacing Walkie Chatter With An In-House Request Tool

Product requests were called by walkies, an outdated tool. A customer asks for a product,t and an associate radios over for a runner to bring it out from the stockroom. It worked but sometimes didn’t. Walkies created three distinct problems:

Walkies increased noise on the sales floor and reduced time with the customer. Multiple requests coming at once left the stockroom runner confused and helpless.

Walkies are customer-facing, hearing repeated requests and unrelated chatter, and can see firsthand when there is an issue in the stockroom. A tool that was thought of as internal was actually part of the customer experience.

Because requests were verbally made, there was no way of tracking how many requests were coming in, what fulfillment time looks like, and what products are asked for but not available.

Walkies became not just an inconvenience but also a problem that needed to be addressed to better support employees and create a hospitable environment for customers.

Build v.s. buy

Build v.s. buy

Adopting a different company’s tool meant adopting the workflow. This would cap our capabilities and dilute our radical hospitality mission.

The expense behind it wasn’t worth it for us. Our Tech team managed to build this in-house without a price per store, per year.

Adopting a different company’s tool meant adopting the workflow. This would cap our capabilities and dilute our radical hospitality mission.

The expense behind it wasn’t worth it for us. Our Tech team managed to build this in-house without a price per store, per year.

The flow at its simplest

The flow at its simplest

Floor:
→ Associate submits request

Item + Style + Size

Destination


→Waits for delivery and builds a connection with the customer

Stockroom:
→Request appears in queue
→Picks the product
→Delivers product

Floor:
→ Associate submits request
- E.g. Item + Style + Size & Destination


→Waits for delivery and builds a connection with the customer

Stockroom:
→Request appears in queue
→Picks the product
→Delivers product

Status Updates and Delivery

Status Updates and Delivery

Explicit states - submitted, picked, delivered, mispicked

Allowing for customers to know what is happening when necessary.

Explicit states - submitted, picked, delivered, mispicked

Allowing for customers to know what is happening when necessary.

MY IMPAct

MY IMPAct

Pilot Leader Meetings:

  • Led numerous pilot store meetings to drive adoption and test new features


QA:

  • Working with pilot leaders to identify current issues before a fleetwide launch

  • Collaborating with the tech team to publish user feedback

  • Testing published user feedback independently and with pilot leaders


Training Materials:

  • Created how-to one-pagers for store support and employee onboarding

Pilot Leader Meetings:
- Led numerous pilot store meetings to drive adoption and test new features

QA:
- Working with pilot leaders to identify current issues before a fleetwide launch
- Collaborating with the tech team to publish user feedback
- Testing published user feedback independently and with pilot leaders

Training Materials:
- Created how-to one-pagers for store support and employee onboarding

Current Outcomes - July 2026

Current Outcomes - July 2026