Skip to main content

Scheduled updates

Scheduled updates allow price changes to take effect automatically at a defined future moment.
This makes it possible to plan and coordinate pricing changes without manual deployment work or midnight operations.

Scheduled updates integrate fully with inheritance, bundles, and historical pricing, and behave deterministically across all nodes.

What Scheduled Updates Are​

A scheduled update is a future version of a price or bundle definition that becomes active at a precise timestamp.

Scheduled updates may modify:

  • Base prices
  • Quantity breaks
  • VAT mode
  • Currency
  • Rounding rules
  • Metadata
  • Bundle definitions
  • Component overrides
  • Pricelist-level settings

Until the activation time arrives, the current version remains active.

At the activation timestamp:

  1. The scheduled version becomes the new “current” version
  2. The previous version becomes part of the historical chain
  3. All price evaluations after that moment use the newly activated data

Benefits​

Predictable Go-Live Behaviour​

Coordinated pricing campaigns or contract changes can be prepared in advance and activated exactly when intended.

No Manual Night-Time Operations​

Midnight changes or regulatory updates no longer require late-night updates, deployments, or API calls.

Seamless Integration With History​

Every scheduled update becomes part of the historical record automatically.

Compatible With Large Catalogs​

Activations scale across millions of SKUs without needing a re-ingestion of the full dataset.

How Quantaprice Applies Scheduled Updates​

When a price is evaluated, Quantaprice determines:

  1. Is a scheduled update relevant?
    If the evaluation timestamp is before activation → use current version.
    If after activation → use scheduled version.

  2. Is historical mode requested?
    If an “as of” timestamp is provided, scheduled updates are considered only if they were active at that moment.

  3. Does inheritance apply?
    Child pricelists use their own scheduled updates first; if none exist, they inherit the parent’s scheduled changes.

After determining the correct version, the resolved price continues through the standard pipeline: inheritance → bundle logic → VAT → rounding.

Interaction With Other Pricing Features​

Inheritance​

Scheduled overrides behave just like regular overrides.
Child pricelists inherit scheduled updates unless they define their own.

Bundles​

Scheduled component or bundle updates activate at their defined timestamp.
Bundle evaluation uses the correct version for each component.

Historical Pricing​

Once a scheduled update activates, it becomes part of the historical timeline automatically.

VAT & Rounding​

Scheduled updates may change VAT mode or rounding rules.
These changes apply only after the activation timestamp.

Best Practices​

  • Use scheduled updates for all timed price changes
  • Prefer scheduled updates over multiple deployments
  • Keep activation timestamps precise, especially for cross-market changes
  • Use metadata to group SKUs for large-scale changes

Summary​

Scheduled updates allow you to plan and activate future price changes automatically and reliably.
They work seamlessly with inheritance, bundles, VAT, rounding, and historical pricing — ensuring correct behaviour at every point in time.