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

  1. Log in to your XoroERP account.

  2. From the main dashboard, navigate to the Apps module.

  3. Open the 3PL Connections tab.

  4. Click Add 3PL Connection.

  5. From the list of available integrations, select Pipe17.

2.2 Install the Pipe17 Integration

  1. Click Install to add the Pipe17 integration to your XoroERP instance.

  2. Once installed, the Pipe17 integration will appear under your active 3PL or integration connections.

2.3 Configure Account and Authentication

  1. Open the Pipe17 integration settings from the list of active connections.

  2. 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

  3. Save the configuration and ensure that connectivity is successful before enabling auto import/export.


3. Workflow

The Order Fulfillment (Pipe 17) integration automates the complete order processing and inventory synchronization cycle between XoroERP and the configured fulfillment partner.

This workflow ensures seamless movement of order, shipment, and inventory data across systems.


3.1 Wave Creation in XoroERP

Sales Orders are created in XoroERP and grouped into waves based on defined allocation rules, warehouse logic, and fulfillment criteria.

Each wave represents a batch of orders prepared for processing through the Pipe 17 integration.


3.2 Product / SKU Export (Push SKU Enabled)

When Push SKU is enabled, product master records are exported from XoroERP to the fulfillment partner.

This ensures that all items referenced in fulfillment transactions exist in the partner system with accurate SKU and product details.

Flow: XoroERP β†’ Pipe 17


3.3 Order Export to Order Fulfillment (Order Push Enabled)

After waves are generated and orders satisfy the configured export filters, XoroERP automatically exports the orders to the fulfillment partner.

These orders are received and queued for picking, packing, and shipment processing.

Flow: XoroERP β†’ Pipe 17


3.4 Shipment Fulfillment and Confirmation

The fulfillment partner processes the exported orders and performs shipment operations.

Once an order (full or partial) is shipped, shipment confirmation and tracking details are generated.

When Fetch Ship Confirmation is enabled in XoroERP:

  • Shipment confirmations are fetched into XoroERP.

  • Related order and wave records are updated with:

    • Shipment status

    • Tracking number(s)

    • Shipped quantities

Flow: Pipe 17 β†’ XoroERP


3.5 Inventory Synchronization (Sync Inventory Enabled)

When Sync Inventory is enabled, XoroERP updates on-hand inventory quantities based on the stock availability reported by the fulfillment partner.

This ensures that:

  • Order allocations are based on accurate, real-time inventory levels.

  • Overselling is minimized.

  • Inventory shortages are identified in a timely manner.

4. Configuration Settings

The Configuration Settings for Pipe17 control which orders are exported, how shipments and quantities are handled, and how inventory synchronization and notifications operate.


4.1 Data Export Settings

The following accounts and configurations are used in XoroERP for Pipe17. These settings can be modified as required.

Pipe17 Account Defines the Pipe17 integration profile used for data exchange between XoroERP and Pipe17.


Export orders to Pipe17 (Checkbox) Enables the export of eligible orders from XoroERP to Pipe17. Orders that meet all configured criteria (store, filters, customer, ship method, etc.) are sent to Pipe17 for routing and processing.


Drop Order(s) from the Following Store(s)

Drop order(s) from the following store(s) Specifies the XoroERP store(s) whose orders are eligible for export to Pipe17.

  • Orders from selected stores are considered for export.

  • Orders from non-selected stores are excluded from the Pipe17 integration.


Block waves created via QuickShip (Checkbox) When enabled, waves created through QuickShip are blocked from export to Pipe17. This is typically used to prevent internal, test, or ad-hoc orders from being routed through Pipe17.


Send Order Updates to Pipe17 (Checkbox) When enabled, order updates such as status or quantity changes are sent to Pipe17 after the initial export, ensuring downstream systems remain synchronized.


Ship Method Name(s) Defines shipping methods that should be excluded from export. Orders using these ship methods will not be sent to Pipe17.


Blocked SKU(s) Lists SKUs that should not be exported. Any order containing these items is excluded from Pipe17 processing.


Allowed Customer(s) Restricts the integration to the selected customers. If left blank, all customers are eligible subject to other filters.


Disable multishipment (Checkbox)

  • When enabled, the first shipment confirmation is treated as final and all wave lines are closed.

  • When disabled, multiple shipment confirmations are supported until the full quantity is shipped.


Filter Configuration

Filter Name / Operator / Value Provides advanced filtering to restrict which orders are exported to Pipe17.


Default SKU (Text field) Fallback SKU used when item identifiers are missing or unmapped.


Split quantity (Checkbox) When enabled, merged quantities are split into individual lines during export.


Auto Create Carrier and Ship Services (Checkbox) Automatically creates missing carrier or ship service records received via Pipe17.


Export ASNs to Pipe17 (Checkbox) Enables exporting Advance Shipping Notices from XoroERP to Pipe17.


Use Ship Date as transaction date (Checkbox) Uses the shipment date as the transaction date for Pipe17 records.


Allow third-party merged shipments (Checkbox) Allows merged third-party shipments to be processed and invoiced separately in XoroERP.


4.2 Inventory Sync Settings

Controls how inventory is synchronized between Pipe17 and XoroERP.

Enable Full Inventory Sync (Checkbox) Activates scheduled full inventory synchronization with Pipe17.


Inventory Identifier Code

Defines the identifier used to match inventory records.


Xoro Inventory Level

Specifies the inventory level in XoroERP used for comparison.


Third Party Inventory Level

Specifies the inventory level received from Pipe17.


Inventory Sync Schedule

Recurring / Once per day, Hours / Mins Defines how frequently inventory synchronization runs.


4.3 Import/Export Settings

The Import/Export Settings control the scheduling and notification behavior for all Pipe17-related data exchange.

Time Zone Sets the time zone used for scheduling all Pipe17 import and export jobs. All automated sync operations will follow this time setting.

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.

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.

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.

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.


5. 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.

Accessing the Operations Page

  1. Open the Apps module in XoroERP.

  2. Navigate to the 3PL Connections or integration list.

  3. Select the Pipe17 connection.

  4. Click on Operations to open the Pipe17 Operations Page.

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).

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.

Previous Exports

View a history of previously exported data with options to manage and reprocess items.

5.1 Orders

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.

5.2 Ship Confirmations

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.

5.3 ASNs

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.

5.4 Inventory Sync / Inventory

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.

5.5 Logs

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?