Smart Wholesaler Feed Sync: setup and help

Install the ZIP in your shop's module manager, then click Configure. The module adds Feed Sync under the selling menu. Its dashboard shows the last run, match rate, active feeds, managed products, unread alerts, and recent runs.

Use Feeds for feed configuration and execution, Dry run for the mapping studio and parse-only checks, Workbench for item review and overrides, and Runs for execution details and rollback. Mappings, Category Mapping, Brand Mapping, and Stock Locations manage the corresponding relationships.

Wholesalers is a read-only list. Installation adds a shared Corsan wholesaler. You can select a wholesaler in a feed or leave it unassigned; this screen does not add or edit wholesalers.

Choose one shop before working in multistore. Feed configuration, product overrides, run details, and credentials belong to the selected shop. The runtime form is also shop-specific, except for the retention settings and Ignore Omnibus price history during rollback, which apply across the module.

The server needs readable source files and writable temporary storage. XML parsing needs XMLReader; XLSX also needs ZipArchive. FTP, FTPS, and SFTP need PHP cURL with support for the selected protocol. Content template HTML processing needs DOMDocument.

Open Feed Sync > Settings > Configuration.

In Default pricing policy, use Add step to build an ordered formula. Operations are Multiply by, Add, Subtract, Divide by, and Add percent. The default is an empty formula, so the normalized wholesaler price passes through unchanged. For example, multiplying 100 by 1.2 and adding 5 produces 125 before rounding.

Round final price defaults to No rounding. The other choices round to 0.01, 0.10, or 1.00. Click Save default pricing policy. Removing every step and rounding clears the default policy. A policy using options this editor cannot represent is displayed without an editable save form.

In Default image and gone-from-feed policies, every control initially inherits its system default:

Click Save default image and gone policies. Feed, category, and product policies can override individual fields. Inherit keeps the broader decision in control; it does not turn the feature off. Run a new dry-run after saving policies.

The Runtime settings form on Settings > Configuration contains these controls. Click Save after editing.

Retention settings accept whole numbers from 0 to 1000000. Pinned runs, unfinished runs, rollback journals, the latest feed run, reviewed details, the latest dry-run, and maintenance owners receive protection from cleanup. Busy feeds are skipped by retention.

Use Regenerate token to replace the selected shop's cron token, then update the scheduler with the new URL. The old cron URL stops authorizing requests. The apply confirmation credential is separate from the cron token.

Open Feeds > Add new feed, or use Edit on an existing row. Save changes with Save.

Use Test connection to download the source and see its byte count and initial content. This does not apply catalog changes.

For local files, place the file inside the shop's var/modules/mprfeedsync/import/ directory and enter its absolute path. Paths outside the configured import directory, including symlinks resolving outside it, are rejected.

Google Sheets must expose a public CSV export. Private spreadsheets requiring an interactive Google login are not supported by this source type.

Use Mapper on a saved feed or open Dry run > Feed mapping studio. The studio reads a sample and stores a reusable mapping profile.

1. Enter Feed URL. The studio does not preload the saved feed URL or include its feed ID in sample and preview requests. A source needing stored credentials can therefore fail in the studio even when the feed's Test connection succeeds.
2. Choose Format, initially auto, or select XML, CSV, JSON, XLSX, or Google Sheets. Optionally select Preset. Supplied presets cover Corsan XML, Google Shopping XML, Ceneo XML, and generic CSV and JSON.
3. For XML, set Record element to the repeated item element, such as o or item, or leave it empty for detection. For CSV, Delimiter can be left empty for detection. For JSON, Array pointer selects the product array, such as products.
4. For XLSX, Sheet selects a sheet by name or number and Header row selects the header row. Blank uses the reader's automatic choices. The initial Fetch sample request does not forward these two overrides in this release; re-enter them after sampling, then use Preview mapped products and save the profile to use them.
5. Click Fetch sample, then review Source fields and their examples. The studio initially leaves fields unmapped and suggests mappings after sampling.
6. Select the source for each field under Map to product fields, then click Preview mapped products.
7. Click Save profile and supply a name. When the studio is opened for a feed, the saved profile is linked to that feed. Otherwise select it later in the feed's Mapping profile field.

