Installation

Installation and maintenance

The installer is a single file and takes about ten minutes. The product ships with no accounts or passwords; Sovos and Yukato details are entered in the panel after installation.

Requirements

Windows Server 2016+ or Windows 10/11 (64-bit), administrator rights.
SQL Server 2016+ (Express is enough). The product creates its own database; inside an ERP database its tables are prefixed.
A Sovos e-Despatch web service user (read access at least) for each sender company.
A Yukato External Shipper API account (Test and/or Live): client id, secret, user, sender company and address ids.
Outbound HTTPS to the Sovos endpoint, the Yukato API and lisans.erp.tr. A corporate proxy is set under Configuration.
No .NET installation needed; the package carries its own runtime.

1. Run the installer

Download Sovos2YukatoKurulum-1.0.0.exe, right-click → Run as administrator. The installer:

unpacks the application to C:\Program Files\ERP\Sovos2Yukato (change with --klasor),
installs the ERP Sovos2Yukato Windows service and starts it on port 5191 (change with --port; a free port is suggested if busy),
writes the access address (IP + port) into the service description,
opens the setup wizard in Edge or Chrome.

The same package performs updates: the connection string, settings, keys and logs are preserved and a health check runs after the service restarts on the new version.

2. Setup wizard (first run)

SQL Server connection: server, authentication type and database name; you cannot continue until Test connection is green. A missing database is created and the schema is installed automatically.
Setup package (optional): a password-protected settings package exported from another installation is previewed and applied; skipped on a fresh install.
Windows service: service state, port and start/stop.
Summary: connection check and service state on one screen; the panel opens.

The first administrator account is admin. Its password is generated on the server by Sovos2Yukato.App.exe reset-admin in an elevated console; it is single-use and must be changed at first sign-in.

3. Configuration

The Configuration screen is a step-by-step wizard. Secrets (passwords, client secrets) are stored encrypted with the machine key and masked on screen.

Sovos accounts — Sovos user, password and tax id for each sender company.
Sovos connection — endpoint (test/live), polling interval; connection test.
Yukato — Test / Live switch, API details per environment, sender company name.
Mapping and schedule — store code → Yukato address map, pull/push/tracking intervals.
Database connection — structured editing and testing of the connection string.
Retail customers — tax ids of recipients whose advices become shipments.
Network / proxy — Automatic, None or Manual (with Windows identity); the reachability test measures DNS → TCP → TLS → HTTPS.
Licence — licence details; offline .erplic file for installations without internet.
E-mail — SMTP server for temporary-password and password-reset mails.

Send a few advices end to end in the Test environment first, then switch to Live.

Accessing the panel

The panel is served at http://<server>:5191; the address is also shown in the service description in Windows Services. If it must be reachable from outside, put an HTTPS reverse proxy (IIS, Caddy) in front of it.

Updates

Licensed installations check the ERP update channel for signed releases; bytes are verified by SHA-256 and the previous version is restored if the post-swap health check fails. To update manually, simply run the new installer.

Removal

Sovos2YukatoKurulum-1.0.0.exe kaldir stops and removes the service. Files, settings and the database are kept.

Recovery commands

Sovos2Yukato.App.exe reset-admin [user] — resets the administrator password (elevated console).
Sovos2Yukato.App.exe lisans-istek — creates a device file for an offline licence.