Return queue
A React block (a whole screen) in Beamline's Shop app.
A queue of return cases. Search by return, order or customer, exactly (the default) or loosely; status tabs with counts, Requires attention first; a date column that shows the event chosen (requested, delivered, in transit since) under that name, while the filters always say they filter by the date requested, so changing what the column shows never changes what's found; one labelled sheet of filters (date requested, resolution, reason, item checks where partly checked includes negative checks, exchange stock hold, payment) that narrow together, each in force a chip that removes it, Clear all for several. Each row: return, order (linked out), the date, resolution, items, customer, status on its tone with what holds it up and an exchange-stock hold expiring or expired. A refresh that fails keeps the rows shown and says the time they're from. Opening a return keeps the query and marks the row it came from. On a phone each return is a summary card.
Use it for
- A queue of cases with stages, where some need a hand and several dates mean different events.
- Filters that intersect and must say which date they filter by.
Not for
- One return's case (return-case).
- A generic data table (data-grid).
Anatomy
- header: the tool's mark, Returns, search and Exact match
- toolbar: status tabs with counts; Date shown; Filters (count)
- chips: the filters in force, Clear all, the date note
- table (phone: cards): return, order, date, resolution, items, customer, status
- filter sheet: date requested, resolution, reason, item checks, exchange stock, payment; Reset, Apply filters
States
- open queue, exact and loose search, several filters, partly checked, hold expiring and expired, requires attention
- nothing matches, loading, refresh failed with rows kept
- phone: summary cards
- right to left: mirrored
- reduced motion: through the tokens
Keyboard
- Tab through search, Exact match, the tabs (arrows), Date shown, Filters, the chips and the table; Enter opens a return
Motion
Nothing runs at rest.
Props
| Prop | Type | Default | Description |
|---|---|---|---|
rows (required) | ReturnRow[] | — | The rows the service found for the query (the queue doesn't filter them itself). |
total (required) | number | — | How many match in all (rows may be a page). |
counts | Partial<Record<QueueTab, number>> | — | How many each tab holds, when known. |
query | ReturnQuery | — | |
defaultQuery | ReturnQuery | — | |
onQueryChange | ((query: ReturnQuery) => void) | — | |
dateBasis | DateBasis | — | |
defaultDateBasis | DateBasis | — | |
onDateBasisChange | ((basis: DateBasis) => void) | — | |
reasons (required) | { id: string; label: string; }[] | — | The return reasons customers pick, for the filter. |
loading | boolean | — | |
error | string | null | — | The last refresh failed: the reason. The rows shown stay as they were. |
loadedAt | string | null | — | When the rows shown were loaded. |
onRetry | (() => void) | — | |
onOpen | ((id: string) => void) | — | Opens a return; the queue keeps its query and marks the row it came from. |
located | string | null | — | The row last opened. |
product | string | — | |
now | string | — | Today, for reservation expiry. |
className | string | — | Classes on the documented visual root; no override by default. |
style | CSSProperties | — | Inline styles on the documented visual root; no overrides by default. |
ref | Ref<HTMLDivElement> | — | Receives the documented native target or imperative handle; omitted by default. |
Built from
- Alert
- Avatar
- Bottom sheet
- Button
- Calendar
- Checkbox
- Context menu
- Data grid
- Date range picker
- Dropdown menu
- Glow
- Kbd
- Label
- Pagination
- Popover
- Radio group
- Search field
- Select
- Sheet
- Spinner
- Switch
- Tabs
- Tooltip
Dependencies
lucide-react
Import
import { ReturnQueue, EMPTY_QUERY } from "@beamline/return-queue";
Get it
Return queue is part of Beamline UI. Install the parts you need in your React app as compiled packages or editable source. Get Beamline · Connect your agent
More in Shop
- Product editor: A product being made in a shop's back office, every value read as text at rest. The variant grid, grouped by the first option, lists each combination…
- Category manager: A shop's product categories, nested and ranked. Each category moves up, down or into another from its menu, and every move gets its own receipt (saving…
- Inventory item: One stock item in a shop's back office, apart from the variants that sell it (how many each uses per unit). Stock per location as stocked, reserved and…
- Plan comparison: Plans side by side against every feature: prices that roll between monthly and yearly, the current and recommended plan marked, a header that stays in…
- Step form: The finished frame for any multi-step form you compose — onboarding, intake brief, questionnaire, booking, application: a wide card with progress, the…
- Orders admin: A shop's order desk: today's orders and revenue, quick filters for what needs doing (to fulfil, unpaid, returns), a virtualised orders grid, and the…
- Order detail: One shop order with payment and fulfilment as two separate lanes. The header says where each stands (paid, partly paid, awaiting, refunded; not…
- Order board: A shop's orders as cards in its columns, on the shared kanban with drag and keyboard moves. Each card: number, estimate or work order, customer, vehicle…
- Order composer: An order made inside a support ticket: products found by name, each variant with its stock drawn and said (in stock, none, oversold, not known) and the…
- Draft orders: A draft order made for a customer in a shop's back office that reads like the order it will become. The lines lead: each with its variant and SKU or…
- Order changes: What happens to a shop order after it's placed. Edit: the order as it stands beside the requested version, each line marked new, changed (old → new…
- Special orders: Customers' special orders as demand to buy for, per outlet: To order apart from Ordered; each product's demand, what is reserved, incoming and on order…
- Order history and fills: Every order the account placed and every fill it got, for a period: totals for volume, fees, fill rate and maker share; orders with their status and how…
- Order ledger: Purchase orders as money. Each order's spend is drawn against its approved total (paid, billed, pending, what is left, and any overrun past the end…
- Ticket orders: A customer's orders inside a support ticket, each action's effect said before it's done: orders and drafts kept apart, a paid draft shown once as its…
- Record search: One search across connected records (customers, vehicles, orders) by name, phone, plate, VIN or order number. What the words look like is said (info)…
- Return case: One return as one place where every act is its own. The return, its order (linked out) and the customer on three cards; the stage said on its tone. Items…
- Return request: Staff start a return from an order, and edit the reasons customers pick. New return: the order's lines as a checklist, each with its variant, price and…
- Purchase orders: A salon's purchase orders, received: the orders down the side, the chosen one beside them. Each line still due reads as a strip of received, this…
- Print quote: A print shop's quoting in three places. Quote: a group of garments that share one imprint and one quantity break, the group's pieces counted together and…
- Service estimate: An estimate for one vehicle. Services added from the catalogue (one not listed for this vehicle said on warning, fit unknown said); each with its lines…
- Job card: A technician's repair order, phone-first. The vehicle, the customer and when it's due in words (due at, due in, overdue by how long); an offline copy…
- Parts tracker: Parts across a shop's work orders: each with its number, the order and vehicle, supplier, quantity and cost (not known said), and where it is: ordered…
- Visit board: The staff board for a walk-in queue: visits move from waiting through called and serving to done today. Arrival (here or on the way), the place in the…