Map EAN, SKU / Manufacturer code, and Supplier ID carefully. EAN and SKU are the main catalog identifiers; supplier IDs can change. Duplicate, ambiguous, ignored, and low-confidence rows are not ordinary writable matches.

The other mapping targets include Name, Price, Stock, Location quantities, Availability, Category, Brand, Images, Features, and Raw attributes. Raw attributes can supply content template values. Location quantities can contain pairs such as PL=5;DE=2.

Variant mapping targets include Variant group key, Variant key, Variant attributes, Combination EAN, Combination reference, Combination price impact, Combination stock, and Combination images. Mapping these fields supplies variant data; it does not enable combination or attribute synchronization. This release's feed editor has no controls for those two permissions, which default to off.

For ordinary fields, transforms run in their displayed order. trim removes surrounding whitespace, digits_only removes non-digits, decimal_normalize converts a price to a decimal value, and lower and upper change case. map_values uses the field's value map. In the availability value map, choose available (1) or unavailable (7) for each supplier value.

The studio also offers prefix, suffix, regex_replace, split, concat, and default_if_empty, with an arguments box. This release does not translate that box into the parameters expected by the transform processor. Do not rely on entered arguments to produce those transformations; inspect the mapped preview before saving.

The sample preview shows up to eight mapped records and a sample match estimate. Run a full Dry-run from Feeds before applying.

The mapper supports Length, Width, Height, Depth, Absolute weight, Volume, Area, package dimensions, package weight and volume, unit length, area, weight, volume, and count.

For each mapped measurement, choose its value field and either enter Source unit, select Unit source field, or use a value containing its unit, such as 25 cm. Unit fields initially use Unit in the value, and no fixed source unit is supplied. A bare number needs an explicit unit. Conflicting or invalid units cause the offer to be refused.

Measurement fields do not use ordinary price or text transforms. Map source length to Height only when it actually represents height. The preview shows source and effective values, including units and inheritance. Missing measurements preserve previously stored values; they do not clear them.

Imported width, height, depth, and weight can also update the corresponding native product values in shop units. Absolute weight means the full physical weight of the variant; the module calculates the native combination weight impact relative to its parent. Other measurements remain in the shared measurement storage.

Review measurements in the mapper, Workbench previews, and the native product page. The product's measurements lock prevents feed changes. Apply requires the reviewed measurement plan to remain current. Conflicts between shops or changes made since the dry-run require another review.

Open the feed's Sync tab.

The six New products only controls also offer Off, Always, and Inherit. Off prevents the field's feed synchronization; Always permits creation and later updates. Inherit uses the broader policy. With no broader override, system permissions allow price, stock, brand, and availability, and block name, description, images, and categories. Product field locks can still veto writes.

Available items with positive stock can update quantity and remain orderable without changing activation or visibility. Available items with zero stock remain orderable, while the shop's out-of-stock behavior applies unless overridden. Unavailable items plan zero stock; ordering is disabled only when the relevant policy is enabled. Unknown availability leaves product state unchanged. Stock and availability permissions can independently preserve their respective fields.

For mapped combinations, one available sibling can keep the parent product orderable when another combination is unavailable.

Use Content templates and manufacturer exclusions in the feed's Sync tab, or open the same panel from Workbench.

For each language and Name, Short description, or Description, enable Use this template and enter the template. Templates are initially absent. Unchecked language templates inherit the shop default language's template. Feed sync permissions and product value locks still determine whether rendered content is written.

Available tokens are:

{wholesaler_name}
{wholesaler_description}
{wholesaler_short_description}
{wholesaler_reference}
{wholesaler_brand}

Enter additional source field names in Selected feed fields (one per line) to make tokens such as {feed:material} available. Use Insert token to insert a token. {{ and }} produce literal braces. Tokens read mapped supplier input; they do not execute PHP or Smarty. Names become plain text and description HTML is sanitized.

Use Preview content to inspect the source and rendered result. In the standalone Workbench panel, click Save import settings. In the feed form, save the feed.

Excluded manufacturers and Excluded supplier brands initially have no selections. Choose shop manufacturers to exclude, or enter one supplier brand per line. Supplier-brand matching ignores case and repeated whitespace. Excluded items and their variant groups remain unchanged and are also protected from gone-from-feed processing.

