# Linking ShopWired as a source - Docs

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

[Learn more](/wizard.md)

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

**Alpha release**

This source is currently in **alpha**. The interface and available tables may change.

The ShopWired connector syncs your e-commerce store data into the PostHog Data warehouse, so you can analyze your products, customers, and orders alongside your product analytics data.

## Prerequisites

You need a ShopWired account with access to API keys. API credentials inherit full access to your store's data.

## Adding a data source

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  Select the tables you want to sync, choose a sync method and frequency, then click **Import**.

Once the syncs are complete, you can start querying this data in PostHog.

When linking ShopWired, you'll need:

-   **API key** and **API secret** – create these under **Account > API keys** in your [ShopWired](https://www.shopwired.co.uk) account.

## Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

-   **Webhook** (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
-   **Incremental** – only new or updated rows are synced on each run, using a cursor field (such as an `updated_at` timestamp). Cheaper than a full refresh, but deletes aren't captured.
-   **Append only** – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
-   **Full refresh** – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See [sync methods](/docs/cdp/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

Orders support incremental sync using their creation date. ShopWired doesn't expose a modified-date filter, so incremental syncs only pick up newly created orders — changes to existing records are only captured by a full refresh.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| API key | password | Yes |
| API secret | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| products | A product in your ShopWired store, including pricing, stock, and SEO fields. | Full refresh | — | — |
| categories | A category used to group products in your ShopWired store. | Full refresh | — | — |
| brands | A brand assigned to products in your ShopWired store. | Full refresh | — | — |
| tags | A tag used to label and filter products in your ShopWired store. | Full refresh | — | — |
| customers | A customer account (regular or trade) registered on your ShopWired store. | Full refresh | — | — |
| orders | An order placed on your ShopWired store, including line items, addresses, and totals. | Incremental, Full refresh | created | — |
| order_statuses | An order status configured on your ShopWired store (e.g. Paid, Dispatched). | Full refresh | — | — |
| vouchers | A discount voucher customers can redeem on your ShopWired store. | Full refresh | — | — |

## Troubleshooting

-   If you see an authentication error, your API key or secret is invalid or has been revoked. Generate new credentials under **Account > API keys** in ShopWired, then reconnect.
-   Syncs of very large stores can be slowed by ShopWired's API rate limit (2 requests per second sustained). The connector backs off and retries automatically, so this shows up as a longer sync, not a failure.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.

### Community questions

Ask a question

### Was this page useful?

HelpfulCould be better