Settings

Open Pohoda → Settings. The screen has two sections in the sidebar tabs, General and Advanced; changes on either tab are saved together.

General

Field	Description
mServer Endpoint	Full URL to the POHODA mServer endpoint, e.g. https://example.tld:444/mserver/service. Required to enable the integration.
Username / Password	Basic-auth credentials sent as an STW-Authorization header. Leave blank if the mServer doesn't require auth.
API key	Optional secret sent as X-API-Key when the POHODA gateway sits behind an API-key-checking proxy.
Company ID (ICO)	POHODA company identifier (ico), included on every generated data pack when set.
Application name	Identifies this integration to POHODA in the application attribute of every request. Required; defaults to Craft CMS.
Default currency	ISO 4217 code (e.g. EUR) used when an order/item doesn't specify its own currency.
Default country code	ISO 3166-1 alpha-2 code (e.g. SK) used for customer addresses that omit a country.
Default VAT code	POHODA VAT rate id (e.g. high, low, none) used when an item/order line doesn't specify its own.
Default warehouse	POHODA warehouse (storage) identifier used on stock exports when an item doesn't specify one.
Enable	Master switch (in the sidebar Details pane). Every export/import call fails fast with a clear error while disabled.

Advanced

Field	Description
HTTP timeout (seconds)	Request timeout passed to the underlying Guzzle client. Defaults to 30.
List batch size	Default page size used by listStockRequest/listOrdersRequest when a console command or service call doesn't override limit. Defaults to 100.
Log XML payloads	When on, every request/response XML body is written to Craft's log — invaluable for diagnosing mapping/schema issues, but verbose; leave off in normal operation.

Use mServer API, Export path, and Stock export request XML also appear on this tab and are saved on the plugin's settings model, but as of v1.2.0 no active service reads them — ItemsService and OrdersService always send XML to the mServer endpoint regardless of these values. Changing them currently has no effect. Use the Import POHODA XML action below for the supported no-mServer stock workflow instead.

The Advanced tab also has two actions:

• Test connection — sends a minimal pohodaTest request using the values currently in the form (including unsaved edits) and reports success/failure inline. Run this after any endpoint or credential change, before relying on scheduled sync.
• Import POHODA XML — uploads a POHODA list-response XML file and parses it straight into the item buffer, without calling the mServer API. Use this when POHODA can produce an export file but the server running Craft can't reach the mServer directly (see Use Cases).

Permissions

The Items and Settings CP sections require the accessPlugin-pohoda permission on top of general CP access, same as any other yStore/craft-core plugin section.