Advanced Product Feeds-m2-advanced-product-feeds

User Guide

Works with:

Advanced Product Feeds

Name: Advanced Product Feeds
SKU: m2-advanced-product-feeds
Price: 199 EUR
Availability: InStock

(m2-advanced-product-feeds)

Gitlab access is only given to Agencies and Freelancers after
approval process.

Please note: we do not provide installation or implementation services for our extensions.

Installation should be handled by the developer or agency managing your store. This approach ensures:

Compatibility with your current setup
Proper configuration based on your specific version
Implementation by someone familiar with your codebase

Although we don’t offer installation, we maintain a curated list of recommended development agencies experienced with our solutions.

If you'd like to receive this list, please contact us at [email protected].

Partnership Inquiries

For partnership opportunities, reach out to: [email protected]

Description

Advanced Product Feeds for Magento 2 & Mage-OS — Built for Any Channel | qoliber

Magento 2 & Mage-OS Product Feed Extension

Advanced Product Feeds for Magento 2 & Mage-OS — Built for Any Channel

qoliber Advanced Product Feeds gives Magento agencies and commerce teams full control over the files sent to Google Shopping, Amazon, eBay, Allegro, Meta and custom channels.

Instead of forcing your catalog through a fixed mapping interface or an external SaaS, the extension gives you a template-driven feed engine. You define exactly what leaves Magento, in exactly the format the destination expects — while generation, scheduling and delivery remain inside your infrastructure.

No per-SKU pricing. No monthly feed SaaS dependency. No arbitrary catalog limits. Streaming generation keeps memory consumption bounded even on very large catalogs, while previews, execution logs and verified delivery help teams catch problems before a marketplace does.

Compare the approaches → Read the documentation →

PHP: 8.1 – 8.5
Per-SKU fees: None
API: REST

Your template · channel-ready output

Template — define it once

@for(products as product)
<item>
  <g:id>{product.sku}</g:id>
  <title>@xml(product.name)</title>
  <g:price>@number(product.price, 2, ".", "")</g:price>
@if(product.is_in_stock)
  <g:availability>in stock</g:availability>
@end
</item>
@end

Generated feed — what the channel receives

<item>
  <g:id>WSH12-28-Blue</g:id>
  <title>Nora Shorts &amp; Tee</title>
  <g:price>1234.57</g:price>
  <g:availability>in stock</g:availability>
</item>

Small formatting mistakes are enough for a marketplace to reject an entire feed. Format-specific helpers handle XML escaping, CSV values, URLs, JSON and number formatting, while Preview lets your team inspect real catalog output before publishing anything.

Why Advanced Product Feeds

One Feed Engine Without Another SaaS Bill

Product feed platforms often become more expensive as catalogs, markets and channels grow. Advanced Product Feeds keeps the generation engine inside Magento, giving agencies predictable infrastructure and merchants predictable costs.

No Per-SKU Fees

Grow from thousands to hundreds of thousands of SKUs without moving into another SaaS pricing tier simply because the catalog became more successful.

Keep Catalog Data In-House

Product, pricing and customer-group data is processed inside Magento. Only the final generated feed is sent to destinations you configure.

Reuse Across Client Projects

Agencies can standardise feed architecture, templates and delivery patterns instead of rebuilding marketplace exports independently for every client.

Scale Without Memory Spikes

Streaming generation processes products progressively rather than loading the entire catalog into memory, keeping resource consumption bounded on large catalogs.

Marketplace product feeds

One Magento Catalog. Multiple Sales Channels.

Start from ready-made feed templates or create a completely custom output for a marketplace, comparison engine, affiliate platform or internal integration.

Google Shopping

Generate Google-compatible product data using a dedicated marketplace template and category taxonomy mapping.

Amazon

Build marketplace-specific outputs including variant and parent relationships rather than flattening the Magento catalog incorrectly.

eBay

Map Magento categories to marketplace taxonomy and automate repeatable export schedules.

Allegro

Dedicated taxonomy support helps agencies serving Central European commerce projects align Magento categories with Allegro's product structure.

Meta / Facebook

Prepare catalog feeds for Meta commerce and advertising without maintaining a separate export pipeline.

Any Custom Channel

XML, CSV, TXT and JSON templates let your team implement specifications that are not covered by a prebuilt marketplace connector.

Catalog automation

Select Products With Rules, Not Spreadsheets

