Automate Everything: Cron Jobs, Scheduled Imports and Exports Explained

Every e-commerce operation has a version of the same routine: someone opens a supplier file every morning, reformats it, imports it, checks for errors, and does it all again tomorrow. Add an export to Shopify, a weekly price sync from the ERP, and a recurring feed push to a B2B platform, and you have a product manager whose day is already half gone before they have done any actual product work. This guide explains how to schedule product import export ecommerce automation in MicroPIM — how cron-based scheduling works, what you can automate, and how to set it up so these tasks run without anyone in the loop.

The Manual Import Trap

The manual import routine feels manageable until it suddenly is not. One delayed import means a price that is wrong for a day. One missed export means a sales channel showing out-of-stock items that are actually in the warehouse. One human error in a reformatted CSV means 300 products with corrupted descriptions pushed to a live store.

The cost of manual recurring imports is not just time. It is inconsistency.

When a human is in the loop for every data transfer, the frequency of updates is limited by that person’s availability. Supplier feeds that could refresh every hour get refreshed once a day because daily is already a burden. Channels that could stay synchronized get checked weekly because more frequent is not realistic with manual effort. The result is a catalog that is perpetually slightly out of date — not broken enough to stop the business, but degraded enough to create friction, errors, and customer service overhead.

The other problem is dependency. When the person who runs the Monday morning import goes on holiday, the import does not run. When the process lives in one person’s head as a sequence of browser tabs and spreadsheet macros, it cannot be handed off, audited, or improved.

Manual data processing is not a workflow. It is a liability. The answer is to remove the human from any task that runs on a fixed schedule and replace them with a machine that does not forget, does not make formatting errors, and does not need a day off.

For a broader look at where manual processes cost the most time in product operations, see how to save 20 hours a week managing your e-commerce products.

Why Cron Jobs Matter for E-commerce

A cron job is a time-based task scheduler. The name comes from the Unix scheduling daemon that has existed since the 1970s, but the concept is universal: define a task and define when it should run, and the system executes it automatically on schedule. No manual trigger required.

For e-commerce product data, cron-based scheduling solves three problems that manual processes cannot.

Reliability. A scheduled job runs at the same time every time, regardless of who is at their desk or what else is happening in the business. The import that runs at 3:00 AM every morning runs at 3:00 AM every morning, including bank holidays, summer Fridays, and the week of a product launch when everyone is stretched thin.

Consistency. Because the same automated process runs the same logic on every execution, the output is predictable. Field mappings do not change. Transformation rules do not change. The channel-specific formatting that takes a human 20 minutes to apply manually is applied in seconds, identically, every time.

Scalability. A manual import workflow that takes 45 minutes for 5,000 products takes 90 minutes for 10,000. An automated workflow that takes 45 minutes for 5,000 products takes 46 minutes for 10,000. The automation scales with the catalog; the human operator does not need to.

The practical effect is that your data stays current without anyone maintaining that currency manually. Inventory levels reflect the latest warehouse data. Prices reflect the latest supplier rates. Channel listings reflect the current product master. The gap between what your data says and what is actually true shrinks from hours or days to the length of one cron interval.

Understanding Automation in MicroPIM

MicroPIM’s automation engine supports three categories of schedulable tasks. Each maps to a different part of the product data lifecycle.

[SCREENSHOT: MicroPIM automation dashboard showing list of active scheduled tasks with next run times]

Imports

A scheduled import pulls data from an external source on a recurring basis and brings it into MicroPIM. The source can be a URL pointing to a supplier’s product feed, a file location, or an API endpoint. MicroPIM fetches the data, applies the configured field mapping and transformation rules, and updates or creates products in your catalog automatically.

Scheduled imports are the right tool for any data source that changes on a regular basis: daily supplier price lists, hourly inventory feeds, weekly catalog updates from a distributor.

Product Updates

A scheduled product update is an automation that modifies existing products in your MicroPIM catalog on a defined schedule without requiring an external data source. This covers recurring internal operations: applying a markup rule every Monday before the business week begins, resetting a promotional price field after a campaign ends, flagging products for review based on staleness criteria.

Product update automations give you workflow orchestration within MicroPIM itself. They are the mechanism for business logic that needs to run on a schedule rather than being triggered manually.

Exports

A scheduled export pushes product data from MicroPIM to an external destination on a recurring basis. The destination can be a connected e-commerce platform — Shopify, WooCommerce, Magento — or a file output in CSV or XML format for any downstream system that ingests product feeds.

Scheduled exports are the mechanism for multi-channel synchronization. Rather than manually exporting and uploading to each channel separately, you configure the export once with the channel-specific field mapping, set a schedule, and MicroPIM handles the distribution from that point forward.

Feed Discovery

