Draft, review, release, adopt
These are distinct decisions. Authors prepare a change; reviewers check it; release makes a version available; consuming systems choose when to adopt it.
Keep the source of truth explicit
A dataset may be maintained here, imported from an authoritative ERP or supplied by an agreed integration. Define ownership before introducing synchronisation.
Retain an understandable history
Earlier released versions should remain identifiable. Reverting data is a new adoption decision, rather than rewriting the record of what a past order used.
Early access starts with an agreed workflow. Supported scope and onboarding arrangements are confirmed with you.