Cron

Everything the module does on its own — pushing your catalog, fetching your orders, declaring your shipments, delivering your invoices — is driven from this tab. Each task has its own URL, and you decide how often each one runs.

Nothing runs by itself: a URL only does something when something calls it. That something is a scheduled task on your server, or a free online service if your hosting doesn't offer one.

Keep your URLs private

Every URL carries a token that authenticates the request. Anyone holding it can trigger the task. Don't publish these URLs, and don't paste them in a public ticket or forum.

How it works

Each panel gives you two things: the URL to call, with a copy button, and a crontab example showing a sensible schedule for that task.

Above each URL, a badge tells you which account the task belongs to and whether it is Active. A cron URL always works for one account — the account number is in the URL itself.

The general shape is always the same:

https://your-shop.com/module/octopiasyncs/cron?token=…&task=…&account=…

Copy the URL, paste it into your scheduler, done.

If your hosting has no cron

Some shared hosting plans don't let you schedule tasks. That doesn't stop you: an online service can call your URLs on schedule, from the outside.

cron-job.org is free, reliable, and the module's URLs are designed to work with it — a plain GET request, no authentication beyond the token, no payload.

Create an account there, add one job per URL, and set the interval each panel recommends.

One job per URL

Don't try to chain several tasks in one job. Each URL does one thing, and giving each its own schedule is what lets you run the light tasks often and the heavy ones rarely.

Products

Pushes every product created or modified in the last 24 hours to Octopia.

It covers all your mapped categories, active products only, with no filter on the Octopia mode. Because it only looks at the last 24 hours, it's meant for a daily schedule — the crontab example runs it at 3 in the morning.

Offers (Full)

Pushes every valid active offer in Full mode to the sales channel you select above the URL.

Unlike the products cron, there is no date filter: it sends everything, every time. That makes it thorough but heavy, which is why the example schedules it once a day.

The Sales channel selector changes the URL — pick the channel, then copy. One job per channel if you sell on several.

Offers (Stock & Price)

Pushes only stock and price updates — nothing else about the product changes.

It's far lighter than Full mode, which is why the example runs it hourly. In practice this is the cron that keeps your marketplace listings in step with your shop during the day, while the Full one rebuilds everything overnight.

Cdiscount only

Stock & Price is a Cdiscount (CDISFR) mode by Octopia's own design. The other channels only accept Full offers.

Orders import

Imports the Octopia orders created in the last 7 days that match the statuses you tick above the URL — typically Accepted and InPreparation.

Orders already imported are skipped, so running it often costs nothing. The recommendation is every 15 to 30 minutes: this is the task that decides how quickly a new order lands in your back office.

Ticking a status changes the URL — set your statuses first, then copy.

Shipments

Declares to Octopia the shipment of every order that reached the Shipped status but hasn't been declared yet.

This one is a safety net as much as an automation. It catches the status changes made by third-party modules, scripts or imports — anything that doesn't go through the order page — and it retries the shipments that were postponed, typically for a missing tracking number.

Recommended schedule: every 30 minutes.

The status is fixed

Shipments are declared for orders reaching PrestaShop's own Shipped status. That status isn't configurable here, because it's the one PrestaShop itself sets when a shipment is recorded.

Invoices

Picks up the invoice of every order currently at the status you select, then delivers the ones not yet delivered — attached to the order on Cdiscount, sent in a discussion elsewhere.

What it picks up depends on the source you chose in E-Invoicing: created in Abby, or issued by PrestaShop. With the source set to None, this cron does nothing at all.

An invoice whose discussion reason isn't available yet is simply retried on the next run. Recommended schedule: hourly.

Cron report e-mail

Enter an address here to receive a report of what a cron did — including when it failed.

The report isn't sent for every task: add &report=1 at the end of a cron URL and only that one will report. This way you can watch the tasks that matter to you without filling your inbox with the routine ones.

Where to start

Put the flag on orders import and shipments first. Those two are the ones a merchant notices immediately when they stop working.

Multi-account

Every URL on this tab belongs to the active account — the account number is part of the URL. With several accounts on one shop, you need one job per task and per account.

Switch account and the tab reloads with that account's own URLs. The badge above each panel reminds you which account you're looking at, so a URL copied from the wrong account is easy to spot.

Don't reuse a URL across accounts

Changing the account number by hand in a URL won't work: the token is tied to the account. Always copy the URL from the account it belongs to.