Usage

Daily use

Once configured the service runs on its own. The panel is for checking status, inspecting a problem document and re-sending it when needed.

Flow

1. Pull: the list of sent advices is fetched from Sovos; UBL and PDF are downloaded for each new document.
2. Filter: documents whose recipient is not on the retail customer list are skipped (and logged).
3. Map: the store code is translated to a Yukato address; without a mapping the address is sent inline.
4. Push: a shipment is created on Yukato, the PDF is attached and the Yukato reference is stored.
5. Track: the transport status is refreshed periodically.

Dashboard

Last pull and push times, status counters (Pending · Sent · Failed · Dead-letter), service and licence state.

Despatches

All advices in one grid: search, drag-to-group, multi-column sort, date range and status filters, Excel/PDF export. The default range is This month; the Today · This week · This year · All chips change it and the choice is remembered.

• Detail (eye icon): a five-tab window — summary, lines, UBL (highlighted XML), Yukato request/response (highlighted JSON), PDF.
• Re-send: a failed or dead-lettered document is rebuilt from its stored UBL and sent again.
• Proof report: a printable report of which advice became which Yukato shipment in a period.

Errors and retries

Transient errors (network, timeout, 5xx) are retried with growing intervals. A document that runs out of attempts moves to dead-letter and waits for a manual re-send. The cause of a permanent error is shown with the Yukato response in the detail window.

Service and logs

The Service screen starts/stops the Windows service and shows its port and description. Logs filters the application log by level; every error entry carries an error id.

Users

Administrator and user roles. New users and password resets get a temporary password, mailed when SMTP is configured and changed at first sign-in.