Custom CFS Warehouse Management Software Development

A container freight station receives sealed containers, strips (devans) them, and holds the cargo per house bill of lading until both the carrier or NVOCC and customs release it; for exports it consolidates LCL cargo into containers. A standard WMS is built around SKUs, pick faces and orders. A CFS system is built around containers, house bills, customs status, free time and storage charges, and it has to prove to customs where every piece was at every moment. Most generic WMS products can't model that without heavy customisation.

Container receipt and gate-in, devanning plans and tally against the manifest, over/short/damaged reporting with photos, location tracking for loose cargo in bonded and general areas, hold and release management per house bill, delivery orders and trucker appointments, LCL export receiving, consolidation and stuffing with load plans, storage and handling billing, and the dashboards on top. We build a full CFS system or the modules your current WMS or spreadsheet setup is missing.

Each house bill carries its own status: manifested, arrived, on hold (customs exam or another agency's hold), released by customs, and freight-released by the carrier or NVOCC. Status comes from your AMS or customs-broker provider or the local customs system, and the delivery screen refuses to hand cargo to a trucker until every required release is on record. Exams and transfers to an examination station are tracked as movements, so the audit trail stays intact.

Customs status and in-bond data through your AMS or ABI provider in the US (CBP ACE), or the national customs system elsewhere, such as ICEGATE in India; container and vessel status from terminals and carriers, often as ANSI X12 315 messages or terminal APIs; drayage and trucker appointment data; barcode or RFID scanners and handheld devices on the floor; and your accounting or ERP system for invoicing. We confirm each provider's interface and costs in discovery, because customs data access usually runs through a licensed intermediary.

Yes. Tariffs for devanning, handling, storage after free time, exams, re-palletising and other accessorials are kept as data your team maintains per customer or per NVOCC, not hard-coded. Free time starts from the event you define, such as devanning complete or availability notice, and charges are calculated per house bill at release, so the trucker or consignee can pay before pickup.

Container stations operate under 19 CFR Part 19 (sections 19.40 to 19.49) with a bond and port director approval, are identified in CBP systems by a FIRMS code, and in-bond movements are filed electronically in ACE since the paper CBP Form 7512 was phased out. The software keeps per-piece custody records, in-bond arrival and export events, and flags cargo approaching the 15-calendar-day general order deadline. Compliance remains your responsibility as the bonded operator; the system gives you the records and alerts to meet it.

We start with a discovery week on your floor and in your data: container volumes, house-bill counts per box, holds, exams, tariffs and the disputes that cost money. Then we ship one workflow at a time, usually import devanning and release first, run it in parallel with your current process on real containers, reconcile the results, and only then switch over. You own the code, the data and the integrations.