1
Store taking regular revenue that cannot wait for manual discovery.
Merchant plan
Built for an e-commerce team that wants to run its own monitoring directly €59 /month · Checkout every 3 min · pages 3 min · 60 monitors · AI included.
Recommended
Coverage, cadence and proof are framed when product, cart, checkout or payment steps break Niveau Business : Checkout every 3 min · pages 3 min · 60 monitors · AI included.

Store taking regular revenue that cannot wait for manual discovery.
E-commerce team needing multi-channel alerts and proof usable by a developer or provider.
WooCommerce journey where checkout needs finer monitoring than catalog pages.
Merchant documenting incidents to arbitrate maintenance, hosting, theme, plugin or payment issues.
Business covers a more complete journey: key pages, conversion funnel, checkout signals and useful revenue checks.
Checkout cadence reduces detection delay on the steps that actually block sales.
One month of data supports maintenance decisions and compares incidents with recent changes.
Email, Slack or Telegram depending on configuration: the right signal reaches the right channel without unnecessary customer data.
Incidents can become shareable proof: diagnosis, technical impact, affected step and recommendations.
Business can apply only authorized and reversible CashFlowCanary-scoped actions, then recheck the journey. Fixes requiring theme, payment gateway, hosting or human arbitration remain for the team or provider.
Business is the balanced merchant tier for moving from simple watch to operational handling without mixing notification, diagnosis and remediation.
Review the Business merchant scope before activation: price, perimeter, use cases, capabilities, proof, exclusions and support boundary.
Business is presented at €59 /month; this Business billing basis is visible before activation framing, so the merchant plan can be evaluated without hidden price assumptions.
Prioritize incidents by revenue impact, AI diagnosis and actionable reports. The Business merchant plan positioning explains the risk level this tier is built for and how it differs from the neighbouring offers.
Checkout every 3 min is the expected watch cadence for the checkout path in Business merchant. Business merchant uses that rhythm to notice revenue-step regressions without running a real payment or collecting card details.
pages 3 min is the page-monitoring rhythm for the merchant store in Business merchant. In Business merchant, it watches storefront availability and funnel context before the team escalates a checkout-specific incident.
60 monitors means the number of monitored checkpoints available for the merchant store attached to the account. In Business merchant, that coverage is allocated to the revenue signals this tier can realistically own: product, cart, checkout, payment, confirmation or selected technical endpoints.
AI included means Business can run the incident report, guarded AI intervention, checkout recheck and intervention report for the merchant store, without including card data or extending beyond the plan limits.
Store taking regular revenue that cannot wait for manual discovery. This Business merchant plan use case is included so buyers can decide whether the offer matches the operational situation, not only the price. For the Business merchant plan, it clarifies the store, portfolio, campaign or team context that should be validated before activation.
E-commerce team needing multi-channel alerts and proof usable by a developer or provider. This Business merchant plan use case is included so buyers can decide whether the offer matches the operational situation, not only the price. For the Business merchant plan, it clarifies the store, portfolio, campaign or team context that should be validated before activation.
WooCommerce journey where checkout needs finer monitoring than catalog pages. This Business merchant plan use case is included so buyers can decide whether the offer matches the operational situation, not only the price. For the Business merchant plan, it clarifies the store, portfolio, campaign or team context that should be validated before activation.
Merchant documenting incidents to arbitrate maintenance, hosting, theme, plugin or payment issues. This Business merchant plan use case is included so buyers can decide whether the offer matches the operational situation, not only the price. For the Business merchant plan, it clarifies the store, portfolio, campaign or team context that should be validated before activation.
Business covers a more complete journey: key pages, conversion funnel, checkout signals and useful revenue checks. For the Business merchant plan, it states the practical change in coverage, cadence, proof, client handoff, operational priority or plan boundary.
Checkout cadence reduces detection delay on the steps that actually block sales. For the Business merchant plan, it states the practical change in coverage, cadence, proof, client handoff, operational priority or plan boundary.
One month of data supports maintenance decisions and compares incidents with recent changes. For the Business merchant plan, it states the practical change in coverage, cadence, proof, client handoff, operational priority or plan boundary.
Email, Slack or Telegram depending on configuration: the right signal reaches the right channel without unnecessary customer data. For the Business merchant plan, it states the practical change in coverage, cadence, proof, client handoff, operational priority or plan boundary.
Incidents can become shareable proof: diagnosis, technical impact, affected step and recommendations. For the Business merchant plan, it states the practical change in coverage, cadence, proof, client handoff, operational priority or plan boundary.
Business can apply only authorized and reversible CashFlowCanary-scoped actions, then recheck the journey. Fixes requiring theme, payment gateway, hosting or human arbitration remain for the team or provider. For the Business merchant plan, it states the practical change in coverage, cadence, proof, client handoff, operational priority or plan boundary.
Business is the balanced merchant tier for moving from simple watch to operational handling without mixing notification, diagnosis and remediation. For the Business merchant plan, it states the practical change in coverage, cadence, proof, client handoff, operational priority or plan boundary.
60 monitors means the number of monitored checkpoints available for the merchant store attached to the account. In Business merchant, that coverage is allocated to the revenue signals this tier can realistically own: product, cart, checkout, payment, confirmation or selected technical endpoints.
Checkout 3 min is the expected watch cadence for the checkout path in Business merchant. Business merchant uses that rhythm to notice revenue-step regressions without running a real payment or collecting card details.
30-day history is the Business merchant retention window used to compare incidents, recent changes and recurring patterns. Business merchant keeps enough evidence to decide whether a break is isolated, repeated or linked to a maintenance window.
Email/Slack/Telegram/WhatsApp alerts means Business can run the incident report, guarded AI intervention, checkout recheck and intervention report for the merchant store, without including card data or extending beyond the plan limits.
PDF reports is the packaged Business incident handoff: affected step, observed signal, timeline and next action. the merchant team can share the Business report with the people fixing the store.
Price: €59/month for Business merchant plan. This comparison item is repeated on the Business merchant plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
Key pages / monitors: 60 for Business merchant plan. This comparison item is repeated on the Business merchant plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
Page frequency: 3 min for Business merchant plan. This comparison item is repeated on the Business merchant plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
Checkout frequency: 3 min for Business merchant plan. This comparison item is repeated on the Business merchant plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
Alerts: Email + Slack/Telegram/WhatsApp for Business merchant plan. This comparison item is repeated on the Business merchant plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
History: 30 d for Business merchant plan. This comparison item is repeated on the Business merchant plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
Evidence pack: Advanced for Business merchant plan. This comparison item is repeated on the Business merchant plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
Exports: PDF for Business merchant plan. This comparison item is repeated on the Business merchant plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
Local AI diagnosis credits/month: 400 for Business merchant plan. This comparison item is repeated on the Business merchant plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
AI incident intervention: Included for Business merchant plan. This merchant plan uses the AI workflow inside the Business scope only: incident report, guarded intervention, checkout recheck and intervention report, without extending the listed cadence, monitor count or support boundary.
Synthetic checkout quota: Not included for Business merchant plan. This comparison item is repeated on the Business merchant plan detail page so the public comparison table and the offer description stay aligned; it explains the visible catalogue promise before activation, without adding hidden entitlement beyond the listed plan scope.
Very critical checkouts where one minute of doubt justifies Premium escalation. This exclusion is part of the Business merchant plan description because it prevents Business from being read as a universal promise. It tells buyers when the Business merchant plan is too small, too advanced or not aligned with the expected operating model.
Business detects, prioritizes and documents incidents at the cadence and scope described above. For the Business merchant plan, remediation stays with the agency, merchant, hosting provider, payment provider or development team, so this tier sells proof and coordination rather than an automatic repair guarantee.
Recommended is the visible catalogue marker attached to Business for this merchant plan; it explains the commercial recommendation without adding any hidden entitlement beyond the listed scope.
Each Business merchant capability is explained in operational terms so activation decisions are based on scope, cadence, proof and limits.
Business covers a more complete journey: key pages, conversion funnel, checkout signals and useful revenue checks. In the Business merchant plan, this item clarifies the operational scope presented before activation: coverage, cadence, proof, handoff or plan limits.
Checkout cadence reduces detection delay on the steps that actually block sales. In the Business merchant plan, this item clarifies the operational scope presented before activation: coverage, cadence, proof, handoff or plan limits.
One month of data supports maintenance decisions and compares incidents with recent changes. In the Business merchant plan, this item clarifies the operational scope presented before activation: coverage, cadence, proof, handoff or plan limits.
Email, Slack or Telegram depending on configuration: the right signal reaches the right channel without unnecessary customer data. In the Business merchant plan, this item clarifies the operational scope presented before activation: coverage, cadence, proof, handoff or plan limits.
Incidents can become shareable proof: diagnosis, technical impact, affected step and recommendations. In the Business merchant plan, this item clarifies the operational scope presented before activation: coverage, cadence, proof, handoff or plan limits.
Business can apply only authorized and reversible CashFlowCanary-scoped actions, then recheck the journey. Fixes requiring theme, payment gateway, hosting or human arbitration remain for the team or provider. In the Business merchant plan, this item clarifies the operational scope presented before activation: coverage, cadence, proof, handoff or plan limits.
Business is the balanced merchant tier for moving from simple watch to operational handling without mixing notification, diagnosis and remediation. In the Business merchant plan, this item clarifies the operational scope presented before activation: coverage, cadence, proof, handoff or plan limits.
The visible Business merchant pricing-card elements are expanded here: billing basis, positioning and scope limits.
Business is part of the public Business card and is repeated here so the merchant plan can be evaluated without ambiguity.
€59 /month is the public Business price shown before activation. The Business merchant tier is attached to one monitored store, which keeps the checkout surveillance budget readable for the internal team.
Prioritize incidents by revenue impact, AI diagnosis and actionable reports. explains why Business exists in the merchant plan catalogue and when this tier should be preferred over the others.
Checkout every 3 min is the Business merchant plan commercial boundary visible on the pricing card. It tells the team what Business merchant plan includes before any custom framing or upgrade discussion.
pages 3 min is the Business merchant plan commercial boundary visible on the pricing card. It tells the team what Business merchant plan includes before any custom framing or upgrade discussion.
60 monitors is the Business merchant plan commercial boundary visible on the pricing card. It tells the team what Business merchant plan includes before any custom framing or upgrade discussion.
AI included is the Business merchant plan commercial boundary visible on the pricing card. It tells the team what Business merchant plan includes before any custom framing or upgrade discussion.
Recommended is a visual recommendation marker for Business merchant plan only. It does not change the contractual limits of Business; the detailed scope above remains the source of truth.
Business merchant details what the buyer can expect to receive, share and verify when an incident occurs.
60 monitors means the number of monitored checkpoints available for the merchant store attached to the account. In Business merchant, that coverage is allocated to the revenue signals this tier can realistically own: product, cart, checkout, payment, confirmation or selected technical endpoints.
Checkout 3 min is the expected watch cadence for the checkout path in Business merchant. Business merchant uses that rhythm to notice revenue-step regressions without running a real payment or collecting card details.
30-day history is the Business merchant retention window used to compare incidents, recent changes and recurring patterns. Business merchant keeps enough evidence to decide whether a break is isolated, repeated or linked to a maintenance window.
Email/Slack/Telegram/WhatsApp alerts means Business can run the incident report, guarded AI intervention, checkout recheck and intervention report for the merchant store, without including card data or extending beyond the plan limits.
PDF reports is the packaged Business incident handoff: affected step, observed signal, timeline and next action. the merchant team can share the Business report with the people fixing the store.
Very critical checkouts where one minute of doubt justifies Premium escalation.
Business merchant detects and documents incidents at its planned cadence. In Business merchant, AI intervention is bounded to allowed, logged actions; anything outside that scope remains with the provider, hosting, payment or code owners.
Business gives the merchant team a clear priority, affected step and evidence usable by the person who fixes the store.
Checkout every 3 min · pages 3 min · 60 monitors · AI included. Business sets how close the watch sits to the checkout and payment path.
Business does not collect card data. Business AI actions, when triggered, stay limited to authorized playbooks and logged checks; it is not a universal repair guarantee.
Example: the store is online but the cart-to-checkout path no longer converts. Business gives the merchant team the affected step, priority and proof before the issue is discovered in revenue numbers.
Business : We verify the monitored site, checkout risk level and useful channels before activation.