Production Inbox

Support

Last updated: August 2, 2026

Use this page to understand the bounded workflow, prepare a safe support request, or report a security concern without exposing credentials or unnecessary customer information.

Current availability

Production Inbox is a private development build. It is not accepting store installations, payments, or production support requests until the dependency security gate and Shopify review preparation are complete.

Before contacting support

  • Confirm you are signed into the correct Shopify store and have permission to use installed apps.
  • Check whether the app displays a synchronization pause, bounded-sync continuation, or failed order-update banner.
  • Review Production rules before treating a blank customization value as blocking.
  • Do not send passwords, verification codes, Shopify access tokens, full payment details, or unnecessary customer identity information.

What to include

  • The permanent shop domain, but no account password or login code.
  • The approximate time, interface language, page, and action where the issue occurred.
  • The Shopify order display number and affected product or SKU when needed; redact unrelated buyer information.
  • A screenshot of the app message if it does not expose private customer or credential data.

Synchronization and production status

Interactive synchronization is intentionally bounded. When more open orders remain, use Continue sync for the next batch. Very large imports stop safely instead of running an unbounded request. Automatic order updates retry a limited number of times and then show a visible recovery action.

Ready, Making, and Done are merchant-controlled workflow states. Shopify order updates do not silently overwrite Making or Done work. Reopen is an explicit merchant action.

Privacy requests

Verified Shopify customer-data requests appear inside the authenticated app for tenant-scoped NDJSON export. Customer and shop redaction webhooks delete applicable app-owned records. Privacy exports should be delivered only through the merchant's required privacy workflow.

Security reports

Report suspected cross-store access, exposed credentials, webhook abuse, data leakage, or unauthorized production changes promptly. Do not publicly disclose exploitable details before the operator has had a reasonable opportunity to investigate and remediate.

Contact

The release support email will appear below after a real operator-controlled address is configured. No placeholder address is accepted by the release gate.