Product inclusion uses Magento's familiar rule-condition model, letting technical and merchant teams define feed eligibility dynamically instead of maintaining static product lists.

Create rules such as in stock, above a specific price, within selected categories, carrying particular attributes or available to a chosen store view. As the catalog changes, the feed selection changes with it.

This is particularly useful for agencies managing large catalogs where manual feed curation quickly becomes another recurring maintenance task.

Magento catalog structure

Export Magento Product Types Properly

Configurable Products

Export enabled variants individually while preserving parent relationships and inheriting suitable parent information where child values are unavailable.

Grouped Products

Use dedicated product-type resolution instead of forcing grouped products through generic simple-product output.

Bundle Products

Bundle structures receive dedicated output handling, providing agencies with control over how complex catalog products appear downstream.

Pricing accuracy

Export the Price Magento Would Actually Show

Each feed runs in a chosen Magento store view and customer-group context, allowing prices to resolve through Magento's normal pricing stack instead of relying only on a raw base-price attribute.

That includes relevant special prices, catalog price rules and tier pricing, making it possible to maintain separate public, B2B or market-specific product feeds from the same Magento catalog.

Product feed reliability

Where Magento Product Feeds Usually Fail

Generating rows is not the difficult part. Feed failures are often quiet: invalid escaping, incorrect prices, a broken scheduled job or a destination that stopped accepting files.

Invalid Output

One invalid value can reject an entire upload.

Format-aware helpers correctly encode XML, CSV, JSON and URLs so catalog data does not accidentally break the destination format.

Wrong Price Context

A technically valid feed can still advertise the wrong price.

Feed generation respects store-view and customer-group context, allowing Magento pricing logic to remain part of the export.

Memory Exhaustion

Large catalogs expose inefficient export implementations.

Streaming generation writes progressively instead of accumulating the entire catalog in memory.

Silent Schedule Failures

A feed can stop refreshing while the channel keeps using old data.

Execution logs capture status, product count, generated file size, duration and warnings. Failed scheduled runs can trigger email alerts.

Broken Delivery

A valid file is worthless if it never reaches its destination.

FTP and SFTP destinations can be connection-tested before production schedules depend on them.

Channel Specification Changes

Fixed mapping interfaces age badly.

Template-driven output lets developers change field names, nesting and formatting directly when a marketplace specification evolves.

Feed delivery

Generate Once. Deliver Where the Integration Needs It.

Local

Generate files directly into a configured server directory.

FTP

Automatically upload generated feeds to traditional FTP destinations.

SFTP

Deliver to secure SFTP endpoints and validate connectivity before scheduling.

Email

Send generated feeds by email where legacy integrations require file delivery.

Delivery destinations are extensible, so agencies can add project-specific output channels without rewriting the feed generation engine.

Built for agencies

Extend the Feed Engine Without Forking It

Product feeds are often deeply project-specific. The architecture is intentionally designed so agencies can add custom marketplace logic without turning the vendor module into a permanent fork.

Taxonomy Providers

Add another marketplace taxonomy through the DI pool instead of altering core code.

Delivery Destinations

Implement S3, webhook or proprietary delivery mechanisms as additional destination services.

Product-Type Resolvers

Extend product transformation logic when a client catalog uses custom product structures.

Field Validators

Add project- or channel-specific validation before generated data reaches production.

Lifecycle Events

Integrate additional workflows around feed generation without modifying the generator itself.

REST + CLI Automation

Provision feed profiles through REST and automate generation or taxonomy sync from CLI and CI/CD.

Template engine

Powered by Tsuku — Open-Source Streaming Templates

Feed rendering is powered by Tsuku, qoliber's MIT-licensed PHP templating library.

Developers work with readable templates instead of closed mapping screens, while streaming execution means products can move through the renderer one at a time. The same architecture that makes templates flexible is also what keeps memory consumption predictable on large catalogs.

Engineering quality

Product Feed Infrastructure You Can Audit

PHPStan · zero reported errors

~400

PHPUnit unit & integration tests

100k+

products scale-tested

8.1–8.5

PHP support

The extension also passes the Magento coding standard with zero reported errors and has been audited for structure, security and performance.

Magento product feed comparison

qoliber Advanced Product Feeds vs SaaS Feed Platforms & Competing Modules

