Skip to Content

Integrations / Nimex Solutions

Connect Odoo to the systems your business already runs on.

Marketplaces, carriers, banks, e-document services, payment providers, phones and plant systems, each connected to the Odoo record it belongs to. We use Odoo's standard connectors where they exist and engineer our own where they do not.

If another system provides an accessible and authorized way to connect, Nimex can engineer the integration your business needs.

Book a Free Integration Consultation Browse the Integrations
  • 50systems in the directory
  • 12built by Nimex
  • 24standard Odoo connectors we configure

How to read this page

Every integration carries one of three statuses. We state it plainly.

A connector we wrote, a connector Odoo ships and we deploy, and a system we can connect once its provider gives authorized access are three different promises. Each tile in the directory, and each step of the workflows below, says which one it is.

  • 12

    Built by Nimex

    We wrote the integration. The connector code is ours, so we know exactly how it behaves, including on a bad day, and where it needs a project-specific check.

    Evidenceour own connector code

    Nilvera · Bulut Tahsilat · WhatsApp (Web protocol) · Cloud PBX · BarTender

  • 24

    Standard Odoo, configured by Nimex

    Odoo ships the connector. We deploy it, configure it for your processes and extend the flow around it where the business needs more.

    EvidenceOdoo's connector, our deployment

    Amazon · DHL Express · UPS · iyzico · Stripe · Odoo IoT Box

  • 14

    Available after technical review

    No connector yet. We engineer it when the provider offers an accessible, authorized API or file exchange, and we tell you before any build starts if it does not.

    Evidencethe provider's authorized API, our engineering

    Trendyol · Hepsiburada · n11 · MNG Kargo · Paraşüt · PLC machine data

Odoo: one database for every connected system BuiltStandardOn review

Integrations directory

Find the systems you use, and how each one connects.

Search by name or filter by business category and status. A system that is not listed is not ruled out: if its provider offers authorized access, we review it.

50 systems

Marketplaces 7

  • Standard Odoo, configured by Nimex

    Odoo Enterprise Amazon connector: orders, stock, fulfilment

    See the fulfilment flow

  • Standard Odoo, configured by Nimex

    Odoo Enterprise Shopee connector

  • Available after technical review

    Available after technical review

    Request a technical review

  • Available after technical review

    Turkish e-commerce platform: orders and stock, after technical review of its API.

    Request a technical review

  • Available after technical review

    Available after technical review

    Request a technical review

  • Available after technical review

    Available after technical review via the provider's authorized seller API

    Request a technical review

  • Available after technical review

    Available after technical review

    Request a technical review

Cargo carriers 11

  • Built by Nimex

    Shipments and labels from the delivery order, tracking written back. Confirmed per project.

    See the cargo integration

  • Built by Nimex

    Shipments and labels from the delivery order, tracking written back. Confirmed per project.

    See the cargo integration

  • Standard Odoo, configured by Nimex

    Odoo shipping connector: rates, labels, tracking

  • Standard Odoo, configured by Nimex

    Odoo multi-carrier connector

  • Standard Odoo, configured by Nimex

    Odoo shipping connector

  • Standard Odoo, configured by Nimex

    Odoo multi-carrier connector

  • Standard Odoo, configured by Nimex

    Odoo shipping connector

  • Standard Odoo, configured by Nimex

    Odoo shipping connector

  • Available after technical review

    Available after technical review

    Request a technical review

  • Available after technical review

    Available after technical review

    Request a technical review

  • Available after technical review

    Available after technical review

    Request a technical review

Banking 4

  • Built by Nimex

    Bank collections fetched every 30 minutes and matched to the customer and bank journal (delivered on Odoo 18).

    See the collection flow

  • Built by Nimex

    Central-bank rates incl. previous-day (T-1) valuation

    See the FX toolkit

  • Bank synchronisation

    Standard Odoo, configured by Nimex

    Odoo Enterprise online bank feeds where the bank is supported

  • Standard Odoo, configured by Nimex

    Odoo Enterprise direct debit mandates

