COMDOX-1650: Roadmap feature updates

src/content/docs/dropins-b2b/requisition-list/index.mdx

@@ -5,6 +5,7 @@ sidebar:
   order: 1
 ---
 
+import Aside from '@components/Aside.astro';
 import { Badge } from '@astrojs/starlight/components';
 
 The Requisition List drop-in lets B2B customers manage requisition lists on Adobe Commerce storefronts. It supports multiple lists per account. Company users can add products to a list from product detail pages and product list pages.
@@ -29,3 +30,7 @@ The following table provides an overview of the Adobe Commerce features that the
 | Requisition list grid view | <Badge text="Supported" variant="tip" /> |
 | Customer authentication required | <Badge text="Supported" variant="tip" /> |
 | GraphQL API integration | <Badge text="Supported" variant="tip" /> |
+
+<Aside type="note" title="Quick Order and lists">
+Quick Order in the storefront adds lines to the cart. There is no out-of-the-box API or UI flow to bulk-add SKUs from Quick Order straight into an existing requisition or favorites list. If you need that path, plan a custom integration rather than assuming the Quick Order surface updates requisition lists.
+</Aside>

src/content/docs/dropins/cart/index.mdx

@@ -32,11 +32,11 @@ The following table provides an overview of the Adobe Commerce features that the
 | Low product stock alert                                          | <Badge text="Supported" variant="tip" />   |
 | Mini-cart                                                        | <Badge text="Supported" variant="tip" />   |
 | No-code UI configurations                                        | <Badge text="Supported" variant="tip" />   |
-| Out of stock/insufficient quantity products                      | <Badge text="Supported" variant="tip" />   |
+| Out of stock/insufficient quantity products (optional inclusion in the cart summary list) | <Badge text="Supported" variant="tip" />   |
 | Product line discounts (catalog rule, special price, tier price) | <Badge text="Supported" variant="tip" />   |
 | Save to wishlist                                                 | <Badge text="Supported" variant="tip" />   |
 | Slots for extensibility                                          | <Badge text="Supported" variant="tip" />   |
-| Taxes: Fixed                                                     | <Badge text="Roadmap" variant="caution" /> |
+| Taxes: Fixed                                                     | <Badge text="Supported" variant="tip" />   |
 | Taxes: Sales, VAT                                                | <Badge text="Supported" variant="tip" />   |
 | Undo remove product from cart                                    | <Badge text="Supported" variant="tip" /> |
 

src/content/docs/dropins/checkout/index.mdx

@@ -3,6 +3,7 @@ title: Checkout overview
 description: Learn about the features and functions of the checkout drop-in component.
 ---
 
+import Aside from '@components/Aside.astro';
 import { Badge } from '@astrojs/starlight/components';
 import OptionsTable from '@components/OptionsTable.astro';
 
@@ -42,8 +43,15 @@ The following table provides an overview of the Adobe Commerce features that the
 | Log in during checkout                                                             | <Badge text="Supported" variant="tip" />  |
 | Low product stock alert                                                            | <Badge text="Supported" variant="tip" />  |
 | Out of stock/insufficient quantity products                                        | <Badge text="Supported" variant="tip" />  |
-| Taxes: Fixed                                                                       | <Badge text="Roadmap" variant="caution" />|
+| Taxes: Fixed                                                                       | <Badge text="Supported" variant="tip" />  |
 | Taxes: Sales, VAT                                                                  | <Badge text="Supported" variant="tip" />  |
 | Terms and conditions consent                                                       | <Badge text="Supported" variant="tip" />  |
 | Zero subtotal checkout                                                             | <Badge text="Supported" variant="tip" />  |
 | Multi-step checkout                                                                | <Badge text="Supported" variant="tip" />  |
+| Payment Services vault and other methods that need extra fields (full `additionalData` on `setPaymentMethodOnCart`) | <Badge text="Supported" variant="tip" />  |
+| Custom row UI per shipping method (`ShippingMethodItem` slot on ShippingMethods)    | <Badge text="Supported" variant="tip" />  |
+| Extensible shipping rate request (`estimateShippingMethods` fragments and models)  | <Badge text="Supported" variant="tip" />  |
+
+<Aside type="note" title="Configuration and hosting">
+Apply gift cards to the order and terms and conditions consent follow your Adobe Commerce checkout configuration. Before you sign off in user acceptance testing, confirm the same rules and extensions are enabled for your hosting model (for example, Adobe Commerce on Cloud Services versus PaaS), because merchants sometimes differ between environments.
+</Aside>