MicroPIM also includes a feed discovery feature that can automatically detect and suggest importable data sources based on a domain or URL pattern. When you connect a new supplier, feed discovery analyzes the available endpoints and identifies product feeds that MicroPIM can import. This removes the detective work of figuring out what format a supplier’s data is in and where to point the import configuration.

Feed discovery is particularly useful when onboarding multiple suppliers or when a supplier’s feed URL changes — MicroPIM can detect the new source and update the automation configuration without manual intervention.

For a complete overview of how imports work in MicroPIM, see the guide to product import methods.

Creating Your First Scheduled Import

Setting up a scheduled import in MicroPIM takes less than five minutes once you have your source data and field mapping defined. Here is the step-by-step process.

[SCREENSHOT: Create new automation dialog with cron expression builder and task type selector]

Step 1: Navigate to Automations. From the MicroPIM dashboard, open the Automations section. This is where all scheduled tasks are listed, created, and managed.

Step 2: Create a new automation. Click “New Automation” and select “Import” as the task type.

Step 3: Configure the source. Enter the URL or file path for your data source. If you have already connected this source previously, you can select it from your saved connections. If the source is new, MicroPIM will attempt to detect the feed format automatically. You can also manually specify the format — CSV, XML, JSON — and the field delimiter if applicable.

Step 4: Map the fields. Assign the source fields to the corresponding MicroPIM product fields. If you have previously imported from this source, the existing mapping will be pre-loaded. Set any transformation rules that apply — markup calculations, field concatenations, conditional value replacements.

Step 5: Set the cron schedule. Enter the cron expression that defines when the import should run. MicroPIM provides a visual builder that translates plain-language schedule descriptions into cron syntax, but you can also enter expressions directly.

Common cron expressions for product import schedules:

Step 6: Save and activate. Save the automation. MicroPIM will display the next scheduled execution time immediately. The automation is active and will run at the next occurrence of the defined schedule without any further action required.

You can also trigger an immediate run at any time using the “Run Now” action — useful for testing a new configuration before its first scheduled execution.

Setting Export Schedules

Scheduled exports follow the same configuration pattern as imports, with the destination replacing the source. The key decision is how frequently your channels need to receive updated data.

Daily exports are the right choice for most multi-channel operations. A nightly export — typically scheduled between midnight and 6:00 AM when platform traffic is low — pushes the day’s product changes to every connected channel before the business day begins. Prices updated in the afternoon are live on every channel by the next morning.

Weekly exports are appropriate for data that changes slowly, such as product descriptions, category assignments, or SEO metadata. If the content refresh cycle in your business is weekly, scheduling a weekly export aligns the automation with the actual cadence of change.

Monthly exports serve archive or reporting purposes — generating a full catalog snapshot at the end of each month, pushing a complete catalog to a print or offline channel that refreshes on a monthly basis, or feeding a business intelligence system that ingests product data on a scheduled cycle.

For channels like Shopify that have API rate limits, scheduling exports during off-peak hours and spreading large catalog pushes across the available API capacity is important. MicroPIM handles the rate limiting logic internally, but the schedule should account for catalog size and available processing time. For detailed instructions on the Shopify export workflow, see how to connect MicroPIM to Shopify.

You can maintain separate export automations for each connected channel, each on its own schedule. A Shopify store might receive daily exports while a B2B platform with slower inventory turnover receives weekly exports. The schedules are independent and managed from the same Automations dashboard.

Monitoring Automation

Scheduling an automation is only part of the workflow. Knowing whether it ran successfully — and being able to act quickly when it did not — is equally important for a reliable product data operation.

[SCREENSHOT: Run history log showing successful and failed executions with timestamps]

Run History and Status Logs

Every automation in MicroPIM maintains a full run history. For each execution, the log records the start time, end time, execution duration, number of records processed, number of records created or updated, and the final status — success, partial success, or failure.

For failed or partially failed runs, the log includes the specific error messages that caused the failure. Common entries include source file not found, field mapping validation errors, destination API authentication failures, and records that were skipped due to data quality issues. Error logs are specific enough to identify the exact row or field that caused the problem, which makes troubleshooting fast.

The run history gives you a complete audit trail for every automated data transfer. If a downstream system reports unexpected product data, you can trace exactly which import run produced that data, what the input was, and what transformation was applied.

Toggling Automations On and Off

Automations can be enabled and disabled individually without deleting them. This is the correct approach for seasonal tasks, maintenance windows, or supplier feeds that are temporarily paused. Disabling an automation preserves the entire configuration — schedule, field mapping, transformation rules — so that re-enabling it requires a single click rather than rebuilding the setup from scratch.

Avoid deleting automations for temporary pauses. Deletion is permanent; the configuration is not recoverable. Toggle the automation off, add a note in the description field if helpful, and toggle it back on when the task should resume.

The “Run Now” Action

Every automation has a “Run Now” action that triggers an immediate execution outside the scheduled cadence. Use this when:

