📢 Black Friday 2025 is live! Enjoy 30% OFF our most popular Odoo solutions - applied automatically. ⚡
Why Our Connectors Use Job Queue (queue_job) – and Why It’s Safe to Use on Odoo.sh

Why Our Connectors Use Job Queue (queue_job) and Why It's Safe to Use on Odoo.sh

When integrating Odoo with external systems like Shopify, Magento 2, WooCommerce, or PrestaShop, you need a way to process large volumes of data reliably, track errors, and ensure no sync gets missed. That’s why we use the widely trusted Job Queue module (queue_job) from the Odoo Community Association (OCA) – and why you shouldn’t be concerned about using it, even on Odoo.sh.

But Isn’t queue_job Forbidden on Odoo.sh?

Odoo.sh’s FAQ mentions that the queue_job module may be “incompatible” due to potential performance degradation under specific conditions:

“Queue_job causing performance degradation (depending on the amount of workers) that can lead to the infringement of our Acceptable Use Policy.” Odoo.sh FAQ – Technical Restrictions

However, this does not mean it’s unsafe or unsupported in general. In fact:

We have many customers running our connectors on Odoo.sh with zero performance issues, even without the extension. That said, if your Odoo.sh project has a large number of workers, using queue_job_cron_jobrunner is a safe and recommended step.

Why We Use Job Queue – and Why It’s Good for You

Here are the key reasons we rely on Job Queue, and why this is a benefit – not a drawback – for your Odoo integration:

1. Reliable Syncing – Even If Something Fails

All operations (like product export, order import, stock updates) are processed in background jobs. This means:

  • If a task fails (e.g. due to API timeout), you’ll see the error

  • You can restart the failed job and retry without data loss

  • No data silently disappears

This is much safer than real-time sync, which can crash without trace.

2. Clear Error Tracking and Notifications

Each job logs:

  • Status (done, pending, failed)

  • Error messages (with full stack trace)

  • Timestamps and triggering users

Your team can:

  • Monitor syncs from the UI

  • Identify problems instantly

  • Contact support with clear details

No more hunting through logs or wondering what went wrong.

3. Scalable for Large Volumes

Have thousands of orders or products?

No problem – jobs are processed in the background without locking up your interface or timing out.

This makes our connectors ideal for:

  • High-traffic stores

  • Businesses syncing frequently

  • Odoo setups with heavy data volumes

4. No Security Risks, No External Dependencies

  • Jobs run entirely within your Odoo environment

  • No data is sent to third-party servers

  • You stay in full control of processing logic

5. Odoo-Native and OCA-Backed

We don’t use external services or strange cron hacks.

The job queue system:

  • Is open-source and actively maintained by the OCA

  • Follows Odoo’s best practices

  • Is trusted by hundreds of other professional-grade modules

We use it because it’s the most stable and professional approach available.

When to Use queue_job_cron_jobrunner on Odoo.sh?

If you’re running our connectors on Odoo.sh and have a high number of workers, or if you’re concerned about compatibility – install Queue Job Cron Jobrunner (queue_job_cron_jobrunner)

It ensures jobs are executed via crons (scheduled actions) – a fully compatible and safe method on Odoo.sh.

Our Own Queue Job Fork Starting from Odoo 19.0

To provide even better performance and full control, starting from Odoo 19.0, our connectors use a custom fork of the Job Queue module.

Why we made this change:

  • To optimize compatibility with Odoo.sh

  • To fix edge cases, like the issue where the same job could be executed multiple times by different workers

  • To introduce improvements tailored to real-world e-commerce scenarios

This fork ensures:

  • Full backward compatibility with standard queue_job behavior

  • Ongoing updates and enhancements as Odoo evolves

  • Seamless integration for our customers – no manual maintenance required

You get the power of job-based architecture, with better stability and fewer surprises.

Still Unsure?

Many of our customers (including those on Odoo.sh) use our e-commerce connectors with job queue support without any issues. If you have any doubts, we’re happy to:

  • Review your setup

  • Recommend the right configuration

  • Help you stay compliant with Odoo.sh policies

Contact our support team – we’re here to help.

Related Posts