Pipe17
1. Overview
The Pipe17 Integration in XoroERP connects your XoroERP environment with Pipe17, an integration hub that routes orders, shipments, and inventory between multiple sales channels and fulfillment systems.
Using this integration:
Orders created in XoroERP can be exported to Pipe17.
Order updates and shipment information can be sent back to Pipe17 to keep external channels and systems synchronized.
Inventory can be synced from Pipe17 into XoroERP, ensuring that stock levels reflect the broader multi-channel ecosystem.
This setup reduces manual effort, minimizes discrepancies between systems, and provides a structured, configurable way to control which data flows to and from Pipe17.
2. Installation
2.1 Connect to XoroERP Instance
Log in to your XoroERP account.
From the main dashboard, navigate to the Apps module.
Open the 3PL Connections tab.
Click Add 3PL Connection.
From the list of available integrations, select Pipe17.
2.2 Install the Pipe17 Integration
Click Install to add the Pipe17 integration to your XoroERP instance.
Once installed, the Pipe17 integration will appear under your active 3PL or integration connections.
2.3 Configure Account and Authentication
Open the Pipe17 integration settings from the list of active connections.
Enter the account details and API credentials provided by Pipe17, such as:
Account or Connection Name
API Key / Token or Credentials
Any required Endpoint or Tenant identifiers
Save the configuration and ensure that connectivity is successful before enabling auto import/export.
3. Configuration Settings
The Configuration Settings for Pipe17 control which orders are exported, how shipments and quantities are handled, and how inventory sync and notifications operate.
3.1 Data Export Settings
The following accounts and configuration will be used in XoroERP for Pipe17. These can be changed later as needed.
3.1.1 Pipe17 Account
Pipe17 The Pipe17 account or integration profile that will be used for data exchange between XoroERP and Pipe17.
3.1.2 Export Orders to Pipe17
Export orders to Pipe17 (Checkbox) Enables the export of eligible orders from XoroERP to Pipe17. When this setting is enabled, orders that meet all configured criteria (store, filters, customer, ship method, etc.) will be sent to Pipe17 for further routing and processing.
3.1.3 Drop Order(s) from the Following Store(s)
Drop order(s) from the following store(s) Defines the XoroERP store(s) from which orders will be exported to Pipe17. Orders created in the selected stores will be considered for export. Orders from non-selected stores will not flow into Pipe17 through this integration.
3.1.4 Block Waves Created via QuickShip
Block waves created via QuickShip in Xoro from flowing into Pipe17 (Checkbox) When enabled, waves created through QuickShip in XoroERP will be blocked from exporting to Pipe17. This is useful when QuickShip is used for internal, test, or ad hoc orders that should not go through Pipe17’s multi-channel routing.
3.1.5 Send Order Updates to Pipe17
Send Order Updates to Pipe17 (Checkbox) When enabled, XoroERP will send order updates to Pipe17 after the initial export, such as changes in order status, quantities, or other supported fields. This ensures that Pipe17 and any connected systems receive up-to-date order information from XoroERP.
3.1.6 Ship Method Name(s)
Ship Method Name(s) Defines the shipping methods that should be excluded from export. Orders using ship methods listed here will not be dropped to Pipe17, even if they otherwise meet all other conditions.
3.1.7 Blocked SKU(s)
Blocked SKU(s) Lists item numbers that should not be exported to Pipe17. Any order line containing these SKUs is excluded from the Pipe17 export logic. This is typically used to exclude non-fulfillable items, charges, or SKUs handled outside the Pipe17 flow.
3.1.8 Allowed Customer(s)
Allowed Customer(s) Restricts the integration to orders belonging to the selected customers. Only orders from these customers will be exported to Pipe17. If no customer is specified, orders from all customers are eligible, subject to other configuration filters.
3.1.9 Disable Multishipment
Disable multishipment (Checkbox) Controls how shipment confirmations are treated in XoroERP for Pipe17 orders:
When enabled, the first ship confirmation from Pipe17 is treated as final. All wave lines are marked as closed, and any remaining unshipped quantities are unallocated.
When disabled, multiple ship confirmations are supported, and wave lines stay open until the entire order is fulfilled.
3.1.10 Filter Configuration
Filter Name / Operator / Value Provides filter controls to further refine which orders are exported to Pipe17.
Filter Name – The field you want to filter on (for example, third-party source or other supported criteria).
Operator – Logical condition applied to the field (such as Contains, Equals, Starts With, etc., as supported).
Value – The value used to match against the selected field.
These filters allow you to precisely restrict the subset of orders that should flow to Pipe17, beyond store-, customer-, or method-based rules.
3.1.11 Default SKU
Default SKU (Text field) A fallback SKU used in fulfillment when no SKU is provided or recognized in the transaction data. This prevents failures in order export or processing due to missing or unmapped item identifiers.
3.1.12 Split Quantity
Split quantity (Checkbox) When enabled, merged item quantities are split during export to Pipe17. This allows Pipe17 and connected systems to handle items individually rather than as a single merged line, according to how downstream systems expect to receive quantities.
3.1.13 Auto Create Carrier and Ship Services
Auto Create Carrier and Ship Services (Checkbox) When enabled, if a carrier or ship service coming via Pipe17 does not already exist in XoroERP, it will be created automatically. This prevents failures caused by missing carrier or ship service definitions and reduces manual configuration overhead.
3.1.14 Export ASNs to Pipe17
Export ASNs to Pipe17 (Checkbox) Enables the export of Advance Shipping Notices (ASNs) from XoroERP to Pipe17. This ensures that shipment and carton information from XoroERP is available upstream in Pipe17 for further sharing or processing.
3.1.15 Use Ship Date as Transaction Date
Use Ship Date as transaction date (Checkbox) When enabled, the ship date will be used as the transaction date for relevant Pipe17-related records. This is useful for aligning financial and operational reporting with the actual shipment date.
3.1.16 Allow Third-Party Merged Shipments
Allow third-party merged shipments (Checkbox) When enabled, third-party merged shipments received via Pipe17 are accepted in XoroERP and processed as separate invoices. This setting supports scenarios where multiple orders or sources are merged into a single shipment and ensures that XoroERP can correctly interpret and bill those shipments.
4. Inventory Sync Settings
The Inventory Sync Settings section manages how inventory levels are synchronized between Pipe17 and XoroERP.
You can schedule regular inventory synchronization and define which fields and levels are used during comparison.
4.1 Enable Full Inventory Sync
Enable Full Inventory Sync (Checkbox) When enabled, XoroERP will perform full inventory synchronization with Pipe17 according to the defined schedule. Activating this option reveals additional inventory-related configuration fields.
4.2 Inventory Identifier Code
Inventory Identifier Code Defines the identifier XoroERP uses to match products during inventory synchronization (e.g., item number or another configured identifier). This ensures that stock levels are correctly mapped between XoroERP and the records coming via Pipe17.
4.3 Xoro Inventory Level
Xoro Inventory Level Determines which inventory quantity in XoroERP is used as the reference for comparison and updates (for example, available or on hand, as supported by your configuration).
4.4 Third Party Inventory Level
Third Party Inventory Level Specifies the inventory level reported by Pipe17 that XoroERP should align with (such as fulfillable quantity or another level supported by Pipe17).
4.5 Inventory Sync Schedule
Recurring / Once per day Defines whether inventory synchronization runs repeatedly at a defined interval or once each day.
Hours / Mins Specifies the schedule or frequency in hours and minutes for inventory sync jobs.
5. Import/Export Settings
The Import/Export Settings control the scheduling and notification behavior for all Pipe17-related data exchange.
5.1 Time Zone
Time Zone Sets the time zone used for scheduling all Pipe17 import and export jobs. All automated sync operations will follow this time setting.
5.2 Enable Auto Import/Export
Enable auto import/export (Checkbox) When enabled, XoroERP automatically runs import and export processes for Pipe17 according to the configured schedule. If disabled, sync operations must be manually run from the Operations Page.
5.3 Receive Import Error Notifications by Email
Receive import error notifications by email (Checkbox) When enabled, XoroERP sends email notifications whenever an import error occurs for Pipe17-related jobs.
Instant Error Email(s) Field to enter one or more email addresses that will receive immediate error notifications. Multiple email IDs should be separated by commas.
5.4 Send Daily Error Email
Send daily error email (Checkbox) When enabled, a daily summary of errors related to Pipe17 imports and exports will be sent to the configured email recipients.
5.5 Exclude Logs
Exclude Logs Allows you to exclude certain logs from email notifications by entering comma-separated keywords. An asterisk
*in a keyword may be used to denote a partial match. This helps limit notifications to the most relevant log entries, avoiding noise from less important messages.
6. Operations Page
The Operations Page for Pipe17 in XoroERP is the central place to monitor, manage, and manually trigger all synchronization activities related to the Pipe17 integration.
6.1 Accessing the Operations Page
Open the Apps module in XoroERP.
Navigate to the 3PL Connections or integration list.
Select the Pipe17 connection.
Click on Operations to open the Pipe17 Operations Page.
6.2 Header Options
The Operations Page header typically includes:
Add Account – Add another Pipe17 account or connection profile, if multiple Pipe17 connections are supported.
Change Account – Switch between available Pipe17 accounts or update connection details.
Remove Account – Disconnect the selected Pipe17 integration from XoroERP.
Settings – Open the configuration settings page for Pipe17 (Data Export Settings, Inventory Sync, Import/Export Settings).
6.3 Sync Xoro Data to Pipe17
This section allows you to manually push data from XoroERP to Pipe17.
Define a date range for orders or documents to be synchronized.
Optionally use search or filter options (such as order number or keyword) to narrow down which records to process.
Trigger a manual sync when:
Initial integration is set up,
Configuration has changed, or
Certain records need to be re-exported.
6.4 Orders Tab
The Orders tab is used to monitor and control the export of orders to Pipe17.
Key actions and elements:
Run – Manually export selected orders to Pipe17.
Mark as Resolved – Mark orders that have successfully exported or been handled.
Mark as Unresolved – Reopen orders that need to be reprocessed.
Filters:
Hide Resolved – Hide successfully processed orders from the list.
Show Errors Only – Show only those orders that encountered errors.
Typical columns include:
Order number or reference.
Last execution date for export attempts.
Status or message, including any error details.
6.5 Ship Confirmations Tab
The Ship Confirmations tab shows shipment data associated with Pipe17.
Run – Fetch or process shipment confirmations related to Pipe17.
Mark as Resolved / Mark as Unresolved – Manage the status of confirmations.
Filters such as Hide Resolved and Show Errors Only help focus on records requiring attention.
This tab ensures that shipments handled through Pipe17 are accurately reflected in XoroERP and that the Disable Multishipment setting is correctly applied.
6.6 ASNs Tab
The ASNs tab manages Advance Shipping Notices exported to Pipe17.
Run – Trigger export of ASNs to Pipe17.
Mark as Resolved / Mark as Unresolved – Maintain processing status.
Filters allow you to view only unresolved or error entries.
This tab provides visibility into ASN traffic and helps ensure that shipment-related data is fully synchronized.
6.7 Inventory Sync / Inventory Tab
If inventory synchronization is enabled, an Inventory or Inventory Sync tab may be available:
Shows recent inventory sync runs related to Pipe17.
Displays execution timestamps and status messages.
Helps verify that inventory quantities are being updated according to the defined schedule and configuration.
6.8 Logs Tab
The Logs tab aggregates all Pipe17-related integration activity.
Shows entries for orders, ship confirmations, ASNs, and inventory sync events.
Supports filters such as Hide Resolved and Show Errors Only.
Typical columns:
Export/Import date and time.
Type (Order, Ship Confirmation, ASN, Inventory, etc.).
Reference or keyword (such as order number).
Message or error description.
The Logs tab is the primary place to troubleshoot issues and confirm that the Pipe17 integration is functioning as expected.
Last updated
Was this helpful?