About You Store Management
This is the installation and configuration guide for About You Store Management, the module you downloaded from your ECOSIRE dashboard. Everything on this page describes the aboutyou_store_management module exactly as it ships today — the facts below were read out of the released build, not from a roadmap.
| Technical name | aboutyou_store_management |
| Odoo versions | 17.0, 18.0, 19.0 (Community or Enterprise) |
| Current shipped version | 17.0 → 17.0.1.1.0, 18.0 → 18.0.1.1.0, 19.0 → 19.0.1.1.0 |
| Price | $499 USD — one-time, per Odoo version |
| Odoo module licence | OPL-1 |
| Category | Connector |
From version 1.1.0 the module installs and runs standalone: no extra ECOSIRE download to install first, nothing to enter before you can sync, and no ECOSIRE server contacted at runtime. Your rights are contractual under OPL-1. If you are upgrading from 1.0.x, see Upgrading from 1.0.x.
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, portal, product, contacts, digest — Odoo installs any that are missing |
| Python packages | requests |
| Platform account | An About You account with API access |
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, then take the archive that matches the Odoo major version you run.
2. Extract into your addons path
unzip aboutyou_store_management_v19_*.zip -d /opt/odoo/addons/
ls /opt/odoo/addons/aboutyou_store_management/__manifest__.py # sanity check
The module must end up as a single top-level aboutyou_store_management/ directory with __manifest__.py directly inside it. If your ls check fails, the folder landed one level too deep or too shallow — move it so the path above resolves.
3. Restart Odoo and install
sudo systemctl restart odoo
- Go to Apps and click Update Apps List (developer mode must be on).
- Search for About You Store Management and click Install.
- Odoo pulls in the Odoo apps listed above automatically.
When the install finishes, a Aboutyou menu appears in the main Odoo app switcher.
Upgrading from 1.0.x
Version 1.1.0 removed the licence client. Upgrading is an ordinary Odoo module upgrade — your instances, mappings, orders, products and payouts are carried over untouched.
- Replace the module folder in your addons path with the new one.
- Restart Odoo and run the upgrade: Apps → About You Store Management → Upgrade, or
odoo -u aboutyou_store_management -d <database>. - The old ECOSIRE dependency module is no longer required by this connector. It can stay installed for other ECOSIRE modules that still use it; this connector no longer reads it.
Two settings that used to advertise an OAuth flow — Access Token and API Password — are gone from the connection form. About You authenticates with a single API key; if you had filled either field, nothing is lost, because neither was ever sent.
Configuration
Connect to About You
Create a connection record on the aboutyou.instance model. The fields the module defines for the connection are:
| Field | Technical name | Type | Required |
|---|---|---|---|
| Instance Name | name | Char | Yes |
| About You Seller Center URL | shop_url | Char | Yes |
| Company | company_id | Many2one | Yes |
| API Key | api_key | Char | No |
| Webhook Secret | shared_secret | Char | No |
| API Version | api_version | Char | No (defaults to v1) |
The API key is the one you issue in Seller Center → Settings → API Keys. The module sends it as the X-API-KEY header on every request; this API has no OAuth flow, so there is no token to exchange or refresh. The webhook secret is only needed if you use the module's webhook endpoints — it is what incoming payloads are HMAC-verified against, and an unsigned payload is rejected.
The fields marked Yes are enforced by the model — Odoo will not let you save the record without them. The technical name is the reliable identifier if your screen wording differs.
The same record carries three order-automation checkboxes — auto_confirm_order, auto_create_invoice and auto_validate_invoice. They run in that order after each order import, and all three default to off, so a freshly connected instance imports orders as quotations and does nothing else. Turn them on one at a time.
The module contacts partner.aboutyou.com (the Seller Center API). Your firewall must allow outbound HTTPS to it.
Scheduled actions
The module installs 13 scheduled actions (Settings → Technical → Scheduled Actions):
| Scheduled action | Runs every | Enabled on install |
|---|---|---|
| Aboutyou: Sync Products | 30 minutes | Yes |
| Aboutyou: Sync Orders | 15 minutes | Yes |
| Aboutyou: Sync Customers | 60 minutes | Yes |
| Aboutyou: Sync Inventory | 10 minutes | Yes |
| Aboutyou: Process Queue Jobs | 5 minutes | Yes |
| Aboutyou: Import Payout Reports | 6 hours | Yes |
| Aboutyou: Import Refunds | 30 minutes | Yes |
| Aboutyou: Auto Risk Detection | 30 minutes | Yes |
| Aboutyou: Generate Analytics | 4 hours | Yes |
| Aboutyou: Webhook Health Check | 60 minutes | Yes |
| Aboutyou: Cleanup Old Logs | 24 hours | Yes |
| Aboutyou: Process Workflows | 10 minutes | Yes |
| Aboutyou: Daily Summary Report | 1 day | 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 module's menu is laid out as:
- Aboutyou → Dashboard
- Aboutyou → Orders
- Aboutyou → Refunds
- Aboutyou → Products
- Aboutyou → Customers
- Aboutyou → Payouts
- Aboutyou → Analytics
- Aboutyou → Operations — Run Operations, Queue Jobs, Logs
- Aboutyou → Configuration — Instances, Locations, Payment Gateways, Scheduled Actions, Webhooks
A normal first run is:
- Save the connection record and confirm the module reports a successful connection before importing anything.
- Review the mapping records so imported data lands on the right Odoo records.
- 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.
- Watch the log records during the first full sync. Failures are recorded there rather than raised at the user.
Troubleshooting
Installation
| Symptom | Cause and fix |
|---|---|
| Odoo refuses to install the module | Check the folder name in your addons path is exactly aboutyou_store_management and that the path is listed in addons_path. Since 1.1.0 there is no ECOSIRE dependency to install first. |
The requests library is required | requests is missing from Odoo's Python environment. Install it into the interpreter that runs Odoo. |
| The module still asks you to unlock it before syncing | You are running 1.0.x. Upgrade to 1.1.0 — see Upgrading from 1.0.x — and the prompt disappears. |
Syncing
| Symptom | Cause and fix |
|---|---|
| The connection will not validate | Test Connection reports the platform's own reason. An empty API key is named as such; anything else is the Seller Center's response to a call on your seller account. Re-copy the key from Seller Center → Settings → API Keys. |
| 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 module's log records 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. |
| An order imported with the wrong date | Fixed in 1.1.0: timestamps arriving with a negative UTC offset were being truncated. Re-import the affected orders after upgrading. |
| Product images were never imported | Fixed in 1.1.0: the wizard's Import Product Images option now reaches 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.1.1.0 |
| 18.0 | 18.0.1.1.0 |
| 19.0 | 19.0.1.1.0 |
ECOSIRE module versions are <odoo major>.<module major>.<minor>.<patch>, so 19.0.1.1.0 is the Odoo 19 build of module version 1.1.0. Your installed version is shown in Apps.
1.1.0
- The module installs and runs standalone: the extra ECOSIRE download it used to require, and the unlock step that came with it, are both gone. Your rights are contractual under OPL-1.
- Every option on the operations wizard now reaches the import it belongs to — date range, skip-existing, import-images and specific IDs. Product images are imported for the first time.
- The three order-automation checkboxes on the connection record now run the workflow they describe. They still default to off.
- Order timestamps that arrive with a negative UTC offset are parsed correctly; they were previously truncated to the year.
- API calls follow the documented Seller Center surface: page/limit pagination, the documented product upsert route, the accept and refund routes for returns, and a connection test against the seller account.
- Webhook payloads that arrive without a valid signature are rejected rather than accepted.
- Dashboard amounts render in the seller's own currency instead of a hardcoded dollar sign.
- The connection form describes API-key authentication instead of an OAuth flow the platform does not offer.