There are three common ways to solve product feeds: move catalog data into an external SaaS, install a fixed Magento export extension, or keep a programmable feed engine directly inside the commerce platform.

qoliber Advanced Product Feeds compared with SaaS feed services and competing Magento product feed modules
Capability	qoliber	Feed SaaS	Competing modules
Commercial model	No per-SKU SaaS fees	Commonly monthly and usage/catalog based	Usually extension licensing
Data processing	Inside Magento	External platform	Inside Magento
Output control	Fully template-driven	Platform-specific mapping UI	Often predefined fields
Large catalogs	Streaming, bounded-memory generation	Depends on service tier and platform	Implementation varies
Pricing accuracy	Store-view + customer-group context	Depends on supplied source data	Often simpler attribute export
Marketplace categories	Mapped in Magento, per store view	Typically mapped externally	Support varies
Delivery	Local, FTP, SFTP, email + extensible pool	Managed by SaaS platform	Varies
Automation	Per-feed schedule, REST and CLI	Service-defined refresh model	Often cron-based
Extensibility	DI pools + lifecycle events + templates	Limited by platform integrations	Varies by vendor
Failure visibility	Execution log + failure emails	External dashboard	Varies

“Feed SaaS” and “Typical Magento Extension” describe common characteristics of those approaches rather than any individual vendor. Features and commercial models vary between products.

Switching product feeds

Keep the Output. Replace the Dependency.

Already running another Magento product feed solution? qoliber can help reproduce existing feed profiles, templates, category mappings and schedules so the files your channels already accept do not need to change during migration.

For agency partners, existing feed configurations can be migrated without starting from a blank implementation.

Technical specifications

Built for Modern Magento & Mage-OS Projects

Platform

Magento Open Source 2.4.x, Adobe Commerce and Mage-OS.

PHP

8.1 – 8.5.

Output

XML, CSV, TXT, JSON and other text formats expressible through templates.

API

REST for feed profiles and templates. No GraphQL.

In the box

Unlimited feed profiles
Feed profiles per channel and store view
Template editor with syntax highlighting
Twelve ready-made marketplace templates
Product filtering through Magento rule conditions
Real-product preview before publishing
Marketplace category mapping
Per-feed scheduling
Custom cron expressions
Local, FTP, SFTP and email delivery
Destination connection testing
Execution log with product count, duration, file size and warnings
Failure notification emails
UTM tracking parameters
Customer-group-aware pricing
CLI feed generation and taxonomy sync
REST configuration APIs
Modular installation

Magento Product Feeds FAQ

Questions

Which marketplaces can I create Magento product feeds for?

Ready-made templates and taxonomy support cover major channels including Google Shopping, Amazon, eBay, Allegro and Meta/Facebook. Because output is template-driven, you can also create feeds for custom marketplaces and integrations.

Which product feed formats are supported?

XML, CSV, TXT and JSON are supported directly, while the template system can generate other text-based formats required by custom integrations.

How large a Magento catalog can Product Feeds handle?

Products are streamed through the renderer and written directly to the output file, so memory consumption is not proportional to total catalog size. The solution has been scale-tested with catalogs above 100,000 products.

Does the feed use Magento catalog prices?

Yes. A feed runs in a specific store-view and customer-group context, allowing Magento pricing rules, special prices and applicable tier prices to be reflected in generated output.

How are configurable products exported?

Configurable products can export enabled variants as individual rows while retaining the parent relationship required by destination channels. Variant information can inherit appropriate values such as names and images where required.

Does my catalog data leave Magento?

Feed generation and rendering happen inside your Magento installation. Only generated feed files are sent to configured destinations. Optional marketplace taxonomy modules can retrieve public category structures from their respective platforms.

Can Product Feeds be automated?

Yes. Every feed can have its own schedule using presets or custom cron expressions. Generation is also available through CLI, while feed profiles and templates can be managed through REST for external deployment and automation workflows.

Does Product Feeds support GraphQL?

No. Product Feeds currently exposes REST APIs for profile and template management. Feed generation and marketplace taxonomy synchronisation are also available through CLI.

How do I know if a scheduled product feed fails?

Every execution is recorded with status, product count, duration, file size and warning information. A failed scheduled run can send an email alert so outdated marketplace data does not remain unnoticed.

Product Feeds for Magento 2 & Mage-OS — Built for Any Channel

Read the documentation → Talk to qoliber →