Sign In
Book a Demo

Priority ERP Integration for Multichannel Orders

Keep Priority ERP as your system of record while orders arrive from every store and marketplace. Pipe17’s order management sends those orders into Priority and returns Priority’s inventory counts and tracking to each channel.
Book a demo
Priority Pipe17 Connector Icon

The Solution for Priority ERP Integration & Order Management

Priority Keeps the Record. Pipe17 Runs the Orders Around It.

When a company on Priority ERP links channels through an iPaaS and routes orders with a legacy OMS, each new store or marketplace adds a feed to build and rules to maintain. Pipe17’s Order Operations Platform takes the place of both, and Priority remains the record for every channel’s orders.
iPaaS & Custom Builds Legacy OMS Pipe17
Native API-First Connectivity ✅ ❌ ✅
Pre-Configured Commerce Connectors ❌ ❌ ✅
Custom Integration Mappings ✅ ❌ ✅
Advanced Order Orchestration ❌ ✅ ✅
Exception Management & Alerts ❌ ❌ ✅
Unified Inventory Management ❌ ✅ ✅
Rapid to Implement & Go-Live ❌ ❌ ✅
Easy to Add / Swap Channels & Flows ❌ ❌ ✅
Low Total Cost of Ownership (TCO) ❌ ❌ ✅

Future-Ready Brands and Fulfillment Providers Run on Pipe17

Sell Everywhere and Keep Priority ERP as the Record

Decision tree of rectangle boxes representing rules-based automation

Every Channel's Orders in Priority

Pipe17 opens a Priority sales order for each order your stores and marketplaces take, and a cancellation made in Pipe17 reaches the matching Priority order.

Magnifying glass over graph, representing analytics across any data source

Channels That Sell Priority's Inventory

Every store and marketplace sells against the inventory in your Priority warehouses, which Pipe17 turns into one accurate count.

Order box on shield with upward arrow around it symbolizing future-proof order operations

Tracking to Channels, 3PL Shipments to Priority

Pipe17 returns tracking from Priority warehouses to the channel that sold the order and posts your 3PLs' shipments to Priority.

Automated Priority ERP Data Flows

Orders and cancellations go from Pipe17 to Priority ERP, along with the shipments your 3PLs make. Warehouses, inventory, shipping requests, and tracking come back from Priority, and orders entered in Priority come into Pipe17.
  • Push Orders to Priority. Each order Pipe17 receives from a store, marketplace, or wholesale channel becomes a Priority sales order with its line items. Filter by source, status, tag, or order ID pattern. Edits made in Pipe17 update the Priority order until Priority starts processing it.
  • Push Cancellations to Priority. When you cancel an order in Pipe17, its Priority sales order is canceled as well, with no second entry for your team.
  • Pull Orders from Priority. Wholesale, phone, and other orders entered directly in Priority come into Pipe17 and route to a warehouse, 3PL, or dropship partner by the same rules as your channels.
  • Pull Shipping Requests from Priority. When Priority creates a shipment for an order from Pipe17, the shipment appears in Pipe17 as a shipping request at the matching warehouse, showing support and planners what each Priority warehouse is about to ship.
  • Pull Fulfillments from Priority. Shipments that leave a Priority warehouse return to Pipe17 as fulfillments with tracking numbers, which Pipe17 sends on to the selling channel.
  • Push Fulfillments to Priority. When a 3PL or another location ships an order, Pipe17 posts the fulfillment to Priority against the original sales order.
  • Pull Inventory from Priority. Pipe17 reads inventory for each Priority warehouse and SKU. Include or exclude SKUs by exact match or pattern, and pull chosen SKUs on demand.
  • Pull Locations from Priority. Pipe17 creates a location for every Priority warehouse, with its own inventory count and a place in your routing rules.

Connect Priority ERP to Your Stores, Marketplaces, and 3PLs

Pipe17 support connects through the Priority REST API with an API user your administrator sets up, then maintains the connection. Shopify and Amazon orders arrive in Priority as sales orders, and 3PL shipments post there too.

Get Every Order into Priority ERP Without Rekeying It

Watch Pipe17 take an Amazon order, create its sales order in Priority, and post the tracking number back to the marketplace once the Priority warehouse ships.
Book a demo
Priority ERP horizontal svg logo black

is better with

Pipe17 horizontal svg logo black

Priority ERP Integration FAQs

Yes, Pipe17 integrates with Priority ERP from Priority Software through the Priority REST API, on a connection Pipe17 sets up and maintains. Pipe17 creates Priority sales orders from your stores and marketplaces, sends cancellations, and takes in orders entered in Priority. It brings back Priority's warehouses, inventory, shipments, and tracking, and Priority stays your system of record.

Pipe17 is the order management system (OMS) beside Priority ERP. Priority keeps the financials and warehouse records, while Pipe17 takes in orders from every channel and decides whether a Priority warehouse or a 3PL ships each one. Pipe17 replaces the iPaaS and legacy OMS that would otherwise split those jobs.

With Shopify and Priority ERP both connected to Pipe17, each Shopify order becomes a Priority sales order, and Shopify sells against the inventory Priority reports. When a Priority warehouse ships the order, the tracking number goes back to Shopify. Filters by order source or tag decide which Shopify orders go to Priority.

Pipe17 pulls orders from Amazon and other marketplaces and creates each one as a sales order in Priority ERP, beside orders from your own stores. Every channel sells against the inventory Priority reports, and tracking from the Priority warehouse goes back to the marketplace that sold the item. A channel you add later sends its orders to Priority the same way.

The inventory Priority ERP reports for each warehouse reaches your sales channels after Pipe17 turns it into the count each store and marketplace can sell. Inventory at your 3PLs adds to that count, giving channels everything you can ship. Channel buffers and safety stock you set in Pipe17 apply before a count reaches a channel, and you decide which SKUs the sync covers.

Connect the 3PL to Pipe17, and Pipe17 posts each shipment the 3PL makes to Priority ERP as a fulfillment on the matching sales order. Your routing rules decide which orders the 3PL ships and which ship from Priority warehouses. Pipe17 connects 3PLs such as ShipBob and Radial, and every 3PL's shipments post to Priority the same way.

A shipping request is Pipe17's record of a shipment that Priority ERP creates for an order from Pipe17, logged at the Priority warehouse that will ship it. When the shipment leaves, it becomes a fulfillment with a tracking number. Your team follows both stages in Pipe17 without signing in to Priority, and the tracking number reaches the channel where the customer bought.

Pipe17 connects to Priority ERP over the Priority REST API, using a Priority API user and password plus your Priority API URL. Your Priority administrator creates the API user and gives it access to the forms the connector reads and writes, such as warehouses and orders. Pipe17 support then sets up the connection with you and turns on the order, inventory, shipping request, and fulfillment flows.

Yes, AI agents using the Model Context Protocol (MCP) see the orders Pipe17 sends to Priority ERP and the inventory Priority reports, once connected to the Pipe17 MCP Server. An agent finds an order, checks whether it has shipped, or reads a SKU's inventory at a Priority warehouse. AI Controls let admins decide whether outside agents connect at all. Pippen, Pipe17's AI agent, answers the same questions inside Pipe17.