Skip to main content

Target Plus Store Management

The ECOSIRE Target Plus Store Management module integrates your Target Plus seller account with Odoo. Target Plus is Target's third-party marketplace, powered by the Mirakl platform — this connector talks to the Mirakl Front and Operator APIs that Target Plus exposes to sellers.

Compatibility: Odoo 17 / 18 / 19 Price: $499 (one-time) License: Up to 3 domain activations

Key Features​

  • Mirakl Front API (PM / OF / SH / IV / O / P endpoints) integration
  • Offer (price + stock) sync — Odoo → Target Plus
  • Order import with marketplace status mapping
  • Shipment + tracking submission with carrier mapping
  • Catalog discovery: attributes (PM11), value lists (VL11), hierarchies (H11)
  • Acceptance / refusal workflow for incoming orders
  • Settlement + invoice report import
  • Multi-instance support (sandbox vs production)
  • OWL 2 dashboard with KPIs and charts
  • License-mixin enforced — one key per Odoo SH or on-prem domain

Prerequisites​

  • Odoo 17, 18, or 19 (Community or Enterprise)
  • An active ECOSIRE license key for this module
  • An onboarded Target Plus seller account
  • Mirakl API key (long-lived bearer token from your seller portal)

Installation​

  1. Download the module ZIP delivered with your purchase.
  2. Extract targetplus_store_management/ into your Odoo addons directory.
  3. Make sure ecosire_license_client/ is also on the addons path (ships in the same delivery).
  4. Restart Odoo and click Apps → Update Apps List.
  5. Search for ECOSIRE Target Plus Store Management and click Install.
  6. Paste your license key when prompted, then click Activate.

Configuration​

Step 1: Get the Mirakl API key​

  1. Sign in to the Target Plus seller portal (Mirakl-powered).
  2. Navigate to My Account → User Settings → API Keys.
  3. Generate a key and copy the API key value.
  4. Note your shop ID if displayed (it's also accessible via S20 Mirakl endpoint).

Step 2: Create an instance in Odoo​

  1. Navigate to Target Plus → Configuration → Instances.
  2. Click Create and fill in:
    • Instance name (e.g. Target Plus — Production)
    • Mirakl host (Target Plus's seller API endpoint)
    • API key
    • Default warehouse, company, pricelist, fiscal position
  3. Click Test Connection to verify (calls S20 /api/account).
  4. Save and click Activate Instance.

Step 3: Sync configuration​

  • Offer Sync — Odoo → Target Plus only (Mirakl model). Push price and stock from your Odoo product variants on a schedule.
  • Order Sync — pull new orders, map to Odoo sale orders, and define an auto-accept window (typically ≤2 hours after the order lands to meet Target Plus SLA).
  • Shipment Sync — push picking validation events back as tracking numbers + carrier codes via OR23 / OR24.
  • Catalog discovery — use Operations → Refresh Catalog Metadata to cache attributes / value lists / hierarchies for offer creation.

Initial Sync​

  1. Open Target Plus → Operations → Initial Import.
  2. Run Refresh Catalog Metadata first (pulls Target Plus's required attributes).
  3. Run Import Orders with the date range of your live history.
  4. Open the Offer Export wizard to push your initial product price+stock list.

Dashboard​

The OWL 2 dashboard renders:

  • KPI cards: orders today / this month, units shipped, acceptance SLA hit rate, settlement balance
  • Sales chart over time with marketplace filter
  • Offer health: live offers, paused, rejected, missing attribute counts
  • Sync queue with retry shortcuts

Troubleshooting​

IssueLikely cause + fix
License is not valid for Odoo versionConfirm the key you pasted matches your installed module version (Odoo 19).
401 on Test ConnectionAPI key expired or revoked from the seller portal. Regenerate and update the instance.
Offers rejectedMissing required attributes — re-run Refresh Catalog Metadata and re-map the missing fields on the product template.
Order import emptyMirakl OR11 is keyed off start_date + order_state_codes. Adjust the import window or include WAITING_ACCEPTANCE.
Webhooks not receivedTarget Plus does NOT support seller-side webhooks; the module polls via cron. Adjust the cron cadence on the Configuration form.

Support​