Supplier synchronization connects three different clocks: when the supplier creates a file, when OpenCart imports it and when customers place orders. A job can run successfully every hour and still publish old stock if the source file has not changed. Start by defining what a trustworthy update looks like.
Import Export PRO supports supplier-file mapping and saved import workflows. Scheduled execution is available through the relevant CRON functionality; confirm the requirements and available component for your installed package before configuring production schedules.
Define who owns each field
Create a simple ownership sheet before connecting a supplier. Stock quantity, purchase cost, selling price, product status and product description should not automatically share the same update policy. A supplier’s recommended retail price may be useful reference data without being the price you want to charge.
| Field | Example policy | Check before publishing |
|---|---|---|
| Supplier stock | Use the latest validated availability | File timestamp and quantity format |
| Selling price | Calculate with the store’s agreed rule | Currency, tax basis and rounding |
| Description | Keep the store’s edited copy | Exclude it from the routine profile |
| Product status | Change only under an explicit rule | Missing row versus confirmed discontinuation |
For multiple suppliers, decide whether stock is added together, taken from a preferred source or capped by a fulfillment rule. Do not add overlapping warehouse quantities unless you know they represent different physical stock.
Validate the source before the importer runs
A download returning HTTP 200 can contain an error page, an empty file or yesterday’s data. Check the expected file type, required column headings, approximate row count and freshness before accepting it. Use tolerances appropriate to your catalog: a sudden drop from thousands of rows to a handful should require investigation.
Protect source credentials and scheduled-job URLs. Keep secrets out of spreadsheets, public repositories and screenshots. Download files to a controlled location and avoid exposing customer or supplier data through publicly accessible import folders. These are operational controls around the import process, not features to assume from a successful download.
Choose a schedule that can finish
Measure a representative import before choosing its frequency. If processing can take twenty minutes, a job every five minutes creates overlap unless a lock prevents concurrent runs. Include download time, validation, import work and cache or feed refreshes in that measurement.
- Fetch the new supplier file to a temporary location.
- Validate its structure and timestamp.
- Acquire an execution lock for that supplier/profile.
- Run the approved import and retain its result.
- Reconcile a sample of changes, then refresh dependent outputs if needed.
- Release the lock and alert the responsible person on failure.
This sequence describes a scheduling wrapper to implement around your chosen workflow. Check which locking, reporting and notification facilities your actual environment already provides; do not assume the extension supplies every part of that wrapper.
Handle zero stock and missing rows differently
A row with quantity zero is explicit information. A missing row may mean the supplier discontinued a product, filtered the export or had a broken job. Treat these cases separately. Keep a record of the last successful observation so you can investigate changes without guessing what the previous file contained.
If a file is stale or invalid, decide in advance whether to retain the last known stock, temporarily suppress affected items or request manual review. The right choice depends on your fulfillment risk. Document it with the team that handles customer orders, especially for products that can sell out quickly.
Reconcile prices and stock after each change
Use a small reconciliation report: records read, matched, created, skipped and rejected; the largest price changes; and the number of items moving to or from zero stock. Review both unexpected spikes and unexpectedly quiet runs. A report showing no changes for days can be a sign of a frozen source.
Test updates against products with options as well as simple products. The parent product quantity may not represent the stock of each size and color. See our variant-stock guide for the distinction, and our CSV import workflow for repeatability tests.
Keep a rollback path and a named owner
Store the last validated source and a recoverable pre-change export for as long as your operational process requires. Test restoring a small selection before relying on a rollback during a busy sales period. Assign a person to investigate failed imports and source-format changes. A reliable sync is a maintained agreement between systems and people, not simply a scheduled command.