Temu Store Management

Temu Store Management connects a Temu seller account to Odoo. This page is the installation and configuration guide for the module you downloaded from your ECOSIRE dashboard. Everything below describes the temu_store_management module as it ships today.

Technical name	temu_store_management
Odoo versions	17.0, 18.0, 19.0 (Community or Enterprise)
Current shipped version	17.0 → 17.0.2.0.0, 18.0 → 18.0.2.0.3, 19.0 → 19.0.2.0.3
Price	$499 USD — one-time, per Odoo version
Odoo module licence	LGPL-3
Category	Connector

Licences are bound to one Odoo major version

A licence issued for Odoo 17 unlocks only the 17.0 download and only validates on an Odoo 17 database. It will not activate on 18 or 19, and the 18.0/19.0 ZIPs will not appear in your dashboard. Buy the version you actually run — and if you later upgrade Odoo, you need the licence for the new version. This is enforced on both the download and the activation paths, so there is no way round it.

Requirements

Requirement	Detail
Odoo	17.0, 18.0 or 19.0, Community or Enterprise. Self-hosted or Odoo.sh — Odoo Online (SaaS) cannot install third-party modules
Odoo apps	base, sale_management, stock, account, delivery, mail, web, product, contacts, knowledge — Odoo installs any that are missing
ECOSIRE dependency	ecosire_license_client — a separate free download, not bundled in this ZIP. See step 3
Python packages	requests
Platform account	A Temu seller/partner account with API access
Licence	An active ECOSIRE licence for this module and your Odoo version

Install the Python packages into the same interpreter that runs Odoo:

sudo -u odoo pip install requests

Installation

1. Download the ZIP for your Odoo version

Sign in at ecosire.com and open your dashboard downloads. You will only be offered the file matching your licence's Odoo version — that is expected, see the warning above.

2. Extract into your addons path

unzip temu_store_management_v19_*.zip -d /opt/odoo/addons/
ls /opt/odoo/addons/temu_store_management/__manifest__.py   # sanity check

The archive contains a single top-level temu_store_management/ directory. If your ls check fails, the module folder ended up one level too deep — move it up so __manifest__.py sits directly inside temu_store_management/.

3. Install the ECOSIRE licence client

temu_store_management declares ecosire_license_client as a hard dependency. It is a separate, free module and it is not bundled in the connector ZIP — Odoo will refuse to install the connector until the licence client is present in your addons path. Download it from your ECOSIRE dashboard alongside the connector and extract it the same way:

unzip ecosire_license_client_v19_*.zip -d /opt/odoo/addons/

4. Restart Odoo and install

sudo systemctl restart odoo

1. Go to Apps and click Update Apps List (developer mode must be on).
2. Search for Temu Store Management and click Install.
3. Odoo pulls in ecosire_license_client and the Odoo apps listed above automatically.

When the install finishes, a Temu menu appears in the main Odoo app switcher.

Activate your licence

How to obtain a licence key

The steps below activate a key you already hold. This is how you get one in the first place.

1. Create an ECOSIRE account at ecosire.com, using the email address you want the licence issued to. Your keys and your downloads both live in that account's dashboard.
2. Buy the module — either directly on ecosire.com, or from the Odoo App Store.
3. Bought on ecosire.com? The key is issued to your dashboard automatically once the order completes. Nothing else to do.
4. Bought on the Odoo App Store? Send us proof of purchase: email [email protected] from the same address as your ecosire.com account, with the Odoo sales-order slip or order reference (the purchase receipt Odoo emails you at checkout). The App Store does not tell ECOSIRE who bought what, so this is how we match your purchase to your account.
5. We issue the key to your dashboard, next to the ZIP for your Odoo version, in the form ECO-XXXX-XXXX-XXXX.

One licence, one Odoo major version

The key is issued against the Odoo major version you bought — see the warning at the top of this page. Tell us which version you run when you send proof of purchase, so we issue the right one.

Before you activate

Set your instance's public URL first. The licence is bound to the domain derived from web.base.url, so activating with a placeholder value binds the licence to the wrong host:

1. Turn on developer mode.
2. Settings → Technical → System Parameters, find web.base.url.
3. Set it to the real HTTPS URL your users browse to, e.g. https://erp.example.com.

Activate

1. Go to Settings → ECOSIRE.COM → Activate License.
2. Paste your licence key.
3. Choose Temu Store Management in the module dropdown (it lists the installed ECOSIRE modules).
4. Click Activate.

Settings → ECOSIRE.COM → License Status then shows, per module, the licence state, last-verified time, Odoo version, module version, support expiry, and whether an offline token is cached.

What the client sends

Activation and validation are plain HTTPS JSON calls to https://api.ecosire.com/api. Every request carries the same five fields:

{
  "key": "ECO-XXXX-XXXX-XXXX-XXXX",
  "module_name": "temu_store_management",
  "domain": "erp.example.com",
  "hw_fingerprint": "<sha256 of this installation's hardware/db identity>",
  "odoo_version": "19.0"
}

Endpoint	Used for
POST /api/licenses/activate	First-time activation — binds the licence to this domain
POST /api/licenses/validate	Ongoing verification
POST /api/licenses/issue-token	Fetches the RSA-signed offline token used for the grace period
POST /api/licenses/deactivate-self	Releases this domain so the key can move to another database

The base URL is overridable through the ecosire.license.api_url system parameter, and the client refuses any value that is not HTTPS. You do not need to change it.

Activation slots, and moving between databases

Each licence carries its own activation limit. New licences default to a single domain; some licences are issued with more. Check License Status, or the licence detail page in your ECOSIRE portal, for the number on yours. Re-activating on a domain that is already bound is a no-op success, not a second slot.

• Odoo.sh staging and development builds do not consume a slot — they are recognised as non-production hosts and activate without binding.
• To move a live licence to a different database, use Deactivate on the activation screen first; that releases the domain server-side so you can activate elsewhere.
• Ten failed activation attempts within an hour trips a client-side rate limiter. Wait up to 60 minutes, or contact support — do not keep retrying a key you are unsure about.

Staying licensed after activation

A daily scheduled action, ECOSIRE License: Background Re-verification, re-checks the licence out of the request path, refreshes the cached offline token, and keeps the last-known-good timestamp fresh. Because of that, a transient network problem, an Odoo.sh rebuild or a worker restart does not lock you out. Verification results are cached for five minutes, so a licence change can take a few minutes to show up.

If you see a hard rejection instead — LICENSE_NOT_FOUND, LICENSE_INACTIVE, LICENSE_EXPIRED, MODULE_MISMATCH, VERSION_MISMATCH or NOT_ACTIVATED_ON_DOMAIN — the grace period is deliberately not granted; fix the underlying problem. See Troubleshooting.

Configuration

Connect to Temu

Open Temu → Configuration → Settings and create a record (model temu.configuration). The connection fields are:

Label	Technical name	Required	Values
App Key	app_key	Yes	Text
App Secret	app_secret	Yes	Text
Access Token	access_token	No	Text
Refresh Token	refresh_token	No	Text
Temu Region	temu_region	Yes	Selection: US, EU
Mall Type	temu_mall_type	Yes	Selection: semi_managed, fully_managed

App Key and App Secret are required. Temu Region (US / EU) and Mall Type (semi_managed / fully_managed) are also required — they change both the API host and the fulfilment behaviour, so set them before the first sync.

The same record carries 11 behaviour checkboxes — sync_products, sync_orders, sync_customers, sync_inventory, auto_sync_products, auto_sync_orders, auto_sync_customers, enable_dac7_compliance, enable_gpsr_compliance, enable_section_321, …. They gate what the connector is allowed to do automatically once it is connected. Leave anything you are not ready for switched off, and turn them on one at a time.

Credentials are issued from the Temu Partner Platform — see partner.temu.com/documentation. The connector talks to openapi.kuajingmaihuo.com/openapi (US) or openapi-eu.kuajingmaihuo.com/openapi (EU), selected by Temu Region.

When the fields are filled in, click Test Connection. The record's status moves to connected only when the platform answers successfully — do not run a first import until it does.

Public endpoint: the webhook receiver

The module registers one publicly reachable HTTP route. It is the only endpoint on this module served without an Odoo login, so it is worth knowing exactly what it does before you expose your instance.

Endpoint	Method	Auth	Purpose
/temu/webhook	POST	public (no Odoo session)	Receives inbound Temu event deliveries

This receiver currently rejects every delivery, on purpose. ECOSIRE's platform contract for Temu does not pin an inbound delivery-signature scheme, which means a payload arriving at /temu/webhook cannot be proven to have come from Temu rather than from anyone else who can reach your instance. Rather than trust an unsigned payload, signature verification fails closed: the endpoint answers HTTP 403 with {"status": "rejected", "message": "signature verification failed"} and processes nothing from the request.

What that means for you in practice:

• You do not need to register this URL with Temu. Pointing Temu at it will produce nothing but 403s.
• Your data still syncs. Product, order, customer and inventory syncing on this connector is driven by the scheduled actions below, which poll the Temu API on your behalf. Real-time push is not how this connector stays current.
• The route is safe to leave exposed. It reads the request body and headers, finds no verifying webhook record, logs the rejection with the caller's IP, and returns. Nothing is written and no record is created.
• The temu.webhook records under the connector's menu (name, topic, delivery URL, secret, delivery and failure counters) exist so the receive path is ready the day a signed Temu delivery scheme is available. They do not enable inbound push today.

