Skip to main content

AliExpress (Global)

Premium connector for AliExpress -- Alibaba Group's global B2C marketplace covering 200+ countries -- from a single Odoo instance. The connector uses HMAC-SHA256 TOP-API authentication, region-aware fulfillment routing across CN / US / EU / RU and the AliExpress Choice premium delivery program, settlement ingestion with AE-Affiliate commission tracking, and 2026 tax reference fields for EU OSS/IOSS, US sales-tax nexus, UK VAT, KSA ZATCA Phase 2 and Brazil RFB.

ModuleAliExpress Store Management
Current shipped version20.0 → 20.0.2.2.13, 19.0 → 19.0.2.2.10, 18.0 → 18.0.2.2.10, 17.0 → 17.0.2.2.10
CompatibilityOdoo 17 / 18 / 19 / 20 -- Community + Enterprise -- On-Premise + Odoo.sh
PriceUSD 499 (one-time, per Odoo version)
LicenseOPL-1
AuthorECOSIRE (PRIVATE) LIMITED

For step-by-step installation, connection, webhook setup and troubleshooting, see the full AliExpress Store Management guide.

2.2.13 (20.0.2.2.13) and 2.2.10 (17.0.2.2.10, 18.0.2.2.10, 19.0.2.2.10) — cleaner shipped files

Code comments, test descriptions and bundled test data no longer carry internal engineering references. Nothing changes in how the connector works, and no settings or data need attention after the update. The same release ships on every series.

2.2.12 (20.0.2.2.12) and 2.2.9 (17.0.2.2.9, 18.0.2.2.9, 19.0.2.2.9) — Products, Contacts and Sales keep their own screens

After installing the connector, the AliExpress imported-products, imported-customers and orders list and search screens could become the default list and search view of every product, contact and sales order screen that does not name its own view — for example a Search More... dialog or another app's action — so users saw only the AliExpress columns and filters. The standard Odoo screens now stay the default everywhere, and the AliExpress menus still open their own screens. The same fix ships on every series.

2.2.11 (20.0.2.2.11) — Declare Shipment only while the parcel is awaited, and entry screens that open full

On Odoo 20.0 the Declare Shipment button and the declaration follow the statuses the automatic retry uses (paid, waiting for the seller, partially sent), and the button stays hidden until Sync Orders has read the order's AliExpress sub-order ids, so an unpaid order or a parcel already in transit is no longer offered for declaration. The dashboard shows No AliExpress Configuration Found only when no configuration exists (17.0, 18.0 and 19.0 had this as 2.2.6), and Configurations and Sync Logs open on their full list instead of a pre-applied Connected / Error filter.

2.2.10 (20.0.2.2.10) and 2.2.8 (17.0.2.2.8, 18.0.2.2.8, 19.0.2.2.8) — settlements read the published period flow

AliExpress withdrew aliexpress.fund.merchant.orderdetail on 2026-11-13. Settlement sync now reads the published period flow (aliexpress.fund.merchant.period.settlefeeitemdetail.query), pages through the whole period instead of keeping only the first page, reads each amount from the money value AliExpress returns (no more periods of zeros), classifies fee lines from their fee name and notes, keeps two genuine fund records for the same order and fee item while counting a re-read page once, and logs the record count AliExpress stated when a period stops at the page limit.

2.2.9 (20.0.2.2.9) — dispute decisions and evidence reach AliExpress

On Odoo 20.0, Accept agrees to the buyer's current proposal (re-read from AliExpress first; a return needs the Return address ID), Decline sends your note as your own proposal with no refund, and Propose an alternative sends your note with the amount in the new Our refund offer field. Evidence lines hold the image itself and upload it with its file type. A decision or upload AliExpress does not confirm is not recorded, and you see AliExpress's answer.

2.2.8 (Odoo 20.0) — stock and price pushes reach AliExpress, refusals are counted

