Mage-OS Shopping Feeds

Mage-OS Shopping Feeds generates product data files inside Mage-OS or Magento Open Source. You control the columns, product selection, inventory rules, schedules, output, and delivery.

Mage-OS Shopping Feeds is the updated version of Rocket Shopping Feeds. We used to sell it. Now it’s free and open source.

The new package consolidates the generic, Google Shopping, Local Inventory, and Promotions modules. Moving existing Rocket Web feeds is a separate, explicit migration.

Yes. The code is free under OSL-3.0, with no license fee or per-feed charge. Your developers can inspect and modify the source.

Get the source on GitHub or install mage-os/module-shopping-feed through Composer. Rocket Web can provide installation, configuration, and custom development as separately scoped work.

Bundled presets cover Google Shopping, Google Local Inventory, Meta Catalog for Facebook and Instagram, Microsoft Merchant Center, TikTok Catalog, and Pinterest Catalog. Google Shopping can also generate a companion Google Promotions file from configured eligible cart price rules.

The Generic preset supports custom delimited feeds with configurable columns, separators, quoting, mappings, and filters. Each destination still needs to accept the generated file; a preset does not establish merchant eligibility or successful ingestion.

The bundled OpenAI / ChatGPT Google-compatible preset is a beta with known format gaps. It has not been updated to OpenAI's current product-feed contract, including seller fields, URL names, variant structure, and preorder values.

Use it only if OpenAI explicitly accepts your exact exported sample and transfer format. It does not provide merchant account access, checkout, or order synchronization. Read the beta limitations.

Map categories, combine attributes, replace text, remove HTML and Page Builder markup, fall back to alternate values, and format prices and currencies. Product identifiers must come from real catalog data.

In 1.2.4, preset title and description limits are not applied automatically. Configure explicit Limit column output rows where needed and review destination diagnostics. Local validation cannot establish that missing or inaccurate source data is correct.

Yes. Configure categories, product types, attribute sets, stock rules, and required output values. Google Shopping also has upper and lower price filters.

Configurable, grouped, and bundle settings control whether parents or associated products become feed rows. Configurable and grouped feeds can inherit individual column values from the parent, child, or a fallback between them. Supported Luma and Hyvä deep links preselect configurable or custom options on the landing page.

Feeds update on a cron schedule or on demand. Queue a run in Admin, or generate a feed through the command line. Batch mode splits larger jobs across runs. Magento cron must be running for scheduled generation.

Recipients can fetch the generated public file, or the module can upload by SFTP or unencrypted FTP, with optional gzip compression. FTP sends credentials and data without encryption. SFTP requires a trusted SHA256 server host-key fingerprint.

Yes. MSI is optional. Aggregate quantities use enabled sources assigned to the feed's website stock and can account for reservations when configured.

Google Local Inventory can map individual MSI source codes to Google store codes. Those rows describe physical-source stock; website reservations are not assigned to each location. Source-level Local Inventory needs Magento's MSI APIs.

Each feed has its own store view and currency, with store-specific attributes, pricing, URLs, and product selection.

Optional schema.org offer microdata supports Google Automatic Item Updates on Luma and Hyvä. Configurable and custom-option deep links work on those themes. Google Ads view_item events are Luma-only. Headless storefront integrations are not verified; generated files remain usable independently of the frontend.

The current CI matrix includes Mage-OS 3.5 and 3.6, and Magento Open Source 2.4.8-p5 and 2.4.9. Magento 2.4.7-p10 has a separate profile with a documented upstream Flysystem advisory. PHP 8.1 through 8.5 is declared, limited to the versions supported by the selected platform.

The declared Magento 2.4.6-p15 floor has dependency and syntax checks, but no installed-store runtime acceptance. Adobe Commerce and custom storefronts need verification on your installation. Standard Admin needs no Nebula package; the optional Nebula grid opens editing, previews, and logs in standard Admin. Review compatibility and tested scope.

The main package installs alongside the original Rocket Web modules without importing or changing their feeds. The optional Rocket Web migration companion is installed separately as rocketweb/module-shopping-feed-migration-rocketweb.

On staging, back up the matching database, code, configuration, output, and encryption key. Keep the legacy modules installed and enabled through schema upgrades. Preview each import; replacement feeds start disabled with schedules and uploads held. Compare generated output before explicitly activating replacements.

Custom code, shared settings, recipient URLs, and trusted SFTP fingerprints require review. Stores without legacy feeds only need the main package. Follow the migration guide.

Version 1.2.4 adds SFTP server verification, keeps upload passwords encrypted until connection, verifies log archives before rotation, and fixes inventory and shipping edge cases. Test Feed now requires Generate Feed permission.

Run setup:upgrade, then enter a trusted SHA256 host-key fingerprint for every SFTP destination. A missing or mismatched fingerprint prevents authentication and delivery. Verify the generated file and transfer on staging before resuming schedules. Read the release notes.