Automatic maintenance during apply, in the feed's Safety tab and standalone import panel, defaults to No. When enabled, the selected shop closes during catalog writes and the module restores its previous maintenance setting afterward. Parse-only and dry-run operations keep it open. The panel displays Maintenance ownership and recovery status, active run IDs, and the last transition.

Open the feed's Pricing tab. All pricing policies initially contain no rules. The calculation starts with the supplier price, converts currency if configured, and normalizes gross prices when requested by Policy JSON. The resulting base is tax-excluded.

The calculation follows shop default, feed, category, then product policies. Use the formula editor's ordered arithmetic steps. Continue from the price so far applies the formula to the previous stage's result. Restart from the original base discards earlier stage results and starts again from the normalized wholesaler price.

Rounding in a rule applies at that rule's stage. Remove a rule or clear its formula to return to inheritance where supported by the editor. Save the feed and run a new Dry-run.

In Workbench, expand an existing product to edit Product pricing policy. It defaults to Use inherited pricing. Select Apply a product formula, then choose on top of the price so far or starting over from the wholesaler price, enter steps, and click Save policy. A fixed custom price with its value lock enabled takes precedence over the formula chain. Fixed prices are absolute tax-excluded catalog prices. A hard field freeze still blocks changes.

Use Explain price to inspect the source price, conversion, formulas, and final result. Pricing rules do not override Sync price by themselves: with New products only, an existing product keeps its price unless a permitted product override applies.

Open the feed's Gone-from-feed tab. These rules concern previously mapped products absent from subsequent runs, rather than records whose availability value says unavailable.

Report only leaves the catalog unchanged. Unavailable turns ordering off. Unavailable and zero stock also sets quantity to zero. Disable deactivates the product and turns ordering off.

Gone changes are planned in dry-run and written during apply. When an item reappears, the module plans restoration of the state it recorded when marking the item gone. Review the restoration rows before applying.

For narrower rules, use Category image and gone policies in the feed's Sync tab. Click Add category policy, choose Category, and set Image strategy or the gone fields: Enabled, Action, After runs, After days, Notice, Hide price, Text mode, and Notice text. They initially inherit, with blank thresholds and text. Precedence starts at 0; a higher value ranks ahead of a lower value.

Product-specific image and gone policies are available on expanded Workbench rows. Their controls initially inherit. An explicit No or empty custom text overrides a broader value just as an explicit Yes does. Product policy takes precedence over category, feed, and shop defaults.

In Product image and gone-from-feed policy, choose Image strategy and click Save image policy. For disappearance handling, set Policy, Action, After runs, After days, Notice, Price, Text mode, and Notice text, then click Save gone policy. Blank thresholds inherit; custom text mode allows an explicit empty notice.

Open the feed's Catalog tab.

Manual rates normally expire after 24 hours and can be refreshed from the configured value. For an intentionally fixed rate, Currency settings JSON accepts {"manual_locked":true}. It also accepts effective_date, expires_at, ttl_seconds, or ttl_hours. NBP uses table A rates, calculating cross-currency conversion through PLN, and caches rates for 24 hours by default. nbp_ttl_seconds or nbp_ttl_hours changes that lifetime, with a minimum of five minutes. nbp_timeout defaults to 10 seconds and nbp_connect_timeout to 5 seconds. Missing or stale rates can block apply.

New products default to inactive with visibility none. You can review and activate them in the normal product editor. For deliberate automatic activation, Policy JSON supports:

{
  "activate_created_products": true,
  "create_visibility": "both"
}

Creation visibility accepts both, catalog, search, or none. Other supported policy keys include id_tax_rules_group for a new product's tax rules, feed_price_tax_mode with gross to remove included tax during price calculation, and allow_backorders for available items with zero stock. The default price interpretation is net, with no explicit backorder override.

deactivate_when_unavailable and hide_when_unavailable default to false. Set them only when you want supplier unavailability to change activation or visibility. The dedicated ordering switch controls disable_order_when_unavailable. Auto-category policies can use category_max_depth, initially 8, and category_max_creates, initially 20.

Open the feed's Safety tab. Save these settings before the dry-run you intend to apply.

The creation percentage accepts ratios up to 1 or percentages above 1. For example, 0.02 and 2 both mean 2%; 1 means 100%. Both the count and percentage safeguards apply. An explicit product scope can adjust the percentage allowance to at least the product count cap. A write limit does not automatically remove other potential creates from the creation safeguard.

