> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/apps-and-integrations/edi-connections/dsco.md).
# DSCO
### **1. Overview**
The **DSCO Integration** in XoroERP enables automated exchange of EDI documents between retailers, DSCO, and XoroERP. This integration supports purchase order import, shipment confirmations, ASN processing, and inventory synchronization, ensuring a controlled, traceable, and reliable EDI data flow.
The DSCO integration is designed for operations and support teams to efficiently manage dropship EDI transactions, monitor document status, and resolve exceptions with minimal manual intervention, while maintaining alignment with retailer-specific fulfillment requirements.
### **2. Workflow**
#### **2.1 Order Import Flow (EDI 850)**
**Sequence:**\
**Retailer → DSCO → XoroERP**
Purchase orders (EDI **850**) are fetched from DSCO for the configured retail trading partner.
Incoming purchase orders are created in XoroERP under the configured **store** and **warehouse location**.
Based on integration settings, purchase orders can be **auto-released** after import and optionally **split by warehouse location** to support multi-location fulfillment.
Item matching is performed using configured item identifiers such as **UPC**, **GTIN**, or retailer-provided item codes to ensure accurate SKU mapping during order creation.
Any validation or mapping issues encountered during import are logged for review and retry.
***
#### **2.2 Shipment Confirmation Flow (EDI 856)**
**Sequence:**\
**XoroERP → DSCO → Retailer**
Once orders are fulfilled in XoroERP, shipment confirmations are generated.
Shipment confirmation documents (EDI **856**) are sent from XoroERP to DSCO, either **individually** or in **batch mode**, based on the configured export settings.
Each shipment confirmation includes key fulfillment details such as shipped quantities, carrier, tracking numbers, and ship dates.
DSCO forwards the shipment confirmation to the retailer, ensuring timely and accurate fulfillment updates.
***
#### **2.3 ASN Processing Flow**
If ASN processing is enabled, Advance Ship Notices are imported from and acknowledged through DSCO based on the configured send and receive document settings.
***
#### **2.4 Inventory / SKU Synchronization**
When enabled, inventory synchronization runs automatically once per day, shortly after midnight, using configured filters for tags and stores.
***
#### **2.5 Error Retry & Status Update**
Failed records are logged with detailed error messages and can be retried after correction without reprocessing successful transactions.
### 3. Settings
#### **3.1 Data Export Settings**
The following accounts and configurations will be used in XoroERP. This can be changed later.
| **Field Name** | **UI Control** | **Description** |
| ------------------------------------ | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Store | Dropdown | Specifies the XoroERP store where incoming purchase orders received from DSCO will be created and managed. |
| Location Name | Dropdown | Defines the default warehouse location in XoroERP where imported DSCO orders will be placed for fulfillment and inventory allocation. |
| Default SKU | Text Field | Specifies a fallback SKU used when item matching fails during DSCO order import, ensuring orders are not rejected due to missing or unmatched item data. |
| Trading Partner | Dropdown | Identifies the retail trading partner for which orders will be fetched and processed through the DSCO integration. |
| Enable Test Mode | Checkbox | Processes all DSCO EDI send and receive transactions in test mode, allowing validation without impacting live orders or inventory. |
| Split Orders by Location | Checkbox | Splits imported DSCO orders into separate XoroERP orders based on warehouse location to support location-specific fulfillment. |
| Sync Purchase Order to Xoro | Checkbox | Enables importing purchase orders from DSCO into XoroERP. Enabling this option reveals the Auto Release Purchase Orders setting. |
| Auto Release Purchase Orders | Checkbox | Automatically releases imported DSCO purchase orders in XoroERP after synchronization, eliminating the need for manual release. |
| Restrict Close and Create for Orders | Checkbox | Restricts manual creation or closure of orders in XoroERP, ensuring orders are managed strictly through the DSCO EDI workflow. |
#### 3.2 Auto Wave Sales Orders
| **Field Name** | **UI Control** | **Description** |
| ------------------------------------ | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Auto Release Sales Orders | Checkbox | Automatically releases sales orders in XoroERP immediately after they are created through the DSCO integration. Enabling this option reveals the Auto Wave Sales Orders setting. |
| Auto Wave Sales Orders | Checkbox | Automatically creates fulfillment waves for eligible sales orders once they meet the configured allocation and fulfillment criteria, removing the need for manual wave creation. |
| WaveCreateCode | Dropdown | Defines the inventory allocation rule applied when sales orders are automatically waved. The selected option controls how and when inventory is reserved for DSCO order fulfillment. |
| Allocate Full Order Only | Selection Option | Allocates inventory only when all order lines and quantities are fully available, ensuring DSCO orders are fulfilled as complete units. |
| Allocate Full Quantity Only Per Line | Selection Option | Allocates inventory for an order line only when its full quantity is available, allowing partial fulfillment by line for DSCO orders. |
| Allocate What Is Available | Selection Option | Allows partial allocation based on available inventory, enabling DSCO orders to be waved and fulfilled even when stock is limited. |
#### 3.3 EDI Document Controls
| **Field Name** | **UI Control** | **Description** |
| ------------------------------------ | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Send Document 855 | Checkbox | Enables XoroERP to send the EDI 855 (Purchase Order Acknowledgment) to DSCO, confirming that purchase orders have been received and accepted for processing. |
| Auto Acknowledge Order | Checkbox | Automatically acknowledges DSCO purchase orders once the EDI 855 document is generated and successfully transmitted. |
| Third Party Client Code | Text Field | Specifies the DSCO client code used to identify the retailer or trading partner for outbound and inbound EDI transactions. |
| Import 855 | Checkbox | Allows XoroERP to import EDI 855 acknowledgment documents received from DSCO and update the corresponding purchase order status in XoroERP. |
| Send Document 856 | Checkbox | Enables XoroERP to send EDI 856 (Shipment Confirmation) documents to DSCO, providing shipment details such as shipped items, quantities, carrier, and tracking information. |
| Send Document 856 in Batch | Checkbox | Sends multiple EDI 856 shipment confirmations together in batch mode, improving performance for high-volume DSCO fulfillment operations. |
| Send Document 810 | Checkbox | Enables XoroERP to send EDI 810 (Invoice) documents to DSCO for retailer billing and financial reconciliation. |
| Allow Document from Different Source | Checkbox | Allows XoroERP to accept and process EDI documents received from multiple DSCO source systems for the same trading partner, instead of enforcing a single source endpoint. |
| Allowed Customer | Text Field | Specifies the customer codes whose EDI documents are allowed to be processed through the DSCO integration. Multiple customer codes must be separated using the \` |
#### 3.4 General Settings
| **Field Name** | **UI Control** | **Description** |
| ----------------------------------------------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Use Purchase Order Number as Customer Purchase Order Number | Checkbox | Stores the purchase order number received from DSCO as the Customer Purchase Order Number in XoroERP, ensuring consistent reference between DSCO EDI data and internal orders. |
| Item Identifier Code | Dropdown | Specifies the item identifier (such as UPC, GTIN, or other DSCO-supported item codes) used to match incoming order lines with items in XoroERP, ensuring accurate item mapping during order import. |
| Use Prepack Item While Dropping Order | Checkbox | Processes incoming DSCO orders using prepack logic by grouping component items into predefined packs during order creation, supporting bundled or prepack items sent by retailers. |
| Recalculate Taxes | Checkbox | Recalculates taxes in XoroERP during DSCO order creation instead of using tax values provided in the EDI file, ensuring tax accuracy based on internal tax configuration. |
| Apply Pricing Rule | Checkbox | Applies XoroERP pricing rules to imported DSCO orders, allowing system-defined pricing, discounts, or contracts to override prices received from the retailer. |
| Filter Name | Dropdown | Selects the order attribute used to filter incoming DSCO orders during import, controlling which orders are created in XoroERP. |
| Operator | Dropdown | Defines the comparison logic applied to the selected filter attribute, such as equals, contains, or greater than. |
| Value | Text Field | Specifies the value used to evaluate the filter condition; only DSCO orders matching the defined criteria are imported into XoroERP. |
#### 3.5 Inventory Sync Settings
| **Field Name** | **UI Control** | **Description** |
| ------------------------------------------------- | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Enable Daily Inventory Sync | Checkbox | Enables a once-per-day full inventory synchronization from XoroERP to DSCO, executed shortly after midnight. The sync sends inventory levels from the previous day, providing retailers with a consistent daily inventory snapshot. |
| Inventory Field | Dropdown | Selects the XoroERP inventory metric sent to DSCO, such as available, on-hand, allocated, or other system-defined inventory values. This determines how inventory quantities are represented to retailers. |
| Sync Inventory of Items Containing Following Tags | Multi-Select / Text Field | Restricts inventory synchronization to items containing specific tags, allowing controlled sharing of approved or DSCO-eligible items only. |
| Sync Inventory from All Stores | Checkbox | Synchronizes inventory from all stores configured in XoroERP, enabling centralized inventory reporting to DSCO. |
| Sync Inventory of Items from Following Stores | Multi-Select Dropdown | Limits inventory synchronization to selected stores, allowing inventory to be shared only from specific warehouses or fulfillment locations. |
#### **3.6 Import / Export Settings**
These settings control how **XoroERP integrates with** Orderful, including job scheduling, automation, and error notifications. They ensure that import and export processes run on time, follow the correct time zone, and provide visibility into integration issues for reliable day-to-day operations.
| **Setting** | **UI Element** | **Description** |
| ----------------------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Time Zone | Dropdown | Defines the time zone used for all scheduled DSCO import and export jobs. All automated DSCO processes—such as order import, shipment confirmation export, inventory sync, and status updates—run according to this time zone to ensure consistent execution timing. |
| Enable Auto Import/Export | Checkbox | Enables XoroERP to automatically run DSCO import and export jobs based on the configured schedule. When disabled, all DSCO-related processes must be triggered manually from the Operations page. |
| Integration Start Date | Date Picker | Specifies the date from which automated DSCO jobs begin running. No scheduled DSCO tasks are executed before this date. |
| Hour | Dropdown | Defines the hour at which scheduled DSCO jobs execute, based on the selected time zone. |
| Min | Dropdown | Defines the minute within the selected hour when DSCO jobs are triggered. |
| Auto Import Start Time Offset | Numeric Input | Allows a negative minute offset to run DSCO import jobs earlier than the scheduled time, helping account for upstream retailer or DSCO processing delays. |
#### Error Handling & Notifications
| **Setting** | **UI Element** | **Description** |
| ------------------------------------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Receive Import Error Notifications by Email | Checkbox | When enabled, XoroERP sends immediate email alerts whenever a DSCO import or export job fails, providing real-time visibility into integration issues. |
| Instant Error Email(s) | Text Input | Becomes available when instant error notifications are enabled. Accepts a comma-separated list of email addresses that receive real-time DSCO error alerts. |
| Send Daily Error Email | Checkbox | Sends a consolidated daily summary email containing all DSCO import and export errors encountered during the day. |
| Daily Error Email(s) | Text Input | Becomes available when daily error emails are enabled. Accepts a comma-separated list of email addresses that receive the DSCO daily error summary. |
| Error Email Filter Keywords | Text Input | Filters out specific DSCO log messages from email notifications using comma-separated keywords or wildcard patterns (e.g., `*Inventory*`), helping reduce alert noise from known or non-critical issues. |
### 4. Operations Page
**Header Options**
* **Import Data** – Manually trigger the import of EDI documents from Orderful into XoroERP using the selected date range.
* **Start Date** – Defines the beginning of the date range for importing EDI documents from trading partners.
* **End Date** – Defines the end of the date range for importing EDI documents from trading partners.
* **Import** – Executes the import process based on the specified date range and selected document types.
***
#### **Previous Exports**
View a history of EDI documents processed through the Orderful integration, with options to track status, review errors, and reprocess records as needed.
***
#### **5.1 Orders**
The Orders tab manages the import and tracking of purchase orders and sales orders exchanged with trading partners through Orderful.
#### **Purpose**
To track, process, and resolve issues related to order synchronization between trading partners and XoroERP via Orderful.
#### **Fields / Displayed Data**
* **Order #** – Unique identifier assigned to the order in XoroERP.
* **Trading Partner** – Indicates the trading partner from which the order was received.
* **Document Type** – Identifies the EDI document type (e.g., Purchase Order 850).
* **Last Execution Date** – Timestamp of the most recent import or processing attempt.
* **Message** – Displays validation errors, mapping issues, or processing status messages.
#### **Options**
* **Run** – Reprocesses the selected order records through the Orderful integration.
* **Mark as Resolved** – Marks the order as successfully processed to prevent duplicate handling.
* **Mark as Unresolved** – Reopens a previously resolved order for reprocessing.
#### **Filters / Checkboxes**
* **Hide Resolved Records** – Hides orders already marked as resolved.
* **Show Errors Only** – Displays only orders that encountered processing errors.
#### **Usage Example**
If an order fails due to item or location mapping issues, enable *Show Errors Only*, review the *Message* column, correct the configuration, and click *Run* to retry processing. Mark the order as resolved once successful.
***
#### **5.2 Purchase Orders**
The Purchase Orders tab specifically tracks inbound purchase order documents received from trading partners through Orderful.
#### **Purpose**
To monitor the import and processing of purchase orders into XoroERP.
#### **Fields**
* **Purchase Order #** – Trading partner’s purchase order reference.
* **Trading Partner** – Source of the purchase order.
* **Last Execution Date** – Timestamp of the most recent processing attempt.
* **Message** – Displays processing or validation details.
#### **Options**
* **Run** – Reprocesses selected purchase orders.
* **Mark as Resolved** – Marks successfully imported purchase orders.
* **Mark as Unresolved** – Reopens purchase orders for reprocessing.
#### **Usage Example**
If a purchase order is missing in XoroERP, users can review this tab to confirm whether it failed during import and retry processing.
***
#### **5.3 ASNs**
The ASNs tab manages outbound Advance Ship Notices (EDI 856) sent from XoroERP to trading partners via Orderful.
#### **Purpose**
To track the creation and transmission of ASNs and ensure shipment details are communicated successfully.
#### **Fields**
* **ASN #** – Unique ASN identifier.
* **Order Reference** – Associated order number.
* **Last Execution Date** – Timestamp of the last export attempt.
* **Message** – Displays export status or errors.
***
#### **5.4 Invoices**
The Invoices tab tracks outbound invoice documents (EDI 810) sent to trading partners through Orderful.
#### **Purpose**
To ensure invoice data is successfully transmitted for billing and reconciliation.
#### **Fields**
* **Invoice #** – Unique invoice reference.
* **Trading Partner** – Invoice recipient.
* **Last Execution Date** – Timestamp of the export attempt.
* **Message** – Displays transmission status or errors.
***
#### **5.5 Logs**
The Logs tab tracks all Orderful EDI activities, providing a complete audit trail of document imports, exports, and system actions.
#### **Purpose**
To monitor, troubleshoot, and verify all EDI interactions between XoroERP and trading partners.
#### **Columns / Information Displayed**
* **Execution Date** – Date and time of the EDI operation.
* **Document Type** – Order, Purchase Order, ASN, or Invoice.
* **Trading Partner** – Source or destination of the document.
* **Reference #** – Associated order, ASN, or invoice reference.
* **Message** – Detailed processing, warning, or error information.
#### **Filters & Options**
* **Do Not Show Resolved Records** – Hides entries already marked as resolved.
* **Filter by Document Type** – Filters logs by Orders, ASNs, or Invoices.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.xorosoft.com/xoroerp-1/apps-and-integrations/edi-connections/dsco.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.