On Odoo 20.0 the stock push now sends each listing's product id and, per SKU, the quantity for its warehouse: set the new Stock Warehouse Code on the configuration, or leave it empty to use the warehouse each listing already holds stock in. Price pushes use the form AliExpress publishes. A stock, price, publish/unpublish or shipment request AliExpress answers as not successful is now counted as failed, with the reason in the log. Shipment declarations send the order's AliExpress sub-order ids, which order sync now keeps; an order imported earlier gets them on its next Sync Orders.

2.2.7 (17.0, 18.0, 19.0 and 20.0) — declare a shipment from Odoo, and no silent empty reads

The order form now has a Declare Shipment button: enter the tracking number, pick the carrier that carries its AliExpress carrier code, and the declaration goes to AliExpress through the published send-goods operation — the platform answers first, so a refusal changes nothing on the order and tells you why. The product and order list calls no longer swallow a failure and return an empty list, so a dead token or a refused route can no longer finish a sync on a clean 0 processed. On Odoo 20.0 only, the Sync Inventory scheduled action now pushes Odoo's on-hand stock every 15 minutes (one row per mapped SKU, on by default, so it overwrites AliExpress stock — clear the configuration's Sync Inventory box if you manage stock elsewhere), and validating an order's delivery with a tracking number and carrier code declares the shipment automatically. On 17.0, 18.0 and 19.0 the job stays read-only.

2.2.5 (17.0.2.2.7, 18.0.2.2.7, 19.0.2.2.7, 20.0.2.2.7) — a failed connection test stays visible, and Odoo 20.0

A failed Test Connection used to be rolled back together with its error, so the configuration kept reading Connected. The Error status, the time of the test and the reason are now recorded on their own transaction, so the record shows the failure and you can reconnect with Exchange Authorization Code or Renew Access Token. The same release is now available for Odoo 20.0.

2.2.4 (17.0.2.2.4, 18.0.2.2.4, 19.0.2.2.4) — the connection keeps itself alive

An expired access token is renewed by the connector itself, before a sync when its expiry is known and on the first refused call when it is not, so connections set up before 2.2.4 keep working too. Token requests are now signed as AliExpress documents them, and the app secret is never sent. A webhook delivery that passes verification is processed instead of dropped (verification stays fail-closed and refuses every delivery today, so data arrives through the scheduled syncs); buyer matching compares email and name literally, a failed record names its AliExpress identifier in the log, a malformed App Secret is refused when saved, Choice SLA compliance is scored from the real placed, shipped and delivered times, and returns, refunds and settlements create their incoming transfer, draft credit note and draft journal entry.

2.2.3 (17.0.2.2.3, 18.0.2.2.3, 19.0.2.2.3) — resilient imports, and the full 2.2 release on 17.0 and 18.0

The 17.0 and 18.0 builds now carry everything 19.0 has (operation registry, affiliate, product feed, disputes, category tree); photobank uploads on 17.0 no longer end in an error, and the shop selector on the affiliate and product-feed screens is visible to AliExpress Managers only. A listing is no longer lost when its picture cannot be decoded (the image is skipped, the listing is imported, and the rejected reference is recorded on the product), and two AliExpress seller accounts can now import the same barcode: the marketplace GTIN is always kept on the product while the unique standard barcode field goes to whichever product holds it first. Version 2.2.2 hardened 36 known real-world connector failure cases — identity idempotency, multi-store isolation, per-record failure containment, terminal-page pagination, webhook signature verification and redacted delivery evidence, order finance and currency completeness, and dashboard date range.

2.2.1 (19.0.2.2.1) — company boundaries

In a multi-company database the AliExpress dashboard and sync endpoints now work only with the connections of the companies you are working in, and starting a sync is reserved for AliExpress Managers. The same release makes order import work again on Odoo 19, reads imported orders correctly on every version, matches a returning buyer to the same contact, and shows dashboard amounts in your company's currency on 17.0 and 18.0.

Key Features​

