Managing technical trading settings

Settings brings together the store's editable technical specifications in a grouped view. The page allows you to search for a setting, limit the visibility to a single family, change values, and reveal secrets allowed by your access rights.

The change may directly affect payments, shipping, email, searches, online store display, or other functions. Only change a setting that you are familiar with and understand how to revert.

Open and limit settings

Open Settings at /configuration . The view groups settings into families, such as Store, Brand, Catalog, Media, Balance, Checkout, Customers, Pricing, Documents, Email, Search, and SEO.

Search for a setting by its display name or technical key. Use a filter to limit the view to a single family. Search and family restriction work together, and an empty result means that no settings were found that meet both criteria.

Each row displays the name, description, and technical key of the setting. The Settings page does not display the last modification time in the row, although the service stores the modification time in the setting data.

Identify the field type

The settings are selected according to the controller configuration. A yes/no value is displayed as a switch, predefined values as a selection, long or structured texts as a multi-line field, and other values as a text field.

Some of the settings generated through the technical extraction function are read-only. They cannot be changed on this page, and disabling the field does not indicate a permissions error.

Do not change a structured JSON value or service key based on the field type alone. The UI does not validate the business format of all settings before saving.

Change the setting value

Change the setting value directly in the row field. The Settings page automatically saves the change approximately 500 milliseconds after the last entry; there is no separate Save button or cancel dialog.

The right side of the row will display Saving , Saved , or Error . Wait for confirmation of success before leaving the page or changing the next pending setting. In an error state, correct the value and make the change again; there is no separate retry button on the page.

Record the original value in a safe change plan before making a risky change. Autosave also makes a server request for unfinished text if typing is interrupted for more than half a second.

Handle secrets securely

Treat the secret setting as hidden and read-only until you select Show . Revealing requires write access and CSRF checking, returns the full value to the field, and records the reveal event in the history.

Once exposed, the field is editable and uses the same autosave as other settings. Do not select Show unless you need the full value. Do not copy the value into a discussion, support ticket, or screenshot.

The secret update history and reveal history store the hidden value, not the raw secret. This does not remove the responsibility for handling the value displayed on the screen.

Verify the impact of the change

Verify the effect of the setting change after saving. Saving writes the new value, logs the event, and resets the settings cache used by the service request. It does not guarantee that the external service will accept the value or that all long-lived processes will reload it immediately.

Test the change in the functionality that the setting controls. Payment and shipping settings require a secure test transaction, email settings require a test message, and settings that change search or the online store presentation require a review of the corresponding view.

If performance deteriorates, revert to the previous value recorded in the plan. There is no one-button undo or visible event history on the Settings page.

Why use the Settings view?

Settings reduce the need to search for technical specifications in different places. Search, grouping and a visible technical key speed up identification of the correct setting and help with troubleshooting.

The page does not create new functionality or new configuration definitions. It changes settings that the service already knows. If the required configuration is not found, first ensure the correct maintenance surface; the need may belong to a separate integration, payment or delivery method view or require development work.

Good to know

Settings only shows the settings rows returned by the interface.

The names and descriptions of the families are partly in English. The technical key is intentionally displayed for identification, but the key name should not be changed in the value field.

Editing and revealing secrets require sufficient permissions. A history of changes is left on the server, but it is not displayed on this page.