The module's remaining routes — /temu/api/status, /temu/api/sync and /temu/dashboard/data — are internal JSON-RPC endpoints used by the module's own screens. They require a logged-in Odoo user and are not part of your external setup.

Scheduled actions

The module installs 6 scheduled actions (Settings → Technical → Scheduled Actions):

Scheduled action	Runs every	Enabled on install
temu: Sync Products	1 hours	Yes
temu: Sync Orders	30 minutes	Yes
temu: Sync Customers	6 hours	Yes
temu: Sync Inventory	15 minutes	Yes
temu: Test Connection	1 days	Yes
temu: Cleanup Old Logs	1 days	Yes

Intervals above are the shipped defaults. Adjust them to your volume — but be aware that the platform, not Odoo, sets the API rate limits, and shortening a sync interval is the usual cause of throttling errors in the logs.

Using the module

The Temu menu is laid out as:

• Temu → Dashboard
• Temu → Products
• Temu → Orders
• Temu → Customers
• Temu → Operations — Import Wizard, Export Wizard, Mapping Wizard, Test Connection, Logs, Reports
• Temu → Configuration — Settings
• Temu → Premium (v19.0.2) — Orders (Shadow), Products (Shadow), Product Images, Customers (Masked), Collections, Locations / FCs, Carriers, Returns, Refunds, Risk / Fraud, Settlements, Analytics, Workflow, Auto-Workflow Rules, Daily Digests

A normal first run is:

1. Test Connection until the instance reads connected.
2. Review the mapping records (categories, order statuses, payment and shipping methods) so imported data lands on the right Odoo records.
3. Run a small import first — restrict it by date or by a handful of products — and check the results before letting the scheduled actions take over.
4. Watch the Logs view during the first full sync. Every sync writes a log line; failures are recorded there rather than raised at the user.

Module-specific notes

• Temu Region and Mall Type are both required and change behaviour, not just labels: the region selects the API host, and semi_managed vs fully_managed determines whether you or Temu own fulfilment. Set them before the first sync.
• The Premium menu groups the shadow records (orders, products, customers), returns, refunds, risk, settlements and analytics.

Troubleshooting

Licensing

Symptom / error code	Cause and fix
VERSION_MISMATCH	The licence is for a different Odoo major version than the database you activated on. Licences are not transferable across Odoo versions — you need the licence for the version you run.
MODULE_MISMATCH	The licence belongs to a different ECOSIRE module. Check you selected Temu Store Management (temu_store_management) in the activation dropdown.
NOT_ACTIVATED_ON_DOMAIN	The database's web.base.url domain is not among the licence's activated domains. Activate on this domain, or deactivate the old one first.
LICENSE_EXPIRED / LICENSE_INACTIVE	The licence is past its expiry or has been suspended/revoked. Check the licence in your ECOSIRE portal.
LICENSE_NOT_FOUND	The key does not exist. Keys are upper-cased before sending, so case is not the problem — re-copy it from your portal.
Activation limit reached	Every slot on the licence is bound to a domain. Deactivate one first.
Too many failed activation attempts	Ten failures in an hour. Wait up to 60 minutes.
Could not determine your Odoo instance domain	web.base.url is empty. Set it, then activate.
The requests library is required	requests is missing from Odoo's Python environment. Install it into the interpreter that runs Odoo.
The downloaded ZIP is the wrong version	The download list is filtered by your licence's version. If you need a different Odoo version, you need that version's licence.

Syncing

Symptom	Cause and fix
Test Connection fails	Re-check every required field in the table above. Most failures are a mistyped secret, or credentials created for the sandbox while the connector points at production (or vice-versa).
Nothing syncs even though the connection is fine	The scheduled actions are disabled at the Odoo level, or Odoo's cron worker is not running. Check Settings → Technical → Scheduled Actions and that --max-cron-threads is greater than zero.
Sync starts then stops part-way	Read the Logs view for that run. Rate limiting and rejected field values are the two common causes; both are logged with the platform's own error text.
Records import but map to the wrong Odoo values	Fix the mapping records under the module's configuration, then re-run the import.
Duplicated products or customers	Run the initial import once. If a first attempt half-finished, check the existing records before re-running rather than importing on top.

Version history

Odoo version	Version you download today
17.0	17.0.2.0.0
18.0	18.0.2.0.3
19.0	19.0.2.0.3

ECOSIRE module versions are <odoo major>.<module major>.<minor>.<patch>, so 19.0.2.0.3 is the Odoo 19 build of module version 2.0.3. Your installed version is shown in Apps and in Settings → ECOSIRE.COM → License Status.

Support

• General troubleshooting
• Licence verification guide
• Email: [email protected]
• Support portal