Company workspaces, customer assignments and current permissions govern access. Connected services receive the information needed for the workflows you enable.
Workspace requests check current membership and permissions. Customer users are limited to assigned accounts. Price visibility is enforced in server responses as well as the interface, and suspended memberships lose workspace access.
Saved provider credentials and stored document files are encrypted by the application. Authorized requests retrieve private invoices, labels and packing slips; these documents are not published as open downloads. This does not mean every business field has application-level encryption.
Orders use explicit transitions and recorded fulfillment stages. A simulation creates no accounting or postage transaction. Unknown provider outcomes pause for reconciliation, and saved receipts help prevent repeating an already confirmed action.
Owners manage company access and exports. Staff roles can carry specific grants and customer restrictions. Buyer administrators and employees have separate capabilities, including whether prices are visible.
Connections and service configuration determine which flows are used. Review provider terms and your own obligations before enabling them.
OAuth authorizes the company’s accounting connection. Customer and product details can be imported; fulfillment can create invoices and write shipping/tracking references. Customer synchronization runs from QuickBooks to V2 only.
Shipping operations send recipient, origin, parcel and service details to request rates or purchase labels. An API-key connection, shipping policy and spending limit are required. Live carrier acceptance remains pending.
Unstructured intake can send order message text to the configured OpenAI extraction service. Recognized structured text is parsed locally by the application without an AI request. Do not include unrelated sensitive information in order messages.
Whapi receives access to an authorized WhatsApp channel. Selected-group rules govern intake, including customer mappings and review policy. Temporary recoverable source text expires after seven days; accepted intake and order history are separate records. Channel delivery is still being validated.
When email is configured, Resend delivers verification, recovery and explicit invitation messages. Proposed software subscriptions use Stripe-hosted test flows; commercial checkout and prices remain unpublished.
This page describes implemented application controls. It is not a certification or service-level agreement. Read the Privacy Policy and Terms of Service for information handling and authorized use. Restore drills, independent security review and commercial launch requirements remain separate acceptance work. No SOC 2, ISO 27001, HIPAA or regulatory compliance claim is made.
Set the company currency, add representative customer and catalog records, and complete a simulation. Review roles, price visibility and delivery details before connecting real services.
Owners can suspend memberships and manage invitations. Disconnect unused provider accounts and check current mappings before enabling automation.
Set up your company, add a customer and your catalog, then practice the workflow with a simulation.