Settings, changed in Atrium and Keystone
Meridian
Meridian holds the settings the products follow, by company, region, site, and product. Customers do not sign in to it. Administrators change those settings in Atrium and Keystone. A change is reviewed, published, and can be rolled back.
Who it is for. Not a screen for customers. Administrators reach it through Atrium and Keystone
Why this is not a module of SAP, NetSuite, or Dynamics
In those suites a price, a location rule, and a tax code are changed in three different modules. Meridian keeps the setting once, and every product follows the published version. Customers never open Meridian to do that. The change is made in Atrium or Keystone.
What the business runs here
- Not a product a customer opens. Settings are changed in Atrium and Keystone
- Settings from the whole platform down to a site or a person, with the more specific rule winning
- A review step before a change goes live, plus a history you can roll back
- A documented default when a setting has not been changed
- Passwords and keys stay out of the setting itself. Products keep working from the last published version if a change cannot be reached
How it works with the rest of the company
Keystone decides which companies exist and which products they may use. Atrium is where an administrator edits a rule. Meridian stores that rule and publishes it. The warehouse, the store, and the other products follow it. They do not offer Meridian as a screen of their own.