Skip to main content

Configuration

Where: Settings → Configuration

Settings → Configuration stacks the panels that define how your store presents itself and reaches people, followed by a raw settings table for anything advanced.

Figure: Settings → Configuration — store identity, branding, email sender, gateways

Settings → Configuration — store identity, branding, email sender, gateways

Store identity​

  • Store name, Brand color (with a picker), and uploads for the logo (PNG, JPG, GIF, WebP, AVIF or SVG — up to 2 MB. Shown on the storefront, admin and vendor dashboards.) and the favicon (ICO, PNG or SVG, ideally square … Leave empty to use your logo.).
  • Social profiles — links shown in the storefront footer.
  • Email sender — From name, From address, the Mailgun sending domain, and the purpose mailboxes: Sales address (quotes, RFQs, follow-ups, cart recovery), Orders address (order confirmations, status updates, invoices, dunning) and Admin copy (blind-copied on every sales and orders email). If the From address doesn't match your sending domain you get the warning "Sender not aligned" — "From address must match the Mailgun domain (…) for DKIM/DMARC." Fix it or your emails risk the spam folder.
  • Notification emails — the addresses that receive team alerts (comma-separated).
  • Stored credentials — payment-gateway and similar keys. "Values are encrypted at rest and never shown. Saving new ones replaces all."

Email sending​

Send from your own mailbox or Mailgun account instead of the platform default:

  • Your mailbox (SMTP) — host, port, username and the mailbox password; press Save SMTP mailbox. Passwords are write-only: the panel only reports that one is stored.
  • Your Mailgun account — paste an API key, choose the region, press Save sending config, then under Domain & DNS press Set up / verify domain and add the records the panel lists to your DNS (e.g. Cloudflare, as "DNS only"). Re-check until every record verifies.
  • Prove it works — enter your address and press Send test email.

The transport order is: your own configuration when complete, otherwise the platform default. See Invoices and Prebuilt automations for what gets sent.

WhatsApp, WhatsApp rooms, Staff numbers​

Connect the store to a WhatsApp number, let the assistant answer there, classify group chats, and link staff numbers. This is a topic of its own — see WhatsApp.

SMS​

Connect your Sozuri project and sender ID so payment reminders can go out by text. See SMS.

AI lead prospecting​

Optional keys the assistant uses when you ask it to find prospects: a Web search key (Brave Search API) and Tender feeds (one RSS/Atom URL per line). Remove the key to switch prospecting off.

Directory listing​

Tick List us in the directory to appear in the platform's public supplier directory, with What you sell, industries (Press enter or comma between each. Up to 12.), Regions served and a Contact email. Press Save listing.

Custom domains​

Serve the storefront on your own domain: type it (e.g. shop.yourcompany.com), press Add domain, add the DNS record the panel shows (Add this DNS record at your domain provider, then click Verify), then Verify. Make primary switches the canonical address; Remove detaches a domain. Details under Websites and custom domains.

Storefront copy​

"Wording shown on your storefront. Leave a field blank to use the default." — the Catalog menu label, the Contact page heading and prompt, the Request a quote heading and prompt, the Company details note, and Why open an account (Shown on the sign-up page and read out by the assistant when a visitor asks what an account gives them.). Press Save copy.

Price visibility​

Who may see list prices on your storefront: Configuration → Quotes & pricing → Who sees list prices (key storefront.price_visibility): public (the default — everyone), customers (only signed-in buyers), quote_only (nobody — a buyer sees prices only on the quote that answers their RFQ, so competitors never do). With quote_only, every product shows Price on request and the cart hands off to a quote request; the assistant follows the same rule.

Invoice payment details​

Store identity → Payments → How to pay (key billing.payment_note) is your payment text: M-Pesa paybill or till and the account to quote, bank name and account, cash on collection, card online. Set Gateway to none when you take no online payment — buyers then see only these instructions and a link to report what they paid; mock is a demo processor that settles invoices without money and is refused in production. The text prints on every invoice PDF, shows in a How to pay box on the buyer's invoice page and in the invoice email, next to a Paid already? link where the buyer reports the M-Pesa or bank reference; those reports land under Sales → Payments as claims to accept or reject. billing.address and billing.contact fill the seller block on invoice and quote PDFs.

VAT on quotes​

Configuration → Quotes & pricing → VAT on quotes (key quotes.tax_display) — exclusive (the default; quotes show prices before VAT and the order adds it) or inclusive (VAT on every quote line, in the total, the email and the PDF). Default tax country (key tax.default_country, e.g. KE) picks the rates for a buyer with no address on file; the rates themselves live under Tax & shipping. See quotes.

Search & AI visibility​

Three switches: Appear in search results, Be cited in AI answers, and Allow use as AI training data. They drive your storefront's robots.txt and content signals — index and cite by default, train only if you say so.

Business profile​

What the assistant and /llms.txt say about you: What you sell, in one sentence, Registered company name, VAT / GST number, Tax / company registration number, Trading since, Contact & reach (sales email and phone, Where you deliver — Comma-separated. Answers "do they ship to me?"), Other profiles, and the Trading address.

The raw settings table​

Below the panels, advanced key/value settings with scoping. "Settings can apply organization-wide or to one website, group, or customer. The most specific one wins."

  1. Press New setting.
  2. Choose Applies to (org / website / group / customer), the Applies-to ID (not for organization scope), the Setting name (e.g. free_ship_threshold), a Value type (Text / Number / Yes-No / List of values / Advanced (JSON)), and the value.
  3. Save. More specific scopes override broader ones — which is what makes per-customer overrides possible.

Check which value applies resolves any key for a given website, group or customer and shows you which scope won.

note

Validations here are strict on purpose: "Org scope must not have a scope id.", "This scope needs a scope id (website/group/customer).", and JSON values must be valid JSON.