Private beta · Shopify
Obsidian Guard adds approval controls around risky refunds, fulfillment decisions, and post-payment order changes in Shopify.
Controlled
The action is routed through Obsidian Guard before execution.
Held
Fulfillment or another downstream consequence is paused before value moves.
Detected
The action happened outside the approved path and is detected where Shopify exposes the event.
Products
Start with refunds, add fulfillment controls, then extend review across post-payment changes and operational exceptions.
Protect money movement
Approve risky refunds before Shopify executes them through the protected Obsidian Guard path.
Protect inventory movement
Hold risky orders before inventory leaves, then release fulfillment after approval.
Protect operational trust
Review risky post-payment changes, bypasses, and operational exceptions.
How it works
Obsidian Guard does not replace Shopify permissions or claim to intercept every native action. It creates a protected path, pauses supported consequences, and records exposed bypass events for review.
Read getting started →Private-beta onboarding links your store and verifies the permissions required for supported protections.
Configure a supported rule, assign reviewers, and choose notification preferences.
Controlled requests wait for a decision; held operations pause; detected actions are surfaced for review.
Approval, rejection, execution, failure, and manual follow-up states appear in activity history.
Integrations
Obsidian Guard's first integration protects risky refunds, fulfillment decisions, and post-payment order changes in Shopify.
Request Shopify beta access →Obsidian Guard is extending its protected-action model to vendor changes, payment approvals, and financial operations in BILL.
Join the BILL interest list →Shopify availability is limited to approved private-beta participants and supported store configurations.
FAQ
Need implementation detail? The customer documentation explains setup, workflows, notifications, and troubleshooting.
Open Documentation →Obsidian Guard adds approval controls around risky Shopify refunds, fulfillment decisions, and post-payment changes before or after value moves, depending on what Shopify supports.
A protected action is a risky operation routed through an Obsidian Guard workflow so the right reviewer can approve or reject it and the outcome can be recorded.
Controlled actions are routed through Obsidian Guard before execution. Held actions pause a downstream consequence such as fulfillment. Detected actions happened outside the approved path and are visible where Shopify exposes the event.
No. Shopify permissions still govern what each person and app can do. Obsidian Guard adds an approval and evidence layer around supported operations.
No. Refund Guard controls refunds submitted through the protected Obsidian Guard path. A refund created directly in Shopify or another app may be detected as a bypass when Shopify exposes the event.
The request records the failed outcome and explains that manual follow-up may be required. An approval is not a guarantee that Shopify will accept the downstream operation.
The product includes notification options for email, Slack, Web Push, SMS, and WhatsApp. Availability depends on plan, configuration, recipient details, and provider delivery.
No. SMS and WhatsApp consume monthly mobile-alert credits. When the cap is reached and overage is not enabled, those channels pause until reset or allowance changes; other configured channels can continue.
Obsidian Guard and its Shopify integration are in private beta. Request access and the team will confirm fit, onboarding, and environment availability.
Shopify is in private beta and BILL is in development. Additional integrations will be announced only as they enter active development.
BILL support is in development and no public release date has been announced.
Private beta
Tell us which store actions matter, who should approve them, and where manual follow-up is acceptable.
Apply for early access