Odoo Base (BaseLinker) Connector PRO

Odoo Base (BaseLinker) Connector PRO

ConnectorsSubscription

199,00 € / year or one-time purchase

Clear
- +

SKU: odoo
Tags:

The Odoo Base Connector (formerly BaseLinker) by VentorTech brings all your sales channels into Odoo through a single integration — orders, per-warehouse stock, prices and tracking sync automatically. What sets it apart: everything runs inside your own Odoo. Jobs, logs and the sync queue live in your database, so you can see every sync and change every rule. Built and supported by a team that has worked with Odoo for 13+ years, from the EU.

Available for Odoo 17, 18 and 19 — Community and Enterprise. (Odoo Online blocks third-party apps and isn’t supported.)

Two ways to connect

A bridge, or native to Odoo?

Base recently released a free official connector. It solves a different problem than this one — here’s the difference in plain terms.

An API-key bridge
Where the sync runs: in an external cloud service — the Odoo module mainly issues an API key.
Where you configure it: in the external interface, outside Odoo.
What lands in Odoo: mostly invoices, with sales orders as an option.
Stock: usually one warehouse and one stock location.
Access to your data: the service signs in to your Odoo over the External API.
Changing behaviour: a fixed feature set — you work with what the service offers.
Fine when Odoo is mainly where you keep the books.
A native Odoo connector — this module
Where the sync runs: inside your Odoo. Jobs, logs and the sync queue live in your own database.
Where you configure it: in Odoo, through a guided setup wizard.
What lands in Odoo: sales orders with deliveries, invoices and payments — plus tracking sent back to Base.
Stock: per warehouse — each Odoo location maps to its own Base warehouse.
Access to your data: Odoo calls the Base API. No outside service signs in to your Odoo.
Changing behaviour: field-level mapping with Python transforms — adjust it without custom development.
Built for when Odoo is where you actually run operations.

Which one you need depends on Odoo’s role. If Odoo is where you keep the books, a bridge can be enough — and we’d rather you knew that. If Odoo is where you run operations — picking, shipping, stock across several warehouses, invoicing rules that differ per order — then the sync has to live inside Odoo, where you can see it, control it and change it.

Data sync coverage

What stays in sync

Full coverage across the data that runs your business — you can find the feature you’re looking for below.

↔Both directions →Odoo to Base ←Base to Odoo
Products
Products & variants↔
Product images→
Categories↔
SKU, EAN / barcode↔
Prices (variant = diff from parent)→
+ pre-flight report flags duplicate & missing SKUs before go-live
Inventory & pricing
Stock levels→
Per-warehouse mapping→
Price groups / pricelists→
Multi-currency prices→
+ configurable quantity source, scheduled sync, batch updates
Orders
Orders → Odoo sales orders←
Deliveries & invoices←
Status updates↔
Tracking numbers & courier→
Payments & delivery costs←
+ filter by marketplace source & status, import as often as every 5 min
Customers & more
Customers & addresses←
Companies vs. individuals (auto)←
VAT numbers (B2B)←
Taxes & carriers (auto-discovered)←
+ matches existing Odoo contacts — no duplicates

Why it works better

Where a native connector earns its keep

Three things that matter once Base is more than a side channel.

Full orders, not just invoices

Base orders become real Odoo sales orders — with deliveries, invoices and payments — and tracking numbers travel back to Base with the right courier. A bridge that only pushes invoices leaves picking, shipping and stock outside Odoo; this keeps the whole order lifecycle where you run it.

Per-warehouse stock, real pricelists

Each Odoo location maps to its own Base warehouse, and Odoo pricelists become Base price groups. Built for setups that are more than basic — several warehouses, several pricelists, B2B invoicing with VAT numbers — not one warehouse and one price.

Nothing fails silently, nothing duplicates

Records match by SKU or EAN, and a pre-flight report lists duplicate and missing SKUs before you start — which is where migrations usually go wrong. Every job is logged in your Odoo and can be retried individually, so a hiccup never quietly creates a second invoice.

The connector does far more than this list

This is the short version. In practice it covers many more data types, settings and workflows than we can show on one page. The fastest way to know it fits your setup is to see it running on your data — free, and with no commitment.

Request a free demo

What you get

What’s included

Buying direct from VentorTech, you get more than the module.

  • Odoo 17–19, Community & Enterprise. One connector, your choice of version and edition.
  • Always up to date. Access to the latest three Odoo versions; the module for a new version is included when you upgrade.
  • Updates delivered to your Git. Pushed to a separate branch in your repo automatically — no manual downloads.
  • Priority support, straight from the developers who wrote the connector — typically same-day or within a few days.
  • A say in the roadmap. Subscriber requests go to the top of the backlog.
  • Guided setup included. Two free 1-hour sessions — an initial walkthrough and a follow-up review.
  • Single-customer license. For one production Odoo instance and its staging/dev instances. Multiple production instances? Talk to us.
  • Installation & Configuration service available separately if you’d like hands-on help getting live.

Common questions

Frequently asked questions

Can’t find your answer? Ask us →

There’s a free official Base connector. How is this one different?
They solve different problems. The official module works as a bridge: it generates an API key so the Base service can sign in to your Odoo from the outside, and the sync itself runs and is configured in Base — built mainly around getting invoices into Odoo. This connector runs inside Odoo: Base orders become Odoo sales orders with deliveries and invoices, stock is mapped warehouse by warehouse, prices flow from your pricelists, and tracking goes back to Base. The honest answer: if Odoo is just where you keep the books, the free module may be all you need. If Odoo is where you run operations — picking, shipping, multi-warehouse stock, per-status invoicing — the sync has to live inside Odoo. That’s what you’re paying for here.
Is “Base” the same as “BaseLinker”?
Yes — Base is the new name for BaseLinker. The connector works with the same platform and all the channels you’ve connected in it.
Which Odoo versions are supported?
Odoo 17, 18 and 19, in both Community and Enterprise editions (on-premise or Odoo.sh). Odoo Online can’t run third-party modules, so it isn’t supported.
How does it handle orders from multiple sales channels?
Base aggregates orders from every channel you’ve connected (Allegro, Amazon, eBay, Shopify and more). The connector imports them into Odoo with order-source tracking, and you can filter imports by marketplace source and by status — so only the orders you want end up in Odoo.
Does it support two-way product sync?
Yes. You can import products from Base into Odoo or export them from Odoo, in both directions. Existing records are linked by Base ID with SKU/EAN as a fallback, and a pre-flight report flags duplicate and missing SKUs before you start.
How will I know if a sync fails?
Every job runs inside your Odoo, with a clear status and reason, and can be retried individually once resolved. Because records match by SKU/EAN and the queue lives in your database, a retry reuses the existing record instead of quietly creating a duplicate.
Do I need technical skills to set it up?
A guided 5-step wizard covers inventory, warehouses, price groups and order sources. You generate a Base API token (My Account → API) and the standard Odoo Sales module is required. Most businesses set it up without a developer; our Installation & Configuration service is available if you’d like help.
Where is my data stored? Is it GDPR-friendly?
The connector is a module running inside your own Odoo — it calls the Base API, and no outside service signs in to your database. VentorTech is based in Poland (EU), with EU-based support and infrastructure, which keeps GDPR straightforward.

See it running on your data

Request a free demo and we’ll walk you through the connector — or connect a demo instance to your Base account so you can try it with your real orders and products.

Request a free demo

Additional information

Odoo Version

17.0, 18.0, 19.0
Related Products