Access and modes

  • Settings requires both account and selected-webshop permission.
  • No-access users are redirected away from Settings.
  • View-only access keeps supported navigation and read-only values but removes Save, Undo, and editing.
  • Edit access or shop-administrator access exposes the editable shell.
  • Lite can show locked controls with an upgrade indicator.
  • Blocked or incomplete onboarding state can prevent access.

Settings opens General by default.

Settings sections

Depending on configuration, navigation can include:

  • General — company identity, receipt behavior, inventory keeping costs, currency, and time zone;
  • Algorithm — forecast and algorithm controls;
  • ABC classification or ABC-XYZ classification;
  • category and service-level simulation surfaces;
  • Email settings;
  • Inventory control;
  • Data management;
  • Miscellaneous;
  • separately gated Users, Billing, Integrations, Imports/Exports, Workflows, Promotions, Assembly, and other modules.

Use these focused guides:

Save and undo

Editable Settings use a shared action bar:

  • Save becomes available only when pending changes are valid and the page is not loading, saving, or temporarily locked.
  • Undo changes restores the saved values.
  • A progress indicator appears while saving.
  • Pending changes protect against accidental navigation or webshop switching.

When a save fails, Settings reloads persisted values and shows failure feedback. Check the fields, correct visible validation, and retry only after loading finishes.

Selected-webshop boundary

Settings belong to the selected webshop. Switching webshop can change the displayed currency, feature flags, algorithm settings, inventory controls, email templates, and other values.

Do not assume a setting is global across every webshop in the account. Confirm the selected webshop before editing.

Downstream effects

Settings can affect other areas without making those areas into Settings editors:

  • Company name can appear in Supplier email and purchase-order communication.
  • Default receipt quantity affects the Delivery editor.
  • Email templates can be used during purchasing and delivery communication.
  • Edit buy orders affects eligible placed orders on Deliveries.
  • Purchase consumes webshop configuration, but Purchase has its own permissions and workflows.

Save and undo Settings changes

Purpose

Save valid Settings changes for the selected webshop or deliberately discard pending edits before navigating away.

Prerequisites

  • Open an editable Settings section for the correct webshop.
  • Make an intentional change in one available section.
  • Review downstream Product, Purchase, Delivery, or integration ownership before saving.

Steps

  1. Review the edited fields and any visible validation.
  2. Choose Save to persist valid changes, or Undo to restore saved values.
  3. Wait for loading and saving to finish.
  4. If navigation warns about unsaved changes, return and choose Save or Undo.
  5. Reopen the section and verify the persisted values.

Fields and columns

  • Selected webshop and section — define the scope of the pending configuration.
  • Save, Undo, validation, loading, and saving state — control whether the form can persist or discard edits.

Save, Undo, loading, saving, validation, selected-webshop context, and unsaved-change warnings control the form lifecycle. No table columns are required.

Expected result

Valid changes are shown after reopening the section, or Undo leaves the previously saved values unchanged.

Limitations

  • Save and Undo availability depends on edit permission, form validity, loading state, and an actual change.
  • Settings apply to the selected webshop unless the interface states otherwise.
  • Saving does not guarantee immediate downstream recalculation or external synchronization.

Errors and recovery

  • If Save is disabled, correct validation, wait for loading, and confirm that a value actually changed.
  • If navigation is blocked, return to the edited section and save or undo before leaving.
  • If saving fails, reopen the section and use the persisted values as the source of truth before retrying.