Financial document services 3

  • Built by Nimex

    UBL-TR documents to the Revenue Administration through the Nilvera integrator

    See e-İrsaliye

  • Built by Nimex

    e-Fatura, e-Arşiv, e-İrsaliye, incoming e-invoices, return invoices, templates and previews.

    See the e-invoice suite

  • Built by Nimex

    Schema-valid XML: tevkifat, iade, customer references, line descriptions

    See the e-invoice suite

Payment providers 7

  • Built by Nimex

    Card-terminal bridge pattern for Odoo Point of Sale: a prototype, not a certified terminal integration.

    See the terminal bridge

  • Standard Odoo, configured by Nimex

    Online payments and POS terminals

  • Standard Odoo, configured by Nimex

    Odoo 19 standard provider, deployed with Nimex's checkout billing-address guard.

    See the iyzico deployment

  • Standard Odoo, configured by Nimex

    Online payments

  • Standard Odoo, configured by Nimex

    Online payments

  • Standard Odoo, configured by Nimex

    Online payments and POS terminals

  • Available after technical review

    Turkish payment gateway, after technical review of its authorized API.

    Request a technical review

Communication platforms 6

  • Built by Nimex

    Finished calls logged on the right customer record with recording, transcript and the provider's AI analysis.

    See the call-centre solution

  • Built by Nimex

    WhatsApp Web protocol, not the official Business API: chats matched to contacts, PDFs sent from records.

    See the WhatsApp solution

  • Standard Odoo, configured by Nimex

    Odoo Enterprise VoIP (SIP)

  • Standard Odoo, configured by Nimex

    SMS gateway

  • Standard Odoo, configured by Nimex

    Odoo Enterprise official WhatsApp integration (separate from our Web-protocol solution)

    Compare with our Web-protocol solution

  • Available after technical review

    SMS notifications from Odoo through the provider's API, after technical review.

    Request a technical review

Industrial systems 3

  • Built by Nimex

    Label print queue from Odoo to BarTender

    See the print queue

  • Standard Odoo, configured by Nimex

    Scales, printers, payment terminals, measurement tools

  • PLC / machine data

    Available after technical review

    Machine counters and status via OPC UA/Modbus gateways, after technical review

    Request a technical review

Data sources & files 3

  • Built by Nimex

    Smart imports with dry runs and logs: catalogues, orders, journal entries

    See smart imports

  • Available after technical review

    Migration or interfaces with legacy Turkish ERP systems, after technical review

    Request a technical review

  • Available after technical review

    Data migration or sync after technical review

    Request a technical review

Social & marketing 4

  • Standard Odoo, configured by Nimex

    Odoo Social Marketing

  • Standard Odoo, configured by Nimex

    Odoo Social Marketing: posts, comments, leads

  • YouTube

    Standard Odoo, configured by Nimex

    Odoo Social Marketing

  • Available after technical review

    Lead and messaging flows beyond Odoo's standard connector, after technical review

    Request a technical review

Productivity 2

  • Standard Odoo, configured by Nimex

    Gmail, Calendar, address autocomplete, reCAPTCHA

  • Standard Odoo, configured by Nimex

    Outlook mail and calendar

Third-party names and logos are trademarks of their respective owners and indicate compatibility or integration, not endorsement. Logos are shown only where the owner's brand guidelines permit it; other systems are identified by name.

Workflow · marketplace fulfilment

From a marketplace order to a shipped parcel and a legal e-Arşiv invoice.

Odoo's standard Amazon connector brings the order in, Odoo reserves stock, a standard carrier connector returns the label and tracking, the connector reports the shipment back to Amazon, and the invoice leaves through Nilvera as an e-Arşiv document, the part Nimex built. Every step below names who built it.

Standard Odoo, configured by NimexBuilt by Nimex

  1. Order syncedThe connector imports the Amazon.com.tr order as a confirmed sales order.Standard
  2. Stock reservedThe delivery order reserves the units in your warehouse.Standard
  3. Label and trackingValidating the delivery requests the carrier label and tracking number.Standard
  4. Shipment confirmedThe tracking reference is sent back to Amazon; the order shows as shipped.Standard
  5. e-Arşiv invoiceThe posted invoice goes to Nilvera as e-Arşiv; the official PDF returns to Odoo.Nimex

We did not build a Trendyol, Hepsiburada or n11 connector: those marketplaces are available after technical review of their seller APIs. Yurtiçi Kargo and Aras Kargo shipments are confirmed per project. Amazon availability depends on your Odoo Enterprise subscription and seller account.

