Distributr sends product data from Orchestr and content from your Laioutr CMS to every channel you need: marketplaces, price comparison sites, ad feeds, retailer listings, ERP systems, spec sheets. Configured in code, versioned in Git.
Maintaining product data is one thing. Getting it everywhere is another.
Every channel wants a different format. Google Shopping, Otto, Kaufland, idealo, the buyer's spreadsheet, the export into your ERP. Today all of that runs through a separate feed tool with its own login, its own data storage and its own sync cycle. That means duplicate work, delay and a second invoice.
Distributr makes distribution part of the platform
The data already lives in Laioutr: product data in Orchestr, content in the CMS. Distributr reads it from there, shapes it per channel and ships it. No import, no reconciliation, no second source of truth. What you change in the cockpit is in the next export.
How it works
Pick the source
Product data from Orchestr, content from the CMS, or both combined.
Define the channel
Field mapping, rules and filters as typed code in the repository.
Check
Preview, dry run and validation against the channel schema before the first export.
Deliver
By pull URL or actively via HTTPS, SFTP, S3 or webhook. On a schedule or on every data change.
Channel configuration is code, not a click path
Every channel is a typed definition in the repository. Field mapping, computed values, filters and exclusions live in code, with full boolean logic including brackets. Changes go through review as a pull request, and a rollback is a git revert. With Larry AI a new channel definition takes minutes instead of hours of clicking.
Two sources, one export
Orchestr provides the base from your backend, whether that is Shopware, Shopify, commercetools or OXID. The Laioutr CMS adds what is not there: customs tariff numbers, retailer-specific attributes, translations, marketing copy. Distributr merges both at export time, field by field and visible in the channel definition.
The channels nobody else serves
Any feed tool can do Google Shopping and Meta. The listing spreadsheet your buyer sends as an Excel file, the export format for your ERP, the PDF spec sheet for the sales team, the download page where retailers pull their own listing data and images: for that there is no standard product. In Distributr it is the same mechanism as any other channel.
Errors surface before the channel sees them
Before every export Distributr validates against the channel schema: required fields, allowed values, GTIN validity, price formats. The diff guard compares the item count with the previous run and blocks the export when the deviation exceeds your threshold. Alerts by email, Slack or webhook come with every plan, not just the most expensive one.
Up to date is not a premium feature
External feed tools price their plans by updates per day: once daily at entry level, more often for a surcharge. Distributr does not need that tier because the data already lives in the platform. You set the rhythm, or let the export run on every data change. No surcharge, no per-country fee, no automatic upgrade when you cross a limit.
Everything distribution actually needs
Channel definitions
Typed code in the repository, versioned and reviewable in a pull request.
Every common format
CSV, XML, JSON, XLSX and PDF, with channel-specific templates.
Marketplaces and price comparison
Google Merchant Center, Meta, TikTok, Pinterest, idealo, Amazon, eBay, Otto, Kaufland.
Retailer listings
Your buyer's Excel template gets mapped once and is filled automatically from then on.
Product spec sheets
Design templates in Studio, render them as PDF per product or range.
Feed health and diff guard
Schema validation before export, with a block on suspicious volume changes.
Asset deep links
Stable image URLs that always serve the current file.
Retailer portal
A download page for listing data, images and spec sheets, public or behind a login.
0 imports
the data is already there
1 direction
out, never in
5 formats
CSV, XML, JSON, XLSX, PDF
No sync surcharge
freshness without a price tier
Full control for developers
Channel definitions, transformations and delivery targets live in code, with type safety from the data source to the delivered field. Preview and dry runs work locally, and snapshot tests protect channels against unintended changes. A new channel is a new definition, not a support ticket at a vendor.