What can you customize yourself in the AI Commerce dashboard?
A summary of the most common dashboard settings, such as currency symbol, decimal separator, texts, statuses, navigation, and footer.
Self-made changes to the control panel
In the AI Commerce Dashboard, you can customize many of your store's out-of-the-box configurations without any software development. These include currencies, order and quote statuses, countries, languages, taxes, domains, payment and shipping settings, as well as links in your store's Custom Navigation view and custom footer links.
The right to change depends on the user's permissions. Always also evaluate the impact of the change on checkout, prices, integrations, search engines, and customer visibility.
Find the right management tool
When using the AI Commerce Dashboard, select the tool based on the information you want to change:
- Currency name, ISO code, exchange rate, symbol, or decimal format: Settings → Currencies .
- Order status name, internal code, color, default, or invoice number requirement: Orders → Order statuses .
- Offer status name, internal code, or default: Offers → Offer Statuses .
- Installed configuration of payment or shipping method: Settings → Payment methods or Settings → Shipping methods .
- Country, language, tax category or tax rate: corresponding register in the Configuration area.
- Domain, language, hreflang, pixels, or chat assistant domain-specific values: Settings → Domains .
- Store's own navigation or footer links: CMS → Custom navigation or Custom footer .
Editing products, categories, service pages, and other actual content belongs to their own content tools, not this list of settings.
Edit currency
In AI Commerce 's Currencies view, you can create a currency and edit its name, three-letter ISO code, exchange rate, left or right symbol, decimal separator, and number of decimal places. You can also set the currency as the default.
Edits are saved automatically. Check the save status before exiting. Changing the default currency and exchange rate can have a significant impact on pricing and reporting, so verify the value and impact before changing. The default currency cannot be deleted.
Manage order and quote statuses
In AI Commerce 's Order Statuses register, you can create and edit language-specific names, internal code, color, default status, and the Requires payment or invoice number setting.
In the Offer Statuses register, you can manage language-specific names, internal code, and default status.
The Code in the control panel is not the API ID of the order status . Do not change the internal code to fix the ERP mapping. A status that is in use or set as default should not be deleted; the user interface checks for usage before deleting.
Manage payment and shipping methods
In AI Commerce 's Payment Methods and Shipping Methods views, you can see the installed modules, their usage status, order, and module-specific settings. Some fields are saved when you change them without a separate global save button.
Only change fields that have a known impact. Payment method keys, IDs, and provider values can affect payment processing. Delivery method codes, customer groups, prices, and ERP mappings can affect checkout and integrations. A new payment process or delivery logic is a development effort, even if the visibility or order of an existing module is a configuration change.
Manage countries, languages, and taxes
AI Commerce 's Settings area has its own registers for countries, languages, tax categories, and tax rates.
- Countries : country name, ISO 2 and ISO 3 codes, default currency, customs threshold, customs rate, and business information requirement.
- Languages : name, two-letter ISO code, translation directory, and flag image filename.
- Tax categories : name and description.
- Tax rates : a definition formed by tax category, region, and tax percentage.
Changes to these registers are automatically saved in the edit view. Country and tax changes can affect cash validation, tax calculation, and the choices offered to the customer. Make a tax decision with financial administration approval; The control panel implements the determination, does not decide the tax treatment.
Manage domain and chat assistant values
In AI Commerce n Domains view, you can manage your online store's hostname, country, language, hreflang value, usage mode, ranking, WordPress domain, ad and analytics pixels, and OpenAI chat help, assistant, and vector inventory tags.
The domain usage mode determines whether that store context is served to visitors. It is not a separate on/off switch for chat. Domains, hreflang, and secrets are high-impact settings. Do not copy API secrets into a support ticket or screenshot, and ensure routing and search engine visibility after the change.
Manage Custom Navigation links and footer
AI Commerce 's Custom Navigation includes language-specific link names, target, hierarchy, order, visibility, and an optional clean SVG icon. The Custom Footer includes language-specific footer links and their order.
Link edits are saved automatically. Deleting requires confirmation and also removes the link translations. After making a change, check each store's language, link target, mobile view, and hierarchy. These tools manage the store's own additional links; the visibility of categories in the main navigation is controlled in the category settings.
Distinguish between a setting, a bug, and a development request
A change made in the AI Commerce Dashboard is usually a setting change, when an accepted value is changed for an existing field, the finished text is corrected, or the visibility and order of an existing module is adjusted.
This could be an error if the save fails, the accepted value does not work as described, or the view gives a conflicting result. Development work is needed when the desired outcome requires new operating logic, new integration behavior, new field, user interface element, or store-specific implementation.
In a support situation, first find the correct Dashboard view and check the user's permission. If the field exists, provide specific instructions and describe the impact. If the field does not exist, classify the need as a bug, partner work, or development request according to its actual owner.