Skip to content

feat(account): BACK-692 show picklist backorder prompts on order details - #2683

Merged
apostoliukG merged 4 commits into
masterfrom
BACK-692-picklist-backorder-order-details
Jul 21, 2026
Merged

feat(account): BACK-692 show picklist backorder prompts on order details#2683
apostoliukG merged 4 commits into
masterfrom
BACK-692-picklist-backorder-order-details

Conversation

@apostoliukG

@apostoliukG apostoliukG commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

What?

Renders backorder prompts per picklist (bundle) option on the account order details page (templates/components/account/order-contents.html), so each backordered bundle option displays its own backorder status — mirroring how the PDP renders per-bundle backorder.

Previously each option only rendered its name/value via the product-options partial. Now, inside the {{#each options}} loop, when an option has quantity_backordered > 0 it additionally renders:

  • {quantity} will be backordered (via the products.quantity_backordered lang string)
  • the per-option backorder_message, when present

This matches the PDP bundle backorder display (assets/js/theme/common/picklist-backorder.js), which shows only the backordered quantity and message per option — there is intentionally no per-option "ready to ship" line. The existing item-level backorder block (ready to ship + backordered + message for the whole line item) is unchanged.

Technical notes for reviewers:

  • The option name is already rendered as the <dt> key, so the combined output reads like the PDP's "<Option name>: N will be backordered" + message.
  • An earlier iteration of this block also rendered a per-option quantity_on_hand ("ready to ship") line using (subtract quantity quantity_backordered). That was removed: the PDP doesn't show it per option, and inside {{#each options}} the quantity token resolves against the option context (not the line item), so the math was unreliable.
  • This depends on the platform exposing quantity_backordered / backorder_message per option in the order object. The item-level fields are confirmed present; the per-option fields could not be verified locally because the only available test order has no bundle options. Reviewers/QA should confirm against an order containing a backordered picklist option.

Requirements

  • CHANGELOG.md entry added (required for code changes only)

Tickets / Documentation

Screenshots (if appropriate)

To be added — pending an order containing a backordered picklist (bundle) option.

🤖 Generated with Claude Code


Note

Low Risk
Documentation-only change to the changelog with no runtime code in the diff.

Overview
This PR only changes CHANGELOG.md: it adds a new Draft bullet for #2683 stating that the account order details page will show backorder prompts for the parent line item (under the product title) and for each picklist option, in line with PDP backorder messaging.

No template, style, or JavaScript files appear in the diff; release notes only.

Reviewed by Cursor Bugbot for commit 59052eb. Bugbot is set up for automated code reviews on this repo. Configure here.

Render per-picklist-option backorder prompts on the account order details
page so each backordered bundle option shows its own "N will be backordered"
message plus the backorder message, mirroring the PDP bundle backorder
display. Item-level backorder prompts are unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@apostoliukG
apostoliukG requested a review from a team as a code owner June 16, 2026 14:24

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 1853cdd. Configure here.

Comment thread templates/components/account/order-contents.html Outdated
apostoliukG and others added 2 commits June 17, 2026 10:26
The order details item-level backorder block previously rendered after the
options/gift-wrapping/event-date list, so the parent product's backorder
prompts (ready to ship / N backordered / message) visually attached to the
last bundle option. Move it directly under the product title so it is clearly
attributed to the parent product, with per-picklist-option backorder prompts
still rendered under each option — matching the PDP layout where the main
product and each bundle show their backorder status separately.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The storefront order object exposes only name and value per picklist option
(verified against a live bundle order) — no per-option quantity_backordered or
backorder_message. The per-option backorder block could therefore never render,
so remove it. Parent-product backorder prompts under the product title remain
the only backorder data the order payload supports.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Comment thread CHANGELOG.md
Resolve conflicts in CHANGELOG.md and order-contents.html by keeping
the implementation merged via #2687 (quantity_ready_to_ship and
linked_bundled_item per-option prompts).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@apostoliukG
apostoliukG merged commit 35d0672 into master Jul 21, 2026
9 checks passed
@apostoliukG
apostoliukG deleted the BACK-692-picklist-backorder-order-details branch July 21, 2026 10:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants