Settings | IMI Life Science

Settings

Purpose: Manage customer experience, commercial operations, and platform controls from one business-focused index.

Find a Settings Area

  • Search by outcome: Search for a concept such as payments, passwords, email, or backups without needing to know its technical category.
  • Check the scope: Each destination states which audience or business process it affects.
  • Review impact guidance: Settings with immediate or broad effects show that guidance directly on the destination card.

Business Groups

  • Customer experience: Website identity, business capabilities, brands, and locations.
  • Sales and engagement: Delivery rules, customer communications, and connected external services.
  • Platform operations: AI services, access and security, backups, recovery, logs, and diagnostics.

Business Capabilities

  • Selling: E-commerce, quoting, guest checkout, payment requests, and payment methods.
  • Storefront: Visitor-facing AI, search, stock visibility, newsletter, and contact controls.
  • Fulfilment: Delivery calculation, warehouses, refunds, order notices, and compliance checks.
  • Administration: Optional AI and inline editing tools for authorized staff.
  • Advanced: Engineering-owned translation migration controls. Use these only during a coordinated rollout and follow the displayed sequence.

Saving and Impact

Most switches save immediately and can change active customer or staff workflows. Configuration forms with a save button apply their fields together. Review the stated scope before changing production settings.

AIMI Credentials

Manage the AIMI API key under Platform operations → AI services. The key is write-only: Back Office shows whether one is configured but never displays its value. Enter a new key and save to rotate it, then use the connection test to verify the endpoint.

Warn Users of Reserved IT Accounts

  • Choose accounts: Open Platform operations → Access and security, then select the administrator accounts strictly reserved for IT.
  • Use the right scope: Select shared, setup, or emergency accounts whose credentials may be changed without notice. Do not select individual staff accounts.
  • Save the list: Selected users see a persistent warning beneath the Back Office header on every page. Removing an account from the list removes its warning.

ERP Orders and Invoices

  • Open: Select a person, then Orders. ERP-linked customers have ERP orders and ERP invoices above their separate website orders.
  • Find: Search order, purchase-order, part, or invoice references. Use the page arrows for additional records.
  • Order scope: The ERP order book includes orders dated in the last 24 months. Quantities, prices, delivery dates, and invoice balances come from ERP.
  • Download: Select PDF beside an issued invoice to download the original archived document. Proforma and VMI documents are excluded.
  • Access: The contact email must match an active website account with both ERP customer identifiers. Staff need Users view and Sales orders view-all permissions, or the Admin role.
  • Configuration: In Settings, Integrations, set AccountingServices Base URL and Invoice archive path, then save invoice settings. The archive reuses the document-share host and read credentials. Credentials remain private.
  • Unavailable records: Refresh when ERP is unavailable. A missing original PDF cannot be recreated here; check the archive configuration or contact the ERP team.

Storefront Comparison And Price Visibility

  • Open the controls: In Settings, open Business capabilities and select Storefront.
  • Product Comparison: Switch off to hide comparison buttons, the selected-products bar, and the comparison page. Saved selections remain available when comparison is switched on again.
  • Show Prices: Switch off to hide monetary amounts across product displays, cart, checkout, payments, order tracking, quotes, and customer account views. Price filters and product structured-data offers are also hidden.
  • Independent controls: Both settings default to on. Hiding prices does not change server pricing, payment amounts, stock, purchasing eligibility, or quoting. These are display controls, not access restrictions on pricing APIs or downloaded documents.
  • Refresh storefront settings: After saving, reload the storefront to load the updated global settings. Local card and layout options cannot override a disabled global setting.

Client CB Destination and Currency Mappings

  • Settings: Open Settings, Integrations, Client CB mappings. Set the domestic ISO country and the ERP company, currency and sales-condition identifiers for each Domestic or Export currency. Save mappings commits the whole configuration together.
  • Destinations: Orders shipped to the configured domestic country use Domestic; all other destinations use Export. Currency does not determine the destination account.
  • Regional prices: Preview and apply each account/currency separately. Domestic and Export schedules can differ. Applying one leaves the other account, legacy schedules and customer-specific contracts unchanged.
  • Validation: Configured identifiers must match active ERP conditions. Missing selling prices, missing ERP-designated defaults and unsupported quantity or delivery constraints block application. Regional schedules are never converted into an unconfigured currency.
  • Checkout: Product displays use the detected country as an estimate. Final pricing is resolved server-side for the shipping country. Run a fresh preview after changing mappings.

Customer Area Visibility

  • Open the controls: In Settings, open Business capabilities and select Customer Area.
  • Choose sections: Independently show or hide Dashboard, ERP Orders, Invoices, Profile, Addresses, Website Orders, Payment Methods, Quotes, Bookings, Support, Email Preferences, and Security. Each switch saves immediately.
  • Consistent visibility: Hidden sections disappear from desktop and mobile account menus, dashboard summaries and shortcuts, and the profile preferences link. Direct visits to hidden sections return to the first available account section, or the homepage if all sections are hidden.
  • Existing eligibility: Switching a section on does not override commerce availability, quoting settings, or ERP customer eligibility. Support visibility also controls nested returns pages; the separate ERP Returns setting still applies.
  • Defaults and scope: All sections default to visible. Login, registration, and Sign Out remain available. These are storefront presentation controls, not backend API authorization or deletion of customer data.
  • Refresh: Reload the storefront after saving to load the updated global settings.

