Skip to main content
Zunn
Get Started
MODULE 66 SPECIFICATION/Technical & Operational Q&A

Clear Answers to Technical, Operational, and Billing Questions.

Everything you need to know about how Fihi executes safe order actions, trains on your store policies, and integrates into your existing commerce stack.

Connect with an Engineer
MODULE 66 · DOMAIN FAQ

Clear Answers to Technical, Operational, and Billing Questions.

Everything you need to know about how Fihi executes safe order actions, trains on your store policies, and integrates into your existing commerce stack.

Fihi implements a dual-layer safety architecture combining deterministic boundary verification and customer identity authentication. First, the AI cannot execute any financial mutation (refunds, cancellations, discount codes) unless the order satisfies explicit merchant-defined boundary rules—such as requiring the order to be in an unfulfilled status and within a strict timeframe (e.g., within 60 minutes of checkout). Second, for unauthenticated channels like Instagram DMs or website chat, Fihi dispatches a one-time cryptographic 6-digit passcode (OTP) to the customer's verified phone or email on file before unlocking order modifications. If any verification step fails, the request is immediately escalated to your human team.

Category: store-safetyGrounded in verified store invariant
Autonomous Storefront Operations Guarantee100% Policy Bound

Zunn Fihi is an enterprise commerce workbench engineered with deterministic boundaries. It cannot issue refunds above your authorized ceiling, mutate fulfilled consignments, or promise unauthorized inventory. For high-risk or ambiguous requests, tickets are escalated to your human team with pre-drafted summaries.