Skip to main content

Store Connector Setup & Product Mapping

This is the complete, self-serve walkthrough for any ECOSIRE Odoo marketplace / store-management connector — Amazon, eBay, Shopify, WooCommerce, Daraz, Noon, MercadoLibre, and 190+ others. Every connector shares the same architecture, so the steps below apply to all of them. Where a step is platform-specific (API credentials, country endpoints), your module's own page under Odoo Modules has the exact values.

You can complete the whole flow yourself in about 15 minutes.

Works on Odoo 17, 18 and 19

Every ECOSIRE connector ships for Odoo 17, 18, and 19 (Community and Enterprise). The screens look slightly different per version, but the steps are identical.

Before you start​

You need:

  • An Odoo 17 / 18 / 19 instance where you can install modules (on-premise, Odoo.sh, or a managed host).
  • Your ECOSIRE license key (format ECO-XXXX-XXXX-XXXX) from your dashboard.
  • The connector ZIP for your Odoo version, from your dashboard Downloads.
  • Your marketplace API credentials (App Key / App Secret / Access Token, or the equivalent for your platform). Your module page lists exactly which fields are needed.

Step 1 — Install the module​

Option A — Apps menu (no server access needed):

  1. In Odoo, enable Developer Mode (Settings → Developer Tools → Activate the developer mode).
  2. Go to Apps → ⋮ (top right) → Upload Module, choose the connector ZIP, and click Import.
  3. Odoo installs it automatically.

Option B — Addons folder (server access):

unzip ecosire-<connector>-*.zip -d /opt/odoo/addons/
sudo systemctl restart odoo

Then Apps → Update Apps List, search the connector, and click Install.

Upgrading an existing install

If the connector is already installed and you are applying an update, drop the new files in and either restart with -u <module_name>, or use Apps → (your module) → Upgrade. A file swap without an upgrade can leave the database missing new columns — always run the upgrade.

Step 2 — Activate your license​

  1. Open the connector's main menu → Configuration / Settings, or Settings → ECOSIRE License.
  2. Paste your license key (ECO-XXXX-XXXX-XXXX) and click Activate.
  3. You should see Active. Each license covers up to 3 domain activations; you can move a license between databases with Deactivate / Move License to This Database.

If activation is rejected, see Troubleshooting below.

Step 3 — Connect your store​

  1. Open <Connector> → Configuration and create a new store record.
  2. Enter your marketplace API credentials (exact fields are on your module page — e.g. App Key, App Secret, Access Token, Refresh Token, Country/Region).
  3. Click Test Connection. A green confirmation means Odoo can talk to the marketplace.
  4. Set the Warehouse and Company the store should use.
Sandbox vs Live

If your connector has a Sandbox Mode toggle, it is for testing only — actions like pushing order status are simulated (a "Dry-run" notice) and are not sent to the marketplace. Turn Sandbox Mode off for your live store.

Step 4 — First sync​

  1. Go to <Connector> → Operations (or the Sync buttons on the configuration).
  2. Run the syncs you need: Products, Orders, Customers, Inventory.
  3. To backfill history, use Import Historical Orders and set a date range.
  4. Watch progress in the Sync Log.

Step 5 — Map products to your existing catalogue​

This is the step most merchants ask about: you already keep your products in Odoo and you want the connector to link to them — not create duplicates, and not split a variant product into several copies.

5.1 — Turn OFF auto-create (one time, per store)​

  1. Open your store under Configuration.
  2. On the Products / Pricing tab, set "Create Missing Products" = OFF.
  3. Save (repeat for each connected store).

With this off, the connector only ever links to an existing product or flags an order for mapping — it never creates a duplicate.

5.2 — Make the SKUs match​

The connector matches each marketplace listing to your Odoo product by:

  1. Internal Reference (default_code) equal to the marketplace Seller SKU, then
  2. Barcode equal to the Seller SKU.

So set each Odoo product's Internal Reference (or Barcode) to its marketplace Seller SKU. For variant products, set the Internal Reference on each variant to that variant's own Seller SKU.

5.3 — Bulk-map from a marketplace export (fastest)​

  1. Export your product list from your marketplace seller centre (Excel/CSV with a Seller SKU column).
  2. In Odoo: <Connector> → Tools → Import Product Mapping (Excel/CSV).
  3. Set Daraz Store / Store = your store, Match By = Seller SKU, upload the file.
  4. Run with Mode = Preview only first — the result log shows which rows would link vs create/skip.
  5. Switch Mode = Only update existing products and run again. The connector links every row whose Seller SKU matches an existing product's Internal Reference or Barcode — no new products are created.
First-run mapping

On your first mapping run your products aren't yet "tagged" to the store. The wizard now finds them company-wide by Internal Reference / Barcode and tags them automatically, so "Only update existing products" maps your whole file on the first try.

5.4 — Fix orders that arrived before mapping​

Orders that came in before you mapped show a placeholder line / "Needs Product Mapping":

  1. Open the order (or select several).
  2. Click Re-map Products in the header.
  3. Each line is re-resolved against your catalogue by Seller SKU → Internal Reference / Barcode and bound to the correct product/variant.

Variant products​

A marketplace listing with several SKUs (e.g. one shoe in sizes 40–44) becomes one Odoo product with several variants, not several products. The connector builds these variants on every import path. If the marketplace export doesn't carry distinguishing size/colour values, the platform sends it as a single SKU and Odoo keeps it as one product — that's expected.

Step 6 — Fulfilment (push status & print labels)​

From a marketplace order in Odoo:

  • Mark Packed — pushes the packed status back to the marketplace. Set the Shipment Provider field on the order first (e.g. "Daraz Express"); the marketplace rejects a pack request with no provider.
  • Ready to Ship — pushes RTS, optionally with carrier + tracking number.
  • Print AWB / Print Invoice — fetches the air-waybill / invoice PDF from the marketplace and attaches it to the order.

Step 7 — Dashboard & multiple stores​

The built-in dashboard shows revenue, orders, customers, products (with variant count), average order value, and sync health, plus a sales-trend chart and order-status breakdown.

  • Use the period filter (Today / 7D / 30D / 90D / Year / Custom) to scope the figures.
  • If you run more than one store, a store selector appears at the top — switch between stores and every figure (including Top Products) is scoped to the selected store, with no cross-store mixing.

Troubleshooting​

SymptomFix
License rejected / "not valid for Odoo version"Update ecosire_license_client to the latest, then re-activate. See common issues.
"Server error: HTTP 201" on activationUpdate ecosire_license_client to 2.1.1+.
Connection failedRe-check API credentials; confirm the Country/Region matches your seller account.
Duplicate products createdSet Create Missing Products = OFF and map by Seller SKU (Step 5).
Variants split into separate productsSet each variant's Internal Reference to its own Seller SKU, then Re-map Products.
"Status not updated" on Mark PackedSet the Shipment Provider on the order; confirm Sandbox Mode is OFF.
AWB won't printConfirm Sandbox Mode is off and the order has live marketplace item IDs; retry.
Missing column / page crash right after an updateYou swapped files without upgrading — run Apps → (module) → Upgrade (or restart with -u <module>).
Sync stoppedCheck Settings → Technical → Scheduled Actions that the connector crons are active.

Need help?​

Last updated on