> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Picqer as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/picqer

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](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`

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

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Picqer connector syncs orders, picklists, purchaseorders, and more into the PostHog data warehouse, so you can analyze them alongside your product data.

## Prerequisites

Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.

## 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.

Enter your Picqer account name and API key to pull your Picqer warehouse and fulfillment data.

Create an API key under **Settings → API keys** in your Picqer account. The key inherits its permissions from its scope, so it can read the records that scope allows.

You'll be asked for:

-   **Account name**: for example `yourcompany`.
-   **API key**

## 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](https://posthog.com/docs/data-pipelines/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

All Picqer tables are full refresh. Each sync replaces the contents of the table.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Account name` | text | Yes |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `orders` | A sales order in Picqer, containing the products a customer ordered and their fulfilment state. | Full refresh | — | — |
| `picklists` | A picklist — the set of products to pick from stock to fulfil one or more orders. | Full refresh | — | — |
| `purchaseorders` | A purchase order sent to a supplier to replenish stock. | Incremental, Full refresh | updated | — |
| `receipts` | A receipt recording the goods received against a purchase order. | Full refresh | — | — |
| `returns` | A return (RMA) of products a customer sent back. | Incremental, Full refresh | updated\_at | — |
| `shipments` | A shipment created for a picklist or return, with the shipping provider and per-parcel tracking. | Full refresh | — | — |
| `stockhistory` | One change of the stock level of a product in a warehouse. History items cannot be changed. | Incremental, Full refresh | changed\_at | — |
| `warehouse_stock` | The current stock of one product in one warehouse, for all products with stock or reservations. | Full refresh | — | — |
| `products` | A product in the Picqer catalog, including its stock and supplier information. | Full refresh | — | — |
| `customers` | A customer record in Picqer. | Full refresh | — | — |
| `suppliers` | A supplier products can be purchased from. | Full refresh | — | — |
| `warehouses` | A warehouse where stock is held and orders are fulfilled. | Full refresh | — | — |
| `locations` | A physical stock location within a warehouse. | Full refresh | — | — |
| `users` | A user account in the Picqer application. | Full refresh | — | — |
| `vatgroups` | A VAT (tax) group applied to products and orders. | Full refresh | — | — |
| `tags` | A tag that can be attached to orders, customers, and other records. | Full refresh | — | — |
| `return_reasons` | A reason a customer can give for returning a product. Resolves `idreturn_reason` on returned products. | Full refresh | — | — |

## Troubleshooting

-   If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
-   If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](https://posthog.com/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.