# Additional setup notes for BigCommerce (services)

## Introduction

This page includes additional information and resources that may be useful when configuring BigCommerce in Patchworks:

* [BigCommerce documentation](#bigcommerce-documentation)
* [Patchworks filters](#patchworks-filters)
* [Special options when pulling data from BigCommerce](#special-options-when-pulling-data-from-bigcommerce)
* [Special options when pushing data to BigCommerce](#special-options-when-pushing-data-to-bigcommerce)

## BigCommerce documentation

The following links to BigCommerce's own documentation may be useful if you need to dig deeper into BigCommerce fields (for example, to configure advanced mappings):

* [BigCommerce REST API documentation](https://developer.bigcommerce.com/docs/rest)

## Patchworks filters

When you are pulling data from BigCommerce, filters can be used to refine the data that is pulled. Available filter options vary, depending on which **entity type** is being synced (for example: orders, products, customers, etc.).

{% hint style="info" %}
For general information about working with filters in Patchworks, please see our [service filters](/product-documentation/patchworks-services/working-with-services/the-anatomy-of-a-service/service-filters.md) page.
{% endhint %}

### Time period filters

A common scenario for filters is to process records created/modified in the last x minutes/hours/days, or within a given timeframe. For BigCommerce, the following time period filter fields are available:

| Field                                                            | Summary                                                                                                                                                                                                                                                                                         |
| ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <ul><li>Min Date Created</li><li>Min Date Modified<br></li></ul> | <p>The minimum date and time for which you want to retrieve records for processing. This parameter can be used to filter results so that you only get data that was created/modified <strong>on or after</strong> the specified date and time.</p><p></p><p>These values are inclusive.</p>     |
| <ul><li>Max Date Created</li><li>Max Date Modified</li></ul>     | <p>The maximum date and time for which you want to retrieve records for processing. This parameter can be used to filter results so that you only get data that was created/modified <strong>before or up to</strong> the specified date and time.</p><p></p><p>These values are inclusive.</p> |

<details>

<summary>Example 1</summary>

Let's say that we only want to process all orders which were created in the last 2 hours. In the Patchworks dashboard, our filters would look as follows:

![](/files/M0oWkar05nMkgTrnusbd)

We can visualise this as below:

![](/files/vwvwNTZiiE7QZ9niv0VI)

</details>

<details>

<summary>Example 2</summary>

Let's say that we only want to process all orders which are between 1 and 2 hours old. In the Patchworks dashboard, our filters would look as below:

![](/files/C1XyC4MxiWxT6AoXn05B)

We can visualise this as below:

![](/files/U8o71S0XtSzEm4bQj9QJ)

</details>

## Special options when pulling data from BigCommerce

When you choose to add BigCommerce as a **source** connector for a Patchworks service, you're prompted to provide details for a set of [standard options which are common to all source connectors](/product-documentation/patchworks-services/working-with-services/the-anatomy-of-a-service/service-source.md), irrespective of the system being used.&#x20;

In addition, depending on the entity being synced, some BigCommerce-specific **source** options may be required. These options are summarised below:

| Entity synced | Field | Field summary |
| ------------- | ----- | ------------- |
| -             | -     | -             |

## Special options when pushing data to BigCommerce

When you choose to add BigCommerce as a **destination** connector for a Patchworks service, you're prompted to provide details for a set of [standard options which are common to all destination connectors](/product-documentation/patchworks-services/working-with-services/the-anatomy-of-a-service/service-destination.md), irrespective of the system being used.&#x20;

In addition, depending on the system you're pulling data from and the entity being synced, some BigCommerce-specific **destination** options may be required. These options are summarised below.

{% tabs %}
{% tab title="NetSuite" %}

| Entity synced | Field | Field summary |
| ------------- | ----- | ------------- |
| -             | -     | -             |
| {% endtab %}  |       |               |

{% tab title="Shopify" %}

| Entity synced | Field | Field summary |
| ------------- | ----- | ------------- |
| -             | -     | -             |
| {% endtab %}  |       |               |
| {% endtabs %} |       |               |


---

# 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/patchworks-services/service-systems/supported-service-systems/bigcommerce-service-connector/additional-setup-notes-for-bigcommerce-services.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.
