Developers Comm-Dev-101 Reddit Questions

A storefront filter is represented in B2C Commerce product search as asearch refinement. Therefore, after creating or selecting an appropriate product attribute, the administrator must create a Search Refinement Definition that associates the refinement with that attribute and the appropriate category/search context.

Merely marking an attribute searchable is not equivalent to defining it as a refinement. " Searchable " primarily determines participation in keyword-search behavior, while a refinement definition instructs the search system to expose attribute values as shopper-selectable filters. The attribute must also contain values on relevant products and be represented in the search index for the refinement to produce useful values.

Changingproductsearchrefinebar.ismlis not normally required. SFRA retrieves available refinements dynamically from the Product Search Model, so configured refinements can appear through the standard refinement components without hard-coding each attribute into the template.

Salesforce confirms that custom Product attributes can be created forsite search, search refinements, or sorting rules, demonstrating that refinement configuration is a distinct use of the attribute.

Study Guide reference:Data Management Using Business Manager Usage — Search Refinement Definitions, custom Product attributes, search indexing, and storefront product filtering.

===============

The required workflow creates a new shipment for a gift item and then modifies shipment information associated with the basket. The OCAPI basket shipment hooks corresponding to those two operations aredw.ocapi.shop.basket.shipment.beforePOSTanddw.ocapi.shop.basket.shipment.beforePATCH.

Salesforce ' s OCAPI hook documentation definesshipment.beforePOSTas the extension point executed before creation of a shipment andshipment.beforePATCHas the extension point executed before modification of an existing shipment. Those operations align directly with the described solution: establish the separate shipment and then apply the necessary changes before final basket validation.

The alternatives involvingbeforeDELETEorafterDELETEare inconsistent with the scenario because no shipment needs to be deleted. The requirement is to separate a gift product into its own shipment, not remove a shipment from the basket.

The concludingvalidateBaskethook provides the final validation stage after the basket/shipment changes have been processed, allowing custom logic to ensure that the resulting basket remains valid.

Study Guide reference:Application Development — OCAPI Shop API hooks, basket extension points, shipment creation and modification, and basket validation.

===============

B2C Commerce provides a dedicatedAvailability Low Ranking Thresholdspecifically for this merchandising requirement. The setting is available in Business Manager under Search Preferences and controls the availability percentage at or below which products are pushed toward the bottom of storefront search results.

Salesforce ' s documentation gives a direct example: entering0.3causes products whose availability is 0.3 or lower to be ranked lower in the search result set.

This is preferable to hiding low-stock or unavailable products using a scheduled job because it preserves normal catalog state and responds through the platform ' s search-ranking engine. A scheduled cleanup introduces latency, custom operational overhead, and unnecessary product-state mutations.

Option B is also not the correct mechanism. Searchable Attribute boost factors influence relevance weighting for indexed attributes; availability already has a purpose-built ranking preference.

Using the low-ranking threshold lets products remain discoverable while prioritizing inventory that is more likely to convert successfully.

Study Guide reference:Data Management Using Business Manager Usage — Search Preferences, Availability Low Ranking Threshold, product availability, inventory-aware ranking, and search merchandising.

===============

The new requirement is additive: the existingCart-Showbehavior should continue running, and the client cartridge only needs to add adataLayerproperty to the response. SFRA ' s preferred mechanism for this type of extension is toappend middleware to the existing routeand enrich its ViewData.

Salesforce documentsserver.appendas a controller-customization mechanism that executes the existing middleware chain and then adds an additional step. A common use is precisely to retrieve and update the current ViewData with extra properties that are needed during rendering.

This also preserves cartridge independence. Throughmodule.superModule, the client cartridge resolves the applicable controller immediately to its right on the cartridge path. If the LINK cartridge exists, its customized route participates. If it is later removed, resolution can fall through to the next implementation, such asapp_storefront_base, while the client ' s appended data-layer logic remains unchanged.

Replacing the entire route unnecessarily couples the client implementation to existing logic and duplicates behavior that SFRA ' s extension model already provides.

Study Guide reference:Application Development — SFRA controller extension,server.append,module.superModule, ViewData, cartridge precedence, and upgrade-safe customization.

===============