top of page

Not-On-File Item Workflows

Goal: Fix the backend process of the front-end NOF workflow

Hopeful Outcome: align the front and backend teams across multiple departments to band together in an effort to not only collaborate but fully understand the differing language and connections that occur across disciplines for one efficient process.

Tools Used

NV398m-Y_400x400.jpg
Power-BI-Logo.png
61_sql-database-generic.90b41636a8.png

Current Process to-date

~ Learn the Problem & Understand the Ask (from AX team)

~ Investigate & Discern the Scope of the Merchandising side

~ (NOW) Narrow in the potential directions

The Gallery

Definitions

Not-On-File

For an item to be buyable, merchandisers authorize specifically what stores that item can be sold at. Not on File items are items that appear in stores that they are not authorized at.

Sellability

status determining if an item contains all of the necessary attributes and data before it can be sold at stores

Assortment

active lists that determine if an item is authorized to be sold at any particular store, city, division, etc. on any specific year/period/week of the year

Backend

This doesn't just refer to the technological and architectural side of products. This refers to the behind-the-scenes of front-end happenings at the store-front.

Biways

issues collection system that acts as one centralized collector of issues from stores that is disconnected from the backend

Current Thoughts

 Doing your due diligence to really figure out the scope will save your team’s time from unnecessary solutioning.

bottom of page