One Work Order - Its Own Books

Every job in TrakIT has one finance page for all of its work orders combined. That's exactly right when you're closing out the job - and exactly wrong when you only want to know whether this container is running a loss. Work Order Finance is a new page built for the second question.

Why this Exists

A job's finance page is comprehensive by design: every estimate, every actual, every account, laid out line by line. That's the right tool for approving a job or reconciling its books end-to-end. It's the wrong tool for a narrower, more common question - how is this one work order doing?

On a job with sixteen containers and forty line items, finding the handful of rows that belong to one of them means scanning a search box, squinting at the WO column, or exporting to a spreadsheet and filtering there. Work Order Finance is that filtered view, given its own page and its own address.

What's on the page?

Open a work order's finance page, and it reads like its job-level counterpart, because the intent is the same: a summary up top, working detail in tabs below - just narrowed to one work order throughout.

• Work Order Information -Workflow, customer, commodity, weight, transporter, and whatever else matters most. The fields aren't fixed in code - an office or role can configure its own set, the same way column choices work everywhere else in TrakIT.
• Account Summary - Income, expenses, gross margin, required margin, disbursements - estimate against actual - totalled from this work order's accounts only.
• Estimates & Actuals - The full toolkit: add, edit, approve, hide, duplicate, tax, quick-edit, drag to reorder. Add an account here and it already belongs to this work order - nothing left to pick.
• Analyse - Account master and category summaries, scoped the same way as everything above.
• Audit Log - Who changed what, filtered to this work order's accounts - not the job's.
• PDF - Print or download a copy laid out the same way as the screen.

Every total on this page, and every account you add from it, belongs to one work order. Nothing here reaches into the rest of the job - and nothing from the rest of the job leaks in. The job still holds all of it. Work Order Finance just gives one branch of that tree a door of its own.

What stays on the job page

A few things are deliberately missing here, because they were never really about one work order:

• Job status & approvals
• Request approval, close, cancel, reopen - a job moves through one status, not six.
• Customer credit rating
• A property of the customer, not the shipment leg.
• Comments, invoices, bills, documents

These live where they were created - at the job level - and Work Order Finance links straight back to all of it.

Getting there

Every work order page now carries a WO Finance link alongside the existing Job Finance one. Follow it, and the address settles at /wofin-[id] - as direct as the page itself. Access follows the same finance permissions as the job page, narrowed by whatever work order filters already apply to your account: if you can't see a work order today, you won't see its finance page either.

Make it yours

The Work Order Information panel runs on the same column system as TrakIT's list pages. An administrator can add fields, remove them, reorder them, or set a different default for a particular office or workflow group - from the existing column admin screen, under Finance WO Info. Nothing about the panel is fixed except the mechanism for building it.

For any questions or concerns, please contact TrakIT Support.

Built for How Freight Forwarders Actually Work: Inside TrakIT's Approach to Workflow, Automation, and Africa's Complexity

Every freight forwarder eventually hits the same wall with off-the-shelf logistics software: the platform was built for someone else's business.

Maybe it assumes a workflow you don't follow. Maybe it charges more every time you add a team member. Maybe it was designed for a market where customs documentation is uniform and predictable - and then falls apart the moment you're routing a shipment through three countries with three different regulatory regimes.

TrakIT was built to solve that problem from day one, in the market where it matters most: Africa. Today it supports freight forwarders across 50+ countries, with deep, battle-tested coverage across 30+ African markets - and everything about the platform, from its workflow engine to its pricing model, reflects the lessons learned getting logistics software right in the world's most operationally complex trade corridors.

Your Workflow, Not a Template

Most logistics platforms give you a fixed process and ask you to adapt your business to fit it. TrakIT does the opposite.

Its workflow engine was designed around a simple reality: no two freight forwarders operate identically, and a forwarder moving goods through Lagos, Mombasa, and Douala can't run the same approval chain, documentation sequence, or exception-handling process as one working purely intra-Europe. Multi-country regulatory complexity isn't an edge case for TrakIT - it's the foundation the architecture was built on.

That means you can configure workflows around how your operations, compliance, and documentation teams actually work - not the other way around. Custom approval stages, conditional routing based on shipment type or destination, role-specific task assignment, and country-specific documentation requirements are all things you configure, not things you request from a vendor roadmap and wait months for.

Reporting That Runs Itself

Ask any ops manager what eats their week, and "pulling reports" is near the top of the list. TrakIT's reporting automation is built to take that off your plate entirely - scheduled reports generated and distributed automatically, so your team, your clients, and your partners get the visibility they need without anyone manually exporting a spreadsheet at 6pm on a Friday.

Because the platform understands shipment data natively, reports aren't static exports - they reflect the real-time state of your operations, filtered and formatted for whoever's reading them: a client wants shipment status, your finance team wants revenue by lane, your ops lead wants exception flags. Same underlying data, automatically shaped for each audience.

Automation That Actually Reduces Work

TrakIT's automated actions go beyond reminders. The platform can trigger real operational events based on rules you define - status updates cascading through a shipment's lifecycle, notifications firing when a milestone is hit or missed, documents routing to the right person the moment they're uploaded. It's the difference between software that tells you something needs attention and software that handles it.

Two features stand out here, both born from real forwarder pain points:

OCR bill of lading extraction - pull structured data directly from BOL documents instead of manually keying it in, cutting a slow, error-prone step out of your process entirely.

Natural language shipment queries - ask TrakIT a question the way you'd ask a colleague ("which Mombasa shipments are delayed past 5 days?") instead of hunting through filters and dashboards.

Integrations Without the Integration Headache

Freight forwarding doesn't happen in one system - it happens across carriers, customs platforms, client portals, and internal finance tools. TrakIT is built to connect to that ecosystem rather than compete with it, with an integration architecture designed to plug into the carrier and customs systems you already depend on. The goal isn't to make you migrate everything to one walled garden - it's to make TrakIT the operational hub that ties the systems you already use together.

Pricing That Scales the Way You Do

Here's where TrakIT breaks from almost every competitor in the space: no per-user fees. Add your whole documentation team, bring on seasonal staff, give your finance department visibility - none of it adds to your bill. For forwarders running lean, growing teams, or seasonal operations (which describes most of the industry), this alone changes the economics of adopting proper logistics software.

Why This Matters Most in Africa

Africa's freight forwarding market has historically been underserved by logistics software built for simpler, more homogeneous trade lanes. Multi-jurisdictional documentation, inconsistent customs digitisation, and highly variable regulatory requirements from country to country have made "off-the-shelf" software a poor fit for forwarders operating across the continent.

TrakIT was shaped by exactly that complexity - not adapted to it after the fact. That's the difference between a platform that tolerates African market conditions and one that was actually designed around them.

See It on Your Own Operations

The best way to understand what a purpose-built platform feels like is to see it against your own workflows, your own shipment volumes, and your own team structure.

Ready to see TrakIT in action? Request a demo, and we'll walk through how it fits your operation - no per-user pricing surprises, no generic sales pitch, just a real look at whether it's the right fit.