Capability areas​

  • Orders -- Full order lifecycle (placed → finish → returned) with region routing, ship-to-country ISO-2, Cainiao tracking number, AliExpress Choice flag for SLA monitoring. Imported orders appear in Odoo as native sale orders, each with an AliExpress page showing the platform status, Choice flag and ship-to country.
  • Products -- Multilingual listings (EN + RU/ES/FR/DE/PT), GTIN-required flag, Choice eligibility, approval state mirror, and a computed compliance-ready flag that warns before you publish a listing missing a barcode, English title, price or taxes.
  • Product images -- Photobank tracker (CDN URL + sequence + state).
  • Customers -- Masked buyer profiles (AliExpress masks PII; the masked payload is stored verbatim).
  • Collections -- Category tree mirror with self-referential parent/child.
  • Locations -- CN origin / US-EU-RU bonded / AliExpress Choice hubs.
  • Carriers -- Cainiao logistics: the carrier record resolves the seller's tracking template, falling back to the public Cainiao tracker, surfaced as a tracking URL on the order.
  • Returns and refunds -- Return lifecycle (created → received → refunded); each return and refund record links back to the imported order it belongs to.
  • Risk -- Fraud scoring per order (flagged when score ≥ 0.7).
  • Settlements -- Finance ingestion plus AE-Affiliate commission tracking; one-to-many ledger lines (sale / fee / tax / commission / adjustment / payout).
  • Analytics -- Per-region daily aggregates (GMV, orders, refunds, Choice orders, affiliate commission).
  • Workflows -- Per-region auto-confirm / auto-invoice / auto-deliver rules (e.g. Choice may auto-deliver on shipped while CN waits for buyer-confirm). Posted invoices are created for the prepaid marketplace orders the run produces.
  • Choice fulfillment programs -- Dedicated AliExpress Choice SLA tracker: handling-hours and delivery-days windows per programme; each order is scored against them from its placed, shipped and delivered times, giving a violation count and compliance percentage.

Multi-Region Runtime​

RegionCodeNotes
China (Origin)cnPrimary fulfillment
United States (Bonded)usState sales-tax nexus
European Union (Bonded)euOSS / IOSS compliant
Russia (Bonded)ruBonded local DC
AliExpress Choice (Premium)choiceStrict handling + delivery SLA

2026 Compliance Deltas​

All identifiers below are editable on the contact's AliExpress page in the Odoo form:

  • EU One-Stop-Shop (OSS) for cross-border > EUR 150 and Import One-Stop-Shop (IOSS) for shipments ≤ EUR 150 -- eu_oss_vat_number and eu_ioss_number on partners
  • US sales-tax nexus kept on partners as reference state codes via us_sales_tax_nexus_states; the module stores the codes, your own US tax configuration applies the rates
  • UK VAT post-Brexit -- uk_vat_number kept on partners as a reference field
  • KSA ZATCA Phase 2 -- keeps vat_registration_number + cr_number on the partner as reference fields; e-invoice XML / QR generation is your KSA localisation app's job
  • Brazil RFB -- CPF and CNPJ identifiers on partners
  • AE-Affiliate API commission tracking on every settlement -- affiliate_commission on the settlement plus a commission ledger line type for affiliate payout reconciliation

Prerequisites​

  • Odoo 17, 18, or 19 (Community or Enterprise edition)
  • An AliExpress seller account with Open Platform access
  • Your own AliExpress Open Platform application (App Key + App Secret)

Getting Started​

  1. Install -- download the ZIP for your Odoo version from your ECOSIRE Dashboard or the Odoo App Store, extract it into your addons directory, restart Odoo and install AliExpress Store Management from Apps. It installs and runs standalone under the OPL-1 licence -- no key to enter, nothing to switch on afterward.
  2. Create an app on the AliExpress Open Platform at the AliExpress Open Platform -- record your App Key and App Secret and request the API areas you will use (product, order, logistics, finance, affiliate).
  3. Connect in Odoo -- create a configuration under AliExpress → Configuration → Settings with App Key, App Secret and the OAuth Access / Refresh Tokens from your application, then run Test Connection until the instance reads connected. The 4-step onboarding wizard (Configuration → Onboarding Wizard) walks through the same flow: Credentials (with sign method), Ship-From Country, AliExpress Choice opt-in, Test Connection.
  4. First import -- AliExpress → Operations → Import Wizard; start with a small date range, review the mappings (categories, order statuses, payment and shipping methods), and watch the Logs view before letting the scheduled actions take over.
  5. Webhook (optional) -- register https://<your-odoo-host>/aliexpress/webhook as your message-subscription destination. It needs one Active webhook record holding the platform's Secret Key -- a one-time setup by your Odoo administrator or ECOSIRE support, detailed in the full guide. Unverified deliveries are rejected with HTTP 403; AliExpress publishes no delivery-signature scheme, so today every delivery is refused and the data arrives through the scheduled syncs.

