• Shipping Logic. Dsco's just released Shipping Logic feature is a first step towards our full Shipping Science capabilities. It allows retailers to provide an estimated or required delivery date that the platform will then use to determine the best carrier and method for ensuring on-time delivery. For ultimate flexibility, Dsco lets retailers configure which carriers and methods we should include when asking carriers for delivery and cost estimates. The priority that retailers set for each carrier will determine the winner in the case of a tie. To utilize this Shipping Science feature, enable it within your account, set your trigger, and configure the allowed carriers and methods for each trading partner. Then, as orders are created, if the appropriate trigger is detected, Dsco will initiate its Shipping Science logic to determine the best carrier and method, apply that to the order, and then send the order to the supplier for fulfillment.
  • Recycled POs. Before the explosion of ecommerce and dropshipping, no one could have imagined running out of PO numbers. Unfortunately, that’s exactly what’s happening for many retailers as the number of individual orders continues to climb. Dsco is resolving this issue by now allowing retailers to choose a set number of days after which a PO number will be archived. Once a PO number is archived, it can then be reused for new orders.
  • New Gift Alert Message for Suppliers. Retailers and suppliers need to be on the same page when it comes to fulfilling gift orders that often come with special instructions. The portal will now display a message alerting suppliers to the gift status of an order, and provide them with gift attribute data through an “Additional Info” tab. This reduces human error and the need for verbal coordination in the gift-order fulfillment process. 
  • New Warehouse Manager Tab. The ability to access multiple supplier warehouse locations for order fulfillment is essential to reducing drop ship delivery costs. Why use a distant warehouse to ship an order when the same supplier has a fulfillment center much closer to the end customer? That’s why Dsco’s new Warehouse Manager feature gives supplier partners the opportunity to add all warehouse locations within their settings. Unlisted warehouses on inventory files will also be auto-added to the Warehouse Manager. This not only allows Dsco to access such location data for its Shipping Science capabilities, but lays the groundwork for later advanced fulfillment optimization features.
  • Required/Expected Delivery Date Editing. Retailers now have the ability to edit the required and/or expected delivery date of an order if “Shipping Logic” is turned off and the order is in either the “Created” or “Shipment Pending” statuses. If the order is in the “Created” status, the retailer does not have to take any further action once the required/expected delivery date has been modified. Meanwhile, if the order is in the “Shipment Pending” status, the platform will display a message informing the retailer to contact their supplier regarding the date change.
  • Last Name Enforcement For Orders Created via API. We love API for its real time data exchange capabilities. We’re well aware, however, that switching to new systems can sometimes lead to unintended issues. This was the case recently when the new API systems of some of our retailer users allowed orders without last names to pass through, despite the fact that their EDI specs required last names for export. This led to a lot of suppliers being unable to export such orders. In order to resolve this issue, we are now enforcing “last name” as a requirement for all orders running through Dsco. Any orders without last names will be returned with an error.


  • EDI 810 Updates Overwriting Line Item Line Number. Some of our retail customers noticed that Dsco Invoice (EDI 810) imports were sometimes exporting an empty line item number. This was caused by supply partners not including the line number in the IT101 segment. We’ve now resolved this issue by having the platform automatically pull missing IT101 line numbers from the original order and populate them on the invoice.
  • DSCO EDI 850 Fixes. We’re happy to say that we’ve fixed two EDI 850 (version 5010) export issues with this week’s release: (1) The 850 export failures that some of our customers were facing have now been resolved; (2) The other 850 export issue with missing CTT segments has also been taken care of and will no longer be a problem.
Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.