orders group requests - BevvyTech/BrewskiDocs GitHub Wiki

Groups – Shipping Requests (/groups/shipping-requests)

Purpose

  • Surface brewery-group orders that need hub coordination so ops can claim, transfer, or release deliveries without diving into each order.
  • Highlight delivery windows, current hub ownership, and recency so the right team takes action quickly.
  • Listed under the top-level Groups menu once the admin.group-deliveries feature flag is enabled.

Data Sources

  • Lists up to the first 200 orders returned by ordersService.list(teamId, token, { groupClaimStatus, groupId }); rows are filtered client-side by search and status.
  • Transfers fetch group membership via groupsService.get(groupId, token) to identify eligible hub breweries.
  • Claim, transfer, and release actions call ordersService.claimGroup, ordersService.transferGroup, and ordersService.releaseGroup respectively to sync with the backend.

Key Interactions

  • Status filter toggles between unclaimed, collating, claimed, completed, or all group orders; the search box matches order number, client, group name, and hub name.
  • Claim marks the active team as hub (setting claim status to collating). Transfer opens a dialog listing other active members; selection moves coordination to that brewery. Release hands the order back to the unclaimed pool.
  • Open navigates to /orders/:orderId where full detail and documentation live.
  • Snackbars confirm success/failure and the table auto-refreshes; the Refresh button re-pulls data on demand.
  • The grid adopts the shared pagination footer so whenever additional result pages are exposed the same 10/25/50/100 selector, cookie-backed preference, and chevron + page-jump dropdown appear without per-view styling.
⚠️ **GitHub.com Fallback** ⚠️