Skip to content

feat(order-panel): header with next action, flow steps, identity strip and tabs for the order details panel - #126

Closed
roncodes wants to merge 14 commits into
release/v0.4.25from
feat/order-details-panel
Closed

roncodes wants to merge 14 commits into
release/v0.4.25from
feat/order-details-panel

Conversation

@roncodes

Copy link
Copy Markdown
Member

Summary

Order details panel from design board 5a. Stacked on #125; review the top commit.

Today the panel stacks ten panels under one "Overview" tab and buries the next action in a menu. Now the header and first strip answer the dispatcher's five questions, and everything else is a tab.

  • Header: order id, status badge, store or network badge, tracking number, checkout id. Actions: the next workflow action (Accept, Mark as Ready, Complete, or a custom activity) promoted to a button, Edit (opens the order edit route), the rest (assign/unassign driver, cancel) behind the ellipsis.
  • Flow steps (Storefront::Order::FlowSteps): the activity flow as numbered steps with the current one marked. A custom order config's flow is walked from created; the default storefront flow is implied (pickup and delivery variants). Canceled orders show a canceled chip.
  • Identity strip (Storefront::Order::IdentityStrip): Customer::Pill, Driver::Pill with an inline Assign driver button when empty, fulfillment type and timing (ASAP, scheduled, booking), total with tip and promotion code.
  • Tabs: Items (order breakdown, store block, other orders in the same checkout via CheckoutSiblings), Route (route and tracking), Payment (details), Activity (activity and comments), Customer (insights), Data (metadata and documents). Extensions' registered tabs are still appended.
  • Panel width 560 → 600px.

Not here: ember-ui Flow::Steps extraction, refund and print actions, the create order form (board 10b, next PR).

Related Issue

Storefront UX overhaul, design canvas board 5a.

Type of Change

  • Bug fix
  • Feature
  • Refactor
  • Documentation
  • Test
  • Chore

Implementation Notes

The tab components are thin wrappers composing the existing detail panels, so no panel was rewritten. actionButtonsFor on storefront-order-actions now returns buttons plus a menu instead of a single menu; the orders table cells from #125 and the panel share actionItemsFor.

Validation

  • Tests — not run locally per the maintainer's request.
  • Lint — not run locally (CI).
  • Build — not run locally (CI).
  • Manual validation — maintainer.

Documentation Impact

  • No documentation changes needed
  • Documentation updated in fleetbase/fleetbase.io
  • Documentation needed but not included

API Reference Impact

  • No API reference changes needed
  • Updated fleetbase/postman
  • API reference updates required but not included

Documentation Notes

docs/storefront → orders: the order panel layout and tabs. needs-docs for the series.

Risk

Anything that relied on the single "Overview" tab key (overview) in storefront:component:order:details registrations keeps working; registered tabs are appended after the six built-in tabs.

Screenshots / Recordings

Design canvas board 5a: https://claude.ai/artifact/771ptEFmi4BLmYHBZuUhWF

The dummy app never ran: ember-classic-decorator (unused) crashes on Ember 5,
lazy loading kept the engine's modules out of the test bundle, and the host
services, config and intl data the panels need were missing. Mirrors what
fleetops already does: eager loading when `ember test` runs from this package,
an inert stand-in for the console's extensions module, the API config the
core adapter reads at module scope, and the legacy built-in components the
engine's templates still use.

The dummy intl service ignores missing locale data, since headless Chrome has
no number formats for every bundled locale, and the order details and network
controller tests stub the host router, fetch and app cache the way the widget
tests already do.
…rce card

Catalog, truck and network index pages use Layout::Resource::CardsGrid with
one card each on Layout::Resource::Card, following the Fleet-Ops anatomy:
identity and subtitle in the header, media or facts in the body, status,
icon actions and meta in the footer, with registry slots at each end.

A catalog card shows its categories with product counts, its hours as a
seven-day strip (the new Storefront::HoursStrip) and its product total; a
draft is dashed. A truck card is a Vehicle::Pill with the online dot, the
vehicle photo, where it serves, and a presence badge that says serving,
offline, inactive, or online with no catalog. A network card shows the logo on
its backdrop, the online state, the currency and member count.

