Org Web Adapter

Editing hungryroot/jira/be_6951_expose_stock_check_tool_in_admin.org

:PROPERTIES:
:ID:       2da8ee36-089b-4648-86ea-5f1d5220e685
:END:
#+title: BE-6951 Expose stock check tool in admin

- source :: https://hungryroot.atlassian.net/browse/BE-6951
- 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:a0ae5b03-760c-432f-8e3e-ff8c290676d0][Status - Needs QA]]

* Tasks
** DONE Experiment with Cursor solution to adding this stock tool to admin :work:hungryroot:sprint102:ep411:be6591:djadmin:project:
:PROPERTIES:
:ID:       330e52fe-bc50-5aeb-2ddc-a798df38af9b
:END:
** DONE Fix failing tests :work:hungryroot:sprint102:ep411:be6591:djadmin:project:
:PROPERTIES:
:ID:       451d2752-5739-fb46-e1e0-4fb662d4f712
:END:
** DONE Change form to GET params and allow embedding without headers or form :work:hungryroot:sprint102:ep411:be6591:djadmin:project:
:PROPERTIES:
:ID:       4f3c00bb-d9ce-59ee-2d32-5e727600c23e
:END:
* Description
We have an existing Django management command that checks in-stock /
out-of-stock status for products and pairings by origin and inventory date,
including per-ingredient breakdowns for pairings. To enable self-service for
Product, Marketing, and Operations teams, expose this functionality in Django
Admin with a custom admin page and form.

The admin UI should allow users to input Origin ID (required), optional Pairing
ID or Product ID, and optional Inventory Date(s), submit the request, and view
results directly in the admin interface without running CLI commands.

Results should be displayed in a clear, readable format (table or structured
sections) showing entity name/ID, origin, inventory date(s), stock status,
customizable units, and—for pairings—a per-ingredient in/out-of-stock breakdown.
The implementation should reuse the existing command’s core logic (factored into
a shared service layer), include validation and helpful error messaging for
invalid inputs or missing inventory data, and be accessible to non-engineering
users via Django Admin permissions.