Understand the information journey
A diagnosis identifies where each shipment is recorded, who updates its information and how its status is checked. It also helps distinguish missing data from a follow up problem. The solution depends on those differences.
- Sources of shipment information.
- People responsible for updates.
- Process statuses and actions.
- Situations that require review.
Which connection does your operation need?
A spreadsheet import may cover a one time data load. Synchronization requires defining which system updates each field, how often and what happens when records differ. Before choosing an approach, we review the current workflow and the tools’ capabilities.
- Spreadsheets: source fields, required data and how information will be updated.
- CRM and WhatsApp: how contacts relate to conversations, available access and each tool’s permissions.
- Human oversight: what happens when data is missing, a source does not respond or a case needs review.
Shipment management in Slack: the Klozer case
ZaTek worked with Klozer to centralize shipment processes that required manual team responses in Slack. The information was brought together in a summary for operational review, as Augusto Méndez explains in the case’s public video.
Connect tools, use a TMS or build custom software?
The first decision is which part of the work your team needs to address. We review whether connecting existing tools is enough, whether a transportation management system (TMS) covers the process or whether a remaining need calls for custom development.
- Connect existing tools: When the data already exists, but the team has to copy or gather it. Access, permissions and the system responsible for each field need to be checked.
- Evaluate an existing TMS: When you need broader transportation management. Compare its features with your operation before developing your own solution.
- Build a custom tool: When available options still leave a specific workflow unresolved. Define its inputs, expected output and the exceptions the team will review first.
If there is no reliable source of information, first define where shipments are recorded and who updates the data. A typical example and an exception help us evaluate the initial scope.
Try managing a shipment
Find a shipment, review its information and record a decision in the interactive demo.
The demo lets you try the workflow and saves your decisions in this browser.
Select EN in the demo to switch to English.
Common questions
Do we need to replace our current system?
That is evaluated during diagnosis. An integration or complementary tool may be sufficient, depending on the system’s capabilities.
Which task should we bring to the call?
A repeated shipment data entry, lookup or follow up task, with examples of how your team handles it today.
Can exceptions be included?
The design should identify cases outside the usual workflow and define who reviews them.
What do we need to review to define the scope?
An example of the current workflow, the tools involved, the data that must move between them and the situations that need a person. We also review access and dependencies before confirming an integration. This helps us define a first implementation and assess its budget.