← Trust Centre
Policy
Workflow Availability Record
“Live” describes a crew: all six crews work with merchants today. Availability describes a workflow: what a crew can read, propose, write or schedule on a given platform. This record is the source every present-tense capability claim on vortexiq.ai resolves to. Where a page and this record disagree, the record governs and the page is corrected.
How to read this record
- Surface is what the workflow touches. Read: the crew observes through the Vortex IQ control plane and makes no change. Proposal: the crew prepares a change for a person to review. Write: an approved change is applied to a store, ad account or repository. Automation: the workflow runs on a trigger or schedule inside an approved scope.
- Available now: verified for the stated public capability. Available on request: needs technical or commercial confirmation for your platform or account before it is promised. Private validation: not generally available. Planned: roadmap only, with no implied release date. Not verified: no public capability statement; treat as unavailable until confirmed in writing.
- Platform names refer to the merchant's commerce platform unless the row says otherwise. Presence of a connector in the catalogue is not an availability claim; connector capability is confirmed during setup.
- Human approval is the default for every write. A merchant may enable bounded automation for agreed workflows. No row below removes that gate.
Store Health, the Pulse crew
| Workflow | Surface | Platforms | Status | Notes |
|---|---|---|---|---|
| Store health scan: storefront, catalogue, settings | Read | Shopify, BigCommerce, Adobe Commerce | Available now | Scan coverage depends on the connectors and permissions granted to the workflow, confirmed during setup. |
| Store health scan | Read | WooCommerce | Available on request | Confirm connector read coverage before promising. |
| Finding enrichment: why, before and after, revenue estimate, exact change; verifier challenge | Proposal | All platforms above | Available now | Revenue impact is an estimate attached to the finding, not a measured result. Unverified findings are held. |
| Chat with the Health Lead, edit the ticket, send to Store Development | Proposal (Ask Viq) | All platforms above | Available now | |
| Scheduled scans and the daily money check that raises alerts | Automation | All platforms above | Available now | Runs inside the scope agreed at setup. |
| Applying a fix | Write | Any | Not this crew | Pulse never applies anything. See Store Development. |
SEO and AI Visibility, the Beacon crew
| Workflow | Surface | Platforms | Status | Notes |
|---|---|---|---|---|
| Catalogue and content read; 12-step SEO and GEO run; proposed titles, descriptions, structured data | Read, Proposal | Shopify, BigCommerce, Adobe Commerce, WooCommerce | Available now | Any catalogue Vortex IQ can read. 10,549 product records enhanced to 10 September 2026; see the claims methodology for what that counts. |
| Content briefs and drafts for category and buying-guide pages | Proposal | Any | Available now | Your specialist reviews and refines before anything publishes. |
| AI readiness check: what Google, image search and AI assistants can see | Read | Any public storefront | Available now | A technical check. Not a promise of citations. |
| Publishing approved metadata and content through the content lane | Write | BigCommerce | Available now | Ships via Store Development with a RollbackPro undo point. |
| Publishing approved metadata and content | Write | Shopify, Adobe Commerce, WooCommerce | Available on request | Publishing path and rollback confirmed per connector during setup. |
| Scheduled SEO and GEO runs with review before publish | Automation | As above | Available now |
Ads Performance, the Compass crew
| Workflow | Surface | Platforms | Status | Notes |
|---|---|---|---|---|
| Live account read; eight optimiser rules; six cross-channel diagnoses with store data | Read, Proposal | Meta Ads | Available now | Every recommendation becomes a finding with the reporting period and metrics behind it. |
| Live account read and recommendations | Read, Proposal | Google Ads | Available on request | Confirm the connected account, data sources and action modes during setup. |
| Governed writes: pause, activate, budget change, creative, budget shift | Write | Meta Ads | Available now | Each write sits behind approval and a verified-and-confirmed gate with rollback. |
| Governed writes | Write | Google Ads | Available on request | |
| Scheduled audits and budget shifts inside an approved scope | Automation | Meta Ads | Available now | |
| Spend, saving or return outcomes | None | Any | Not promised | Results are recorded per account, not forecast. |
Store Experience, the Prism crew
| Workflow | Surface | Platforms | Status | Notes |
|---|---|---|---|---|
| Shopper journeys in a real browser: search, product, cart, checkout, with screenshots and a verdict per journey | Read (browser) | Any storefront reachable in a browser, staging or live | Available now | A passing check is a record, not a finding. |
| Journeys behind a login | Read (browser) | As above | Available now | Credentials are used once for the run and are not stored. |
| Scheduled journey checks before and after releases | Automation | As above | Available now | |
| Failed journey handed to Store Development as a finding | Proposal | Per the Store Development rows | Available now | Whether the fix can be applied follows the Store Development platform rows. |
| A/B experiments | Write | Any | Planned | Not part of today's runs. No release date implied. |
Store Development, the CodeCraft crew
| Workflow | Surface | Platforms | Status | Notes |
|---|---|---|---|---|
| Finding ingest from every crew; classification into API fix, content, code or guided | Proposal | All | Available now | The lane chosen is shown on every ticket. |
| API fix lane: setting or content change applied after approval, with an undo point | Write | BigCommerce | Available now | Undo point through RollbackPro. |
| API fix and content lanes | Write | Shopify, Adobe Commerce, WooCommerce | Available on request | Confirmed per connector. Undo point stated per change. |
| Code lane: scoped theme change, challenged by a separate review crew, opened as a pull request | Write (repository) | Any platform with a theme repository CodeCraft can open pull requests against | Available now | Requires repository access. Merge and deployment stay with your developer. |
| Guided lane: numbered steps for the person who can make the change | Proposal | Any | Available now | Used when no API path exists. Never a dead end. |
| Result check by the crew that raised the finding | Read | All | Available now | A proposal prepared, a pull request opened, a change applied and a result checked are four different outcomes and are named as such. |
Migration and Recovery, the Bridge crew
| Workflow | Surface | Platforms | Status | Notes |
|---|---|---|---|---|
| Catalogue migration with scope, starting counts, run tracking and destination counts (BC Migration) | Write (destination) | Destination: BigCommerce | Available now | Sources confirmed per project. Exceptions listed for a person to resolve. Launch sign-off stays with your team. |
| Catalogue migration to other destinations | Write (destination) | Shopify, Adobe Commerce, WooCommerce destinations | Available on request | |
| Restore points and rollback of a supported change (RollbackPro) | Write | BigCommerce, Shopify | Available now | Each change states whether it has a restore point. |
| Restore points | Write | Adobe Commerce, WooCommerce | Available on request | Confirmed per store and workflow during setup. Each change states whether it has a restore point. |
| Change history for every change made through the workforce | Read | All | Available now | The ledger behind sign-off and audit. |
| Staging environments: StagingPro (BigCommerce), Vortex Staging (Shopify), DryRunPro (Adobe Commerce and Magento) | Write (staging) | As named | Available now | Separate Vortex Apps, each described on its own page. Not an automatic safety net under every crew. |
Platform-level statements
| Statement | Surface | Scope | Status | Notes |
|---|---|---|---|---|
| Commerce platforms supported | Read | BigCommerce, Shopify, Adobe Commerce and Magento Open Source; WooCommerce for selected workflows | Available now | Per the rows above. Write and rollback vary by platform and workflow. |
| Connector catalogue | Catalogue | Over 200 connectors | Catalogue presence only | Read, write, staging and rollback capability is confirmed per connector during setup. |
| Crews never hold a store credential; the control plane reads and writes on their behalf | Architecture | All | Available now |
Source, ownership and review
- Source: the product reference and crew copy supplied by the founders on 10 September 2026, reconciled with the live crew pages and Vortex Apps pages. Statuses confirmed by Product on 11 September 2026.
- Owner: Product. Marketing may not upgrade a status on this page without Product confirmation in writing.
- Review: quarterly, next due 11 December 2026, or sooner when a workflow changes status. A status is downgraded immediately if its evidence cannot be confirmed.
- Corrections: press@vortexiq.ai.
