Using the CRON Functionality in the Fastbay Module (v.6.7.0 >)

The Fastbay module allows automated synchronization between PrestaShop and eBay, even when the catalog is managed through external tools such as scripts, automatic importers, or ERP software.

⚠️ If you are using PrestaShop in a standard way, there is no need to configure any cron: the module automatically synchronizes products upon saving them, thanks to PrestaShop’s native hook system.

🔧 What is Fastbay’s CRON

The CRON feature allows automatic updates to eBay via links callable by browser or scheduled on the server at regular intervals (cronjob).
Setting up a cronjob is the responsibility of the server administrator and may vary depending on the operating system and hosting control panel.

The available links are grouped into three tabs in the “Link CRON” section of the module:

ADD / CLOSE: to manage new product publications and closing listings
UPDATE: to synchronize quantities, prices, and other modifications
BY PRODUCT: selective synchronization using product ID (new in version 6.7.0)

📧 If you enter an email address in the “Email for CRON notifications” field (in the General tab), you will receive a technical report by email after each synchronization. Leave it blank to disable notifications.

➕ Adding and Closing Products

These URLs are used to:

Publish new products to eBay
Close listings for out-of-stock products

ℹ️ If using cron jobs, it is critical to correctly configure the automatic closing of products to avoid showing unavailable items on eBay.

Example links:

Add new products:
...&action=syncCron&add=1
Close products:
...&action=syncCron&close=1

🔁 Updating Products

Use the following URLs to update products already published on eBay:

🕐 Products modified in the last X minutes (new in version 6.7.0)

Allows bulk updating of products that have been modified on the shop within the last X minutes.
Modified products are detected based on the date_upd field in PrestaShop — the time value can range from 1 to 360 (6 hours).

...&action=syncCron&modifiedbyminutes=10

⛔ Maximum 500 products per execution

📆 All modified products (incremental)

...&action=syncCron&reviselastimport=1

⚠️ In PrestaShop 1.7, receiving an order does not update the date_upd field: if you use external systems, you must update this field manually.

🛑 Zero quantity products (only if OUT OF STOCK MODE is enabled)

...&action=syncCron&revisezero=1

💥 Update all products

...&action=syncCron&revise=1

🚫 Not recommended for large catalogs – Max 500 products per execution. If more than 500 are detected, the cron will fail with an error message.

🆕 Sync by Product ID (v.6.7.0)

For advanced users and integrators — This mode allows precise, targeted updates of specific products by specifying their IDs in the link.

Example:
...&action=syncCron&id_products=1,2,3

🔹 Limit: max 500 IDs per execution
🔹 ⚠️ Requires that an external system dynamically generates the list of product IDs to be updated

⚙️ Advanced Features

🧪 Test without actual synchronization

Add &dryrun=1 to any cron URL to simulate execution without sending any updates to eBay. A report email will still be generated.

🔗 Combining operations

You can combine multiple operations into a single URL, e.g.:
...&action=syncCron&add=1&close=1

⚠️ Not recommended for large product volumes – it’s best to split actions when possible.

⏱️ Performance and Limits

All cron executions are synchronous: the module sends product data and waits for a response from eBay before continuing.
On average: 2–3 seconds per product.
Fixed limit: 500 products per execution.
The module sets a maximum timeout of 3600 seconds. Some servers may ignore this value. If needed, ask your hosting provider to increase max_execution_time.

🔍 Which CRON do I need?

Depending on how you manage your product catalog in PrestaShop, you might not need to configure any cronjob at all. Check the guide below to identify the solution that best fits your case.

✅ Using PrestaShop Back Office Only

Scenario: You manage your products directly in PrestaShop (product sheets handled via back office).
Solution: No cron configuration is required.
The Fastbay module uses native save hooks to automatically sync with eBay.
✔️ Make sure that sync on save is enabled in the SYNC tab of the module.

🔁 Using systems that trigger native save hooks

Scenario: You use software that updates products via PrestaShop APIs or that triggers native product save hooks.
Solution: No cron configuration is required.
✔️ The module detects changes through hooks and updates eBay automatically. Make sure sync on save is enabled in the SYNC tab of the module.

⚙️ Using external systems that update the database directly

If you’re using tools that modify products directly in the database, you need to configure cronjobs based on the behavior of your importer:

Scenario	Recommended Solution	Example Cron URL
I update the `date_upd` field only for modified products	Use the reviselastimport cron to update only products with a more recent update date than the last sync.	`...&action=syncCron&reviselastimport=1`
My import system runs at regular intervals (e.g., every 60 minutes)	Use the modifiedbyminutes cron with an appropriate interval (from 1 to 360 minutes)	`...&action=syncCron&modifiedbyminutes=10`
My external system returns the IDs of the modified products	Use the per product ID cron, with a dynamic list of IDs generated by your system	`...&action=syncCron&id_products=123,456,789`

🛠️ Recommendations

Always test the URL manually in your browser before scheduling it on the server.
Automated cronjob configuration must be handled by a system administrator or your hosting provider.
If the cron works in the browser but fails on the server, the issue lies in the cronjob configuration, not in the module itself.

FastBay

Cron