# Pro Pack ### 1. Overview The **ProPack integration** allows XoroERP to send orders and products to ProPack for fulfillment and receive shipment updates back into XoroERP. Using this integration, you can: * Export **products** from XoroERP to ProPack so item data stays in sync. * Export **orders** from selected stores for picking and shipping in ProPack. * Receive **ship confirmations** from ProPack to update shipments in XoroERP. * Monitor **SKU syncs** and **log activity** for troubleshooting and audit. Configuration is done once in the **ProPack Integration Settings**, and day-to-day activity is managed from the **Operations** page. *** ### 2. Installation Follow these steps to connect ProPack with XoroERP: 1. **Navigate to Apps** * Go to **Apps** in XoroERP. * Open the **3PL Connections** section. 2. **Add ProPack Connection** * Click **Add 3PL Connection**. * Select **ProPack** from the list of available 3PLs. * This will install/activate the ProPack integration and open the configuration screen. 3. **Enter ProPack Credentials** * Fill in the API keys / credentials provided by ProPack (if applicable). * Save the connection. * Once saved, ProPack will appear in your list of connected 3PLs. 4. **Configure Data Export & Scheduling** * Complete the **Data Export Settings** and **Import/Export Settings** (detailed in the next section). * Optionally enable **Auto Import/Export** to automate the sync. After installation and initial configuration, you can manage day-to-day integration from the **ProPack Operations** page. *** ### 3. Configuration Settings #### 3.1 Data Export Settings These settings control **what** is exported to ProPack and **which orders/products** are included.
| Setting | UI Element | Description | | -------------------------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Export Products to ProPack | Checkbox | When enabled, product master data (SKUs) is exported from XoroERP to ProPack. **This ensures that items exist in ProPack before any orders are exported**, preventing order processing failures due to missing SKUs. | | Link Item(s) Containing Following Tags | Tag List | Restricts which items are included in the product export. **If left blank**, all items in XoroERP are eligible for export. **If one or more tags are selected**, only items associated with those tags are exported to ProPack. | | | | | *** #### **Export Orders to ProPack (Checkbox)**
| Setting | UI Element | Description | | ------------------------------------------------------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Export Orders to ProPack | Checkbox | When enabled, XoroERP exports eligible orders to ProPack. **Orders created in eligible stores are exported after applying configured exclusions and filters.** | | Drop Order(s) From the Following Store(s) | Store List | Excludes orders from selected XoroERP stores. **Any order created in a selected store will not be exported to ProPack**, even if order export is enabled. | | Block Waves Created via QuickShip in Xoro from Flowing into ProPack | Checkbox | When enabled, waves created using **QuickShip** in XoroERP are prevented from being exported to ProPack. **This is useful when QuickShip fulfillment is handled entirely within XoroERP and should not pass through ProPack.** | *** #### Shipping
| Setting | UI Element | Description | | ------------------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Ship Method Name(s) | Text Field | Specifies ship methods that should be **excluded from export** to ProPack. **Any order using a listed ship method will not be exported.** Leave this field blank to allow orders with all ship methods. | | Blocked SKU(s) | Text Field | Lists SKU codes that should be **excluded from order export** to ProPack. **Any order line containing a listed SKU will be skipped during export.** Leave blank to allow all SKUs. | | Allowed Customer(s) | Text Field | Restricts order export to specific customers. **If customers are listed, only orders belonging to those customers are exported.** If left blank, orders for all customers are eligible, subject to other configuration rules. | *** #### Disable Multishipment
| Setting | UI Element | Description | | --------------------- | ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Disable Multishipment | Checkbox | Controls how shipment confirmations received from ProPack are handled in XoroERP.**When enabled**, the first ship confirmation from ProPack is treated as final. All wave lines are closed, and any remaining unshipped quantities are unallocated and not expected to ship later.**When disabled**, multiple shipment confirmations are allowed until the entire order quantity is fulfilled. | *** #### **Filter Options**
| Setting | UI Element | Description | | ------------------------------ | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Filter Name / Operator / Value | Configuration |

Allows defining one or more filters to control which orders are exported to ProPack.

