Matrix Filters
channel = "Meta"\ncountry = "DE"\nstock > 0\nprice >= 10\ncategory in ["Shoes","Bags"]
A separate matrix and rules for every feed.
Create, adapt, and maintain product feeds for any requirements of partners, advertising systems, and platforms — without development, without manual workarounds and without the 'fear of breaking things'.
A separate matrix and rules for every feed.
Feeds are no longer a 'technical project.' You control the format, the product set, required fields, scheduling, and output logic—as confidently as you manage campaigns.
Virtually every channel has its own requirements for structure, fields, and formats. In a typical process, marketing defines the task, and then a queue of developers, contractors, and manual edits begins.
In traditional feed managers, you are limited by rigid presets or manual configuration. Here, every feed is a separate scenario, where you can control what is exported,, how it is exported, and when it is updated..
Performance: Different feeds for campaigns (brand/sale/outlet), regional pricing, stock exclusions, custom mandatory fields.
Marketplace: Strict structural compliance, nested attributes, and category-specific requirements.
Partners: Feed as a contract—we lock down structure, versions, and schedules, quickly creating variations for different partners.
SEO: Generating structured exports for aggregators and showcases, controlling field completeness and description quality.
Format is structure. Partner requirements are input data. The marketer manages the logic and meaning, while the system handles the technical implementation.
Fields, order, nesting, data types—replicated without code.
Mandatory fields, fallbacks, and source priorities—all manageable and transparent.
Scenarios are saved as configurations, making them easy to repeat and scale.
Traditional solutions hit roadblocks: 'This format is unsupported,' 'You need a developer,' or 'This requires custom work.' With NotPIM, the system itself handles the complexity of formats and rules.
Partner file, specification sheet, reference export.
Field → type → rule → nesting → sequence.
Next up: matrix filters, scheduling, variations.
If a partner provides requirements and a sample file, a marketer can simply upload the example. The system will build the feed model and suggest everything needed for launch.
You don't need to write a technical description of the format.
You don't need to 'assemble' the format manually.
The marketer works at the level of meaning.
Feed Generator allows you to control which products are included in a specific feed and which data is outputted. This is necessary for different channels, assortment A/B testing, promotions, regional requirements, and partner restrictions.
Rules are clear to the business and reproducible for the team.
Prices, availability, and assortment change constantly. Feed Generator allows you to manage feed behavior over time: scheduling, update frequency, generation modes, and data completeness requirements.
Hourly / Daily / Weekly, plus dedicated update windows for partners.
Different feeds update at different rates: promotional feeds more often, SEO feeds less frequently.
Mandatory field rules and fallbacks to prevent feed rejection.
Modify feed format, structure, and logic via the assistant. Simply describe the task: the assistant understands the context of the current scenario and applies changes precisely.
Add a field sale_price and make it mandatory for the “Shoes” category.
Done. Added sale_price, a mandatory rule for “Shoes”, with a fallback from promo_price.
Knows which feed and which rules are already in place.
Shows what has changed and where.
Doesn't break other scenarios or channels.
The second workflow is even simpler: select a ready-made format for popular platforms. In most cases, marketing doesn't need to configure anything at all.
You can start with a ready-made format and then extend it with your own rules and filters.
Selected format → connected data → received feed.
Add fields, rules, filters, variants.
Save variations for different channels and teams.
The Feed Generator is equally valuable for marketing and business. Marketers gain autonomy and speed, while the business achieves scalability and predictability without increasing the load on development.
Feed Generator is not an advertising platform and does not replace campaign analytics. It solves a different problem: managing product data output — formats, rules, matrices, and scheduling.
Move complexity into the system and manage feeds as flexibly as marketing campaigns. Start with a ready-made format or upload a partner's sample—and launch faster than you can agree on the specs.
Briefly and to the point—about feeds, formats, and real channel management.
No. Feed Generator is designed from the ground up for autonomous marketing operation without developer involvement.
Yes. Each feed is a separate scenario with its own logic, product matrix, and rules.
Yes. CSV, XML, JSON, XLSX, and their variations, including nested structures and non-standard requirements.
It is enough to upload this example. The system will recognize the format and create the feed model automatically.
No. The marketer works with logic and rules, while the system handles the technical implementation.
Yes. Filters by category, brand, availability, price, and other parameters are configured separately for each feed.
Yes. Regional feed versions are created as separate scenarios with their own specific rules.
Yes. The system includes a library of ready-made formats for popular advertising and affiliate platforms.
Yes. A ready-made format serves as a starting point that can be extended and customized.
You can define rules for mandatory fields, fallback logic, and data quality requirements.
The frequency is configurable: from several times per hour to infrequent updates for SEO channels.
Yes. The same dataset can be utilized across different scenarios with varying logic.
The system applies defined fallback rules or flags issues without breaking the entire feed.
Yes. Changes to format, rules, and logic can be specified via plain text commands to the Assistant.
No. The Assistant operates within the scope of the current scenario and does not affect other feeds.
Yes. The system is designed to handle large catalogs and numerous parallel feeds.
Yes. You can create feed versions and variations for different hypotheses and channels.
From a few minutes—especially if a ready-made template or partner example is used.
Yes. The scenario-based approach allows for convenient work across different projects and requirements.
Autonomy, speed in launching new channels, and independence from IT.