Apply also requires a configured feed, a valid confirmation credential, and a prior successful or warning dry-run matching the current configuration. Changes to policies, safety limits, pricing, content settings, or overrides can require a new dry-run. Destructive image operations additionally depend on the reviewed feed content and gallery state.

Open Category Mapping, select Feed, then click Open. Use Scan feed sample to collect values from a configured generic mapping feed, or run a dry-run first.

Strategy defaults to the feed's Category strategy. Choose the default-category, automatic-path, or manual-map strategy and click Save strategy. For each Feed category, select Target category and click Save category maps. Initially no maps exist.

Product category overrides take precedence, followed by active feed-value maps. These maps can apply even when the overall strategy is not manual. Without a map, manual strategy falls back to the default category. Automatic-path strategy resolves or creates categories beneath Category root, subject to its depth and creation limits. Category writes still follow Sync categories and field locks.

Open Brand Mapping, select a feed, and use Scan feed brands after a dry-run or apply has collected brand values. Choose Manufacturer for each Feed brand. Create if missing defaults to No; enable it to create a manufacturer from the supplier brand name when no manufacturer is selected. Click Save brand maps. Brand matching normalizes case and whitespace.

Brand assignment follows product overrides and feed brand maps, then existing manufacturer-name matching. Creation requires the map's creation permission. Sync brand still controls ordinary writes. The list also lets you remove an unwanted brand map with Delete.

Open Stock Locations to pre-create or edit locations. New feed location codes can also create locations during apply.

Click Save location. The list shows location mode, linked warehouse, feed-map count, product count, quantity, and activity. Delete also removes that location's module stock ledger rows.

Enable Sync location stock in the feed and map Location quantities. Stock aggregation determines the shop quantity: sum, maximum, a primary location, or a specific location. Warehouse settings JSON can supply feed_location_map, warehouse_map, primary_location_code, specific_location_code, and country_location_map.

Primary location first considers the country-to-location map, then the configured primary code, then the first supplied location. Specific location uses the configured code; if that code is missing from the supplied quantities, its aggregate is zero.

For example, to use only the supplier's PL location, select Specific location and enter:

{"specific_location_code":"PL"}

When no location quantities are supplied, reconciliation uses the aggregate feed quantity. When a previously recorded location disappears from a nonempty set of location quantities, its recorded quantity is planned as zero. The per-location mass-zero safeguard can block unexpectedly large reductions.

Open Workbench, select Feed, and click Reload feed to generate a fresh matching dry-run. Search by name, EAN, SKU, or category, or use Status filters such as Matched, New, Excluded, Excluded manufacturer, and Ambiguous.

The grid shows source identity, price, category, match state, exclusion, and actions. Product overrides initially have no custom values, no value locks, and no exclusion. Enter a custom title or price and keep its value lock enabled to use it during apply. Choose a category for an override that takes precedence over normal category resolution. Edits are saved automatically; wait for the saved message.

Use Expand to edit localized Custom title, Short description, and Description, inspect resolved changes, and set product pricing or image and gone policies. Variant groups can expand into their member rows where variant data is present. Use Explain price for the calculation and source details.

Exclude defaults to off. When enabled, Skip leaves the item unchanged; Deactivate plans deactivation of an existing product. Selected rows can be changed with Exclude selected, Deactivate selected, or Clear overrides. Deactivation is applied through the normal dry-run and apply workflow, not immediately when the override is saved.

Mappings lists product associations, confidence, ignored state, frozen fields, and category overrides. Ignore prevents a mapping from being used for normal synchronization; Unignore reverses it. Category opens the Override category selector; click Save override to save the preference, or Clear category on the mapping to remove it. Freeze locks stock, price, availability, name, description, and images for the product in that shop. Unfreeze clears its product field freezes.

Use Remap to correct an existing association. Product ID defaults to its current target and Combination ID to its current combination, or 0 for a product-level target. Enter valid targets belonging to the selected shop and click Save mapping. Remapping does not copy the source product's freezes to the destination product.

The native product editor also marks fields managed by Feed Sync and exposes field locks. A frozen field keeps the merchant's current value, including against ordinary value overrides. Unlocking it allows the effective synchronization policy to control it again. Locks on shared catalog fields can affect writes from another shop that shares the same product data.

