A read-only health layer across four commerce systems
When failures are relational, not isolated
Catalog sync, configurator recommendations, Webflow CMS, and SureCart data all depend on each other. When one drifts out of alignment with the others — a stale sync, a configurator referencing a SKU that no longer exists — the failure often isn't visible from any single service's own health check.
Catching that requires something that can see across all of them at once.
The implementation goal
Build a lightweight Cloudflare Worker that can report on the health of the sync Worker, the configurator Worker, and their relationship to Webflow and SureCart — all from dedicated, read-only routes.
A control-room Worker with no write access to anything
The supervisor calls existing service endpoints, compares their state, and surfaces mismatches through simple health routes, giving the team a single place to check whether the commerce stack is actually in sync.
Because it never writes anywhere, adding it introduced no new failure modes.
Our other projects
The brief was to build a lightweight control-room service that could report on cross-system health without becoming yet another writer inside the commerce stack.
When catalog sync, configurator recommendations, Webflow CMS, and SureCart data all interact, the most common failures are relational — two services quietly disagreeing — rather than a single endpoint being down. Diagnosing that by hand means checking multiple services separately and comparing state manually.
The supervisor had to stay strictly read-only. It could not write to SureCart, Webflow, or any of the other Workers it monitors — its entire value comes from being safe to add without introducing new risk.
SoFlow built a dedicated Cloudflare Worker supervisor exposing health routes for system-wide checks, a sync Worker catalog summary, and a configurator endpoint summary — all read-only, with optional token protection.
The supervisor calls the existing read-only endpoints of the sync and configurator Workers, optionally authenticates with a supervisor token, and reports any mismatches it finds — without writing to Webflow, SureCart, or any dependent service.
- Read-only cross-service health reports across sync, configurator, Webflow, and SureCart
- Dedicated sync Worker catalog health summary
- Dedicated configurator endpoint health summary
- Optional supervisor-token protection on routes
- Zero write access to any monitored system
Operational reliability across the commerce stack became something the team could check in one place, rather than infer from separate services, with no added write risk.
- Dedicated routes: /health/system, /health/sync, and /health/configurator
- README explicitly documents the service as read-only
- No write permissions granted to any monitored system
Isn't a monitoring tool just overhead?
Not when the systems it watches interact this closely. Catalog sync, configurator recommendations, Webflow CMS, and SureCart data all depend on each other staying aligned, and most failures in that kind of setup are relational — a mismatch between two services — rather than a single endpoint going down. A read-only supervisor catches exactly that kind of failure before it becomes a customer-facing problem, and adds no risk because it never writes anything itself.
Why put this in Webflow if external code is involved?
Webflow is one of the systems being checked, not where the checking happens. The supervisor runs as its own Cloudflare Worker so it can call the other services' health endpoints independently, without any of that logic needing to live inside Webflow.
What is needed before publishing?
A redacted sample health report or endpoint response that demonstrates the mismatch detection without exposing internal system details.
This work shows SoFlow treats custom builds as systems that need ongoing observability, not just code that ships and gets left alone after launch.
Isn't a monitoring tool just overhead?
Not when the systems it watches interact this closely. Catalog sync, configurator recommendations, Webflow CMS, and SureCart data all depend on each other staying aligned, and most failures in that kind of setup are relational — a mismatch between two services — rather than a single endpoint going down. A read-only supervisor catches exactly that kind of failure before it becomes a customer-facing problem, and adds no risk because it never writes anything itself.
Why put this in Webflow if external code is involved?
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Catalog and configurator issues could only be checked by visiting each service's own endpoint individually, with no single view of whether they still agreed with each other.
The platform gained one central, read-only surface for checking relational health across the sync and configurator Workers, Webflow, and SureCart.
Webflow can display public pages and content, but it has no way to check whether the Worker services behind the commerce stack — sync, configurator, and the data they depend on — are still aligned with each other. That kind of cross-service health check has to live outside Webflow, in code built specifically for it.
