Zum Inhalt springen

OPALTerms Versioning

Manage versions of your terms and conditions traceably and record verifiably for each order which version of the text a customer agreed to – ready for multiple tenants, countries and channels.

OXID eShop 7.4Direct from the platform vendor

Proof of what applied, if it ever comes to a dispute.

Which version of the terms did the customer agree to?

For every order, it should be clear which version of the terms the customer agreed to – even years later. The OPAL versions the terms, keeps published versions immutable and stores the accepted version with a timestamp for each order. The original wording remains reproducible.

What the OPAL solves for you

Every version of the terms is preserved: the OPAL manages versioned terms that become immutable once published, each with a “valid from” date.

Verifiable consent per order: which version a customer agreed to, and when, is stored with the order – the original text can be reproduced at any time.

Ask selectively: if the terms change for ongoing subscriptions or contracts, you obtain renewed consent only from the customers affected.

Part of the OPAL family

OPALs are building blocks from OXID eSales: a proven, solid foundation that needs to be adapted to your system landscape and integrated into your shop.

Features at a glance

Versions with status and “valid from”

Draft, published, archived – exactly one version is always active, each with a “valid from” date. Published versions are immutable; that is the core of the proof.

Multilingual, logically linked

You maintain language versions separately, but they stay assigned to the same version – so no language is stuck on an old version while another has already been updated.

Consent stored with the order

On order completion, the accepted version, customer and timestamp are stored permanently with the order – not as a reference to “the one active at the time”. The text valid at the time of the order can be reproduced in its original form from the order.

Versioned linking & checkout block

In checkout, the page links to the specific version – not to “latest”, so an old order won't later point to the wrong text. Without consent to the current version, checkout can't proceed.

Comparison and change classification

A diff view for admin and support shows the difference between two versions. You mark each change as editorial or material, optionally with a changelog. You make the classification yourself; the module doesn't assess it.

Targeted re-acceptance for contract customers

Notification and renewed consent can be enabled selectively for customer groups (ongoing subscriptions, framework agreements, memberships), for example only for material changes, via in-app, email or webhook.

Who is this OPAL for?

Shops with:

Shops with subscriptions and contracts

You have subscriptions, memberships or framework agreements that continue across changes to your terms.

What the OPAL delivers here

Even after a change to your terms, it's clear for every ongoing contract what was agreed. You only obtain consent again where it's necessary – from the customers it affects.

Frequently asked questions

Price

€20/month

OPALs are also available in subscription packages.

Any questions?

0 characters / 5,000

Request OPAL Terms Versioning

Version your terms and conditions and record verifiably for each order which version was agreed to.