Odoo Baselinker Connector PRO Release Notes

IMP A failed auto-workflow step is now also reported as a failed background job with the same error message shown on the “Order Automation” form, so stuck orders are visible in the Job Queue and in any job failure notifications you have configured. Retrying or skipping the step is still done from the “Order Automation” form.
IMP Retrying a failed automation step no longer leaves its earlier failed background jobs behind — once the step succeeds or is skipped, previous attempts are cancelled automatically. Steps that are not part of a status’s automation no longer create background jobs at all.
IMP The background jobs of the order automation are now listed under “View Related Jobs” on the external order, alongside the import jobs.
IMP A manual “Import Orders” run no longer tries to fetch an unlimited backlog in one request: after 50 pages the rest is handed over to background jobs, preventing timeouts on large backlogs such as an initial import or a long connector downtime. Background runs are bounded too, so a store API that never signals the last page can no longer produce an endless chain of jobs.
FIX Fixed the “Automation Status” column showing “Running” for external orders whose automation had not started yet — they are now shown as “Pending”. Existing orders are corrected automatically when installing this version.
FIX Fixed an error when clicking “Run Again” on the “Order Automation” form, which failed instead of restarting the automation.
FIX Fixed a remaining case where an order could be missed during a multi-page import run: an order modified in the store while the run was in progress changed position in the result set, so the order at a page boundary was never fetched. Pages are now read by a stable, immutable key, and the resume date only moves forward once the whole run has completed — an interrupted run re-reads its orders instead of skipping them.
FIX Other improvements and fixes implemented to boost overall performance, stability, and reliability.

BRK Order status export behavior change: the Cancelled / Paid / Shipped status exports now work on their own, without the former master “status export” toggle. A store that had one of them enabled while the master option was disabled will start sending that status after the upgrade — review each store’s Automation Jobs settings after updating.
NEW Added a “Default Invoice Date” setting to the Auto-Workflow configuration (per e-commerce order status, next to “Create Invoice”), letting you choose whether invoices created by the connector use the Sales Order date (“Order Date”, default — previous behavior) or the date the invoice is actually created.
NEW Added a “Consistency Wizard” on the Data Import tab (available in debug mode) to detect discrepancies between the external records stored in Odoo and the actual data in the e-commerce store. For the selected entity — products, attributes, categories, taxes, shipping and payment methods, and more — it reports which records no longer exist in the store, which are not mapped to an Odoo record, and, for products, which have a variant mismatch. Obsolete external records can be deleted right from the wizard.
NEW Added a “Refresh Stock from Store” action on the product form, allowing users to pull current stock levels from an e-commerce store for a single product on demand. The wizard asks which store to read from and which Odoo location to apply the quantities to, then applies them to the product’s variants via an inventory adjustment. This replaces existing quantities in the mapped locations, so it is intended for controlled stock alignment rather than routine synchronization.
NEW Added a “Payment Method” field on external payment methods, next to “Payment Journal”, allowing e-commerce payment methods to be mapped to Odoo payment methods. It is applied to all payments created by the connector; when left empty, the journal’s default is used.
NEW Added detailed order import trace logs, showing which pages were fetched, how many orders each contained, and how the import resume date moved. To enable, activate the “Save Logs” checkbox on the Testing tab and add “Orders Import” to the Log Types.
IMP Reworked product → store synchronization to clearly separate linking a product from publishing it. Selecting a store on a product no longer immediately publishes or overwrites its content and images in the store. Publishing is now always an explicit action: the new “Export to Stores” button on the product, or “Link & export now” in the redesigned “Manage Store Connections” mass action, which offers per-store choices (Link only / Link & export now / Unlink) and a confirmation step before anything is sent — preventing accidental overwrites of live listings. “Auto-Export Product Updates” now does only what its name implies: it keeps already-published products up to date and never performs the first publish.
IMP Reworked “Auto-Export New Products” (per store). When enabled, newly created products are automatically linked to the store and published — but only once they satisfy that store’s “Required Fields for Initial Export” (e.g. internal reference / SKU), so incomplete products are never sent. Until a product is ready it is shown as pending first export, with a banner listing what is still missing. Existing connections keep their previous setting on upgrade.
IMP Unified order fulfillment and status export so each event works on its own. “Auto-Export Shipments & Tracking” now marks orders as shipped/fulfilled in the store on all platforms when a delivery is validated in Odoo (the tracking number is optional), and the Cancelled, Paid/Invoiced and Shipped status exports each push on their own dedicated option, while “Auto-Export Manual Status Changes” now covers only status changes made by hand on an order. The Automation Jobs tab was reorganized to match: clearer option names, each setting grouped with its related option, lighter inline help, and a quick link to configure when the paid status is sent per payment method.
IMP Redesigned the auto-workflow (“Order Automation”) form around a clear summary of what happened: the current state of every step, which step the automation stopped at, and the error itself shown directly on the form. A failed step no longer produces a separate failing background job with an unexplained error message — instead, the step can be retried or, when it is safe to do so, skipped right from the form, so most failures can be resolved without contacting support.
IMP Reworked the per-order-status automation configuration. The order statuses list now shows a “Will Do” column summarizing what each status triggers (individual step checkboxes are hidden by default), and the status form previews the effective sequence of steps that will actually run, taking dependencies between them into account — so it is clear upfront that, for example, enabling payment registration also requires an invoice. A new bulk wizard allows configuring the same automation steps for several order statuses at once.
IMP Cleaned up the external order form and list. A new “Automation Status” field (Done / Running / Failed / Skipped / Cancelled) replaces the previous unreliable error indicator and is shown as a colored column in the list, making it easy to spot orders whose automation needs attention. The unexplained pipeline buttons were removed from the form — automation is now managed from the “Order Automation” form itself — and the remaining fields were regrouped for readability.
IMP Improved the product catalog validation test (“Run Validation Test”). Validation now runs through the import wizard and offers a new “Run Validation in Background” option that fetches the catalog in batches via background jobs — preventing request timeouts when validating large or slow stores.
IMP Product export validation now lists all missing required fields at once, each with both its user-friendly label and technical name (e.g. “Internal Reference” (default_code)), making products easier to fix before export.
IMP Added the ability to delete a single webhook directly from the Webhooks list, instead of only removing all of them at once. The webhook is deleted both in Odoo and in the e-commerce store after confirmation; if the store’s API rejects the request, the webhook is kept in Odoo and the error is shown to the user.
IMP Multiple small UI/UX improvements across connector views, including in-context guidance on the product and store-connection screens explaining what each action does.
FIX Fixed a critical issue where orders could be skipped or missed when a single import run had to fetch more than one page of orders (typically 250+ orders — after a long connector downtime, an initial import, or a bulk update in the store).
FIX Fixed an issue where order import failed when an order line referenced a product variant that could not be found in Odoo. The configured “Fallback Product” is now applied in this case as well, instead of only for lines with missing SKU or ID details.
FIX Fixed a misleading result message for the “Auto-Link” action on product mappings, which reported a successful import even when no Odoo product was actually linked. The action now returns a proper Auto-Link summary and can be run on several selected products at once.
FIX Fixed an issue where duplicating a product field definition via Odoo’s standard “Duplicate” action created a broken, non-editable record. It now produces the same editable copy as the “Duplicate to Edit” button.
FIX Fixed an issue where webhooks stopped working on databases named “odoo”. Since Odoo 18.0 the standard web client is served from /odoo, which conflicted with the connector’s webhook URLs. Webhook endpoints have been moved to a dedicated path that cannot clash with Odoo’s own routes; previously registered webhooks keep working, so no reconfiguration is needed.
FIX Other improvements and fixes implemented to boost overall performance, stability, and reliability.

