Skip to content
Birdhouse

Configure Quote-Price Versioning

Quote-price versioning lets you maintain multiple pricing configurations for the same product, each with an activation date. The system automatically uses the correct version based on the current date.

Role split

Section titled “Role split”
  • Product/Ops: Create the new version entry and set the effective date.
  • Engineering: Update the pricing calculations.
  • Both: Test on staging before the effective date.

Prerequisites

Section titled “Prerequisites”
  • A published quote-price entry in Strapi
  • Understanding of the quote-price content type (see Quote-Page Components)

Steps

Section titled “Steps”

1. Understand version selection

Section titled “1. Understand version selection”

The system selects the quote-price version where effectiveFrom is the most recent date that is less than or equal to today. This means:

  • A version with effectiveFrom: 2025-01-01 activates on January 1, 2025
  • If a newer version exists with effectiveFrom: 2026-01-01, it takes over on January 1, 2026
  • The older version remains active until the newer one’s date arrives

2. Create a new pricing version

Section titled “2. Create a new pricing version”
  1. In Strapi, navigate to Content Manager > Quote price
  2. Duplicate the existing quote-price entry for your product
  3. Update the effectiveFrom date to when the new pricing should activate
  4. Modify the pricing calculations (in the type dynamic zone — either json-builder or private-pengine)
  5. Publish the new entry

The effectiveFrom field is a required date field on every quote-price entry.

Section titled “3. Link versions via the metadata”

Each quote-price entry has a metadata component (quote-price.meta) that identifies which product it belongs to. Ensure the metadata matches across all versions of the same product so the system can find and compare them.

4. Common use cases

Section titled “4. Common use cases”
Use case Approach
Annual premium adjustment Create a new version with effectiveFrom set to Jan 1 of the new year
Regulatory price change Set effectiveFrom to the regulation’s effective date
Mid-year correction Create a version with the correction date

5. Test before the effective date

Section titled “5. Test before the effective date”
  1. Staging: Deploy the new version to staging Strapi and verify pricing calculations
  2. Date simulation: If possible, test with a future date to confirm the version switch works
  3. Rollback plan: Keep the old version published — the system will fall back to it if the new version is unpublished

See also

Section titled “See also”