Connecting an ERP and running syncs
Test the Mikro, Parasut, Logo, Netsis and Dia connectors on one screen, dry-run a preview, pick the active ERP and read the sync history.
If your products and stock already live in an ERP, feeding the same data into your store by hand is wasted work. The ERP connections screen gathers all five connectors — Mikro, Paraşüt, Logo Tiger / GO, Logo Netsis and Dia — in one place, showing each one's state, what it can actually do, and why its last sync failed. Exactly one connector is active at a time, so there is never any doubt about which system is telling the truth.
Avant de commencer
- The ERP plugin enabled on your store
- An account with view permission for integrations
- A service user with API access on the ERP side (for Dia, the web-service module must be included in your subscription)
- The connection settings loaded for your store — if any are missing the screen names them
Étapes
Les écrans sont illustratifs ; les données de votre panneau différeront.
Étape 1: Open the ERP connections screen
Go to Finans → ERP Bağlantıları. Each connector appears as a card in one of three states: active, configured, or not configured. The badges on the card show what that connector can genuinely do — pull products, pull stock, push orders and push contacts.
ERP connections
Manage your Mikro, Paraşüt, Logo Tiger/GO, Netsis and Dia connections on one screen, with their sync history and errors.
Mikro
ActiveOn-premise full ERP — products, stock, orders and contacts
Paraşüt
ConfiguredCloud pre-accounting — pulls products, stock and contacts
Logo Tiger / GO
Not configuredPulls products and stock over the Logo REST service
Dia
Not configuredCloud ERP — the web-service module must be in your subscription
ERP connections — exemple de vue du panneau Étape 2: Test the connection
The test button on the card fires a real request at the ERP. If it fails, the message you get back is the connector's own: it either names the missing setting outright ('Eksik ayarlar: …') or passes the ERP's error text through verbatim. It is never a generic failure notice, so read it — most setup problems are stated there exactly.
Not configuredLogo Tiger / GO
Missing settings: logo-firm-no, logo-base-url
Test connectionView historyLogo Tiger / GO — exemple de vue du panneau Étape 3: Dry-run a preview
Once the test passes, take a rehearsal that writes nothing: the preview button reads products from the ERP and stores none of them. You get back 'preview finished: N records fetched, nothing was written'. If N is close to the product count you expect, you are talking to the right company/period; if it comes back zero, the permissions or the firm code are wrong.
Dry runMikro
Preview (writes nothing)Test connectionPreview finished: 1,284 records fetched. Nothing was written.
Mikro — exemple de vue du panneau Étape 4: Choose the active ERP
If the dry run looks right, press Aktif yap on that card; you will see the confirmation and the badge turns to active. Only one connector can be active at a time — activating a second drops the first back to 'configured' without deleting its settings.
ERP connections
Mikro
ActiveLast sync: success — 30.08.2026 08:40
Paraşüt
ConfiguredLast sync: success — 12.08.2026 19:02
Set as activeActive ERP connection updated
ERP connections — exemple de vue du panneau Étape 5: Check the capabilities before you expect a direction to work
Not every connector does everything, and the card does not hide it; there is no separate comparison screen, the badges on each card are the answer. Logo Tiger / GO and Logo Netsis carry only the product-pull and stock-pull badges. Mikro, Dia and Paraşüt also push contacts; only Mikro and Dia push orders. If a capability is not on the card, that direction does not run on that connector.
ERP connections
Mikro
ActiveÜrün çekme · Stok çekme · Sipariş gönderme · Cari gönderme
Paraşüt
ConfiguredÜrün çekme · Stok çekme · Cari gönderme
Logo Tiger / GO
Not configuredÜrün çekme · Stok çekme
Logo Netsis
Not configuredÜrün çekme · Stok çekme
Dia
Not configuredÜrün çekme · Stok çekme · Sipariş gönderme · Cari gönderme
ERP connections — exemple de vue du panneau Étape 6: Read the failures in the sync history
The history table at the bottom lists every run with its connector, direction, status, record count and start time. A status is running, success, failed or partial. The error-detail column on a failed row carries the ERP's own message — read it before opening a support request. Use the card's history link to focus on one connector and 'show all' to come back.
Sync history
Connector Direction Status Records Started Mikro Pull products Success 1,284 30.08.2026 08:40 Mikro Pull stock Partial 1,190 30.08.2026 08:44 Paraşüt Push contacts Failed 0 29.08.2026 21:10 Mikro Connection test Success — 29.08.2026 17:05 A failed sync tells you why it failed; the error text is the ERP's own message.
Sync history — exemple de vue du panneau
Conseils
Always preview before a real write
The writing sync is the secondary button and the dry-run preview is the primary one — deliberately. A real sync fired with the wrong firm code can write thousands of foreign records into your catalogue; the preview performs the same read and touches nothing.
Mikro and Paraşüt also have their own working screens
The Finans menu carries separate Mikro ERP and Paraşüt entries that open those systems resource by resource: contacts, stock, orders, invoices, e-documents, quotes, collections/payments and production on the Mikro side; contacts, products, sales invoices, purchase bills, stock and warehouses on the Paraşüt side. The Paraşüt row also appears for stores that only have the e-invoice plugin.
Questions fréquentes
- Which screen do I enter the credentials on?
- ERP credentials are held in your store's private settings and are not exposed as an editable form in the panel; they are loaded during setup. The screen's job is to verify them: if something is missing, the card names the exact setting in its 'missing settings' line and the connection test repeats it. If no connector is listed at all, contact support.
- Can I use two ERPs at once?
- No — there is a single active connector. You can configure both and switch between them with 'set as active'; the inactive one keeps its settings and its sync history, only the source being read changes.
- The sync came back partial — what now?
- Partial means some records went through and some did not. Open the error-detail column on that row in the sync history: the ERP's message usually names the record it rejected. Fix it and re-run the same direction.
Extensions associées
La tâche décrite ici est fournie avec ces extensions.
Essayez dans une démo en ligne
De vraies boutiques utilisant cette fonctionnalité. Ouvrez-les et explorez.
Guides associés
Tracking income and expenses in the ledger
Set up cash and bank accounts, keep current-account balances, record income and expenses, and feed paid orders into the ledger automatically.
Bulk product import from Excel (Smart Import)
Upload your Excel file, let AI map the columns, and import hundreds of products with their variants into your store in a single pass.


