A locked-down admin surface for SureCart product metadata
Metadata tools without a safety net
Commerce teams running on metadata-driven catalogs eventually need an operator tool for product and variant data - but a hand-rolled admin script that can patch live commerce records with no UI, no feature flag, and no access model is a liability rather than a convenience.
Turn a legacy script into a governed platform service
Migrate the existing metadata Worker into a named, documented platform service that keeps the browser admin UI, the protected SureCart proxy routes, and product/variant inspection - while adding an explicit gate around any metadata write.
A hardened SureCart metadata Worker with writes off by default
Operators get a browser UI for inspecting SureCart product and variant metadata through authenticated proxy routes, with the ability to write changes only when an admin secret and a metadata-write flag are both present.
Our other projects
The brief was to make SureCart product and variant metadata easy to inspect and safely maintain, without ad hoc API calls or the SureCart API key ever touching the browser.
Metadata-driven commerce systems need operator tooling, but direct admin scripts are risky the moment they can patch products or variants without a clear UI, feature flag, or access model behind them.
The admin surface handles live commerce data, so public screenshots must use fake or redacted values, and metadata writes stay disabled unless specific environment flags are deliberately enabled.
SoFlow migrated the legacy metadata Worker into a clearer platform service: the same browser admin UI, the same protected SureCart API proxy routes, product and variant inspection, and gated metadata write behavior, now with a documented migration path and operator workflow.
The Worker serves the admin UI and an embeddable loader, requires an admin secret on every request, proxies SureCart read routes, and only allows a metadata write through when both authentication and a write-enable flag are present at the same time.
- Browser UI for SureCart product and variant inspection
- Admin-secret protected JSON API routes
- Metadata writes disabled by default
- Separate flags for debug mode, metadata writes, and test product creation
- Documented migration notes and operator workflow
Commerce operators get a safer way to inspect and maintain metadata, with sensitive writes kept behind explicit, intentional gates rather than open by default.
- Production migration completed and verified
- Metadata writes disabled by default across environments
- Cloudflare Access configuration documented as a required hardening step before wider rollout
Could this admin tool be rebuilt for a different SureCart store?
Yes. The pattern - a protected proxy Worker with a browser admin UI and write routes gated behind secrets and feature flags - is store-agnostic. Reusing it means re-provisioning the admin secret, mapping the new store's product and variant fields, and setting up Cloudflare Access for that team.
Why put this in Webflow if external code is involved?
Webflow is the public storytelling and CMS layer. External code should stay in the app, Worker, or integration layer where it can be versioned, secured, and tested.
What is needed before this becomes a full case study?
A sanitized admin UI screenshot with fake or redacted product data, and confirmation that Cloudflare Access is fully configured, before this is promoted beyond a proof card.
This proves SoFlow can build admin tooling where operational power over commerce data stays separated from the public Webflow experience - and gated behind explicit, auditable controls.
Could this admin tool be rebuilt for a different SureCart store?
Yes. The pattern - a protected proxy Worker with a browser admin UI and write routes gated behind secrets and feature flags - is store-agnostic. Reusing it means re-provisioning the admin secret, mapping the new store's product and variant fields, and setting up Cloudflare Access for that team.
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
Metadata inspection and maintenance ran on a legacy Worker with an unclear name and a thinly documented admin surface.
The tool now lives under a clear platform name, with a documented access model and write behavior that defaults to safe.
Webflow can present commerce content beautifully, but it has no mechanism for safely inspecting or patching SureCart product metadata. That kind of operational access belongs in a protected Worker admin surface, not the CMS layer.
