Six portals, six exports
Every system brings its own metrics, its own periods and its own names for the same thing. Consolidation happens by hand and is out of date the next day.
Data · Live
scroll Marketing Performance Monitor
One cockpit across every channel. And the warning before the numbers tip.
Today the figures sit in six portals and everyone pulls their own spreadsheet. The monitor brings them together, normalises them and turns them into views, warnings and prioritised proposals. Nothing is executed without approval.
Where it breaks down
The monthly report arrives too late to change anything.
Selling across several channels means collecting figures from several portals. By the time they form a picture the month is over and the decision can no longer be made, only explained.
Drops surface late
A channel suddenly delivers less, a fee changes, stock runs dry. Nothing fails, the numbers just get worse, and it is noticed in hindsight.
Tasks disappear into chat
The insight emerges in a meeting, the task in a message, and two weeks later neither can be found.
The solution
Observe, surface, propose. People do the executing.
The monitor is the operational data layer across every channel. It collects continuously, adds things up and speaks up by itself when something falls out of range.
Metrics, stock levels, prices, competitor offers and ad data come in on a schedule and are mapped onto one shared model. Only then does one channel become comparable with another, and only then does an overall view make sense at all.
On top of that run observers that do not wait for an error but for a deviation. If the volume of new entries collapses, if a field loses coverage, if a margin tips after a fee change, the result is a message in plain language rather than just a number.
Observation becomes proposal: price adjustment, reorder, ad action. Each proposal carries priority and reasoning and waits for a decision. Accepted proposals become tasks with an owner, so the insight does not end in a message.
MetricsStock healthPrice watchingAnomaliesProposalsTickets
In practice
Three situations where days decide money.
Stock covers nine days
The monitor weighs coverage against lead time and speaks up before the item runs out. With a reorder proposal, not a number somebody still has to interpret.
A fee change eats the margin
Margin per item is recalculated continuously. If it tips below the threshold, the price proposal is ready for approval, with competitor offers alongside for comparison.
A traffic channel drops
Instead of guesswork the anomaly arrives with context: since when, how sharply, and which other metrics moved at the same time.
How it works
Connect, normalise, observe, decide.
Connect
Marketplaces, shop, ad accounts and merchandise management are connected and come in on a schedule.
Normalise
Different metrics and periods are brought onto one shared model. Only then is a comparison across channels sound.
Observe
Thresholds and reference values run alongside. Anomalies report themselves, as a sentence with context rather than a bare number.
Decide
Proposals are accepted, rejected or deferred. Accepted, they become a task with an owner.
Let us look at which anomalies your figures from the last three months would have shown.
Arrange a conversation Core capabilities
What the module brings.
Metrics across every channel
Revenue, units, visibility and margin side by side instead of in six portals. Down to the individual variant if you want.
Stock and stock health
Coverage against lead time, slow movers, shortfalls, and discrepancies between ordered and delivered.
Price and competitor watching
Your prices against competitor offers, with adjustment proposals inside the boundaries you set.
Anomaly detection
Volume collapses, coverage losses and unusual channel patterns. Every message a finished sentence with context.
Proposals with approval
Prioritised as now, this week, structural or purely informational. Nothing executes without a decision.
Ticket and task system
An accepted proposal becomes a task with an owner, a deadline and a history.
Notifications
A digest by email, urgent messages by messenger or into the tool the team already uses.
History and snapshots
Every metric is kept over time. That makes it possible to answer later what things looked like before the measure.
Knowledge transfer assistant
Recurring routines are captured in structure with the people responsible, so knowledge does not hang on one person.
Automations
Trigger, condition, action. For routine where case-by-case approval adds no insight.
Interface for agents
Other tools reach metrics and proposals through a defined interface, with rate limiting.
Two-factor sign-in
Access only with a second factor, roles and permissions per area, a complete trail of executed runs.
Where it works
Three roles, three measurable outcomes.
Procurement
Reorders come from coverage and lead time instead of experience. Fewer shortfalls at the top, less dead capital at the bottom.
Marketing
Budget moves to where it carries, because channels become comparable. Drops surface within days, not in the quarterly report.
Management
One set of figures for everyone. Discussions turn on decisions rather than on whose spreadsheet is right.
A look inside
Two views that make the difference from a monthly report.
On the left the cockpit, where a deviation becomes visible while it happens. On the right the list, where the deviation turns into a decision. Both are the same workplace, not two separate tools. The tabs are switchable.
Revenue 7 days€128,400
Margin18.4 %
Returns6.1 %
Fee change at one marketplace. 34 items affected, 11 of them below target margin.
Revenue 7 days€71,900
Margin14.2 %
Buy box share62 %
The decline comes almost entirely from one marketplace. Price proposals are ready for approval.
Revenue 7 days€38,600
Margin31.8 %
Abandonment68 %
The own shop carries the overall margin. The only thing standing out here is checkout abandonment.
Spend 7 days€9,240
Revenue per euro3.1
Without revenue2 campaigns
Two campaigns have run six days without revenue. A proposal to pause them is in the list on the right.
When a metric tips, you see it here first
Metrics across every channel side by side, the threshold as a line in the trend, the anomaly marked exactly where the curve crosses it. The tabs are switchable.
Price Raise prices below target margin ApproveReject
Stock Coverage 9 days, lead time 21 ApproveReject
Ads Campaign without revenue for 6 days ApproveReject
Price Competitor undercutting persistently ApproveReject
Now means: it affects margin or availability within this week.
Stock Prepare reorder ApproveReject
Listing Images below minimum resolution ApproveReject
Ads Shift budget to campaigns that carry ApproveReject
Returns Return rate above target ApproveReject
This week means: plannable, but not to be left lying. Usually procurement or content.
Listing Standardise attributes ApproveReject
Range Review slow movers for delisting ApproveReject
Process Goods receipt: discrepancies accumulating ApproveReject
Structural means: no rush, but otherwise the effort returns every month.
Done Price adjustment approved · procurement
Done Reorder triggered
Rejected Promotional stock running out · reason logged
Done Campaign paused
23 items handled in the last 30 days
Average time in the list: 1.4 days
Rejected with a reason: 5 of 28
The deviation becomes a decision
Prioritised, every proposal with its reasoning. Accepted, it becomes a task with an owner and a deadline, instead of a message nobody finds again.
Abstracted representation with invented values. Which metrics, thresholds and priorities apply in your installation is something we define together.
Where it sits
One knows the customers, the other knows the channels.
The monitor sits beside the Customer Intelligence Hub. Both share platform, sign-in and operation, and both work on the same principle: observe and propose, people decide.
Culture
Enable people, do not replace them.
Agents
Automate processes, create room to work.
Knowledge
Secure experience and make it usable.
Content
Scale communication, on brand and on quality.
Foundation · Data basis
Normalised channel data as context for every module. This is where the monitor sits.
Foundation · Operation and sovereignty
Cloud, hybrid or on-premise, on the Local AI Server if you wish.
Modules that build on the channel data
Customer Intelligence HubThe customer view beside it
Content CreatorContent for the channels
Agent-as-a-ServiceTakes over recurring runs
Reduziertes CRMQuotes from the conversation
Corporate MemorySourced knowledge as context
Echtzeit-OrchestrierungReacts to process changes
The monitor is built to be industry-neutral. It is most densely proven today in retail with several sales channels, because that is where the number of portals and the speed of change are greatest.
Operation and data sovereignty
Your figures stay your figures.
Revenue, margin and stock are among the most sensitive data a company holds. Which is why you decide where they live.
Cloud
Operated in European data centres, with monitoring and updates during live operation. The fastest route to the first cockpit.
Hybrid
Sensible when merchandise management and costing stay in your own network while the evaluation across them runs together.
On-premise
Entirely in your own network, on the Local AI Server if you wish. Evaluation by language models then stays in the building too.
One quote says more than many promises
“The biggest effect was not the dashboard, it was that the system speaks up on its own. We now react within days instead of on a monthly rhythm, and you can see it on exactly the items we make money with.”
Head of E-Commerce, Brand manufacturer with multichannel distribution
Pricing
One setup, one predictable operation.
Tiered by connected channels and the scope of observation. Setup covers connection, normalisation, thresholds and onboarding the team.
| Package | For whom | Scope * | Setup * | Operation * |
|---|---|---|---|---|
| Starter | First overview | up to 3 channels · up to 5,000 item variants · hourly retrieval · metrics and warnings | from €6,900 | €199 / mo. |
| Business | Operational steering | up to 8 channels · up to 50,000 variants · anomaly detection · proposals · ticket system | from €14,900 | €399 / mo. |
| Pro | Multichannel at scale | unlimited channels · variants and retrieval interval by agreement · price proposals · agent interface | from €24,500 | €790 / mo. |
CorporateSeveral brands or national subsidiaries, a dedicated operating environment or particular requirements for evidence: on request.
Channels and connections
The strongest lever in the price. Every connection brings its own interfaces, limits and quirks. The channels of the package are included, each further one costs from €1,200 setup and €39 per month.
Data volume and retrieval interval
Item variants times channels times retrievals per day is the actual load. Hourly instead of daily multiplies the volume twenty-four times, which is why the interval is in the quotation and not in a footnote.
History and retention
Twenty-four months of metric history are included. Anyone wanting to compare across several seasons books the extension at €49 per additional year and month.
Operation includes maintenance, updates, upkeep of the connections and a monthly quota for AI usage. Fees of the connected portals and server and hosting costs are billed separately.
* Guide values. Scope, volumes and prices are adapted to your actual needs in the quotation, because the number of channels, the data volume and the retrieval interval drive the effort.
All prices are net, plus statutory VAT.
Frequent questions
What decision makers ask first.
Does the system change prices by itself?
No. It produces proposals with reasoning and waits for a decision. For narrowly defined recurring cases an automation can be set up, but that is a deliberate approval in the individual case and not the default.
Does this work without marketplaces?
Yes. The principle is channel-independent: collect metrics, make them comparable, report deviations. Marketplaces are the most densely proven case today because that is where the most systems run side by side.
How many systems have to be connected for it to carry?
Two are enough to see value, because comparing even two channels answers questions that were open before. The full value emerges when sales, stock and costs come together, because only then can margin be calculated soundly.
What happens when a portal changes its interface?
The run fails or delivers less, and both are noticed: an error is reported as an error, a silent volume drop as an anomaly. Adapting the connection is part of operation.
The first step
Two channels. Three months of history. An honest look back.
We connect two of your channels and run the observers over the history of recent months. After that you can see which anomalies you would have noticed earlier, and what that cost.