src/content/docs/dropins/order/index.mdx

@@ -3,6 +3,7 @@ title: Order overview
 description: Learn about the features and functions of the order drop-in component.
 ---
 
+import Aside from '@components/Aside.astro';
 import { Badge } from '@astrojs/starlight/components';
 import OptionsTable from '@components/OptionsTable.astro';
 import Diagram from '@components/Diagram.astro';
@@ -15,7 +16,7 @@ The order drop-in component consists of multiple containers that display order d
 
 - Order data containers display order details within the customer account, guest user areas, and on the order confirmation page.
 - Returned merchandise authorization (RMA) containers guide users through the return process and display a list of created return requests.
-- The `OrderSearch` container enables guest users to locate their orders using a combination of email, ZIP code, and order number. This ensures easy access to order details even for users without an account. (Logged-in customers can also use this form.)
+- The `OrderSearch` container enables guest users to locate their orders using a combination of email, last name, and order number. This ensures easy access to order details even for users without an account. (Logged-in customers can also use this form.)
 
 The component's initialization process helps manage data retrieval and event emission, ensuring that containers receive the necessary data without individual fetching.
 
@@ -33,15 +34,21 @@ The following diagrams provide a visual composition of the order details and ret
 
 ## Supported Commerce features
 
-The following table provides an overview of the Adobe Commerce guest user features that the order component supports:
+The following table provides an overview of the Adobe Commerce order and return features that the order component supports:
 
 | Feature                                                          | Status                                     |
 | ---------------------------------------------------------------- | ------------------------------------------ |
 | Cancel order (with email confirmation)                           | <Badge text="Supported" variant="tip" />   |
 | Create a return                                                  | <Badge text="Supported" variant="tip" />   |
-| Filter orders by time of purchase                                | <Badge text="Supported" variant="tip" />   |
+| Filter orders by time or purchase date                           | <Badge text="Supported" variant="tip" />   |
+| Look up a specific order by email, last name, and order number (`OrderSearch`) | <Badge text="Supported" variant="tip" />   |
 | Reorder                                                          | <Badge text="Supported" variant="tip" />   |
-| Search orders                                                    | <Badge text="Roadmap" variant="caution" /> |
+| Search orders (for example keyword search across order history)   | <Badge text="Roadmap" variant="caution" />   |
 | View list of orders on the account                               | <Badge text="Supported" variant="tip" />   |
+| View order comments marked visible on storefront in Commerce Admin | <Badge text="Supported" variant="tip" />   |
 | View order status                                                | <Badge text="Supported" variant="tip" />   |
 | View return status                                               | <Badge text="Supported" variant="tip" />   |
+
+<Aside type="note" title="Order lookup versus order search">
+The supported row for `OrderSearch` covers locating a known order when the shopper already has email, last name, and order number. The roadmap row covers richer search (for example, keyword search across the full order list in the account area).
+</Aside>

src/content/docs/dropins/payment-services/index.mdx

@@ -2,19 +2,27 @@
 title: Payment Services overview
 description: Learn about the features of the Payment Services drop-in component.
 ---
+import Aside from '@components/Aside.astro';
 import Link from '@components/Link.astro';
 import { Badge } from '@astrojs/starlight/components';
 
-The Payment Services drop-in component renders the credit card form and the Apple Pay button.
+The Payment Services drop-in component renders Payment Services checkout methods (for example credit card and Apple Pay). Shoppers can also see Alternative Payment Methods (APM) when your Adobe Commerce configuration exposes them.
+
+<Aside type="note" title="Test payment on every page that takes money">
+A surface is simply a place in the storefront where a shopper can pay, for example, full checkout, the cart page, the mini-cart, the product page, or a one-click express checkout you added. Digital wallets and express pay buttons are not guaranteed to look or behave the same in each of those places, even when the table below marks a method as supported for this drop-in.
+
+Use the table below as the list of methods this drop-in can integrate. Then, in your own project, click through each place you take payment and confirm which methods actually appear. Your theme, blocks, and Adobe Commerce configuration decide what shoppers see. Hosting also matters: Adobe Commerce on Cloud Services and other Adobe Commerce hosting setups do not always return the same methods everywhere, so run your checks in the environment that matches production.
+</Aside>
 
 ## Supported payment methods
 