Basic Quote Request Mode

  • Choose the workflow: Open Settings, Business capabilities, Selling and checkout, then enable Basic quote request mode. The setting saves immediately and is off by default.
  • Customer view: Customers can still submit requests and view their request details. Quote lists, details, and dashboard summaries show Submitted, requested prices, and no offer expiration or accept and decline controls.
  • No approval workflow: Review and save request pricing directly in Back Office. Send to Customer and offer validity controls are unavailable. Saving a submitted request keeps it Requested rather than moving it to Draft, and sends no quote-ready notification.
  • Read-only enforcement: Sales blocks sending offers for customer approval, customer acceptance, and customer rejection while this mode is enabled, including direct API calls. Authorized Back Office users can still reject requests.
  • Standard mode: Switch this mode off to restore the normal customer offer status and acceptance or decline workflow. No quote records are rewritten.
  • Availability and refresh: B2B Quoting still controls whether quote requests are available. Reload the storefront after changing the mode to load the updated global settings.

Chatbot System Prompt

  • Edit the policy: Open Settings, Platform operations, AI services, then use the Chatbot policy Editor tab. Save chatbot prompt writes only this policy and applies to AIMI and Ollama. The saved/unsaved indicator and character counter track the draft; Discard changes returns to the saved text without writing.
  • Protect the scope: Keep the assistant focused on IMI Life Science products, technical resources, relevant applications, website navigation, and customer support. The initial policy declines unrelated requests, including recipes and off-topic follow-ups, and protects confidential instructions and customer information.
  • Preserve safeguards: Retain the rules for untrusted messages and retrieved documents, factual accuracy, valid source links, and safety-critical questions. The prompt cannot be blank. A failed save retains your draft for retry.
  • Activation: Changes may take up to five minutes to reach the AI service. The policy applies to every chat turn, including existing conversations and both semantic and keyword retrieval. Saved administrator policies are not reset by initialization.
  • Review answers: Prompt instructions reduce off-topic behavior but do not guarantee model compliance. Test representative off-topic requests, follow-ups, and legitimate product questions with your configured model.
  • Use the sandbox: Open Sandbox, choose a test scenario or enter a Test message, then Run test. It uses the current draft immediately, public-content retrieval, and the saved AI provider without saving the policy or creating a production chat session. Follow-ups stay local to that draft; changing the draft starts a new test conversation on the next run. Reset sandbox clears its conversation. Drafts are limited to 16,000 characters; test messages to 4,000, with at most 20 prior messages sent per request.
  • Review versions: Open History to read retained Cms.GlobalSetting audit entries for this policy, including archived entries. Select Saved version or Before change to preview the recorded text, actor, and timestamp. History requires audit-read permission in addition to settings-management permission. Audit delivery is asynchronous; use Refresh history if a recent save is not visible.
  • Restore a version: Select a recorded snapshot, choose Restore version, and confirm. Confirmation replaces the saved policy and any unsaved draft with the selected text. The normal settings save creates a new audited change and keeps prior entries. Cancel preserves your draft; an unconfirmed restore keeps the dialog and local draft for review or retry.
  • History retention: Only actual retained prompt snapshots are restorable. Metadata-only or malformed entries are ignored; purged audit records cannot be recovered by this editor. A lost response does not prove that a save failed, so refresh history before retrying an unconfirmed restore.
  • Sources: Storefront source references start collapsed for each answer. Select Sources to expand or collapse the reference links.

Policy Conflict And Recovery

  • Concurrent edits: Saves and restores compare the exact saved text before writing. If the policy changed elsewhere, the draft is kept and saving is blocked. Review the latest saved policy, then choose Keep draft after review only when you intend to retain your edit against that newer baseline.
  • Lost responses: The editor verifies the saved policy before allowing another write. If the intended value is already saved, it acknowledges it without repeating the write. If verification is unavailable, use Refresh saved policy when connectivity returns. Your draft remains available.
  • Bounded operations: Writes have a 30-second deadline and recovery reads 20 seconds. Sandbox tests have a 90-second deadline and Cancel test preserves the question. Late canceled responses cannot replace current results. Browser requests are not automatically replayed after rate limiting.
  • Restore safety: Confirmation is disabled if the saved baseline or selected retained audit snapshot changed, or history cannot be verified. Close the dialog and review refreshed history. A restore never silently chooses a different snapshot.
  • Leaving the section: Back to settings requires confirmation before discarding a draft or test message, and running operations must finish or be canceled first. Browser unload warns about unsaved work. Other application navigation is not globally blocked; save or use the section exit before navigating away.
  • Service recovery: Rate limits, unavailable dependencies, invalid model output, and timeouts are reported separately. Failed tests keep the question and policy; changing the policy or saved provider starts fresh follow-up history. Audit availability still depends on retained records and the shared audit transport.