> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Big Cartel on Vortex IQ

> Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Big Cartel.

Monitor store performance, find catalogue and operational problems, and safely apply approved changes to Big Cartel.

[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [View setup guide](/integrations/bigcartel) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=bigcartel)

<CardGroup cols={5}>
  <Card title="34">
    performance signals
  </Card>

  <Card title="8">
    automated checks
  </Card>

  <Card title="1">
    prepared fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="5">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup cols={2}>
      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>

      <Card title="Grow revenue">
        Improve discovery, conversion, campaigns and repeat purchase.
      </Card>

      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Catalogue quality">
        Identify missing, inconsistent or outdated product data.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls.
  </Tab>

  <Tab title="Monitor (34)">
    ### Monitor performance

    34 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Protect revenue (13 signals)">
        | Signal                                      | Alert behaviour  | What it tracks                                                                                               |
        | ------------------------------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------ |
        | **Ad Spend on Out-of-Stock Products**       | Merchant rule    | Ad Spend on Out-of-Stock Products, broken down by row.                                                       |
        | **Cancellation Rate**                       | Alert band 1 / 3 | Cancelled share of orders. Rising cancellations point to stock or expectation mismatches.                    |
        | **Email Share of Revenue**                  | Merchant rule    | Email Share of Revenue, broken down by row.                                                                  |
        | **High-Value Customers Unengaged on Email** | Merchant rule    | High-Value Customers Unengaged on Email, broken down by row.                                                 |
        | **Low-Stock (Tracked)**                     | Merchant rule    | Tracked products nearing zero - restock prompt before a hero sells out.                                      |
        | **Order Status Mix**                        | Watch only       | Split of pending / paid / shipped / refunded / cancelled. Quick read on where orders sit.                    |
        | **Out-of-Stock (Tracked)**                  | Alert band 0 / 5 | Tracked products at zero stock. Big Cartel exposes per-option stock; OOS-with-demand is recoverable revenue. |
        | **Refund Rate**                             | Alert band 2 / 5 | Refunded share of orders over 30 days. The core product-trust signal for a creator with no support desk.     |
        | **Refund-Rate Spike**                       | Alert band 2 / 5 | Fires when refunds suddenly accelerate - early warning of a product or fulfilment problem.                   |
        | **Refunded Orders**                         | Merchant rule    | Count of refunded orders with a spike alarm against the 30-day baseline.                                     |
        | **Revenue at Risk**                         | Merchant rule    | Estimated revenue exposed by sold-out heroes, stuck orders, and (when siblings connect) cross-channel leaks. |
        | **Slow PDPs Driving Cart Loss**             | Merchant rule    | Slow PDPs Driving Cart Loss, broken down by row.                                                             |
        | **Sold-Out Products**                       | Alert band 0 / 5 | Products marked sold-out. Sold-out bestsellers still on the storefront are quiet revenue leaks.              |
      </Accordion>

      <Accordion title="Run operations (10 signals)">
        | Signal                        | Alert behaviour    | What it tracks                                                                                                                                           |
        | ----------------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
        | **Avg Time to Ship**          | Merchant rule      | Hours between paid and shipped. Indie makers run slower SLAs; 72h is a sensible nudge threshold.                                                         |
        | **Discount Dependency**       | Alert band 20 / 40 | Share of orders (30d) carrying an order\_adjustments/discount entry with a bracketed code, e.g. \[FREESHIPPING]. Discount codes are a Gold-plan-and-abov |
        | **Fulfillment Rate**          | Alert band 95 / 90 | Share of orders (30d) with shipping\_status = shipped - the real, confirmed Big Cartel field, independent of payment\_status.                            |
        | **Order Processing Backlog**  | Alert band 10 / 50 | Surfaces when unshipped orders pile up beyond the normal pace for the store.                                                                             |
        | **Orders by Country**         | Watch only         | Order count by destination country - matters for makers shipping internationally.                                                                        |
        | **Pending Orders**            | Alert band 10 / 50 | Orders awaiting action. A burst usually means a payment-gateway hiccup or a fulfilment backlog.                                                          |
        | **Plan Product Cap Usage**    | Merchant rule      | Active products vs the plan tier's product cap. Crossing the cap forces an upgrade or delistings.                                                        |
        | **Sold-Out Bestseller Alert** | Alert band 0 / 5   | Flags when a recent bestseller goes sold-out so the maker can restock before momentum dies.                                                              |
        | **Total Customers**           | Watch only         | All-time customer count. Base for the new-vs-returning split.                                                                                            |
        | **Unshipped Paid Orders**     | Alert band 10 / 50 | Paid but not yet shipped beyond 48h - the broken-promise signal for a lean maker shipping by hand.                                                       |
      </Accordion>

      <Accordion title="Grow revenue (9 signals)">
        | Signal                           | Alert behaviour    | What it tracks                                                                                         |
        | -------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------ |
        | **Average Order Value**          | Alert band 0 / -5  | Revenue / order count. For makers, a drop often means discount over-reliance.                          |
        | **New vs Returning Customers**   | Watch only         | 30-day split of first-time vs repeat buyers. Shows whether growth is acquisition or loyalty led.       |
        | **Order Volume**                 | Alert band 0 / -10 | Count of placed orders with trend. Pairs with revenue to separate volume vs AOV moves.                 |
        | **Products with No Description** | Alert band 5 / 20  | Empty descriptions hurt SEO and conversion. AI-fill is a one-click action target.                      |
        | **Products with No Image**       | Merchant rule      | Listings with zero images convert poorly - free conversion lift to fix.                                |
        | **Repeat Purchase Rate**         | Alert band 25 / 10 | Share of customers with >1 order. For indie brands, repeat rate is the cheapest growth lever.          |
        | **Revenue Trend**                | Watch only         | Daily revenue line over 90 days - spots seasonality and drop campaigns.                                |
        | **Shipping as % of Revenue**     | Alert band 5 / 15  | Shipping charged vs revenue. A high share for a maker often means under-charged international postage. |
        | **Total Revenue**                | Alert band 0 / -5  | Gross revenue across the selected window with vs-previous-period trend. Top of the indie-store pulse.  |
      </Accordion>

      <Accordion title="Catalogue quality (1 signals)">
        | Signal              | Alert behaviour | What it tracks                                                                 |
        | ------------------- | --------------- | ------------------------------------------------------------------------------ |
        | **Active Products** | Watch only      | Count of live listings. Baseline for the plan-cap and catalogue-hygiene cards. |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal                     | Alert behaviour | What it tracks                                                                               |
        | -------------------------- | --------------- | -------------------------------------------------------------------------------------------- |
        | **Top Customers by Spend** | Watch only      | Highest-spend buyers over 90 days - the VIP shortlist for early-access drops and thank-yous. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (8)">
    ### Audit risks and opportunities

    A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail.

    <AccordionGroup>
      <Accordion title="Fulfillment rate below 90%">
        **Severity** critical · **Outcome** Protect revenue · **Fix status** Candidate remediation

        When more than 1 order in 10 is failing to reach fulfilment, customers have paid for goods that are not shipping on time; refunds, chargebacks and support load follow quickly.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-FULFIL-001`
      </Accordion>

      <Accordion title="Cancellation rate above 10% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Report only

        More than 1 in 10 orders is being cancelled. Unlike a return, a cancellation often means the customer changed their mind or hit a problem before the order even shipped, checkout friction, a payment failure, an unexpectedly long delivery estimate, which usually points to a fixable step in the order f

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-CANCEL-001`
      </Accordion>

      <Accordion title="Refund rate above 5% over 30d">
        **Severity** high · **Outcome** Protect revenue · **Fix status** Candidate remediation

        More than 1 in 20 orders is being refunded. Beyond the direct revenue loss, this rate also carries payment-cost consequences, processors and payment gateways watch refund and dispute rates, and a sustained high rate can affect processing terms independent of the lost sale itself.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-REFUND-001`
      </Accordion>

      <Accordion title="Discount > 20% of revenue (margin erosion)">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only

        Discounting above roughly 20 percent of revenue erodes margin quickly, often without lifting volume enough to pay for itself, and trains customers to wait for codes.

        Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.

        Reference: `ECOM-DISCOUNT-001`
      </Accordion>

      <Accordion title="Products with zero or negative stock">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Every product at zero or negative stock is a page a customer can still find, still add to cart in some storefront setups, and still be disappointed by. Zero-stock listings that stay live also keep spending any ad budget or SEO ranking pointed at them, driving traffic to a product nobody can actually

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-INVENTORY-001`
      </Accordion>

      <Accordion title="Repeat-customer rate below 20%">
        **Severity** medium · **Outcome** Grow revenue · **Fix status** Candidate remediation

        Fewer than 1 in 5 customers comes back for a second order. Acquiring a first-time customer is almost always the most expensive part of earning their business, so a repeat rate this low means the store is paying that acquisition cost repeatedly instead of earning a second (cheaper) sale from customer

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CUSTOMER-001`
      </Accordion>

      <Accordion title="Products missing SEO title">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Prepared fix

        Products without SEO titles compete in search under their bare product names; pages that could rank for buying keywords stay invisible.

        A prepared, approval-gated fix exists: the proposed change, affected records, risk, reversibility and verification are shown before execution.

        Reference: `ECOM-CATALOGUE-002`
      </Accordion>

      <Accordion title="Products missing description">
        **Severity** low · **Outcome** Grow revenue · **Fix status** Candidate remediation

        A product with no description gives a shopper nothing to evaluate beyond a photo and a price. It also gives search engines almost nothing to index, so these products are simultaneously converting worse for visitors who do find them and ranking worse in organic search for anyone who has not.

        A likely corrective operation exists, but its mapping and recovery are not yet complete, so execution is not offered. Evidence and recommended manual steps are provided.

        Reference: `ECOM-CATALOGUE-001`
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Automate">
    ### Automate approved work

    Vortex IQ is integrated with **5 read** and **0 write** operations across account products, accounts, account customers, account orders on Big Cartel. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words.

    Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution.

    [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=bigcartel)

    #### Ready to build your first Big Cartel workflow

    Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build.

    <Accordion title="Browse the operations you can build with">
      | Resource          | Read operations | Write operations |
      | ----------------- | --------------- | ---------------- |
      | account products  | 2               | 0                |
      | accounts          | 1               | 0                |
      | account customers | 1               | 0                |
      | account orders    | 1               | 0                |

      Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
    </Accordion>
  </Tab>
</Tabs>
