> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/blueprints/patchworks-blueprints/shopify-and-netsuite/available-process-flows-shopify-and-netsuite/netsuite-greater-than-shopify-create-update-companies-contacts-and-payment-terms/get-all-payment-terms-for-mapping.md).

# Get all Payment terms for mapping

## Introduction

This 'utility' flow can be used to output Shopify GIDs for payment terms. You will need these to [populate the Net terms to payment terms cross-reference lookup during the installation and setup process](/product-documentation/blueprints/patchworks-blueprints/shopify-and-netsuite/installation-guide-shopify-and-netsuite/stage-1-patchworks-setup-shopify-and-netsuite.md#net-terms-to-payment-terms-template) for this blueprint.

## Process flow snapshot

<details>

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

<img src="/files/PqebS4Xf2V37eeVReUQN" alt="" data-size="original">

</details>

## Limitations

There are no limitations to note for this flow.

## Assumptions

There are no assumptions to note 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

This process flow does not use flow variables.

### 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="190.171875">Shape</th><th>Notes</th></tr></thead><tbody><tr><td>Trigger</td><td>This process flow is designed to be run manually when required.</td></tr><tr><td>Notify <br><br><code>Branch</code>: <code>Missing information</code> </td><td><p>Configure the <a href="/pages/qJOdm6pHm3I8Ovog6Ola">notify shape</a> for your own notification preferences in the event that locations have missing information. <br><br><code>Alert level</code>: Defaults to <code>error</code> but can be changed if needed<br><code>Channel</code>: Defaults to <code>email + log</code> but can be changed if needed<br><code>Email Limit</code>: Defaults to <code>5</code> but can be changed if needed<br><code>Notification Group</code>: Replace the <code>notify</code> placeholder which your required notification group. </p><p><code>Message</code>: If required, you can change the placeholder message.<br><br>For more information please refer to our <a href="/pages/qJOdm6pHm3I8Ovog6Ola">Notify shape</a> and <a href="/pages/ul3TLNVYRLYUGugTOFLU">Notification groups</a> pages.</p></td></tr><tr><td>Connector (Shopify)</td><td>If you did not add or select a Shopify instance during the blueprint <a href="/pages/ZuNUyYvEy14sajACk8N9">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 GIDs of payment terms</code> </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

This process flow does not use scripts.

### Cross-reference lookups in this process flow

This process flow does not use cross-reference lookups.