Skip to main content

Troubleshooting Guide: DSDLink Import Conflicts and Routing Logic

Distributor steps for DSDLink orders landing in Import Conflicts or on a later delivery date in Encompass: check cut-off times, locked load sheets and Routing Method 2 logic. Requires v25.01+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 25.01

Pre-Conditions

  • DSDLink Integration: Active account for customer order submissions.

  • Routing Configuration: Exchange Configuration set to Routing Method 2: Next Scheduled Delivery Event Then Stop.

  • Cut-off Times: Defined "Order Cut-Off Times" in Route Types (e.g., 4:00 PM).

  • Permissions: User access to the Import Conflicts dashboard and Invoice Audit records.

Steps

  1. Identify the Conflict: Navigate to the Import Conflicts dashboard and locate the invoice.
    ​
    ​

  2. Verify the Submission Timestamp: Open the Invoice Audit. Compare the "Date Added" against your Route Type cut-off time.
    ​
    ​

  3. Check Load Sheet Status: Check the Field Audit for the intended delivery date. If the Load Sheet was "Locked for Routing" (by a user or Auto_Lock_LoadSheets) before the invoice arrived, the "Push" logic was triggered.
    ​
    ​

  4. Review the PO Date: Check the raw 850 file for the PODate. The dashboard often displays this requested date, even if the system attempted to find a different stop based on routing rules.
    ​
    ​

  5. Contact Support if Unresolved: If the target date does not align with the customer's schedule, contact support with the following:
    ​
    ​

    • Invoice Audit ID and Customer ID.
      ​
      ​

    • Exact Error Message (e.g., "Problem 5: Order cut-off time passed").
      ​
      ​

    • Timestamp of order submission vs. your system's cut-off.
      ​
      ​

    • Exchange Task ID.

Fields And Definitions

In an Exchange Configuration using Routing Method 2, the software validates the order date against your routing schedule and warehouse status.
​
​

How the Logic Works

  1. The Start Point: Regardless of the date the customer selects in DSDLink (PODate), the system resets its search starting point to Today + 1 (tomorrow).
    ​
    ​

  2. The Cut-off/Lock Check: The system checks the Route Type cutoff and the Load Sheet status. If the invoice arrives after the cutoff (e.g., 4:01 PM) or the Load Sheet is Locked for Routing, that date is skipped.
    ​
    ​

  3. The Push: The system jumps to the next scheduled stop in the customer's record. This is why an order for "tomorrow" may show a date for "next week" if it was submitted just minutes after the load sheet locked.

  • Routing Method 2: Logic that finds the next valid delivery date based on the customer’s assigned stop schedule, starting from Today + 1.
    ​
    ​

  • Locked for Routing: Status of a Load Sheet meaning that no additional edits can be made while picking and routing is in process. No further invoices can be added without manually unlocking it.
    ​
    ​

  • Import Conflict: A holding area for invoices that cannot be placed on a Load Sheet due to errors or missed cut-offs.
    ​
    ​

  • PODate: The specific delivery date requested by the customer in the DSDLink interface.

Best Practices

  • Align Lock Times: Coordinate your Auto_Lock_LoadSheets schedule with your order cut-off times.
    ​
    ​

  • Monitor Post-Cutoff: Review the Import Conflicts dashboard daily shortly after the cut-off time to manually move orders that missed the window.
    ​
    ​

  • Communicate with Users: Ensure DSDLink users know that even a one-minute delay past the cutoff will push their order to the next scheduled delivery.

Did this answer your question?