Changelogs - ExWorks Integration & EDI Comms & More
Changelog Updates
| Change Log Updates |
|---|
| 1. ExWorks Support |
| 2. New Row Color Settings on the dispatch screen |
| 3. Update to Warehouse App printing Location (BIN) Labels |
| 4. Added more Excel Export reports - based on customer feedback |
Big Shout Out to the Amazing Crew Over at ExWorks
We got to know the team at ExWorks this month. As truckers, we obviously knew the ExWorks trucker login system, but this month we got to know some executives and staff behind ExWorks. We were seriously surprised at how kind and supportive they were.
Robust EDI Communication System
We are really happy to say that we have built an excellent EDI system. We designed it to allow for the expansion of other EDI providers with ease. We currently support all EDI messages for acceptance, arrivals, departures, sending comments, documents, and of course, sending invoices. We are very happy with the EDI protocol and excited to implement new features for our customers.
You may ask why we spent the time building an in-house EDI system. EDI is a staple in a TMS. Sending status updates is a significant part of our mission, and this isn't something we would personally purchase from a third party and pass on the costs.
We believe that our hands-on experience as truckers gives us an edge over our competition in implementing these features.
Some History of EDI (Electronic Data Interchange)
EDI gets a bad rap simply because it's considered "old." But you can also flip that and call it wise.
This was our experience in learning about EDI. Sure, it's not the most modern way of B2B communications out there, but after we learned it and implemented it, we realized it's way less of a pain than the modern ways of doing things.
Did you know that EDI was actually invented by our government (National Institute of Standards and Technology (NIST))? Some very intelligent minds decided to get together at the dawn of the internet and create something called "standards." Personally, I think a lot more thought went into EDI than someone's JSON REST implementation.
What MyCartage Does with EDI
We wanted to expose EDI to your team, so we decided to let you look at the EDI files. Our idea is that while it's typically not standard for non-technical people to know how to read EDI files, we remember that we were once managers of trucking companies and liked knowing all there is to know. We learned about EDI files even though we had software that did it for us.
We think it is important for managers to have an idea and understanding of all things, and a little extra knowledge doesn't hurt anyone. Why not let everyone get to know this information? See for yourself what you are actually accepting from these forwarders.