• Testing a newly configured automation before its first scheduled run
• Running an out-of-cycle import when a supplier publishes an unscheduled price update
• Re-running a failed automation after fixing the underlying error
• Pushing an urgent catalog update to channels before the next scheduled export

“Run Now” executions appear in the run history alongside scheduled executions. The log entry records them as manual runs rather than scheduled runs, which maintains the clarity of the audit trail.

Next Scheduled Execution

The Automations dashboard displays the next scheduled execution time for every active automation. This is useful for planning and for confirming that a schedule is configured correctly. If a cron expression produces an unexpected next execution time — for example, a schedule intended to run weekly is showing a next run in four days rather than seven — you can catch the error before it causes an inconsistency.

Advanced: Combining Automation with Feed Discovery

For operations managing a large number of supplier feeds, the combination of scheduled imports and feed discovery reduces the ongoing maintenance work of keeping automation configurations current.

The typical problem with multiple supplier feeds is that suppliers change their feed URLs, file formats, and field structures without consistent advance notice. A scheduled import that ran successfully for months begins failing because the supplier moved their feed to a new CDN path or added a new required field. Without feed discovery, catching and fixing that change requires a support ticket, manual investigation, and manual reconfiguration.

With feed discovery enabled for a supplier connection, MicroPIM periodically checks the configured source domain for changes to feed availability and format. When a feed URL changes, MicroPIM can detect the new location and update the import automation without manual intervention. When a new product feed becomes available from a supplier — a new brand, a new product line — feed discovery surfaces it as an available import source so that you can onboard it with a few clicks rather than a full configuration exercise.

Feed discovery is particularly effective for distributors and multi-brand suppliers who manage dozens of separate feed files. Rather than configuring and monitoring each feed individually, feed discovery provides a centralized view of all available import sources from that supplier and flags changes automatically.

This combination — scheduled imports driving regular data updates, feed discovery maintaining those imports as sources evolve — is the foundation of event-driven product management at scale. The automation adapts to changes in the data environment rather than requiring human intervention every time something in the supply chain shifts.

Troubleshooting Failed Jobs

Automated imports and exports fail for a predictable set of reasons. Most failures are fast to diagnose and fix if you know where to look.

Source not reachable. The most common import failure is a source URL that is temporarily or permanently unavailable — a server timeout, an expired authentication token, or a URL that has changed. Check the error log for the specific HTTP response code. A 404 means the URL no longer exists and the configuration needs to be updated. A 401 or 403 means an authentication credential has expired or changed. A 503 means the source server was temporarily unavailable, and re-running the automation with “Run Now” once the server recovers will resolve it.

Field mapping validation failure. If a supplier changes their feed format — adding a new required column, renaming an existing one, or changing the delimiter — the field mapping in MicroPIM will no longer match the source data structure. The error log will identify which field failed validation. Open the import configuration, update the field mapping to match the new source structure, and re-run.

Data quality errors causing partial failures. An import can complete partially, processing most records successfully while skipping others due to data quality issues — missing required fields, values outside acceptable ranges, duplicate SKU conflicts. Partial success runs appear in the run history with a count of skipped records. The error log details which records were skipped and why. Depending on the cause, the fix may be in the source data (contacting the supplier to correct their feed) or in the MicroPIM configuration (adjusting validation rules or deduplication settings).

Export authentication failure. Scheduled exports to connected platforms fail when the platform API credentials stored in MicroPIM expire or are revoked. Shopify, WooCommerce, and Magento all use access tokens that can be manually revoked from the platform’s admin. If an export begins failing with an authentication error after previously working, check that the API token or app credentials in MicroPIM’s connection settings are still valid in the destination platform. Regenerate and update the credentials if needed.

Timeout on large catalogs. Exports of very large catalogs can time out if the processing window is shorter than the time required to complete the operation. If a previously successful export begins timing out after catalog growth, review the export schedule — running large exports during low-traffic overnight hours gives more processing time. MicroPIM also supports paginated exports for large catalogs, which split the operation into sequential batches rather than a single transaction.

For questions about importing from a specific platform or supplier format, the getting started guide covers the initial setup and field mapping process in detail.

Manual recurring tasks are a choice, not a requirement. Every import that runs on a fixed schedule, every export that pushes the same data to the same destinations, every update that applies the same rules every Monday morning — all of these are candidates for automation. Setting them up in MicroPIM takes minutes. After that, they run without involvement, without errors introduced by reformatting, and without dependency on any individual’s availability.

The automation dashboard gives you full visibility into every scheduled job, its run history, and its next execution. When something fails, the error log tells you exactly what went wrong and where to fix it. When something needs to run outside the schedule, “Run Now” executes it immediately.

Ready to replace manual imports with scheduled automation? Start your free 14-day trial at app.micropim.net/register — no credit card required. Your first scheduled import can be live in under ten minutes.

Need help configuring a specific supplier feed or export destination? Contact our team and we will walk through the setup with you.