> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/learn-netsuite/synchronization-flows/purchase-order-sync.md).

# Purchase Orders

Explore the seamless synchronization of Purchase Orders between NetSuite's ERP system and HotWax Commerce, optimizing inventory management.

When a Purchase Order is raised in NetSuite's ERP system, it needs to be seamlessly synchronized with HotWax Commerce, where the store associates employ an intuitive Receiving App by HotWax Commerce for the efficient receipt of inventory.

## Export purchase orders from NetSuite

Schedule SuiteScripts to export purchase orders

```
HC_MR_ExportedPurchaseOrderCSV
```

SFTP location

## Import purchase orders into NetSuite

Open `Catalog` in Job Manager, search for the import purchase order job, then configure its schedule.

```
Import purchase orders
IMP_ASN_PO_FEED
```

See [Manage a job](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/administration/job-manager/jobs/job-details.md) for current scheduling instructions.

## Export received purchase orders from HotWax

Schedule a job in the integration layer to export received POs from the OMS and place them at an SFTP location for NetSuite to import

Check SFTP locations for received purchase orders

```
/home/{sftp-username}/netsuite/purchaseorder/receipt
```

## Import received purchase orders into NetSuite

Schedule the SuiteScript in NetSuite to consume this PO receipt feed and save it in NetSuite.

```
HC_SC_ImportPurchaseOrderReceipts
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hotwax.co/documents/learn-netsuite/synchronization-flows/purchase-order-sync.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