After changing overrides or locks, run a new Dry-run, inspect it, and apply from Feeds.

Set Sync images to Always if you want ongoing gallery synchronization for existing products, then choose the effective Scoped image strategy or inherited policy.

Open Images on a Workbench row to see the product gallery, which feed supplied each image, protected counts, and planned additions or removals. In Augment mode, Keep protects an image from feed removal. Position choices are Auto (feed order), Cover (first), Position…, and Last. A pinned position also protects the image. Returning it to automatic order can release the automatically added protection.

Upload your own images through the normal product editor. Use Augment when you want to preserve and pin these images. The Workbench image panel manages existing images; it is not an upload form.

Gallery changes, position rules, and protection changes can make the reviewed plan stale. Click Reload feed for a fresh dry-run before applying. Shared products can share gallery ordering between shops, so the last shop to synchronize can determine that order.

Use Dry-run on a Feeds row to fetch the configured feed, match items, and build planned changes without writing the catalog. Review the result in Workbench and Runs > Details.

The separate Parse-only dry run form under Dry run takes Configured feed, or Feed URL and Adapter. Click Run dry run to collect parsing metrics. This parse-only operation does not replace the matching dry-run required for apply.

Before applying, check matched, unmatched, duplicate, ambiguous, ignored, create, update, and skipped rows. Review stock and availability reductions, prices, category assignments, content, measurements, and image removals. Resolve source and mapping problems, then generate another dry-run after changes.

Click Apply on the feed and confirm the prompt. The admin action supplies the shop's apply confirmation credential. Either Apply enabled for this feed or Enable apply in this shop must be enabled. The module fetches the feed again, plans changes, evaluates safeguards, and performs allowed writes.

Runs on the same feed are serialized. A conflicting run can finish with status locked. A safeguard refusal produces blocked. A completed run can contain skipped, deferred, or failed rows, so use the row reasons and applied totals to understand the outcome.

Ordinary writes may proceed when feed content has changed since the dry-run if configuration and other safeguards still permit them. Destructive image changes require a matching reviewed feed and image plan. Measurement writes and reviewed content or brand operations can also require a fresh review when their inputs change.

Open Runs and click Details. The list shows mode, status, planned and applied counts, circuit-breaker state, duration, date, pin state, and detail storage. Details include summary counts, metrics, and before-and-after rows. Use Action and Status under Diff filters to narrow the rows.

Use Pin run to protect details from retention and Unpin run to release that protection. Under Run history retention, Preview retention shows the cleanup plan and protected reasons. Execute retention performs a bounded cleanup. If it reports Retention budget reached. Execute again to continue., repeat it to process remaining candidates. Expired details display Details compacted/expired under the retention policy.

To undo an apply, use Rollback this run in its details, or Rollback in the list. The feed row's Rollback action targets its latest eligible apply run. Confirm the prompt, then inspect the new rollback run.

Rollback uses the recorded write journal. It can restore supported changed fields and remove products or combinations created by the apply only when deletion guards permit it. Later catalog changes, changed images, or ownership conflicts can prevent restoration or deletion. Already rolled-back rows are skipped. Partial and deferred rows remain visible with their reasons; a successful rollback request does not mean every original change was reversed.

The default Ignore Omnibus price history during rollback setting allows an otherwise unchanged Feed Sync-created product to be deleted when only mpromnibus history changed. It does not discard that history or bypass other product-change guards.

Copy Cron URL from Settings > Configuration for the selected shop. For example, replace this sample with the actual URL:

0 * * * * curl -fsS "https://your-shop.example/module/mprfeedsync/cron?action=sync&token=YOUR_CRON_TOKEN"

action=sync and action=parse run parse-only operations. action=dryrun builds matching dry-run details. Add id_feed=123 to target a configured feed; without it, the endpoint runs active feeds. Each call processes the chosen feeds immediately. Schedule does not enforce per-feed intervals in this release.

The public endpoint also supports action=status, action=prune_run_history, and action=dropship_maintenance. Retention previews by default; add execute=1 to execute it. Read the returned JSON and per-feed results to distinguish completed, blocked, and failed operations.

