Publishing Model
Discounts support a publishing model that allows testing out changes before making them available to customers.
This is achieved using two data instances:
StagingLive
When a discount is created it is in a status of "Staged", which means it is only available on the Staging data instance. The discount can then be tested on a non-customer facing application/website.
Once happy with the discount, it can be published to the Live data instance. This makes it available to customers.
When a discount is updated, only the staging data instance will reflect those changes. The discount needs to be published to the Live data instance to reflect the changes.
Below is the list of all statuses and their definitions:
- "Staged" - only available on the
Stagingdata instance. - "Modified on Staging" - available on
Livedata instance, but there are changes on theStagingdata instance. - "Live" -
StagingandLivedata instances are the same. - "Suspended" - not available on
StagingorLivedata instances. - "Archived" - this acts as a 'soft' delete.
Expressions also support this publishing model.
See the Management Tooling - Discounts page for more details on how to use the publishing model in the tooling.
Processor API
The settings passed to the Processor API determine which data instance is used. See the Processor API Definitions for more details.