Filter Name specifies the order attribute to filter on (for example, Ship to Country, Order Date, Order Tags, Ship Service, or Order Type).

Operator defines the comparison logic (such as Contains, Does Not Contain, Equals, Greater Than, Less Than, etc.).

Value is the keyword, date, or numeric value used for matching. These filters help refine and restrict the subset of orders that are pushed to ProPack, such as exporting only orders for a specific country or tag.

| *** | Setting | UI Element | Description | | ------------- | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Currency Code | Text Field / Dropdown | Defines the currency code used when exporting orders to ProPack (for example, USD, CAD, or EUR). **This ensures that order values are communicated in the correct currency expected by ProPack.** | | Exchange Rate | Numeric Field | Specifies the exchange rate used when currency conversion is required during export. **This value is applied to convert order amounts into the configured currency code.** | | Default SKU | Text Field | Defines a fallback SKU used when a ProPack shipment confirmation line does not include a SKU. **This prevents processing failures caused by missing or incomplete SKU references in ship confirmations.** | *** #### 3.2 Import/Export Settings These settings control **scheduling** and **notifications**.
| Setting | UI Element | Description | | ----------------------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Time Zone | Dropdown | Selects the operational time zone for the ProPack integration. **All automated import and export schedules run according to this selected time zone.** | | Enable Auto Import / Export | Checkbox | When enabled, XoroERP automatically runs ProPack-related imports and exports based on the configured schedule. **Enabling this option reveals scheduling controls such as recurring frequency and run time.** | | Integration Start Date | Date Field | Specifies the date from which the automated ProPack scheduler becomes active. **Transactions prior to this date are excluded from automated processing.** | | Recurring / Once per Day | Radio Option | Determines how often automated jobs run. **Recurring** runs at regular intervals, while **Once per Day** runs a single time each day at the configured time. | | Hour / Min | Numeric Fields | Defines the time of day for the first run and subsequent scheduled executions, based on the selected scheduling mode. | | Auto Import Start Time Offset | Numeric Field | Applies a negative minute offset to the scheduled execution time, allowing data to be fetched slightly earlier than the defined schedule. **This is useful when upstream data availability is delayed.** | *** #### 3.3 Email Notifications & Log Filters #### **Receive Import Error Notifications by Email(Checkbox)**
| Setting | UI Element | Description | | ------------------------------------------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Receive Import Error Notifications by Email | Checkbox | When enabled, XoroERP sends **instant email notifications** whenever a ProPack import process fails. This allows teams to respond quickly to issues and minimize processing delays. | | Instant Error Email(s) | Text Field | Specifies the email address(es) that should receive instant error notifications. **Multiple email addresses can be entered, separated by commas.** | #### **Send Daily Error Email(Checkbox)**
| Setting | UI Element | Description | | ---------------------- | ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Send Daily Error Email | Checkbox | When enabled, XoroERP sends a **daily consolidated summary** of all ProPack integration errors. This helps teams review issues at a glance without receiving multiple individual alerts. | | Daily Error Email(s) | Text Field | Specifies the email address(es) that should receive the daily error summary. **Multiple email addresses can be entered, separated by commas.** | | Exclude Logs | Text Field | Defines which log entries should be **excluded from instant and daily error emails**. Enter comma-separated keywords or wildcard patterns. **Supports `*` for partial matching** (for example, `*info*`). | *** ### 4. Operations Page The **Operations** page is where you monitor and manage day-to-day ProPack integration.\ It includes four tabs: * **Orders** * **Ship Confirmations** * **SKU** * **Logs** The overall behavior is similar to ReadyShipper, but field labels and filters are specific to ProPack. *** #### 4.1 Orders
Use the **Orders** tab to push orders from XoroERP to ProPack and monitor their export status. **Purpose** * Export eligible orders to ProPack for fulfillment. * Track whether orders exported successfully or encountered errors. * Re-run or reprocess problematic records. **Key Actions** * **Run**\ Triggers export of selected orders from XoroERP to ProPack based on your configuration and filters. * **Mark as Resolved**\ Marks the selected records as resolved/handled in XoroERP. Useful after you verify that an export issue or warning has been addressed. * **Mark as Unresolved**\ Reopens previously resolved records so they can be reviewed or reprocessed again. **Search / Filter Fields** * **Order #** – Search by order number. * **Keyword** – Search by keyword (may include customer name, tag, or reference text). You also have global filters like: * **Hide Resolved** – Hide all records marked as resolved to focus on active or pending ones. * **Show Errors Only** – Display only records that have errors or warnings. **Information Displayed** Typically includes: * **Order #** – XoroERP order reference. * **Last Execution Date** – Date/time of the last export attempt. * **Message** – Status or error message from the export attempt (e.g., success, missing SKU, invalid ship method). > Use *Show Errors Only* to quickly locate failed exports, correct the issue (like a missing SKU or a blocked method), and run them again using **Run**. *** #### 4.2 Ship Confirmations
Use the **Ship Confirmations** tab to receive and review shipment data returned from ProPack. **Purpose** * Import shipment confirmations from ProPack back into XoroERP. * Update shipment status and quantities for exported orders. * Review and troubleshoot shipment-related errors. **Key Actions** * **Run**\ Fetches and processes shipment confirmations from ProPack. * **Mark as Resolved**\ Marks selected shipment records as handled after validation. * **Mark as Unresolved**\ Reopens records for further investigation or reprocessing. **Search / Filter Fields** * **Ship Confirmation #** – Search by ProPack shipment reference. * **Keyword** – Search based on a keyword (could be order ref, customer, or comment text). Global filters may include: * **Hide Resolved** – Exclude resolved confirmations from the grid. * **Show Errors Only** – Focus only on failed or problematic confirmations. **Information Displayed** * **Ship Confirmation #** – Unique shipment identifier from ProPack. * **Last Execution Date** – When the confirmation was last processed. * **Message** – Status, errors, or additional notes related to the confirmation. Once confirmations are processed successfully, shipment data in XoroERP (quantities, tracking, status) is updated accordingly. *** #### 4.3 SKU
The **SKU** tab manages product synchronization between XoroERP and ProPack. **Purpose** * Push new SKUs created in XoroERP to ProPack. * Update existing SKUs (e.g., description, UOM) in ProPack when changed in XoroERP. * Monitor SKU sync errors and reprocess them if needed. **Key Actions** * **Run**\ Pushes or updates SKUs in ProPack. * **Mark as Resolved**\ Marks SKU records as handled, typically after a successful retry or fix. * **Mark as Unresolved**\ Reopens SKU records for investigation. **Search / Filter Fields** * **SKU #** – Search by item number. * **Keyword** – Search by generic keyword (description, tag, etc.). **Information Displayed** * **SKU #** – The product code from XoroERP. * **Last Execution Date** – Last sync attempt for this SKU. * **Message** – Status or error message (e.g., product created, updated, invalid data). > ProPack supports SKU creation and updates driven from XoroERP, so SKU tab is critical to keep item data aligned. *** #### 4.4 Logs
The **Logs** tab gives you a consolidated view of all integration activity and is your main troubleshooting tool. **Purpose** * Monitor export/import runs for **Orders, Ship Confirmations, SKUs**. * View detailed success/failure messages. * Filter down to only errors for quick debugging. **Search / Filter Columns** Common columns include: * **Export Date / Import Date** – When the job ran. * **Type** – Entity type (Order, Ship Confirmation, SKU, etc.). * **Keyword** – Allows free-text search. * **Order Ref #** – Order reference (if applicable). Additional filters: * **Hide Resolved Exports** – Only show records that are still pending/unresolved. * **Show Errors Only** – Focus strictly on failed or error entries. **Information Displayed** * **Import Date / Export Date** * **Start Date / End Date** * **Entity Type** * **Resolved (Yes/No)** * **Type** – Direction (Import/Export) or entity subtype. * **Message / Details** – Status and error details. You can use the **Exclude Logs** setting in configuration to prevent certain log messages from appearing in email notifications. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.xorosoft.com/xoroerp-1/3pl-connections/pro-pack.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.