# Shopify > Brightpearl - fulfillment

## Introduction

The flow retrieves `fulfilled` orders from Shopify and then searches for them in Brightpearl. The `product`, `quantity` and `warehouse ID` are sent to create a goods out note for these orders in Brightpearl.

{% hint style="info" %}
This blueprint includes two process flows to handle the sync of fulfillments between Shopify and Brightpearl: Shopify > Brightpearl (detailed here) and [Brightpearl > Shopify](/product-documentation/blueprints/patchworks-blueprints/shopify-and-brightpearl/available-process-flows-shopify-and-brightpearl/brightpearl-greater-than-shopify-fulfillment.md). You only need to run ONE, depending on which way you want the sync to work.
{% endhint %}

## Process flow snapshot

<details>

<summary><img src="/files/y1IE71BfODU6ZRj1HNMM" alt="" data-size="line"> Click to view process flow snapshot</summary>

<div align="left"><figure><img src="/files/9SwIl1gA9tOarpH2Y8x0" alt=""><figcaption></figcaption></figure></div>

</details>

## Limitations

<table><thead><tr><th width="266.79296875">Limitation</th><th>Summary</th></tr></thead><tbody><tr><td>Tracking</td><td>The goods out note does not support tracking numbers.</td></tr></tbody></table>

## Assumptions

<table><thead><tr><th width="266.79296875">Assumption</th><th>Summary</th></tr></thead><tbody><tr><td>Brightpearl orders are up to date</td><td>This flow assumes that orders exist in both systems.</td></tr><tr><td>Sync direction</td><td>Running this flow assumes that you want to sync fulfillments in this direction (i.e. from Shopify to Brightpearl). If required, a flow for the reverse direction is available (<a href="/pages/Icslft8mApBOg1nlyBym">Brightpearl > Shopify fulfillments</a>). You should run one or the other.</td></tr></tbody></table>

There are no assumptions to consider for this flow.

## Customisation

To ensure that this process flow runs as required, some customisation options are available. These are documented in the following sections:

* [Flow variables](#flow-variables)
* [Process shape shapes](#process-flow-shapes)

### Flow variables

The table below summarises [flow variables](/product-documentation/process-flows/building-process-flows/dynamic-variables/flow-variables.md) defined for this process flow.

<table><thead><tr><th width="163.5078125">Flow variable</th><th>Summary</th><th>Default value</th></tr></thead><tbody><tr><td>datefrom</td><td>Set the relative number of days to look back for orders. Update the default value as required.<br><br>This variable is referenced in the first Shopify connector, where a filter query is defined to determine which orders to pull.</td><td>-24 hours UTC</td></tr></tbody></table>

{% hint style="info" %}
For information on working with flow variables, please refer to our [flow variables documentation](/product-documentation/process-flows/building-process-flows/dynamic-variables/flow-variables.md).
{% endhint %}

### Process flow shapes

This process flow includes some shapes that can be configured with your own settings. Please see guidelines in the table below.

{% hint style="warning" %}
Shape settings determine the outcome of process flows. Do not change shape settings unless they are listed below.&#x20;
{% endhint %}

<table data-full-width="false"><thead><tr><th width="220.09375">Shape</th><th>Notes</th></tr></thead><tbody><tr><td>Trigger</td><td>No default schedule is defined. If you decide to sync in this direction (as opposed to syncing from <a href="/pages/Icslft8mApBOg1nlyBym">Brightpearl to Shopify</a>), you should set a schedule in line with your fulfillment requirements. For example, if warehouse activity stops at 6pm, you might run this flow at 7pm each day.</td></tr><tr><td>Connector (Shopify)</td><td><p>If you did not add or select a Shopify instance during the blueprint <a href="/pages/IUEvmNmJ8fj8u3vFE4Rn">installation process</a>, the following settings must be configured:<br><br><code>Source instance</code> : Set to your required <code>Shopify</code> instance.<br><code>Source endpoint</code> :  Set to <code>POST Get ffulfilled orders via graphql</code><br><code>Filter</code> : The default filter references the <code>datefrom</code> <a href="#flow-variables">flow variable</a> as below:</p><pre data-overflow="wrap"><code>fulfillment_status:fulfilled AND (financial_status:authorized OR financial_status:paid OR financial_status:pending) AND created_at:>='{{flow.variables.datefrom}}'
</code></pre></td></tr><tr><td>Connector (Brightpearl)</td><td><p>If you did not add or select a Brightpearl instance during the blueprint <a href="/pages/IUEvmNmJ8fj8u3vFE4Rn">installation process</a>, the following settings must be configured:<br><br><code>Source instance</code> : Set to your required <code>Brightpearl</code> instance</p><p><code>Source endpoint</code> :  Set to <code>GET Search orders</code><br><code>Parameters</code> :  A default filter is defined to search (and match) on <code>externalRef</code> where the value is set to <code>[[payload.name]]</code></p></td></tr><tr><td>Connector (Brightpearl)</td><td><p>If you did not add or select a Brightpearl instance during the blueprint <a href="/pages/IUEvmNmJ8fj8u3vFE4Rn">installation process</a>, the following settings must be configured:<br><br><code>Source instance</code> : Set to your required <code>Brightpearl</code> instance</p><p><code>Source endpoint</code> :  Set to <code>GET Order details</code><br><code>Id</code> :  Set to <code>[[payload.id]]</code></p></td></tr><tr><td>Connector (Brightpearl)</td><td><p>If you did not add or select a Brightpearl instance during the blueprint <a href="/pages/IUEvmNmJ8fj8u3vFE4Rn">installation process</a>, the following settings must be configured:<br><br><code>Source instance</code> : Set to your required <code>Brightpearl</code> instance</p><p><code>Source endpoint</code> :  Set to <code>POST Create goods out note</code><br><code>Id</code> :  Set to <code>[[meta.salesid]]</code></p></td></tr></tbody></table>

## Reference

Reference information for this process flow is documented in the following sections:

* [Scripts used in this process flow](#scripts-in-this-process-flow)
* [Cross-reference lookups used in this process flow](#cross-reference-lookups-in-this-process-flow)

### Scripts in this process flow

<table><thead><tr><th width="293">Script</th><th>Summary</th></tr></thead><tbody><tr><td>Brightpearl determine fulfilment lines</td><td>Only outputs the lines that are fulfilled for Brightpearl.</td></tr></tbody></table>

### Cross-reference lookups in this process flow

This process flow does not use cross-reference lookups.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.wearepatchworks.com/product-documentation/blueprints/patchworks-blueprints/shopify-and-brightpearl/available-process-flows-shopify-and-brightpearl/shopify-greater-than-brightpearl-fulfillment.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.