Auction Dashboard

An auction-first command center: which auctions are open, which are closing this week, how ready each one is, and which closed auctions still need their results uploaded.

org-owner org-admin team-lead

The Auction Dashboard lives under Operations > Auction Dashboard in the left sidebar. It is centered on auctions — every open auction surfaces as a card with its own progress bars and inline actions — with a queue at the bottom for auctions whose end date has passed but whose results CSV hasn't been uploaded yet. Access is restricted to org-owner, org-admin, and team-lead.

Dashboard Components

From top to bottom, the page renders:

  • Header — A Warehouse filter dropdown on the left and three station shortcut buttons (Processing, Put-Away, Picking) on the right.
  • KPI Strip — Four cards: Auctions Open, Closing ≤ 7 days, Items Ready, and Revenue 30d.
  • Auction Board — One card per non-closed auction, sorted by soonest auction date. Each card shows vendor, date range, platform, lot/item counts, four progress bars (Cataloged, Put-Away, Exported, Sold), a countdown, and three inline actions: Open, Upload Results, and Assign.
  • Post-Auction Queue — Auctions whose end date has passed but whose results CSV has not been uploaded yet. Each row has a one-click Upload Results button that opens the upload page pre-scoped to that auction.
  • Worker Activity Feed — The last 50 activity-log entries, auto-refreshed every 30 seconds.
Screenshot

Warehouse Filter

org-owner org-admin team-lead

The Warehouse dropdown in the header narrows the dashboard to auctions that have at least one item physically located in the selected warehouse. The default is All warehouses — tenant-wide.

When you pick a warehouse:

  • The KPI Strip recalculates against open auctions touching that warehouse (Auctions Open, Closing ≤ 7 days, Items Ready). Revenue 30d stays tenant-wide because it's a commercial number, not a warehouse one.
  • The Auction Board only shows auctions with items in that warehouse. The per-auction progress bars also narrow to the items in that warehouse, so a multi-warehouse auction shows its warehouse-specific slice.
  • The Post-Auction Queue is unaffected — results upload is an auction-level action, not a warehouse one.

Your selection is reflected in the URL, so links and bookmarks survive a reload.

Tip:

Cross-warehouse auctions appear under every warehouse they touch, with each warehouse's progress shown independently. To see the auction's full picture, switch back to All warehouses.

KPI Strip

org-owner org-admin team-lead

Four headline numbers across the top of the dashboard, sized for at-a-glance reading:

  • Auctions Open — Count of auctions whose status is not closed.
  • Closing ≤ 7 days — Open auctions whose auction_date falls within the next seven days. The pressure metric — if this is non-zero, those cards are also at the top of the Auction Board.
  • Items Ready — Items in cataloged or put_away status across open auctions. This is what's available to ship out the door.
  • Revenue 30d — Sum of sold_price across items sold in the last 30 days.

The first three respect the Warehouse Filter; Revenue 30d does not (it is always tenant-wide).

Auction Board

org-owner org-admin team-lead

The centerpiece of the dashboard. One card per auction that is not yet closed, ordered by soonest auction date first (auctions without a date sort to the end).

What Each Card Shows

  • Header — Auction name (with an external-link icon when an auction_url is set), vendor name, date range, and the countdown ("Closes in 3 days" / "Closes today" / "Ended 2 days ago"). The right corner shows a status badge and a platform pill.
  • Counts — Lot count and item count for the auction.
  • Progress Bars — Four stacked bars, each with a per-bar percentage:
    • Cataloged — Items with a non-null cataloged_at.
    • Put-Away — Items in put_away status.
    • Exported — 100% if any export exists for the auction, otherwise 0%. This is an auction-level yes/no — see Exporting for how exports are generated.
    • Sold — Items in sold status. Driven by the auction results CSV upload (see Post-Auction Queue below) or by the Mark as Sold bulk action on auction / lot / item lists (see Picking > Mark as Sold).
  • Inline Actions — Three buttons at the bottom of the card:
    • Open — Opens the auction in the Auctions resource for full edit / item / lot / export / assignment management.
    • Upload Results — Opens the Upload Auction Results page pre-scoped to this auction; serial matching is restricted to this auction's items.
    • Assign — Jumps to the Master Controller (Employee Assignments) page.
Tip:

A persistent gap between Cataloged and Put-Away usually means cataloging is outpacing put-away — a sign to rebalance workers via Master Controller.

Post-Auction Queue

org-owner org-admin team-lead

The Post-Auction Queue lists every auction whose end date (auction_end_date, falling back to auction_date) has passed but whose results CSV has not been uploaded yet — i.e. results_uploaded_at is null. This is the punch list of "auctions waiting on their results."

Each row shows the auction name, the end date, the platform, and an Upload Results CTA. Clicking it opens the Upload Auction Results page with the auction pre-selected — serial matching is restricted to that auction's items, which prevents serials from a re-run colliding with a different auction.

Once the upload finishes and matches at least one item, the parser stamps results_uploaded_at = now() on the auction and it drops off the queue.

The queue is tenant-wide — it does not respect the Warehouse Filter — because results ingestion is an auction-level action.

See Picking > Uploading Auction Results for the upload workflow and the formats supported.

Worker Activity Feed

org-owner org-admin team-lead

The Worker Activity Feed is the section labelled "Worker Activity Feed — Last 50 activities — auto-refreshes every 30 seconds". It is not a real-time / push stream — Livewire polls the server once every 30 seconds and replaces the list with the most recent 50 activity-log entries.

What Appears in the Feed

Activity log entries are written by a small number of workflows. In practice the feed will show:

  • Scanned — Written by the Processing Station when a worker scans an item. Shows the item title and serial number.
  • Put Away — Written by the Put-Away Station when an item or pallet is placed at a location. Shows the destination location code or pallet number.
  • Mark Sold — Written by the Mark as Sold bulk action on auction / lot / item lists. Shows the per-item price.

Each row shows the user's name, the action label (e.g. scanned, put away, mark sold), the description, and a relative timestamp.

Note:

Other workflows (export generation, pick-list creation, auction status changes, login events) are not currently written to the activity log and will not show up in this feed.