Skip to main content

Printful Store Management

This is the installation and configuration guide for Printful Store Management, the module you downloaded from your ECOSIRE dashboard. Everything on this page describes the printful_store_management module exactly as it ships today — the facts below were read out of the released build, not from a roadmap.

Technical nameprintful_store_management
Odoo versions17.0, 18.0, 19.0 (Community or Enterprise)
Current shipped version17.017.0.2.0.1, 18.018.0.2.0.0, 19.019.0.2.0.0
Price$499 USD — one-time, per Odoo version
Odoo module licenceLGPL-3
CategoryConnector
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 those 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

RequirementDetail
Odoo17.0, 18.0 or 19.0, Community or Enterprise. Self-hosted or Odoo.sh — Odoo Online (SaaS) cannot install third-party modules
Odoo appsbase, sale_management, stock, account, delivery, mail, web, portal, product, contacts, digest, knowledge — Odoo installs any that are missing
ECOSIRE dependencyecosire_license_client — a separate free download, not bundled in this ZIP. See step 3
Python packagesrequests
Platform accountA Printful account with API access
LicenceAn 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 printful_store_management_v19_*.zip -d /opt/odoo/addons/
ls /opt/odoo/addons/printful_store_management/__manifest__.py # sanity check

The module must end up as a single top-level printful_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. Install the ECOSIRE licence client

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

unzip ecosire_license_client_v*_*.zip -d /opt/odoo/addons/
If the licence client is not in your dashboard

The licence client is distributed separately from the connector archives. If you cannot see it in your downloads, email [email protected] with your licence key and we will send it to you — do not try to install the connector without it, because Odoo will simply refuse.

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 Printful Store Management and click Install.
  3. Odoo pulls in ecosire_license_client and the Odoo apps listed above automatically.

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

Activate your licence

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 Printful 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 HTTPS JSON calls to https://api.ecosire.com/api. Every request carries the same five fields:

{
"key": "ECO-XXXX-XXXX-XXXX-XXXX",
"module_name": "printful_store_management",
"domain": "erp.example.com",
"hw_fingerprint": "<sha256 of this installation's hardware/db identity>",
"odoo_version": "19.0"
}
EndpointUsed for
POST /api/licenses/activateFirst-time activation — binds the licence to this domain
POST /api/licenses/validateOngoing verification
POST /api/licenses/issue-tokenFetches the signed offline token used for the grace period
POST /api/licenses/deactivate-selfReleases this domain so the key can move to another database

The base URL is overridable through the ecosire.license.api_url system parameter. You do not need to change it.

Activation slots, and moving between databases

Each licence carries its own activation limit, and new licences default to a single domain. Some licences are issued with more. Do not assume a number — check Settings → ECOSIRE.COM → License Status, or the licence detail page in your ECOSIRE portal, for the limit on yours. Re-activating on a domain that is already bound is a no-op success, not a second slot.

  • 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 one 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 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 Printful

Create a connection record on the printful.instance model. The fields the module defines for the connection are:

FieldTechnical nameTypeRequired
Instance NamenameCharYes
API Tokenapi_keyCharYes
Companycompany_idMany2oneYes

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 4 behaviour checkboxes — auto_validate_inventory, auto_confirm_order, auto_create_invoice, auto_validate_invoice. They gate what the module 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.

The module's own source contacts these hosts: api.printful.com, developers.printful.com. Your firewall must allow outbound HTTPS to them.

Scheduled actions

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

Scheduled actionRuns everyEnabled on install
Printful: Sync Products30 minutesYes
Printful: Sync Orders15 minutesYes
Printful: Sync Customers60 minutesYes
Printful: Sync Inventory10 minutesYes
Printful: Process Queue Jobs5 minutesYes
Printful: Import Payout Reports6 hoursYes
Printful: Import Refunds30 minutesYes
Printful: Auto Risk Detection30 minutesYes
Printful: Generate Analytics4 hoursYes
Printful: Webhook Health Check60 minutesYes
Printful: Cleanup Old Logs24 hoursYes
Printful: Process Workflows10 minutesYes
Printful: Daily Summary Report1 dayYes
Printful: Poll Pending Mockup Tasks5 minutesYes
Printful: Process Subscription Renewals1 dayYes

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:

  • Printful → Dashboard
  • Printful → Orders
  • Printful → Refunds
  • Printful → Products
  • Printful → Customers
  • Printful → Payouts
  • Printful → Analytics
  • Printful → Operations — Run Operations, Queue Jobs, Logs
  • Printful → Premium 2026 — Mockup Tasks, Subscriptions, Fulfillment Regions, Print Techniques
  • Printful → Configuration — Instances, Locations, Payment Gateways, Scheduled Actions, Webhooks

A normal first run is:

  1. Save the connection record and confirm the module reports a successful connection before importing anything.
  2. Review the mapping records 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 log records during the first full sync. Failures are recorded there rather than raised at the user.

Troubleshooting

Licensing

Symptom / error codeCause and fix
VERSION_MISMATCHThe licence is for a different Odoo major version than the database you activated on. Licences are not transferable across Odoo versions.
MODULE_MISMATCHThe licence belongs to a different ECOSIRE module. Check you selected Printful Store Management (printful_store_management) in the activation dropdown.
NOT_ACTIVATED_ON_DOMAINThe 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_INACTIVEThe licence is past its expiry or has been suspended. Check the licence in your ECOSIRE portal.
LICENSE_NOT_FOUNDThe key does not exist. Keys are upper-cased before sending, so case is not the problem — re-copy it from your portal.
Activation limit reachedEvery slot on the licence is bound to a domain. Deactivate one first.
Too many failed activation attemptsTen failures in one hour. Wait up to 60 minutes.
Could not determine your Odoo instance domainweb.base.url is empty. Set it, then activate.
The requests library is requiredrequests is missing from Odoo's Python environment. Install it into the interpreter that runs Odoo.
Odoo refuses to install the moduleecosire_license_client is not in your addons path. See step 3.

Syncing

SymptomCause and fix
The connection will not validateRe-check every required field in the table above. Most failures are a mistyped secret, or credentials created for a sandbox while the module points at production (or vice-versa).
Nothing syncs even though the connection is fineThe 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-wayRead 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 valuesFix the mapping records under the module's configuration, then re-run the import.
Duplicated products or customersRun 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 versionVersion you download today
17.017.0.2.0.1
18.018.0.2.0.0
19.019.0.2.0.0

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

Support