The problem

Background work is easy to lose track of.

The syncs, imports and reports that keep a commerce operation running tend to grow one script and one scheduled task at a time.

  1. Scattered across servers

    Each integration runs somewhere different, on its own schedule, and only the person who wrote it knows where.

  2. “Did it run?”

    Without a record of each run, nobody can say whether last night’s import finished, failed or never started.

  3. Manual steps, manual errors

    Exports, re-keying and one-off mappings repeated every week, each one a chance to get the data wrong.

How it works

Define it once, then let it run.

  1. Define the job

    A coded job for developers, or a no/low-code workflow for the rest of the team, with its settings in one place.

  2. Schedule it

    At a time of day, a few minutes past every hour, or manually, on demand.

  3. Every run recorded

    The outcome, when it started and finished, how long it took, and a summary of what it did.

  4. Watch and act

    See successes, warnings and failures at a glance, run any job now, and report each run to Service Monitor.

Overview

What ran, what’s running, and what’s next.

The overview counts the runs that succeeded, warned and failed, with the success rate for the last 30 days, then shows recent activity, anything queued or running now, and every job with its schedule, next run and last run.

  • Warnings kept separate from failures, so a run that finished with problems doesn’t pass as a clean success.
  • Run now starts any job on demand, outside its schedule.
The Jobs page: 27 succeeded, 0 warnings, 0 failed and a 100% success rate over 30 days, recent Channel IQ ecommerce sales and website analytics runs, nothing running now, and all jobs with schedules such as At 07:00 AM, At 5 minutes past the hour and Manual, with next run, last run and Run now
Hourly Channel IQ refreshes, a daily catalog audit and on-demand jobs.
History

Every run, and what it did.

Job History lists every run with its outcome, when it finished, how long it took and a plain summary, such as “Updated 7 order(s) modified since 20:05 UTC”. Filter by outcome, job and period, or search by job name or run number.

  • A page for each run with its start, finish, duration and every message it logged.
  • Run again from the run itself, or open all runs of that job.
Job History filtered to the last 7 days: successful Channel IQ ecommerce sales and website analytics runs, each with when it finished, how long it took, a summary such as Updated 7 orders modified since 20:05 UTC, and its run number
The last 7 days of runs, each with a summary of what it did.
Run #60302 of the Channel IQ website analytics job: success, started and finished 2026-10-29 15:15 UTC, took 519 ms, with one message saying it refreshed 7 days of data, and buttons for History, All runs of this job and Run again
One run: when, how long, and what it reported.
Heartbeats

Know when a job doesn’t run.

Add one line to a job’s settings and every run reports to Service Monitor; a failed run reports a failure. If a job stops reporting in on time, Service Monitor opens an incident and alerts you.

  • Catches the silent failures: a job that never started is noticed, not just one that errored.
  • One alert when the problem is confirmed, and one when it recovers.
The Reporting heartbeats panel in Service Monitor: endpoint, header, active key, curl and PowerShell examples, and the one line to add to a Commergenix Job Engine job definition so every run reports automatically
The one line that connects a job to Service Monitor.
What it runs

The work behind every Commergenix module, and your own.

Every Commergenix module shares one job engine, so the work they do on a schedule shows up in the same place as the jobs you add.

Product data syncs

Move and convert data between ERP, PIM and ecommerce platforms, such as an ERP to PIM sync or a customer account sync.

Pricing updates

Such as Price Director’s daily job that reads metal prices and adds them to the price history.

Sales and analytics refreshes

Channel IQ’s hourly refreshes of storefront orders and website analytics.

Catalog audits

Data Auditor runs your catalog rules against every product in your PIM on a schedule.

Reports and cleanup

Recurring reporting and data cleanup that would otherwise be exported and fixed by hand.

Reusable mappings

Define a complex data mapping once and use it across jobs, instead of rebuilding it for each one.

Connected systems

Jobs for the platforms you already run.

Job Engine moves data between the ERPs, PIMs and ecommerce platforms Layer One works with every day. Running something not listed here? Tell us what you use.

  • Optimizely
  • Shopify
  • nopCommerce
  • Sitecore
  • inriver
  • Akeneo
  • Epicor
  • Infor
  • Affiliated Distributors
Built to be trusted

Background work you can see.

A record of every run

Outcome, start, finish, duration and every message, kept for each run of each job.

Warnings aren’t hidden

Runs that finished with problems are counted as warnings, apart from successes and failures.

Failures reported out

Connect a job to Service Monitor and a failed or missing run becomes an incident and an alert.

Your jobs only

Each company sees its own scheduled and on-demand jobs and their history.

Who it’s for

For teams whose systems need to stay in sync.

Integration owners

Every sync and import in one list, with a record of each run and a heartbeat on the ones that matter.

Developers

Write coded jobs once and let Job Engine handle the schedule, the run history and the reporting.

Ecommerce and operations teams

Create and run no/low-code workflows, and check that last night’s work finished without asking IT.

FAQ

Common questions

What kinds of jobs does it run?

Data movement and transformation between ERPs, PIMs, ecommerce platforms and reporting tools, plus the scheduled work of the other Commergenix modules, such as Channel IQ refreshes, Data Auditor’s catalog rules and Price Director’s daily metal prices.

Do I need a developer to create a job?

No. Developers can write coded jobs, and non-technical users can create, manage and run no/low-code workflows.

How are jobs scheduled?

At a time of day, at a set number of minutes past every hour, or manually. Any job can also be started with Run now.

How do I find out a job failed?

The overview counts failures and warnings, and Job History shows each run’s outcome and messages. Connect the job to Service Monitor and a failed or missing run alerts you.

Do the other Commergenix modules use it?

Yes. Every Commergenix module shares one job engine, so their scheduled work appears alongside your own jobs.

Let’s talk

Bring your syncs, imports and reports into one place.

Tell us which jobs your team runs today, where they run and which ones are still done by hand. We’ll show you how they’d look in Job Engine and tell you honestly where it doesn’t fit.