Dieses Stellenangebot ist nicht mehr verfügbar
Über
OVERVIEW
Our fresh food operates on a strict 5-day lifecycle. For example, items delivered to our warehouse on Monday expire on Friday, and any remaining items from that batch must be removed on Saturday.
The process flow is:
1. Fresh food is delivered to our warehouse
2. From the warehouse, products are distributed to individual stores
3. Items are then sold, deleted (e.g., theft, spoilage), transferred between stores, or expire
At any given time, we may have multiple active batches of the same product in circulation. The system must be able to track up to four different batches simultaneously (typically two, rarely more than three), each with its own expiration date.
The goal is to create a dashboard that tracks:
- Batch-level inventory
- Store-level inventory
- Sales
- Deletions (with reason codes)
- Expiration timelines
The dashboard must clearly show which products in each store are:
- Expiring within 2 days
- Expiring within 1 day
- Expiring today (0 days)
- Already expired
Additionally, the tool must allow us to manually record transfers of items between stores, and continue tracking that specific batch and its expiration after the transfer.
INPUTS
1) Manual Inputs (Warehouse-Level)
Our team will manually enter:
- Batch arrival date (warehouse delivery date)
- Expiration date (5-day lifecycle)
- Total quantity received per batch
There are no timestamps at the warehouse level — only batch quantity and expiration date.
2) System-Generated Reports (Store-Level)
These reports are exported from our POS/inventory system and will be provided to feed into the dashboard:
- Entry Summary Report
Shows what items were entered into each store and includes timestamps.
- Sold Detail Report
Shows what items were sold in each store.
- Delete Summary Report
Shows items removed from inventory for reasons other than sale (e.g., theft, spoilage, damage). Includes reason codes.
LOGIC & FUNCTIONALITY REQUIREMENTS
1) FIFO Logic (Store-Level)
FIFO should be applied only for warehouse-to-store allocation, not for customer purchase behavior.
- The system should assume the oldest warehouse batch is sent to stores first (FIFO applies to distribution/entry into stores).
- The system must NOT assume the oldest batch is sold first or deleted first. Customers may purchase newer items first, leaving older items on the shelf.
- When multiple batches of the same item exist in a store at the same time, the dashboard should still track inventory by batch/expiration date so we can identify exposure to near-term expiration even if sales don't follow FIFO.
- If multiple entries occur on the same day, the Entry Summary timestamp should be used to determine the order in which inventory from batches is considered to have been distributed/entered into stores (earlier entries first).
2) Store-Level Live Inventory Tracking (Batch-Aware)
The dashboard must calculate and display current inventory per store by combining:
- Items entered into store
- Items sold
- Items deleted (with reason)
- Items transferred in or out
- Batch expiration dates
Important clarification:
Because customer behavior does not follow FIFO, the dashboard must still track and display inventory by batch. However, when sales and deletions occur, the system will need a defined method for how those reductions are attributed to batches.
We are open to the freelancer recommending the best approach here (for example, a configurable assumption, or an allocation rule), as long as the end result supports accurate expiration risk tracking.
At all times, the dashboard should be able to show:
- How many units of each product remain in each store
- The associated expiration date(s) of those units
- Which items are at risk of expiring soon or already expired
3) Expiration Alerts (Color-Coded)
The dashboard should visually flag inventory per store using color-coded indicators for:
- 2 days until expiration
- 1 day until expiration
- Expiring today (0 days)
- Already expired
This should allow us to quickly identify which stores require action.
4) Manual Store Transfers
The dashboard must include functionality to manually record transfers of product between stores.
When a transfer occurs:
- Inventory must decrease in the originating store
- Inventory must increase in the receiving store
- The batch identity and expiration date must remain intact
- The product must continue to be tracked correctly after the transfer
END GOAL
We are looking for a clear, accurate, and operational dashboard that provides real-time visibility into fresh food inventory and expiration risk across all stores.
Contract duration of 1 to 3 months. with 30 hours per week.
Mandatory skills: Microsoft Excel, Data Visualization, Tableau, Python, Data Analysis
Sprachkenntnisse
- English
Hinweis für Nutzer
Dieses Stellenangebot wurde von einem unserer Partner veröffentlicht. Sie können das Originalangebot einsehen hier.