Docs
Purchase Order Display

Purchase Order Display

The purchase order list layout, columns, badges, and interactions

Purchase Order Display

The Purchase orders screen is a sortable, filterable table of all POs for the current shop. Rows mirror the implementation in Purchase Order Display (dashboard): destination/supplier route, document numbers, status, payment, dates, arrival progress, and amount.

Row layout (“Route” column)

Each row starts with:

  • Expand control — show or hide line items (product, variant, quantity, cost, line total) under the row.
  • Destination — warehouse / delivery location.
  • Supplier — shown under the destination on wider viewports.
  • Tags — optional tag chips when present.
  • On small screens, PO# and Payment may inline here for space.

Table columns (desktop)

ColumnWhat you see
RouteDestination, supplier, tags, expand; mobile-friendly PO# / invoice shortcuts
PO#Outline badge, e.g.
PO#128
— shop sequence number
Invoice #Editable reference / invoice number (inline save)
Line ItemsCount of lines on the PO
StatusLifecycle badge — see Order statuses
PaymentPaid / Unpaid / Payment overdue + short due date
Created DateWhen the PO was created
Expected ArrivalProgress toward estimated arrival; red when arrival is overdue (not delivered)
AmountOrder total in PO currency

Sorting is available on several columns (e.g. PO#, payment due, created, arrival, amount) via the column headers.

Status & payment badges (live components)

Order status (same components as the app):

Draft
Ordered
Shipped
Delivered
Canceled

Payment column:

Paid
Unpaid
Payment overdue

Interactions

  • Click the row (outside inline inputs) to open the full PO in the order modal for edit/view.
  • Expand the row to preview lines without leaving the list.
  • Invoice # can be edited in place on the list where shown.

Arrival overdue uses estimated arrival vs today for orders that are not Delivered. Payment overdue uses payment terms and due date — they are different signals.

Mobile

On narrow screens, columns collapse: key fields move into the Route column, and horizontal scroll may appear for the rest. Touch targets follow the same row click / expand behavior.

Use status filters (including overdue where available), payment filters, supplier filters, tags, date range, and search to narrow the list. Filter chips and the table stay in sync with the same status rules as Purchase order management.