Full details: the AliExpress Store Management guide.

API Details​

FieldValue
Auth methodHMAC-SHA256 (recommended) -- HMAC-MD5 still supported for legacy apps
Sign typeTOP-API standard signed-request envelope
OAuthOAuth2 Access Token + Refresh Token, held per configuration and restricted to the System group
Rate limitsSliding-window per-second and per-method QPS limiter + 5,000 calls/day app cap, with backoff and retry on throttling
Gatewayapi-sg.aliexpress.com -- /sync for TOP methods, /rest for OAuth tokens
WebhookTOP message subscription: the receiver signature-checks every delivery and fails closed; imported data arrives through the scheduled syncs
Key config fieldsapp_key, app_secret, access_token, refresh_token (masked, System group only)

Dashboard​

AliExpress → Dashboard renders KPI tiles computed from your real records -- total sales, orders, average order value, customers, imported products, out-of-stock listings, sync success rate -- each with its change versus the previous period and in your active company's currency. Period filters cover today / 7 days / 30 days / 90 days / year / custom range. The sales-trend and order-status charts drill down to the underlying AliExpress orders on click, Top Products ranks your five best sellers by the revenue of their real order lines, and an activity feed streams the latest sync log entries. The dashboard auto-refreshes every 60 seconds, and with no configuration yet it explains itself and links to Settings instead of showing empty numbers.

Daily Digest​

A daily scheduled action records an HTML summary of activity as a digest record under AliExpress → Finance → Daily Digests (this build records the digest rather than mailing it).

Troubleshooting​

IssueSolution
Connection failedVerify App Key + App Secret; confirm the OAuth access token is fresh; check the Open Platform app has the required API areas enabled
Sync not runningCheck Odoo scheduled actions; confirm the configuration is Active
Duplicate productsReview SKU + GTIN matching in Operations → Mapping Wizard
Orders not importingVerify the date range of your import; a single bad record is contained and logged -- read the Logs view
Test Connection failsThe record now shows Error with the reason; fix the credential it names, then use Exchange Authorization Code or Renew Access Token and test again
Token expiredThe connector renews the access token itself with the stored refresh token (or use Renew Access Token on the configuration). If AliExpress refuses the renewal, the refresh token has lapsed too: re-run the OAuth consent flow and use Exchange Authorization Code with the new code
Signature errorHMAC-SHA256 vs HMAC-MD5 mismatch -- verify the sign method on your Open Platform app matches the onboarding wizard
Choice SLA breachOpen Logistics → Fulfillment Programs (Choice SLA); each order is scored against the handling and delivery windows from its placed, shipped and delivered times, and the violation count and compliance percentage follow from that
Push does nothingListing publish/unpublish and stock and price push are explicit actions on the listing record (or the Export Wizard) and need a listing already linked to an Odoo product. On 17.0, 18.0 and 19.0 the Sync Inventory scheduled action is read-only; on 20.0 it pushes on-hand stock every 15 minutes for every mapped SKU, into the configuration's Stock Warehouse Code (or the listing's own AliExpress warehouse)

Live Demo​

Try the connector on our sandbox at aliexpress.demo.ecosire.com -- request a login from info@ecosire.com.

Support​


AliExpress Store Management 19.0.2 -- OPL-1 -- Built by ECOSIRE (PRIVATE) LIMITED -- ecosire.com