Freight Forwarding and Customs Application

The job file is the thing, and nothing standard models it

A freight forwarder does not sell an order. It opens a job file. The job file carries a shipper, a consignee, a notify party, a mode, an origin and destination port, a carrier, a master and house bill or airway bill, one or more containers or packages, a commodity with HS codes, a customs entry, and a stack of charges — some bought from a carrier in one currency, some bought from a trucker in another, some sold to the customer in a third.

Profit is per job file, and it is the difference between what was bought and what was sold on that file. That number is what forwarders most often cannot see until the accounts are closed, because the buy side sits in supplier invoices in the accounting system and the sell side sits in customer invoices, and nothing joins them at the job level.

Meanwhile the operational reality — vessel sailed, arrived, customs entry filed, duty paid, released, delivered, empty returned — is tracked in a spreadsheet, a WhatsApp group and somebody's head. When a customer asks where their container is, someone goes and finds out.

Zoho Books handles the invoices and the vendor bills correctly. Zoho CRM handles the customer relationship. Neither has a job file, because a job file is a vertical structure. Creator, Deluge, Zoho Flow and the Books REST API are what you need to build it and join the two financial sides at the job level.

What ECOSIRE builds

This is a build-to-order application. Nothing is pre-built and there is no download or trial. After scoping, ECOSIRE builds it against your trade lanes, your charge codes, your customs regime and your Zoho Books organizations.

The job file (Zoho Creator)

A Job_File form holds the shipment: job number generated by a Deluge function on your own numbering scheme, direction (import, export, cross-trade), mode (sea FCL, sea LCL, air, road, rail, multimodal), incoterm, shipper, consignee, notify party, origin and destination ports with UN/LOCODE, carrier, vessel and voyage or flight number, master and house document numbers, and the responsible operations owner.

Related records hang off it: Container_Package, Commodity_Line, Charge_Line, Customs_Entry, Milestone_Event and Job_Document. Everything is a record, so everything is reportable.

Containers, packages and commodities

Container_Package records carry container number with a Deluge check-digit validation, container type and size, seal number, gross and net weight, volume, package count and package type. For LCL and air, the same form handles loose packages with dimensions and chargeable weight, computed in Deluge from volumetric rules you specify per mode.

Commodity_Line records hold the goods description, HS code, country of origin, quantity, unit, invoice value and currency. HS codes are held in a reference form so operations pick from your own maintained tariff list rather than typing free text, and duty and tax rates per HS code can be held against that list where your regime makes that useful.

Customs milestones and entries

A Customs_Entry record per job holds the entry type, declaration number, customs office, filing date, assessment, duty and tax amounts, payment reference and release date. Milestone_Event records give the file its operational timeline — booking confirmed, cargo received, loaded, departed, arrived, entry filed, assessed, duty paid, released, delivered, empty returned — each with planned and actual date and time, and the user who recorded it.

Because milestones are records with planned dates, a scheduled Deluge workflow can flag files where a milestone is overdue, and demurrage or detention free-time clocks can be tracked per container against the agreed free days, warning before charges start rather than after they land. Zoho Flow can push those alerts into email or Cliq, and customer milestone notifications can be sent automatically from the file.

Cost versus sell, per job, per currency

This is the core of the application. Every Charge_Line on a job file carries a charge code from your own charge master, a buy side (vendor, cost amount, cost currency) and a sell side (customer, sell amount, sell currency), with the exchange rate applied at the rate you nominate. Deluge functions roll these into total buy, total sell, gross profit and profit percentage per job file in your base currency, and per container or per chargeable weight unit where you want the unit economics.

Accrual matters here: the job shows profit from the moment charges are entered, whether or not the carrier has invoiced yet, and accrued-versus-actual variance is visible when the vendor bill arrives.

On the financial side, Deluge custom functions create the customer Invoice and the vendor Bills in the correct Zoho Books organization through the Books API, against the right Customer and Vendor records, with your tax treatment configured — VAT, GST, zero-rating for international transport, or reverse charge as your regime requires. Books document ids are written back onto the charge lines, so the job file's profit and the accounts agree instead of being two separate opinions.

Multi-organization operation is supported where you run more than one Books organization for more than one legal entity, with the job file routed to the correct organization.

Quotations and CRM

Rate enquiries live in Zoho CRM as Leads and Deals. A Quotation record in Creator prices a shipment from your charge master and rate cards, and on acceptance converts into a job file with the quoted charge lines carried over as the expected sell side — which is what makes quoted-versus-actual margin a report rather than an argument. A Sigma widget embedded in the CRM Deal detail page shows the live job status without leaving CRM.

Documents

Job_Document records hold bills of lading, airway bills, packing lists, commercial invoices, certificates of origin, delivery orders and customs paperwork as file uploads with type, version and date, optionally linked to a per-job WorkDrive folder through Zoho Flow. Creator print templates generate your house bill, delivery order, arrival notice and job cost sheet on your own letterhead.

Who this is for

Sea and air freight forwarders, customs brokers and clearing agents, NVOCCs, project cargo and breakbulk operators, and 3PLs running forwarding alongside warehousing — companies already on Zoho, or moving to it, that need the job file and its profitability joined to the accounting rather than reconstructed from it.

How delivery works

1. Scoping call. We go through your trade lanes, modes, charge master, rate card structure, customs regime and declaration types, tax treatment, Books organizations and document layouts, and agree what is in scope. 2. Fixed quote. A written scope and a fixed price. Customs authority integrations and multi-entity handling are priced explicitly rather than discovered mid-build. 3. Build. ECOSIRE builds the Creator application, Deluge functions, profitability engine, milestone workflows, Flow connections, Books integration, print templates and reports. Typical lead time is two to four weeks depending on scope. 4. Install in a test environment. Deployed into a sandbox or test section of your Zoho org with your own sample job files, so operations and accounts validate real charge structures and a real month's profitability before live data is involved. 5. Production. On sign-off, deployment into your production org, migration of agreed reference data — customers, vendors, ports, charge codes, HS codes, rate cards — and go-live alongside your team. 6. Support. A defined post-go-live support window for defect fixes and configuration adjustments, with training and written documentation handed over.

There is no instant download and no ready-made product. You are buying a scoped build delivered into your own Zoho org, with the Deluge source handed to you.