Smart Wholesaler Feed Sync

What the module does

MPR Feed Sync is a back-office feed synchronisation module for PrestaShop. It fetches wholesaler product feeds, normalizes records into a common product model, matches them to existing products and combinations, stores dry-run diffs, and applies catalog changes only after the configured safety gates allow the run.

The module can update stock, price, availability, category, brand/manufacturer, names, descriptions, images, combinations, attributes, and features. Each area is controlled by per-feed switches, so a feed can be limited to stock and price only or expanded to product creation and variant handling when the shop is ready.

Back-office location

After installation, use Sell > Feed Sync. The module dashboard shows the last run, match rate, active feeds, managed products, open alerts, next schedule label, recent runs, and quick links to Feeds, Mapper, Runs, and Configuration. Opening the module configuration redirects to the mapper/preview controller.

Global configuration

Open Sell > Feed Sync > Configuration to copy the token-gated cron URL and adjust runtime limits.

• Global apply enabled: master switch for apply mode. Apply still also requires a fresh dry run and confirmation token.
• Fetch timeout seconds, Fetch connect timeout seconds, and Fetch max bytes: transport limits used by feed fetching.
• Sync lock TTL seconds: lock lifetime for feed runs so overlapping runs are skipped instead of writing concurrently.
• Product create max count, Combination create max count, and Create max percent: global creation caps used by safety gates.
• Image max count, Image max bytes, Image timeout seconds, and Image connect timeout seconds: limits for image import.

Creating a feed

Open Sell > Feed Sync > Feeds and add a feed. Required fields are the feed name and feed URL/path. Choose the wholesaler, source type, adapter or mapping profile, matching priority, priority order, sync scope, category behavior, safety thresholds, schedule, and active status.

• Feed URL / path accepts HTTP(S), FTP, FTPS, SFTP, Google Sheets URL/ID, or an absolute local path inside the configured import directory.
• Source type supports url, ftp, ftps, sftp, file, and google_sheets.
• Compression can auto-detect gzip, force gzip, or disable decompression.
• Source settings JSON stores advanced options such as Google Sheets gid and range.
• FTP/FTPS/SFTP authentication fields store username/password and optional SFTP private-key path/passphrase. Blank password/passphrase fields keep the existing secret when editing.

Mapping feeds

Use Sell > Feed Sync > Mapper to probe a source, sample records, create or save mapping profiles, and preview normalized items. Canonical fields include ean, sku, supplier_id, name, price, stock, location_quantities, avail, category, brand, variant_group_key, variant_key, variant_attributes, features, combination_ean, combination_reference, combination_price_impact, combination_stock, combination_images, images, and raw attrs.

Available transforms include trim, digits_only, decimal_normalize, lower, upper, prefix, suffix, regex_replace, split, concat, default_if_empty, and map_values. Presets include Corsan XML, generic Google Shopping XML, generic Ceneo XML, generic CSV, and generic JSON.

Dry runs, apply, and rollback

Use Dry-run on the Feeds screen or run the cron endpoint with action=dryrun. A dry run fetches the feed, parses it, builds a product index, matches feed items, writes mprfeedsync_run and mprfeedsync_run_diff rows, and stores a configuration signature on the feed.

Use Apply only after reviewing the dry-run result. Apply mode requires apply enablement, a valid confirmation token, a fresh dry-run signature, currency-rate readiness, and passing safety gates. Apply writes planned rows and records applied/skipped/error status per diff row. Rollback actions are available from the Feeds and Runs screens for apply runs.

Matching and overrides

Matching uses existing module maps first when coherent, then the configured match_priority. Unique EAN and SKU/reference matches are high confidence; supplier-reference-only matches are low confidence and are blocked from writes unless policy allows them. Duplicate feed keys, ambiguous catalog candidates, ignored maps, and unsafe skipped rows are not treated as writable rows.

The Mappings controller lets admins freeze a map, unfreeze it, ignore/unignore it, manually remap it to another product ID, or set/clear a product category override. Freezing protects stock, price, availability, name, description, and images for that map.

Categories and brands

Category strategy can be default, manual, or auto_path. Product category overrides win first, active category maps win next, manual strategy relies on those maps, and auto-path can create or resolve category paths under the configured root category during apply.

Brand sync uses the brand map table. A feed brand can map to a PrestaShop manufacturer, or Create if missing can create a manufacturer from the feed brand value during apply. Product overrides can also supply a manufacturer override.

Stock locations

When sync_location_stock is enabled, feed location_quantities are written to module location ledgers and the shop stock quantity is updated from the selected aggregation strategy. Supported strategies are sum, max, primary_location, and specific_location. Stock locations can be virtual module-managed locations or linked to Advanced Stock Management warehouses.

Currency and pricing

If source_currency is set and differs from the shop currency, the module requires a configured rate provider before apply. Rate source can be manual or nbp, with optional rate margin and settings JSON. Rates are cached in mprfeedsync_currency_rate; missing or stale required rates block apply.

Dropship order forwarding

Open Sell > Feed Sync > Dropship Orders to configure order forwarding per feed. It is disabled by default. The default generic_export adapter writes an order document to disk and does not contact a supplier. To send externally, choose email_csv, email_xml, or http_post, set the trigger order status ID, and provide supplier email, endpoint URL, options JSON, or auth JSON as needed.

The module listens to actionValidateOrder and actionOrderStatusPostUpdate. When an order reaches the configured status, it resolves only lines owned by the feed, creates an idempotent queue item per order/feed pair, dispatches it, and keeps response/error data. The retry cron action processes due queued or failed forwarding records up to the configured attempt limit.

Cron endpoint

The front controller is /module/mprfeedsync/cron and requires the stored token. Supported actions are parse, sync, dryrun, apply, status, and forwarding retry aliases such as forwarding_retry. Optional parameters include id_feed, ad-hoc url, adapter_key, profile, id_mapping_profile, confirm or apply_token, limit, and scoped products.

Operational notes

• The module supports PrestaShop from 1.7.0.0 up to the installed _PS_VERSION_ according to the module constructor.
• Install creates module tables for feeds, profiles, product maps, overrides, run history, diffs, categories, brands, currency rates, locations, order forwarding, images, price rules, alerts, and locks.
• Runtime schema reconciliation and hook checks are performed before admin and cron operations when available.
• Run locks are stored in mprfeedsync_sync_lock and prevent overlapping runs for the same feed or ad-hoc URL.
• System integrity checks and module table maintenance are available from the integrity controller.