IMP Added a “Store Mappings” smart button on product field definitions, showing how many store-specific mappings use the definition and opening them in one click.
IMP Aligned the column order in mapping lists so the external (e-commerce) record is always shown before the Odoo record, matching the rest of the mapping views.
FIX Improved contact matching during order import to prevent duplicate contacts. A previously mapped contact that has no parent company is no longer reused when the order requires a company (B2B) context, and company assignment changes are now detected correctly — avoiding wrongly reused or duplicated contacts.
FIX Fixed an issue where e-commerce payments registered in a currency different from the order currency were recorded without conversion, resulting in an incorrect payment amount. The amount is now correctly converted from the external currency into the order currency.
FIX Fixed an issue where matching existing Odoo records by name during import used the current user’s language instead of the integration’s store language. In multi-language setups this could fail to find existing records (attributes, categories, delivery carriers, taxes, pricelists, order sub-statuses) and create duplicates. Matching now consistently uses the integration language.
FIX Fixed an issue where a block-level export job could be linked to the wrong record — a product template ID was stored in the field meant for the e-commerce store — causing the job to reference an incorrect record.
FIX Other improvements and fixes implemented to boost overall performance, stability, and reliability.

IMP Added “Auto-Link” button for attribute values, allowing users to quickly map external attribute values to existing Odoo attribute values — particularly useful when working with custom attribute mappings.
IMP Improved VIES VAT validation handling when the service is temporarily unavailable or overloaded. The connector now automatically retries the request up to 3 times before proceeding — and if the service remains unavailable, the order is imported successfully with a note added to the contact’s chatter to flag the unvalidated VAT number.
FIX Fixed an issue where product export used incorrect company context in multi-company setups. When a product was shared between multiple companies, the connector could export data (such as taxes and cost price) from the wrong company instead of the one associated with the integration, resulting in incorrect values being sent to the e-commerce store.
FIX Fixed an issue where external records created during product export were assigned the name “False” instead of the actual product name from the e-commerce store. This occurred when the connector detected an existing matching product and switched to import mode — the product name is now correctly retrieved and stored on the external record.
FIX Fixed an issue where product webhooks did not respect the product import filters configured in the integration settings (e.g. “import active products only”). Products received via webhooks are now validated against the same filters as the regular import process, preventing unwanted products from being created in Odoo.
FIX Fixed an issue where product export failed with a “Duplicate internal reference” error in multi-company setups when two companies had products with the same SKU. The connector now correctly scopes the duplicate SKU check to the integration’s company, allowing products with identical SKUs across different companies to be exported without conflict.
FIX Other improvements and fixes implemented to boost overall performance, stability, and reliability.

NEW Released the first version of the Baselinker connector, providing full integration between Odoo and Baselinker. Key features include order import, product synchronization, inventory sync, auto-workflow, and price group synchronization mapped to Odoo pricelists.

Odoo Baselinker Connector PRO

2.2.1

2.2.0

2.1.6

1.0.1

1.0.0

Cart