MIZ OKI Signal for Shopify — App Listing Copy

Document status: approved-copy candidate; merchant-facing wording only
Product status: Preview · in development for anticipatory intent and advanced Growth Control surfaces
Distribution posture: direct/unlisted pilot distribution before any public Shopify App Store release
Canonical sources: SIGNAL_SHOPIFY_MASTER_v4.md and SIGNAL_OVERVIEW_v5.md

App name

MIZ OKI Signal

Short description

Connect Shopify commerce truth to governed marketing decisions, margin-aware reporting, and a human-approved 90-Day Growth Control Pilot.

One-line value statement

See what changed, what is likely incremental, what it means after real costs, and what should be reviewed next—without surrendering control of your store or advertising accounts.

Full description

MIZ OKI Signal connects Shopify orders, refunds, products, inventory, fulfillment and customer-consent events with the merchant's approved marketing and analytics stack.

The app is designed for an observe-first operating model. It helps a merchant assemble evidence, reconcile contribution economics, identify measurement gaps, and review governed recommendations. It does not promise a performance outcome and it does not make an advertising-platform change merely because a recommendation exists.

During the standard 90-Day Growth Control Pilot, the merchant and MIZ OKI team progress through three governed phases:

• Observe: connect the approved stack, validate data quality, establish cost and baseline inputs, and define the Decision Jobs to study. No live execution changes.
• Validate: register qualified experiments, reconcile margin against the merchant's own books, and grade predictions against outcomes.
• Recommend: deliver contextualized decision proposals with evidence, constraints, rollback information, and named human approval.

Advanced anticipatory-intent capabilities are labeled Preview · in development. They use privacy-bounded, content-free interaction evidence and governed creative metadata; they are not mind reading, and they never authorize an action by themselves.

Key capabilities

Commerce truth

• Ingest approved Shopify order, refund, product, fulfillment and inventory events.
• Reconcile revenue with merchant-declared COGS, shipping, payment, pick-and-pack, return and other approved cost inputs.
• Preserve source, tenant, consent and retention context for governed processing.

Connector onboarding

• Connect approved marketing, analytics and lifecycle platforms through tenant-scoped authorization.
• View connection status, account identifiers where safe, scopes, verification time and health.
• Keep raw secret values out of ordinary onboarding records and read responses.

Measurement and causal evidence

• Define the Decision Jobs the pilot will evaluate.
• Register holdouts before first exposure when causal activation is required.
• Package estimates, uncertainty, refutation evidence and decision history into auditable records.

Margin-aware recommendations

• Evaluate recommendations against validated merchant costs and inventory posture.
• Keep net-yield and measurement writebacks off until their own evidence and approval gates are satisfied.
• Refuse or withhold proposals when required evidence or constraints are missing.

Human-controlled decisioning

• Route material proposals through the Decision Control Plane and named human approval.
• Keep advertising accounts merchant-owned.
• Preserve kill switches, tenant allowlists, policy checks and rollback paths.
• Never allow an optimizer, scorer or scheduler to call an advertising platform directly.

Preview · in development: anticipatory intent evidence

• Use content-free sequences such as dwell, scroll, swipe, partial-watch and form-lifecycle states within a closed signal vocabulary.
• Produce explanation payloads and uncertainty rather than a bare score.
• Reject prohibited signal classes, including audio capture, keystroke dynamics, gaze tracking and fine-grained location.
• Keep prediction in shadow mode until a registered holdout and real calibration evidence exist.

What the app does not do

MIZ OKI Signal does not:

• guarantee revenue, profit, ROAS, lift or cost reduction;
• read a person's thoughts or claim telepathic insight;
• capture prohibited audio, keystroke, gaze or fine-location signals;
• invent COGS, treasury constraints, inventory thresholds or creative rights;
• make an advertising-platform change without the governed authorization and action-runner path;
• treat a platform-reported conversion as proof of incrementality;
• flip Preview labels based on synthetic or illustrative data.

Merchant setup

A merchant completes setup in the authenticated onboarding flow:

1. Confirm the organization and approved pilot scope.
2. Select the Decision Jobs and any F1–F5 frontier surfaces to evaluate.
3. Authorize the required connectors and verify their health.
4. Enter and validate COGS, fulfillment, payment, return and other approved economics.
5. Declare any required treasury, LTV, inventory, geo and creative-access inputs.
6. Review named gaps and the immutable onboarding snapshot.
7. Receive human approval for Observe mode.

Saving onboarding information is not pilot activation. Missing information remains not_configured; it is never inferred.

Shopify permissions and data use

The requested Shopify scopes are limited to the data streams and installation operations documented in the reviewed app configuration. The installation flow validates the shop domain, OAuth state and callback signature before token custody and registry activation.

Operational and compliance webhooks are handled through governed routes. Customer/person-related processing remains consent-gated and subject to retention and erasure contracts. The app deactivates shop access on uninstall and preserves the audit state required for governed cleanup.

Exact permissions may change only through a reviewed scope change that is visible to merchants and may require reauthorization.

Security and privacy summary

• OAuth is preferred where available.
• Non-OAuth credentials are stored in tenant-scoped Secret Manager records.
• Raw credentials are never returned after submission.
• Sensitive-category and prohibited-signal rules fail closed.
• Tenant isolation is enforced across onboarding and connector records.
• Material decisions retain evidence, policy and approval context.
• Merchant data is not used to make cross-tenant decisions.

Support

Support: support@mizoki3.com
Pilot inquiries: hello@mizoki3.com
Security or privacy requests: use the contact identified in the merchant's onboarding record or the governed support channel.

App review notes

• The product begins in direct/unlisted pilot distribution. Public App Store submission is a later distribution gate.
• The app's default posture is Observe; advanced writeback and execution surfaces remain off unless independently approved.
• Any screenshots or examples showing values must label them ILLUSTRATIVE, SIMULATED, PREVIEW, or TARGET according to the claims ledger.
• Anticipatory intent copy must always retain Preview · in development framing and must never use mind-reading language.
• Merchant-owned ad accounts and named human approval remain binding product rules.

Prohibited listing edits

Do not add:

• outcome guarantees or unverified percentages;
• “AI reads your customers' minds” or equivalent language;
• claims that recommendations automatically execute;
• claims that the app replaces the merchant's agency, finance team or legal/privacy obligations;
• a public availability statement before distribution and real-install evidence are verified.