Overview
RCA J2C DownfilesSync is the Pro system plugin that keeps J2Commerce downloadable products aligned with versioned ZIPs on your server. You ship builds into free/ and pro/ package folders under the J2Commerce attachment root; the plugin maps products to those folders, points the primary product file at the newest {package}_{version}.zip, and can register older GPL builds plus an optional CHANGELOG. Manual Add Files paths go stale after every release unless something syncs them. This plugin is that sync.
What problem am I actually solving?
J2Commerce stores downloadable products as database rows with a path to a file on disk. When you use Add Files and pick a filename, that path is static until someone edits it again. If your release process drops a new ZIP into a folder every time you ship, the catalog still points at yesterday’s filename until you fix it by hand. Sync reads the folder, finds the highest version, updates the lowest-id managed product file row so index zero stays current, and optionally attaches prior ZIPs so shoppers can still reach older GPL builds without you clicking through product files for an hour.
How sync discovers products (1.1 and later)
Full Auto is the default. The plugin matches each downloadable product’s master variant SKU to a folder name on disk under free/{sku}/ or pro/{sku}/ and syncs every ZIP that follows the naming rules. SKU pairing ignores letter case, but the folder path uses the SKU as stored in J2Commerce, so on case-sensitive servers the disk folder must match that capitalization (RCA uses all-lowercase SKUs and folders). You do not need a Product folder map line for every SKU when names already align.
Retail sellable-only (default on, 1.2+) limits Auto and sellable warnings to storefront folders — usually pkg_* package products and standalone extensions. Child folders that exist only for Joomla Updater feeds beside a package suite appear under Ignored folders on the Sync panel, not as errors you must “fix” by creating fake products.
Manual mode and Auto plus map overrides remain for legacy sites and for deliberate per-child ZIP delivery to separate product IDs.
What you get in the package
The install package is plg_system_rca_j2c_downfilessync (element rca_j2c_downfilessync). Current retail documentation reflects version 1.2.4. You get plugin options on the Settings tab (sync mode, retail rules, Product folder map), a Sync panel with Sync Now, mapped folders, ignored updater paths, and sellable unmapped warnings, optional scheduled sync through com_ajax when you set a Cron key, product-save sync for mapped downloadable products, change-only sync with optional force=1, and a frontend shortcode to list version filenames. Updates arrive through the Pro private feed at https://recreatinganew.com after purchase.
What this is not
This is not J2Commerce itself, not your CDN, and not RCA J2C DirectDownload. RCA J2C DirectDownload is the separate free content-plugin path for article-level free grabs with the rcadownload shortcode. DownfilesSync keeps J2Commerce product file rows aligned with files you already placed on disk. It does not build ZIPs, pull from RCA update feeds, or upload releases for you.
Who should use this?
Use it if you sell or distribute extensions through J2Commerce, store {package}_{version}.zip files under free or pro package folders, and you are tired of editing product files every time you bump a version. Use it if you want prior versions listed for transparency without hand-maintaining a dozen product file rows after each build.
Who should skip it?
Skip it if you do not use J2Commerce downloadable products at all. Skip Manual-only workflows if you refuse to align master SKUs with folder names and will not maintain map overrides — wrong IDs or folder names sync garbage or nothing useful, and the plugin will not guess your catalog for you.
How does it fit with other RCA J2Commerce tools?
RCA J2C DirectDownload reads J2Commerce product files after sync keeps those files current. RCA extension releases that land in L2 download folders pair naturally with Auto mode when J2Commerce master SKUs match sellable folder names (pkg_rca_* for package suites).
Where should I read next?
Use Quick start for the shortest path to one successful sync. Use Requirements for the disk tree and naming rules. Use Configuration for Auto versus Manual versus overrides and every option. Use Integrations for DirectDownload and release workflow. Use Troubleshooting when the Sync panel lists unmapped folders or sync errors you do not understand yet.