Org Web Adapter

Editing hungryroot/jira/be_6945_create_django_management_command_to_assess_pairing_product_stock_status_by_origin.org

:PROPERTIES:
:ID:       d1756c44-9896-465c-abf7-ae5605efad68
:END:
#+title: BE-6945 Create Django management command to assess pairing product stock status by origin

- source :: https://hungryroot.atlassian.net/browse/BE-6945
- tags ::   [[id:3a477c02-e26d-40f7-a719-0aa1cd169dd8][Hungryroot API Project]]
- epic ::   [[id:86327fb4-0f66-4bc6-9068-c414cea77042][EP-411 Eng Parking Lot]]
- sprint :: [[id:26939bb8-164c-402e-8a6a-6ae8c99d3e59][HR BE Sprint 102]]
- status :: [[id:4d41d978-e56f-45c1-88d1-e2c76510972e][Status - Complete]]

* Tasks
** DONE Ask Cursor to make a first pass on a pairing product stock management command :hungryroot:project:be6945:ep411:djmgmt:sprint102:
:PROPERTIES:
:ID:       061f6d74-ac9c-50a3-d874-bcd27f01847b
:END:
** DONE Kick the tires and test stock status command locally :hungryroot:project:be6945:ep411:djmgmt:sprint102:
:PROPERTIES:
:ID:       d30789aa-f8ea-21ff-b4a7-00710146115e
:END:
** DONE Update command to take just pairing-id or product-id :hungryroot:project:be6945:ep411:djmgmt:sprint102:
:PROPERTIES:
:ID:       ccae8668-628f-2eff-32d9-da19abc19903
:END:
** DONE Verify output of product stock comamnd is correct :hungryroot:project:be6945:ep411:djmgmt:work:
:PROPERTIES:
:ID:       cfdd68b2-1701-2251-80a9-b2d51ecd7395
:END:
** DONE Address PR review comments :hungryroot:project:be6945:ep411:djmgmt:work:
:PROPERTIES:
:ID:       7b1b38ed-85d6-8f05-4da8-af5946ffe26d
:END:
** DONE Fix failing tests :sprint102:hungryroot:project:be6945:ep411:djmgmt:work:
:PROPERTIES:
:ID:       ad8ae2ee-40dc-73df-c7c0-be3466441386
:END:
* Description
Create a Django management command to check stock status for pairings or
products given an origin ID and inventory date(s). For pairings, report which
ingredients are in/out of stock. For products, report in/out of stock. Support
checking multiple upcoming inventory dates when only an origin is provided.

Requirements

Core Functionality

Accept inputs:

--pairing-id (optional): Pairing ID to check

--product-id (optional): Product ID to check

--origin-id (required): Origin ID (fulfillment center)

--inventory-date (optional): Specific inventory date (YYYY-MM-DD). If omitted
and only origin is provided, check current and upcoming inventory dates (3-4
dates)

Stock status logic:

Product: customizable_units = swappable - sold. In stock if customizable_units >
0, otherwise out of stock.

Pairing: Check all ingredients (via PairingIngredient). Pairing is in stock only
if all ingredients have customizable_units > 0. Report per-ingredient status.

Output format:

JSON or human-readable table

Include:

Entity ID (pairing/product)

Entity name

Origin ID and name

Inventory date(s)

Stock status (in stock/out of stock)

For pairings: breakdown of ingredient statuses

Additional metrics: swappable, sold, available, customizable_units

Extended Functionality (Origin-only mode)

When only --origin-id is provided (no pairing/product ID, no inventory date):

Calculate current and upcoming inventory dates (3-4 dates) using
get_algolia_sync_inventory_dates() or similar

Return stock status for all dates

Optionally filter to active products/pairings only

Command Usage Examples

# Check specific pairing for specific date
python manage.py check_stock_status --pairing-id 123 --origin-id 1
--inventory-date 2024-01-15

# Check specific product for specific date
python manage.py check_stock_status --product-id 456 --origin-id 1
--inventory-date 2024-01-15

# Check pairing for multiple upcoming dates (origin-only mode)
python manage.py check_stock_status --pairing-id 123 --origin-id 1

# Check all upcoming dates for an origin (origin-only mode)
python manage.py check_stock_status --origin-id 1

cceptance Criteria

[ ] Command accepts --pairing-id, --product-id, --origin-id, and
--inventory-date arguments

[ ] Command correctly calculates stock status using customizable_units =
swappable - sold

[ ] For pairings, command reports status for all ingredients

[ ] When only origin is provided, command checks 3-4 upcoming inventory dates

[ ] Command outputs clear, structured results (JSON or table format)

[ ] Command handles edge cases: missing inventory records, inactive
products/pairings, invalid IDs

[ ] Command includes appropriate error handling and validation

[ ] Command follows existing management command patterns (see
app/management/commands/nightly.py)

[ ] Command is well-documented with docstrings

Notes

Consider adding --verbose flag for detailed output

Consider adding --format flag to choose between JSON and table output

Consider caching inventory queries if performance becomes an issue

This command will be useful for operations teams to quickly assess stock
availability for troubleshooting and planning