-The following table provides an overview of the payment methods that the Payment Services drop-in supports. The "Payment method code" column lists the `PaymentMethodCode` enum value for each method:
+The following table provides an overview of the payment methods that the Payment Services drop-in supports. When a row lists a `PaymentMethodCode` value, it matches the enum used in code. Local Payment Methods depend on what Adobe Commerce returns for your store, so there is no single enum value for every LPM.
 
 | Payment method    | Payment method code | Status                                     |
 |-------------------|---------------------|--------------------------------------------|
 | Apple Pay         | `APPLE_PAY`         | <Badge text="Supported" variant="tip" />   |
 | Credit/debit card | `CREDIT_CARD`       | <Badge text="Supported" variant="tip" />   |
+| Local Payment Methods (LPM) | Not applicable (configured in Adobe Commerce) | <Badge text="Supported" variant="tip" />   |
 | Google Pay        | `GOOGLE_PAY`        | <Badge text="Roadmap" variant="caution" /> |
 | PayPal Fastlane   | `FASTLANE`          | <Badge text="Roadmap" variant="caution" /> |
 | PayPal buttons    | `SMART_BUTTONS`     | <Badge text="Roadmap" variant="caution" /> |

src/content/docs/dropins/personalization/index.mdx

@@ -3,6 +3,8 @@ title: Personalization overview
 description: Learn about the features and functions of the personalization drop-in component.
 ---
 
+import { Badge } from '@astrojs/starlight/components';
+
 The personalization drop-in component provides a set of tools and containers designed to display content conditionally, based on Adobe Commerce customer groups, segments, and cart price rules.
 
 ## Overview
@@ -16,3 +18,14 @@ These listeners request the currently applied customer groups, segments, and car
 When you add a `TargetedBlock` container to a page, it displays only when the customer groups, segments, and cart price rules specified in the block configuration match the groups, segments, and rules stored in the cookie.
 
 When you specify a block type for a `TargetedBlock`, only the first targeted block of that type is rendered on the page. This behavior enables you to create a fallback chain of targeted blocks.
+
+## Supported Commerce features
+
+The following table provides an overview of the Adobe Commerce targeting inputs the personalization drop-in uses:
+
+| Feature | Status |
+| ------- | ------ |
+| Customer group targeting | <Badge text="Supported" variant="tip" /> |
+| Customer segment targeting | <Badge text="Supported" variant="tip" /> |
+| Cart price rule targeting | <Badge text="Supported" variant="tip" /> |
+| Fallback chain by block type | <Badge text="Supported" variant="tip" /> |

src/content/docs/dropins/product-details/index.mdx

@@ -40,12 +40,21 @@ The following table provides an overview of the Adobe Commerce features that the
 | Bundle product type             | <Badge text="Supported" variant="tip" /> |
 | Configurable product type       | <Badge text="Supported" variant="tip" /> |
 | Image gallery                   | <Badge text="Supported" variant="tip" /> |
-| Grouped products                | <Badge text="Roadmap" variant="caution" />      |
+| Product videos in gallery       | <Badge text="Supported" variant="tip" /> |
+| Numeric attributes at Admin display precision | <Badge text="Supported" variant="tip" /> |
+| Downloadable product options                                     | <Badge text="Supported" variant="tip" /> |
+| Grouped products                | <Badge text="Supported via SDK" variant="tip" /> |
 | Product details                 | <Badge text="Supported" variant="tip" /> |
 | Simple product type             | <Badge text="Supported" variant="tip" /> |
-| Virtual product type            | <Badge text="Roadmap" variant="caution" />      |
+| Virtual product type            | <Badge text="Supported" variant="tip" /> |
 | Zoom                            | <Badge text="Supported" variant="tip" /> |
 
+<Aside type="note" title="Virtual products on the PDP">
+Standard virtual products are supported because Catalog Service maps simple, virtual, downloadable, and gift card product types to `simpleProductViews`. If the PDP loads but add-to-cart fails, check storefront SKU and URL rules first (for example, lowercase product URLs). Read [SEO indexing](/setup/seo/indexing/) and [AEM prerender](/setup/configuration/aem-prerender/) before you treat the issue as an unsupported product type.
+
+Separately, product types that need extra shopper inputs not included in the default PDP—such as virtual gift cards with recipient fields or complex custom options—may remain partially supported until you add custom containers or validation.
+</Aside>
+
 ## Render product types
 
 The PDP component supports rendering different product types configured in your Adobe Commerce instance by default using data provided by the <Link href={"https://developer.adobe.com/commerce/webapi/graphql/schema/catalog-service/"} text={"Catalog Service GraphQL API"} />. Adobe Commerce supports seven product types, but the Catalog Service GraphQL API schema maps these to two types:

src/content/docs/dropins/product-details/quick-start.mdx

@@ -11,6 +11,9 @@ import Link from '@components/Link.astro';
 
 The Product Details drop-in provides a comprehensive product display page with image galleries, pricing, options, swatches, and add-to-cart functionality for all product types.
 
+<Aside type="note" title="Prerequisite: SKU and URL normalization">
+On AEM prerender storefronts, SKU and path normalization affects shopper actions. A product can appear in search, on the PLP, and on the PDP but still fail add-to-cart if the SKU or product URL does not follow documented lowercase and path conventions. Read [SEO indexing](/setup/seo/indexing/) and [AEM prerender](/setup/configuration/aem-prerender/) before you assume a product-type limitation.
+</Aside>
 
 <div style="background-color: var(--sl-color-blue-low); border-left: 4px solid var(--sl-color-blue); padding: 0.75rem 1rem; border-radius: 0.25rem; margin: 1rem 0;">
 <strong>Version: 3.0.2</strong>

src/content/docs/dropins/product-discovery/index.mdx

@@ -98,4 +98,16 @@ The following table provides an overview of the Adobe Commerce features that the
 | ---------------- | -------------------------------------------- |
 | Simple Product View | <Badge text="Supported" variant="tip" /> |
 | Complex Product View | <Badge text="Supported" variant="tip" />      |
+| Simple-like product types (simple, virtual, downloadable) in catalog and search | <Badge text="Supported" variant="tip" />      |
+| Virtual products in search results and PLP | <Badge text="Supported" variant="tip" />      |
+| Category and search PLPs with facets, sort, and pagination | <Badge text="Supported" variant="tip" />      |
+| Configurable page size on product listing (block configuration) | <Badge text="Supported" variant="tip" />      |
+| Custom product attributes on the product listing | <Badge text="Supported" variant="tip" />      |
+| Store code in the URL path with filters and search state | <Badge text="Supported" variant="tip" />      |
+
+<Aside type="note" title="Listings, URLs, and special product types">
+If a virtual product appears in Product Discovery or PLP results but a shopper action fails, validate SKU formatting, product URL paths, and storefront configuration first. Do not assume PLP or search is missing virtual-product support.
+
+Ordinary simple, virtual, and downloadable products fit default listing cards. Product types that need extra inputs not shown on a default card—such as virtual gift cards with amount or message fields—may still need custom listing or PDP behavior.
+</Aside>
 

src/content/docs/dropins/recommendations/index.mdx

@@ -30,6 +30,7 @@ The following table provides an overview of the Adobe Commerce features that the
 | Trending products                                             | <Badge text="Supported" variant="tip" /> |
 | No-code UI configurations                                     | <Badge text="Supported" variant="tip" /> |
 | Slots for extensibility                                      | <Badge text="Supported" variant="tip" /> |
+| Recommendation units scoped to catalog and store view (`recommendationsByUnitIds`) | <Badge text="Supported" variant="tip" /> |
 
 ## Section topics
 

src/content/docs/dropins/wishlist/index.mdx

@@ -3,6 +3,7 @@ title: Wishlist overview
 description: Learn about the purpose, features, and use cases for the wishlist drop-in component.
 ---
 
+import Aside from '@components/Aside.astro';
 import { Badge } from '@astrojs/starlight/components';
 
 The wishlist drop-in component provides both guests and registered customers with a mechanism to store products they are interested in purchasing later.
@@ -25,3 +26,7 @@ The following table provides an overview of the Adobe Commerce features that the
 | Wishlist a product for customers | <Badge text="Supported" variant="tip" />      |
 | Move a product from wishlist to cart | <Badge text="Supported" variant="tip" />      |
 | Move a product from cart to wishlist | <Badge text="Supported" variant="tip" />      |
+
+<Aside type="note" title="Scope and compatibility">
+The drop-in does not include built-in wishlist sharing, multiple named wishlists per customer, or full multi-store wishlist isolation beyond what your Adobe Commerce configuration and storefront routing provide. Adobe Commerce on Cloud Services (ACCS) behavior for wishlists has changed across releases, so validate end-to-end behavior for your contract and storefront surfaces before you promise parity with legacy Luma experiences.
+</Aside>