Store promotion scheduling fields are now optional and nullable

What's new

start_at and end_at on store promotions are no longer required and may be null. The change applies to both the request and the response across every store promotion endpoint.

Impact

You can now create an open-ended promotion (no fixed start or no fixed end) by omitting these fields or setting them to null. Existing schedules continue to behave the same way.

Changes

Resource	Change
create_store_promotion	start_at and end_at became optional and nullable in both request and response
get_store_promotions, get_store_promotion, update_store_promotion, bulk_update_store_promotions, get_user_promotions	start_at and end_at became optional and nullable in the response

Upgrade

• If your client or generated types expect start_at and end_at to always be present and non-null, update them to handle missing or null values.

Need help?
Contact our integration team at [email protected]