Massive Multifeed Import&Sync (MMIS)

What it does

• Multiple independent Import Profiles, one per supplier/feed
• CSV, XML or JSON feeds — over URL, local file, or FTP
• Column-to-attribute mapping, with formulas and text functions
• Configurable products (variants), including multiple simultaneous attributes
• Grouped products (independent items sold together)
• Category tree created automatically from the feed's category path
• Image gallery with role mapping (base/small/thumbnail/gallery) and automatic compression
• Group/Rule filters to route different subsets of a feed to different categories or markups
• Absolute or relative stock updates, backorders, "new" flag
• Live preview of unsaved changes, before you save the profile
• Scheduling per profile (cron), or run on demand from a button/CLI
• Safe, reversible deletions: products are disabled first, deleted only after a configurable grace period
• Full compatibility with M2E Pro: changes are correctly reported to it even with the fastest write strategy (direct SQL)
• Adopt it on a catalog that is already indexed, without changing a single address: product URL key, category tree root, category path and image file names are configurable templates, so they can match exactly what your current importer already produces.

Fully translated admin, in 7 languages

The whole admin interface — every label, tooltip and guide — is available in:

Magento automatically shows the module in whichever language each admin user has configured — no setup needed.

Built for real catalog sizes

These are real measurements from a production deployment, not lab estimates — a live store syncing a genuine large supplier catalog (hundreds of thousands of SKUs, hundreds of thousands of images) on ordinary, non-exotic server hardware.

Test server: 12-core Intel Xeon E5-2690 @ 2.90GHz, 10GB RAM, PHP 8.5, with the database on a separate dedicated server — a standard mid-range setup, not high-end hardware. The 600 products/second figure compares to roughly 1 product/second with Magento's native import mechanism on the same data.

Two problems you only meet once the shop is running

Neither of these appears while you are configuring an import. They appear weeks later, with real orders and real customers, and by then the catalogue is in production. We build these modules from behind the counter, so they are handled — with a switch, and with the trade-off stated up front.

The order you cannot ship

You sold two pieces on Monday. You have them, boxed, on the bench. On Wednesday you go to create the shipment and Magento refuses: the product is not available. Nothing is wrong with your stock — overnight the supplier ran out, the sync did its job and set the quantity to zero.

With “Keep items with orders still to ship available” the quantity still drops to zero — that figure is true and stays true — but the stock row is not marked out of stock while an order is waiting to be shipped. You ship. Nobody else can buy it, because the quantity really is zero.

The usual workaround found in forums — turning off stock management on that product — makes it sellable forever, including when it really is finished, and nobody remembers to turn it back on. This switch does not do that. It gets sharper the more often you sync: updating stock every half hour means meeting this case 48 times more often than updating it once a night.

Your photo, somewhere else every morning

You photographed the product better than the supplier did, or added the shot with the measurements — the one that stops the phone calls. You put it last. Next morning it is in the middle. The morning after, somewhere else again. The feed numbers its own images 1 to N without knowing one of those slots is yours: two images end up claiming the same position, and which one wins is decided by an internal id.

With “Keep images you added by hand” your photo is placed after the ones from the feed and stays there. An article with 5 feed photos plus yours: yours is number 6, tonight and every night. Turn the switch off instead and the gallery mirrors the feed exactly — images that are not in the feed are detached from the product, while the file itself is kept, because it may belong to another product too.

One thing said up front, rather than discovered later: if the article disappears from the feed and the module deletes it, your photo goes with it. It is the same product page — there is no way to delete the product and keep one of its images attached. If you want to keep it, download it first, or turn off automatic deletion of articles that left the feed.

Documentation

Full installation steps and a complete field-by-field user guide (mapping, formulas, configurable and grouped products, categories, images, scheduling, CLI) live on their own reference page:

→ Read the full documentation

Money-back guarantee

Not satisfied within 30 days of purchase? Request a refund yourself from your account area (codingrow.com/login), no questions asked. The refund is processed instantly, automatically, and the license is deactivated upon confirmation.

Changelog

Current version: v3.21.0