Updates

  • We have updated our logic for accepting tracking number data. The Dsco platform will now return a warning for tracking numbers that are invalid. When the Dsco platform receives invalid tracking numbers, those values are stored, the order status updates to Shipped, and a warning will be given. For suppliers who upload files to their Dsco accounts (whether by automated process or through the portal), we will send an email to warn the supplier that invalid tracking numbers were detected. For suppliers who input tracking numbers into the portal manually, without the use of files, a pop-up will ask the user to confirm that they wish to save tracking numbers detected as being invalid.

  • We have updated the way ISA13 numbers increment on retailer accounts. Rather than storing separate ISA13 numbers for each automated job on an account, and incrementing those numbers only when the related job runs, we now store only one account-wide ISA13 number which increments every time any job on the account runs.

  • We have updated the functionality of several invoice fields in the portal. Discount Due Date and Discount Days Due are no longer recommended fields. Also, users are required to populate either the Net Due Date field or the Net Days field, but not both.

Fixes

  • Fixed bug that did not allow a user to pass validation pop-up if either Net Due Date or Net Days was populated.
  • Fixed bug in step 4 of Gandalf, Working with Orders, which threw an error if the user selected portal/manual file upload in Step 2, and later complied with instructions in Step 4 and also shipped test SKUs via two separate shipments.
  • Fixed bug that allowed a user to begin the process of creating an invoice via the portal for orders not in Shipped status.
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.