Operating-model analysis
Are Excel and Gmail enough to run import operations?
Excel and Gmail remain useful for calculations and communication, but they do not by themselves create one current shipment identity, controlled evidence trail, named owner, and reportable operating state. Tyllus adds that record layer by connecting shipment data, files, activity, costs, exceptions, and reporting without pretending to replace email, spreadsheets, carriers, brokers, or government systems.
By Ayhan Karaca, Co-Founder · Updated: September 9, 2026
The problem is not file size; it is missing operating context
Microsoft documents that one Excel worksheet can hold 1,048,576 rows and 16,384 columns. Google says a personal Gmail message can carry attachments up to 25 MB, while work or school limits depend on the administrator and larger attachments become Drive links. Those are impressive storage and delivery capacities. Neither specification answers which row is current, which attachment belongs to which shipment, who owns the next action, or whether a number in a weekly report can be traced to its source.
A workbook, inbox, and folder can each contain correct information while the operation is still fragmented. The control gap appears when a shipment reference changes in one place, a revised invoice remains in a reply chain, an ETA update has no owner, or finance sees a cost without the decision history behind it.
| Published evidence | Useful interpretation | Do not infer |
|---|---|---|
| Excel: 1,048,576 rows and 16,384 columns per worksheet | A worksheet can store a large operational list | That a large list is controlled, current, or auditable |
| Gmail: 25 MB personal attachment limit; larger files use Drive links | Email and linked storage can move files | That a sent file has the right shipment, version, reviewer, or owner |
| Dartmouth study: 50 operational spreadsheets; 0.8%–1.8% formula-cell error rates | Operational spreadsheets deserve explicit review and controls | A logistics-industry error rate, an '88% of spreadsheets' rule, or Tyllus savings |
| CBP FY2024: 38.4 million entries and more than 32.5 million imported cargo containers | Import work operates at material national scale | Your team's volume, error rate, delay cost, or automation benefit |
What should replace the spreadsheet-inbox-folder triangle?
Do not replace every tool. Replace the assumption that any one of them is the shipment system of record. Keep spreadsheets for bounded calculations and exports, email for external conversation, and approved file services where required. Put the operating state in a controlled record that has a stable shipment identity, structured fields, evidence, activity history, owners, and reviewable status.
The test is simple: can a permitted colleague open one shipment and answer what it is, what changed, what evidence supports the state, who must act, and which portfolio number includes it—without reconstructing several personal tools?
Read the operating-model steps
Give the shipment one identity. Connect source files and messages to that identity. Record the current state and next owner. Review exceptions and professional decisions. Report from the accepted records and retain drill-through evidence.
How Tyllus controls the record without claiming to replace Gmail or Excel
Tyllus connects orders, shipments, suppliers, partner activity, documents, milestones, tracking context, costs, invoices, exceptions, notes, and owners in the same workspace. Teams can import supported shipment data through a preview-and-confirm flow, keep documents with the relevant shipment, review activity, and report or export from recorded operational data.
Tyllus does not ingest arbitrary Gmail history, make an uploaded spreadsheet correct, certify a document, file with customs, move cargo, or guarantee that a partner responds. Its role is narrower and more useful: make the available operating context reviewable and keep the next action from depending on one person's inbox memory.
- Use one shipment identity instead of copying status across independent trackers.
- Keep a file with its source, shipment, review state, and related action—not only its filename.
- Separate recorded facts, external signals, human decisions, and unresolved exceptions.
- Build reports from the same records the team operates, with filters and drill-through context.
- Export when downstream reconciliation requires Excel; do not turn the export back into an uncontrolled master.
When is Excel or Gmail still the right tool?
Excel is still appropriate for an analyst's bounded model, a reviewed calculation, or an approved export. Gmail remains appropriate for conversations with parties who operate by email. The risk begins when a local workbook becomes the only current shipment state or when an inbox becomes the only evidence that a request, response, or revised document exists.
Choose the smallest control that solves the real failure. A very small team may start with naming rules and ownership discipline. As shipment count, partner count, exceptions, access requirements, and reporting needs grow, a shared operational record becomes more valuable.
What result should an importer measure after the change?
Measure your own baseline and closed outcomes: the share of active shipments with a current owner, required-document status, accepted invoice state, and complete cost evidence; the time from a material change to assigned action; duplicate requests; unresolved exceptions; and the percentage of report values that drill through to a shipment record.
Do not borrow a spreadsheet study, national import volume, or vendor estimate as your result. Improvement is credible only when the definition, period, denominator, source completeness, and before-and-after population are preserved.
Move an open email thread into an owned workflow
Use the migration guide’s handoff template to name the owner, deadline, current file and closure evidence. Its pilot and recovery gates help preserve open work when the operating record changes.
Map one real shipment across your current tools.
Bring the workbook columns, inbox handoffs, folder structure, and reports you use today. Tyllus can show which context belongs in the shared operating record and which tools should remain specialist inputs or outputs.