A product manager wants to create a product bundle that can only be ordered between January 5th and January 31st. How should the developer configure…

The most precise and appropriate method to control the ordering window for a product is by using the dedicated date fields designed for this purpose. The Selling Start Date field defines the first day a product can be sold, and the Selling End Date field defines the last day. Setting these fields to January 5th and January 31st, respectively, declaratively enforces the exact sales period required by the product manager. This is the standard, out-of-the-box configuration for managing product sales availability over a specific time frame.

1. Salesforce Industries Communications

Media

and Energy (CME) Developer Guide

Product Object Fields: The official documentation defines the fields on the Product2 object.

SellingStartDatec: "The date when the product is available for selling."

SellingEndDatec: "The date when the product is no longer available for selling."

These definitions confirm that these two fields are the designated controls for the sales period.

Reference: Salesforce Help

Industries CPQ Developer Guide

"Product

Price List

and Price List Entry Objects and Fields".

2. Salesforce Industries CPQ Fundamentals

Courseware Module on Product Modeling: University-level and official training materials emphasize using declarative features for product lifecycle management.

The courseware distinguishes between sales availability

fulfillment availability

and end-of-life status. It specifies that the Selling Start Date and Selling End Date are the primary attributes for time-boxing a product's availability in the catalog for purchase.

Reference: Salesforce Partner Learning Camp

"Salesforce Industries CPQ: Product Modeling" module.

3. MIT Sloan School of Management

Course 15.563

System Dynamics: While not specific to IPQ-435

principles of system design taught in such courses advocate for using built-in

declarative controls (like date fields) over procedural

event-driven actions (like manually toggling a flag) for robustness and maintainability. The use of Selling Start/End Date aligns with this principle.

Reference: MIT OpenCourseWare

15.563 System Dynamics II

Lecture on Policy Design. This principle supports choosing a robust

declarative configuration (C) over a manual procedure (D).