Created
Mar 29, 2023 1:51 PM
Tags
- Pain points
- regulatory requirements
- planning workflows
- demanding execution
- Players
- Using cargowise currently
- shipment data, e-docs, shipment milestones, client communication, reporting
dacc8959359443d2b04a3a20f29ac036
Notes
- Uses cargowise
- Modules that can accomodate, supports a wide range of modes air ocean etc
- Connecting with APIs and EBIs in various systems, network effect, both partners on the same system
- Don’t have to manually create the data
- Timing issue, time difference
- Can your system ingest automation updates from ports rails terminals
- vessel departed, vessel arrived
- Cargowise has their own automation, no manual data entry
- Big importers need TMS that can accommodate the customs piece
- All integrated customs documents, e-doc drag and drop into the file
- Customs team has access to all of that and they can verify that
- Pain points
- Better visibility into the customs side,
- something put on hold, something is in an exam
- No good insight into exactly what’s happenign
- tied into the ACED portal
- has to be done by phone or email
- Customs is integrated with TMS’, would take some work with CBP to feed the updates
- Can be very overwhelming, can tailor it well and add custom fields, won’t work with you
- Make it more dynamic and flexible, get boxed in
- Customer service is
- Could never imagine leaving cargowise, but do plugins or boltons
- Much easier to change if you’re domestic vs international
- Freight movement has good visibility
- partnering with project 44
- Manual file in cargowise when it’s not on the platform, EDI file or
- remove this
- not a consideration
- Integrate modstone, origin freight movement, when it departs arrives
- gap when it arrives, pick up
- gate out lose tracking
- truckers dray providers until the customer’s door
- hole
- empty container
- Drayage containers never use tracking