Tyllus platform

Import operations software for teams moving 10 to 100+ containers a month

Tyllus is import operations software for importers and their import teams. It keeps every ocean shipment in one reviewable record: purchase orders, container tracking, document reading, an 11-step workflow for US imports (Mexico skips the ISF step) that sends suppliers, forwarders and customs brokers their requests automatically, customs readiness, landed cost, exceptions and reports. It covers US ocean imports and Mexico definitive ocean imports.

Updated: October 3, 2026

What does Tyllus do?

Tyllus runs the day-to-day work of importing: it collects what each shipment needs from your partners, reads the documents, tracks the container and builds the landed cost. Each module below has its own page with the full detail.

  • Order management: each purchase order holds the PO number, supplier, equipment, cargo-ready date and must-arrive-by date, moves through six statuses on its own and becomes a shipment in one click.
  • Shipment Hub: every shipment keeps its workflow steps, partners, documents, tracking, costs and activity history together, with filters for needs attention, delayed and missing documents.
  • Container tracking and ETA: automatic tracking on 11 ocean carriers, including MSC, ONE, Evergreen, HMM, Yang Ming and ZIM; for any other line the Tyllus team checks the ETA, ports and ETD for you.
  • Document collection: Tyllus reads 8 US document types, from the commercial invoice to CBP Form 7501, and 7 for Mexico, then cross-checks 23 shipment fields across five sources.
  • Partner follow-up automation: 9 of the 11 US workflow steps send the right supplier, forwarder or customs broker a request automatically, followed by reminders (Mexico skips the ISF step); partners never need an account.
  • Customs workflow: the customs request reaches your broker 7 days before ETA, and the customs page shows readiness per container, filed entries and spend by HTS code.
  • Landed cost and duties: costs are created from the documents Tyllus reads (goods, freight, broker fees, duties and fees), so each shipment shows its landed cost line by line.
  • Reporting and exceptions: dashboard cards for in transit, arriving soon, needs attention and documents pending, plus spend, volume, partner and trade-lane reports with CSV export.

Who is Tyllus built for?

Tyllus is built for importers that move roughly 10 to 100+ ocean containers a month and work with several suppliers, freight forwarders and customs brokers at the same time, for example in home goods, furniture, lighting, textiles and consumer products.

Purchasing, logistics, operations, finance and management share one workspace with Owner, Admin and Member roles. A single operator can also start alone through self-serve sign-up and invite colleagues later.

  • Scope: ocean imports into the United States and definitive ocean imports into Mexico.
  • Team members and partners can work from any country.
  • The product is available in English, Turkish, Italian and Spanish.
  • Partners join only when a step needs them, through secure links and without an account.

How does a shipment run in Tyllus?

US shipments follow an 11-step import workflow, and Mexico shipments follow the same steps without ISF filing. Each step has a named owner (the supplier, the freight forwarder, the customs broker or your own team), and most steps send that partner a request automatically, with reminders until it is answered.

When the ETA moves, Tyllus re-times every step that depends on it, so the customs request and the document checks still go out at the right moment.

The 11 US workflow steps grouped into seven stages; Mexico skips the ISF step.
Read the shipment stages as text

1. Start from a purchase order or a spreadsheet; supplier, equipment and dates carry over. 2. The supplier sets the cargo-ready date through a secure link. 3. The forwarder confirms the booking and then the stuffing. 4. For US shipments the broker confirms ISF filing, and the supplier uploads the shipping documents, which Tyllus reads. 5. The forwarder submits the MBL and container numbers, and Tyllus tracks the container to arrival. 6. The customs request goes to the broker 7 days before ETA, missing documents are requested 5 days before ETA, and the forwarder confirms arrival or reports a delay. 7. After arrival the forwarder uploads its invoice and a final documents check asks for anything still missing.

What can Tyllus do across the import process?

The table maps each capability to what Tyllus does today and the page that explains it in full.

Tyllus capabilities at a glance
CapabilityWhat Tyllus doesWhere to read more
Container trackingTracks containers automatically on 11 ocean carriers from the container number plus the MBL or carrier name; the Tyllus team checks ETA, ports and ETD for any other line; every route appears on a world map.Container tracking and ETA
ETA changesRe-checks ETAs every day, re-times the customs request, document checks and invoice request when an ETA moves, logs each material change and flags a shipment Delayed when its ETA passes without arrival.Container tracking and ETA
DocumentsReads 8 US and 7 Mexico document types, marks each value Accepted or Needs review, cross-checks 23 fields across five sources and shares files through expiring links or one ZIP download.Document collection
Purchase ordersKeeps PO number, supplier, equipment, dates and custom columns; six statuses with automatic changes; Create shipment carries the data over in one click.Order management
Partner coordinationCoordinates suppliers, forwarders and customs brokers; 9 of the 11 US steps send requests automatically (Mexico skips ISF), with reminders, importer warnings and secure links that need no account.Partner follow-up automation
CustomsSends the customs request to your broker 7 days before ETA; shows readiness per container, filed entries from the 7501, and spend by HTS code (US) or TIGIE/NICO code (Mexico).Customs workflow
Landed costBuilds costs from the commercial invoice, forwarder invoice, 7501 or pedimento and broker invoice; shows landed cost per shipment, invoice coverage and top-5 spend by partner.Landed cost and duties
Exceptions and reportsShows a needs-attention panel, delayed and missing-documents filters, alerts for missing invoices and high duty, and spend, volume and trade-lane reports with CSV export.Reporting and exceptions
TeamsOwner, Admin and Member roles, email invitations that expire after 7 days, a private workspace and activity history on every shipment.Tyllus for enterprise import teams
Ask Tyllus AIAnswers plain-language questions about shipments, costs, customs, documents and tracking across up to 1,000 shipments; it reads and summarizes and never changes data on its own.Data and AI

How does a team start using Tyllus?

Sign up yourself, without a sales call, with Google or with email and password. Onboarding takes two steps: name the workspace and pick a first goal. No integrations are needed to start.

  • Create a shipment by hand.
  • Import the Excel file you already use; Tyllus matches the columns for you.
  • Open the sample shipment, a safe sandbox that never affects your numbers or emails partners.
  • Ask the Tyllus team to set it up with you, including an optional 15-minute setup call.
  • Track a container on its own, without creating a shipment.

What is Tyllus, and what is it not?

Tyllus is the operations layer for your imports: tracking, documents, purchase orders, partner coordination, customs readiness, landed cost and exceptions in one shipment record. It is not a freight forwarder, carrier or licensed customs broker, and it does not file customs entries. It works alongside the forwarders, carriers and brokers you already use and keeps their answers in one place.

Where Tyllus applies

Tyllus covers ocean container imports into the United States and definitive ocean imports into Mexico. Air, truck, rail and parcel shipments are outside its scope.

Run your next shipment in Tyllus

Create an account without a sales call, open the sample shipment or import your spreadsheet. Your partners join when the first request goes out.