Logo & Mikro setup

This page is aimed at business and operations users. Technical architecture and developer details are in docs/ERP_INTEGRATION.md.

Overall flow

1. Open a Logo or Mikro record under Dashboard → Accounting integrations, set it Active, and choose a safe write mode (default: manual CSV only).
2. On Dashboard → ERP product mappings, complete SKU → ERP stock code, unit, and VAT mappings (sync from products or add rows).
3. Ensure customers have a ledger/cari code or tax ID; when an order is created, a job enters the ERP order queue.
4. Download CSV from the queue or order detail and import into the ERP. Turn on auto-dispatch only after the process is stable.

Paths: /dashboard/accounting · /dashboard/integration-mapping?provider=logo or provider=mikro · /dashboard/integration-outbox.

Shared preparation

Clarify on the ERP side

• How orders are created: manual CSV, watched import folder, stored procedure / local agent.
• Whether Convord product / variant SKU fields match ERP stock codes (or use a mapping table).
• How customers are resolved in the ERP (<strong>cari/ledger code</strong> preferred; otherwise tax ID).

Products and variant SKUs in Convord

Fill SKU for every product. If you use weights/variants, each variant should have its own SKU.

Mapping panel

Manage your active mapping set on ERP product mappings: add SKU rows or “sync from products”; check default unit and VAT mappings. Queue CSV download requires a mapping snapshot.

Safe write and automation

In settings, safe write mode: manual CSV only, import file only, or procedure only. Auto ERP dispatch is off by default; enable only after ~20 successful transfers and solid mapping/customer data.

Logo — user perspective

Convord first writes the order to the outbox queue. Common Logo paths: manual CSV import or (advanced) SQL stored procedures / local agent. Classic “REST connection test” is not used for Logo; direct Logo REST push is disabled in production.

In the dashboard

1. Accounting integrations → Logo → Start setup / Settings.
2. Optionally API endpoint / API key for a bridge; for operations set safe write mode and mark the integration Active.
3. Complete SKU mapping on ERP product mappings (provider=logo).
4. Place a test order → download CSV from the ERP order queue or from order detail.

Mikro — user perspective

Common pattern: drop a delimited CSV into an import folder. Alternative: bridge master-data pull (customers/products/stock) and optional local Convord ERP Agent. Order push still goes through the outbox.

In the dashboard

1. Accounting integrations → Mikro → Settings.
2. Choose transport: file (import path + file prefix) or bridge (URL). Variant: Mikro Fly / Run / Jumbo, etc.
3. In file mode, enter a writable import path and Test connection; in bridge mode use health check and sync buttons.
4. Mapping panel (provider=mikro) + test order → queue / CSV.

Manual CSV (recommended start)

Default and fallback path:

• Download CSV for the job from the ERP order queue (mapping snapshot must be present).
• Alternatively download Logo / Mikro CSV from order detail (/dashboard/orders/{id}/erp-manual-export/logo or .../mikro).
• Product name columns (PRODUCT_NAME / UrunAdi) help verification in Excel; without mapping, the stock column may show the internal SKU.

Logo columns: ORDER_NO;STOCK_CODE;PRODUCT_NAME;QTY;UNIT;UNIT_PRICE
Mikro columns: BelgeNo;StokKodu;UrunAdi;Miktar;Birim
Format: UTF-8 (BOM), delimiter ;.

Checklist (summary)