"Food trucks" reads "Trucks" in the UI; the food-truck model, routes and
permissions keep their names. The catalogs and trucks pages gain the search
the header already offered.
@roncodes roncodes added needs-docs Requires documentation updates needs-human-review Requires human review before proceeding type:feature Feature or enhancement labels Oct 10, 2026
@roncodes
roncodes force-pushed the feat/order-details-panel branch 2 times, most recently from 4f5dcdf to 7c4fecd Compare October 10, 2026 08:16
… and crashed createRecord; the store summary is store_summary
…s own sidebar for each

- storefront service tracks a network context derived from the network route
- StoreSelector becomes the context switcher with a Networks group and create-network
- application route loads networks; sidebar rewrites for the network context
- network page is a full page with an identity strip; the list hides while one is open
- new Trucks section for a network backed by FoodTruckFilter::network
- network orders and customers are scoped to the network being viewed, not the active store
- createNewNetwork lives on the storefront service
…enu without Networks

- trigger: context icon, name, STORE/NETWORK label and caret; blue for a store, indigo for a network; invitation badge
- menu: Stores and Networks groups with tiles, currency or member count, a check on the active one, readable in dark mode; footer actions read New store / New network
- store navigation follows the design order (Dashboard, Orders, Products, Catalogs, Customers, Trucks, Promotions, Settings); networks live in the switcher, not the menu
- network page loses the All networks button; leaving a network is the switcher's job
@roncodes
roncodes force-pushed the feat/order-details-panel branch from 7c4fecd to 5dfca3c Compare October 10, 2026 09:31
…e sidebar re-renders on a switch; networks report their store count
…d an invite panel

- network index is now an Overview (stat tiles, members with 7-day share, invitations, recent orders); settings move to networks.index.network.settings
- NetworkController gains overview, invitations, resend and revoke; one Invite per recipient carrying category, expiry, message and approval in meta
- OrderFilter/CustomerFilter gain a network filter on meta.storefront_network_id; the network orders and customers routes use it
- Storefront::Network::InvitePanel (by email, shareable link, add a store you manage) replaces the share-network and add-stores modals
- stores page: store identity column via a new store descriptor, All/Online/Offline/Invited tabs, bulk assign category and remove, invitation rows with resend/revoke/invite again
- store and network resource descriptors registered with the shared identity registry; SelectOption::Store wrapper; width-style helper
…ost re-export broke console boot before the lazy engine loaded
…ore stacks and next actions

- a multi-store checkout is one expandable row (customer, stores, fulfillment, total with tip split, shared driver, least-advanced status) that opens into each store's order
- status tabs (needs action, preparing, ready for pickup, out for delivery, completed, canceled) drive the status query param; grouped/flat toggle
- new cells: reference, stores (identity stack of store pills), fulfillment, total, driver (inline assign), status, placed, actions (next action promoted, rest behind an ellipsis)
- order index resource keeps meta.checkout_id so the console can group
…lide with the networks list's page, sort and query
…ive questions first

- header: id, status and store/network badges, the next workflow action promoted to a button, Edit, the rest behind a menu
- Storefront::Order::FlowSteps renders the activity flow as steps (custom order configs contribute their own)
- Storefront::Order::IdentityStrip: customer, driver with inline assign, fulfillment and timing, total with tip and promotion
- tabs: Items (with store block and the other orders of the checkout), Route (with tracking), Payment, Activity (with comments), Customer, Data (metadata and documents); registered tabs still appended
- panel widened to 600px
@roncodes
roncodes force-pushed the feat/order-details-panel branch from 5dfca3c to 3a5e69c Compare October 10, 2026 10:19
@roncodes

Copy link
Copy Markdown
Member Author

Superseded by the single overhaul PR (one branch, one PR targeting release/v0.4.25, per maintainer request).

@roncodes roncodes closed this Oct 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-docs Requires documentation updates needs-human-review Requires human review before proceeding type:feature Feature or enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant