Skip to content

ERP bridge for Logo, Mikro, Nebim and Netsis

Four ERPs share one screen: each address renders the same view with only the provider changed. What differs is what the provider needs and what it can do, which the platform reports for each ERP (see What differs per ERP). Each has its own address, and the page title is the ERP’s name.

ERP Screen
Logo ERP /settings/integrations/logo-rest
Mikro ERP /settings/integrations/mikro
Nebim ERP /settings/integrations/nebim-v3
Netsis ERP /settings/integrations/netsis-rest

They need the settings.manage permission. The screen opens with: “Connect your own ERP so orders, invoices and stock stay in step. You supply the ERP credentials; they stay on your network.” and “Nothing happens until you connect.” It adds a cost note: “The ERP’s license or API fee is paid by you to the ERP vendor; CIQRA does not buy or resell it.” If the platform has the bridge switched off, the screen says “Nothing is sent to or read from any ERP until it is switched back on.”

The four pages pass nothing but the provider; the differences below come from the provider registry and connectors behind them. Every connection starts the same way: draft, dry run, all flows off.

Logo (Tiger 3 / Go 3, REST) Mikro (Run / Jump / Fly) Nebim V3 (Integrator) Netsis (3 / Wings, NetOpenX REST)
Credentials you supply REST client id, REST client secret, Logo user, Logo password API Key, API user, API password Database name, user group, Integrator user, Integrator password Netsis user and password, database name, database user and password
Also needed Logo REST service (port 32001 by default), Logo Objects license, firm number MikroAPI service (port 8094 / 8084), API Key issued with the license, firm and branch number Nebim V3 Integrator on IIS, the CIQRA Nebim query package installed by your DBA NetOpenX license, REST reachable on the local network only, a REST build newer than 2.0.6.9, a least-privilege SQL account
Products from the ERP Yes, if the ERP has an items resource Yes Yes, through the query package Yes
Stock from the ERP Needs a stock resource on your installation Yes, per warehouse Yes, through the query package Needs a database-administrator-defined query
Prices from the ERP Yes, if the ERP has a sales price resource Yes, if a price list exists Yes, through the query package No: no documented price-list endpoint
Orders and invoices to the ERP Yes Yes Yes, through the query package Yes, as stock slips
Collections to the ERP Needs a collection resource found on your installation Yes Yes (card payments) No: the document body is not confirmed
Products to the ERP No Yes No No
Order cancellation No Yes Yes No

Other differences. Firm code and Branch code are given when you create the connection; Logo uses the firm number (1 if empty), Mikro the firm and branch number (branch 0 if empty), and Mikro also takes a work year. Netsis refuses a REST service that answers on a public interface. Mikro is the only one that can read an e-document’s state back, and Nebim creates it automatically. Several vendor field names are marked Secondary or Unverified and are confirmed against your installation before use.

“CIQRA reaches your ERP through a small agent installed on your own network. It connects outward only, so you open no port, and your ERP credentials never leave your machine.” A new connection starts as a draft in dry-run, “with every flow and collections switched off.” Its status is Draft, Connected, Blocked by a security check or Disabled, and its mode is Dry run or Live. A Stop everything switch pauses the connection; “Orders keep queuing and nothing is lost.” Remove connection withholds waiting documents; “Documents already in your ERP stay there; nothing is deleted from it.”

Creating a connection asks for a Name, and optionally a Firm code and Branch code.

Four numbered parts:

  1. Bridge agent — the CIQRA Bridge Agent runs on a machine that can reach your ERP and is paired with a one-time code. The screen shows whether the agent is connected, and offers New pairing code, Use for this connection and Revoke. The agent “only connects outward over HTTPS; no port is opened.”
  2. ERP credentials — including ERP address (local network), which “must be an address on your own network; a public address is refused.” Credentials are “sealed to your agent and never stored by CIQRA”, and the fields are write-only.
  3. Test connection — “Checks the connection, the login and one read. It writes nothing.”
  4. What this ERP offers — Discover reads the ERP’s version, warehouses and which flows it supports.

“Each flow is switched on by you, one by one. A flow opens only when your ERP supports it.” The flows are Products from the ERP, Stock from the ERP, Prices from the ERP, Orders to the ERP, Invoices to the ERP, Collections to the ERP and Products to the ERP. Two of them are marked as moving data in bulk and are off until you turn them on: collections (“This moves money records”) and products to the ERP (“A bulk data change”); switching on prices from the ERP asks for confirmation because “Prices in your ERP become the base prices customers see.”

Each flow has Send for real: in dry run, “documents are built and shown, nothing is sent” and a passed connection test is needed.

The tab also holds Who wins on a conflict (one source, The ERP or CIQRA, for Stock, Price and Names, texts and images; “CIQRA campaigns and discounts apply on top of the ERP price and are never written back to the ERP”) and Who issues the e-document: My ERP issues it or CIQRA issues it. “Exactly one side may number an invoice”, and the mode cannot change once documents were issued.

Field mapping has one row per field — the CIQRA field on the left, the ERP’s field on the right — with Load template. Reference tables map Warehouse, Price list, VAT code, Payment account and Carrier keys. Example order preview “builds the document an order would send. Nothing is sent.” ERP field names lists every field name the bridge uses with a confidence of Official, Secondary or Unverified; the screen says secondary names are confirmed against your installation before use.

“Every flow at a glance.” Each flow shows Healthy, Behind, Needs attention or Off, the documents waiting, and the monthly document count. Documents that need attention can be Retryed, marked Fixed, send again or Skipped (“Skip closes a document without sending it.”). Dry-run previews are “Shown, never sent.” Latest runs gives read, applied and error counts.