Workflow · financial document processing

Supplier e-invoices that fill themselves in, and collections that find their invoice.

Incoming e-invoices are fetched from Nilvera page by page across a 90-day window. The vendor bill is filled from the UBL-TR XML: vendor by tax number, products by supplier code, expense account from the vendor's default. Its total is cross-checked against the amount on the XML before the accountant posts it. On the receivable side, Bulut Tahsilat collections are matched to the customer and arrive as bank statement lines, ready for Odoo's reconciliation.

Built by NimexStandard Odoo reconciliation

  • Vendor by VKN / TCKNPlaceholder and ambiguous tax numbers are refused with a message, never guessed; unknown vendors can be created from a prefilled wizard.
  • Totals cross-checkedA rebuilt total that differs from the XML is flagged on the bill and listed under its own filter.
  • Collections without double importsA unique payment id prevents duplicates; unmatched payments wait in a pool for the accountant.

Bills are posted by the accountant, never automatically. Pagination and the 90-day window are part of our Odoo 18 fetch; the Bulut Tahsilat integration was delivered on Odoo 18. Invoice matching itself is Odoo's standard reconciliation.

Explore the e-invoice suite

Workflow · customer communications

WhatsApp messages and phone calls, on the customer they belong to.

A message to the company's WhatsApp number is matched to the contact by phone number, and the quotation PDF goes out from the quotation itself. When a call ends on the cloud PBX, its record arrives in Odoo matched on the last ten digits, with the recording, the transcript and the provider's analysis, and a routing rule opens the Field Service task.

Built by Nimex

WhatsApp runs on the WhatsApp Web protocol, a QR-paired session of the company's own number, not the official WhatsApp Business API: no Meta-approved templates, and messages reach only numbers that use WhatsApp. Odoo Enterprise's official WhatsApp integration is a separate, standard option.

Calls are ingested after they end; there is no live screen pop while the phone rings. Transcripts and scores come from the PBX provider's AI service; Odoo itself calls no language model.

Explore the WhatsApp integration Explore the call-centre integration

API engineering capabilities

Built to keep running when the other side does not.

An integration is only as good as its behaviour on a bad day: a provider that times out, a webhook that arrives twice, one malformed document in a batch of forty. This is how our connectors are built, shown on a day of their log.

How we connect

  • REST / JSON
  • SOAP / XML
  • Webhooks
  • SFTP and file drops
  • Excel / CSV
  • EDI · UBL-TR

Authentication

  • OAuth 2.0
  • API keys and bearer tokens
  • Signed requests (HMAC)
  • Certificates

Reliability

  • Scheduled jobs and queues
  • Retries with limits
  • Idempotency on unique ids
  • Fault-tolerant batches
  • Audit logs

Monitoring

  • Fetch logs with counters
  • Error states on the record
  • Chatter notes and to-dos
  • Pools for unmatched items

How we assess a new integration

Six gates between "can you connect it?" and a connector in production.

Every system marked "available after technical review" goes through the same path. The first two gates are the honest ones: without accessible and authorized access there is no integration, and we say so before anything is built.

  1. 01Access

    Does the provider offer an API, a webhook or an agreed file exchange your account can use?

    Interface found, or a clear no
  2. 02Authorization

    Credentials, contracts or partner approval issued to your company, with the scopes the flow needs.

    Credentials and scopes confirmed
  3. 03Documentation & sandbox

    Endpoints, limits and error codes read; test calls made against a sandbox or a test account.

    Test calls answered
  4. 04Data mapping

    Which records move, in which direction, with which identifiers, and what Odoo does with each one.

    Field map and sync rules
  5. 05Build & test

    Connector built inside Odoo with retries, idempotency and logs, tested with your real scenarios.

    Accepted on staging
  6. 06Monitor

    Logs, counters and error states your team can read, with the record-level trail kept in Odoo.

    Live, with a log

Gates 01–02 passWe estimate the build and proceed through gates 03–06.

No authorized accessWe stop and say so, and look for an alternative such as a file exchange the provider supports.

Engineered integrations in depth

See the integrations we built, step by step.

Chat with us