action=apply requires the separate shop apply confirmation credential as confirm or apply_token, together with the cron token, a configured feed, apply permission, and a matching prior dry-run. The visible Cron token alone cannot authorize catalog writes. For routine reviewed writes, use Apply in the back office; server administrators can configure the apply endpoint or the supplied CLI tools with the separate credential.

The module registers shared scheduler tasks for parsing feeds hourly, recovering import maintenance every five minutes, retaining run history hourly, and maintaining dropship tickets every fifteen minutes. Their execution depends on the shop's shared scheduler running.

Server administrators can run a matching dry-run directly from the shop root:

php modules/mprfeedsync/bin/match-diff-dry-run.php --id-shop=1 --id-feed=123 --show-diffs

The corresponding apply tool is bin/apply.php, with explicit --id-shop, --id-feed, and --confirm arguments. These tools also support product and feed-key scopes. Configure limits and scope before generating the dry-run intended for that apply.

Open Dropship Orders > Supplier profile to add a supplier, or choose an existing supplier's button to edit it.

Click Save supplier profile. The profile form does not expose the order-status trigger, email recipients, HTTP endpoint, or adapter options required for automatic dispatch. Selecting an automatic adapter here alone does not configure it to send orders. Manual B2B is usable through the ticket workflow below.

Order creation and order-status hooks collect lines from bound feed mappings into supplier tickets. Maintenance can repair missed ticket creation. Feed synchronization being inactive does not itself remove a supplier binding. Tickets for mixed orders include only the lines resolved to the supplier.

The supplier ordering code comes from the mapped supplier SKU. Missing or ambiguous codes remain warnings instead of being replaced with a shop reference or supplier ID. Review warnings about supplier code, delivery, phone, billing, currency, or conflicting sources before placing the supplier order.

Open a ticket from Dropship Orders or the order's dropship panel. Copy individual values or use Copy whole ticket for manual entry into the supplier's system. Then enter Supplier order number and click Mark placed.

Use Tracking numbers (one per line) and Shipment confirmation before Save shipment. Choose Add parcels; keep ticket placed for a partial shipment, or I confirm the entire ticket has shipped for completion. Cancel ticket requires a Cancellation reason. Reopen ticket and Correct ticket are available where the current ticket state permits them.

For an unplaced ticket, use Preview refresh before placement to compare the stored snapshot with current order and source data, then Apply displayed changes if appropriate. Placed snapshots are frozen and their comparisons are read-only. Reload when the page says another operation changed the ticket.

When mprwarehouserevolution is enabled for the same shop, Feed Sync collects its dropship source alongside feed mappings. Shared source resolution detects overlapping lines and conflicts. Feed Sync owns the combined native order panel.

Dropship maintenance also expires recipient data for closed tickets after the shared default of 180 days. Tickets with erased recipient data have restricted editing.

Start with the run's Details, row Reason, dashboard Open alerts, and the source Test connection result. Use Settings > Integrity for required component and database checks. Settings > License, Support, and Update open the module's corresponding management screens.

A low match rate often needs corrected EAN or SKU mappings. Repeated supplier keys can create duplicate rows; several catalog candidates can create ambiguous matches. Inspect these identities rather than applying them as ordinary updates.

If a field remains unchanged, inspect its Sync permission, New products only mode, product freezes, custom value locks, exclusions, and feed priority. For missing images, also inspect the image plan, effective count cap, download limits, and whether a fresh reviewed plan is required.

Set Active to No to remove a feed from all-active-feed processing. Also remove any scheduler request or CLI job explicitly targeting that feed, since explicit feed actions can still run it. To prevent catalog apply, turn off both the feed-level and shop-wide apply permissions and stop automated apply jobs.

Disable the module in the module manager to stop its normal hooks. Remove external scheduler entries when you stop using it. Disabling does not reverse catalog changes already applied.

Before uninstalling, finish active imports and resolve automatic maintenance recovery. Uninstall refuses while these conditions remain unresolved, with Maintenance recovery must complete and active imports must finish before uninstalling.

Uninstall removes module configuration, menus, registered cron tasks, feed definitions, mappings, run history, rules, alerts, and locks. It removes Feed Sync's bindings from the shared dropship system, while shared dropship tables and history are preserved. Uninstall does not roll back imported catalog products or other catalog changes. Perform any required rollback before removing the module and its journals.

Requires PrestaShop 1.6.1.0 or later and PHP 7.1 or later.