This article answers the most common questions we receive about the second phase of our 2021–22 Security Initiative.
What is 3PL Central's 2021–22 Security Initiative?
3PL Central is dedicated to providing a safe and secure experience to all 3PL Warehouse Manager customers, and one way we accomplish this is by complying with cybersecurity best practices. Our 2021–22 Security Initiative consists of two phases.
Phase I: On June 30, 2021, we discontinued support for the HTTP protocol on June 30, 2021 and required all customers to migrate to and utilize the HTTPS encrypted communication protocol for all communication with our systems.
Phase II: On March 1, 2022, we are sunsetting three product offerings: ODBC, SOAP APIs, and our Classic Mobile application. This requires all customers to migrate to newer solutions, such as Small Parcel Suite, REST APIs, and SmartScan, by February 28, 2022.
Why are you sunsetting these product offerings?
The most important reason for sunsetting ODBC, SOAP APIs, and Classic Mobile is to greatly improve the security standing of our software and your business. It will also enable us to free up valuable resources that are used to maintain these legacy technologies so that we can put all our focus and effort into enhancing existing products and building new products that bring more value to your business.
How will sunsetting these product offerings improve security?
These offerings are considered legacy technologies, which are often vulnerable to both security and compliance risk because they cannot be updated with the latest security protocols.
According to Help Net Security, malware attacks increased by 358% in 2020, and legacy technology is a common vulnerability that is targeted by cybercriminals. Utilizing the latest security offering decreases your chances of a costly malware or ransomware attack.
How can I tell if this security change requires action on my part?
All customers who are impacted by these security changes were contacted via email and in-app messaging on October 5, 2021 and will receive monthly reminders until sunsets go into effect on March 1, 2022.
If any of the below statements apply to you, you are required to take action to migrate to a new solution:
- Your warehouse leverages our ODBC offering to export order tracking information into a third-party shipping software
- You and/or your customer utilizes a SOAP API integration that was not built or deployed by 3PL Central
- Your warehouse uses our Classic Mobile scanning solution
If these statements do not apply to you, no further action is required on your part at this time.
What steps do I need to take if I believe this change requires action on my part?
The process varies depending on which product offerings you currently use. To help you better understand what your next steps are, we’ve created the following help articles:
- Preparing for ODBC Sunset
- Migrating from SOAP to REST API
- Migrating from Classic Mobile to SmartScan
What does REST API offer that SOAP does not?
REST API has much more robust credentialing requirements compared to SOAP API, which makes it a significantly safer method of communication. REST also offers a number of capabilities that are not available through SOAP (e.g., placing inventory on hold) and is regularly updated with new functionalities.
What does SmartScan offer that Classic Mobile does not?
SmartScan offers a variety of new features that are not accessible through Classic Mobile—including the ability to create new receipts, edit basic receipt information, update track-by's when receiving against an ASN, confirm receipts, print MU labels, pick in batches, pick directly to bins, modify packages when packing orders, look up MU information, and count inventory by location.
What if I can't replicate my existing workflows in SmartScan?
We are aware that there are a few features available in Classic Mobile that are not yet built into SmartScan, and we expect to release these features in SmartScan before the planned sunset date of March 1, 2022.
That's why we're asking you to test your current workflows in SmartScan as soon as possible. If you find that something is missing, we need you to submit a support case immediately so that we have your use case captured and can address the issue before Classic Mobile is sunset. Please see our article for Migrating from Classic Mobile to SmartScan for further guidance.
Why are you requiring me to change my workflow(s) during busy season?
We understand that the last several months of the year is extremely busy for your business. That's why we're letting you know about these important security changes and the required actions in advance so that you can plan for them over the next few months. ODBC, SOAP API, and Classic Mobile will not be sunset until March 1, 2022, so you have time to take action after this year's peak shipping season.
What happens on March 1st if I still haven’t taken action?
If you haven’t migrated to a new solution by February 28, 2022, you will experience disruptions. This includes being no longer able to export shipping information with ODBC, communicate with the WMS through SOAP APIs, or use handheld scanning devices to manage your inventory.
What if my question isn't answered here?
If you have a question related to this security initiative that is not answered in this FAQ article or in our email communications, please reach out directly to your Customer Success Manager (CSM) or contact firstname.lastname@example.org.