The Priority connector links the app with your Priority ERP through the Priority REST API. It sends orders from the app to Priority and brings locations, inventory, shipping requests, and fulfillments from Priority into the app. The connector is in beta, and the Pipe17 support team sets it up for you.
With this connector, you can:
- Create your Priority warehouses as locations in the app.
- Push orders to Priority, and send cancellations for orders that are already in Priority.
- Pull inventory from Priority for each location, and pull inventory for specific SKUs on demand.
- Pull shipping requests and fulfillments with tracking numbers from Priority.
- Push fulfillments from your other fulfillment channels to Priority.
Setup
Before you begin, make sure you have:
- The connector turned on for your organization. This connector is in beta, so submit a support request to turn it on.
- An API user in Priority, with its username and password. Your Priority administrator can create it.
- Your Priority API URL. The API user must be able to read the warehouses list at this URL.
You can’t connect Priority on your own. The Connect pop-up shows a link to request setup, and the Pipe17 support team configures the connection with you.
To connect Priority:
- Navigate to Integrations in the app.
- Click Add Integration, and then select Priority.
- Click the request setup link in the pop-up. The support team contacts you to collect the connection details.
- Provide the API username for the Priority API User Name field.
- Provide the API password for the Priority API User Password field.
- Provide the API URL for the Priority API URL field.
- Confirm the Priority API Type with the support team: Generic or Orthofeet Custom.
- The support team clicks Connect.
- After you connect, choose the flows you want to use: toggle on Pull locations from Priority and Pull shipping requests from Priority, and set Process orders information, Process fulfillment information, and Process inventory updates.
Settings
| Setting | Description | Options/Default |
|---|---|---|
| Pull locations from Priority | Creates a location in the app for each Priority warehouse. | On/Off. Default: On |
| Process orders information | Sends orders from the app to Priority. | Disabled, Push orders to Priority. Default: Disabled |
| Pull shipping requests from Priority | Creates shipping requests in the app from shipments in Priority. | On/Off. Default: Off |
| Process fulfillment information | Sets whether fulfillments move from Priority to the app, from the app to Priority, or both. | Disabled, Pull fulfillments from Priority, Push fulfillments to Priority, Push and pull fulfillments. Default: Disabled |
| Process inventory updates | Pulls inventory from Priority into the app. | Disabled, Pull inventory information from Priority to Pipe17. Default: Disabled |
| Apply inventory updates only for SKUs matching following patterns | Updates inventory only for the SKUs you list. Enter a SKU for an exact match (not case-sensitive), or wrap a pattern in slashes, such as /^ABC/, to use a regular expression. |
Optional. Empty includes all SKUs |
| Apply inventory updates only for SKUs not matching following patterns | Skips inventory updates for the SKUs you list, for example when you want to manage stock for a sale by hand. Uses the same format as the previous setting. | Optional. Empty excludes none |
| Force inventory resync | Starts a full inventory pull on the next run instead of waiting for the next scheduled pull. | On/Off. Default: Off |
| Process only orders with specific order ID patterns | Sends only orders whose order ID matches a pattern you list. Uses the same format as the SKU pattern settings. | Optional. Empty sends all |
| Process only orders ingested from specific source in Pipe17 | Sends only orders that came into the app from the sources you list. | Optional. Empty sends orders from all sources |
| Push only orders with specific statuses | Sends only orders in the statuses you select. | Multiselect. Default: Ready for fulfillment, Cancelled |
| Process only orders assigned following tags | Sends only orders that have at least one of the tags you list, for example wholesale_order. |
Optional. Empty sends all |
Flows
| Flow | Direction | Notes |
|---|---|---|
| Locations | Priority → Pipe17 | Checks every 5 minutes. Creates a location for each new Priority warehouse. Warehouses that already have a location are skipped. |
| Orders | Pipe17 → Priority | Checks every 5 minutes. Creates new orders in Priority and updates orders that Priority hasn’t processed yet. Orders that Priority already processed aren’t updated. When an order in Priority is canceled in the app, the app cancels it in Priority. Canceled orders that aren’t in Priority yet aren’t sent. |
| Orders | Priority → Pipe17 | Not supported. The app doesn’t pull orders from Priority. |
| Inventory | Priority → Pipe17 | Pulls inventory for each active location. The time between full pulls grows with how long the last pull took, and is at most about a day. To pull right away, turn on Force inventory resync, or run the Pull inventory from Priority by SKU action for specific SKUs (use * to match several SKUs). Pushing inventory to Priority isn’t supported. |
| Shipping requests | Priority → Pipe17 | Checks every 5 minutes. Creates a shipping request for each new Priority shipment. The order must already be in the app, and the Priority warehouse must match a location in the app. |
| Fulfillments and tracking | Priority → Pipe17 | Checks every 5 minutes and looks back 14 days. Creates fulfillments with tracking numbers for orders that are in the app. If no shipping request exists for the shipment, the app creates one. Tracking numbers that already have a fulfillment are skipped. |
| Fulfillments and tracking | Pipe17 → Priority | Checks every 5 minutes. Sends fulfillments for shipping requests that are assigned to this connector. The order must be in Priority, and the fulfillment location must match a Priority warehouse. |
The Priority API accepts one request about every 1.5 seconds, so large syncs can take some time.
Troubleshooting
The connection fails
The app couldn’t sign in to Priority or read your warehouses. Check that the API username, password, and URL are correct, that a Priority API Type is selected, and that the API user can read warehouses in Priority. Then contact the support team to update the connection.Orders don’t reach Priority
Check that Process orders information is set to Push orders to Priority, and that the order’s status is selected in Push only orders with specific statuses. Also check that the order matches any order ID patterns, sources, or tags you set.Inventory doesn’t update
Inventory is pulled per location, so make sure Pull locations from Priority is on and your locations are active. Check that the SKU isn’t excluded by the SKU pattern settings. To pull now, turn on Force inventory resync or run the Pull inventory from Priority by SKU action. To learn more, see Getting Started with Locations in Pipe17.A shipment or fulfillment from Priority doesn’t appear in the app
The app skips Priority shipments and fulfillments when it can’t find the matching order in the app. Make sure the order exists in the app and that its Priority warehouse is set up as a location.A fulfillment isn’t sent to Priority
The app sends a fulfillment only when the order exists in Priority and the fulfillment location matches a Priority warehouse. Check that the order was pushed to Priority and that the location came from Priority.
Need Help?
If you need additional assistance:
- Use Ask Pippen, our AI agent, located at the top of the platform page.
- Submit a support request with as much relevant detail as possible. Learn how to submit a request.
We’re here to help you succeed with your operations.
Comments
0 comments