What does Kadmoon do?

We are a US analytics firm focused entirely on foreign trade. We turn the data buried in your customs, logistics, and ERP systems into decisions: landed cost and margin, duty and tariff exposure, shipment visibility and OTIF, customs and compliance analytics, inventory, and an executive control tower. Everything is built on a governed model, delivered on the Microsoft stack, and lives in your own tenant.

Do we have to be a Microsoft shop?

No. Your data can live anywhere: SAP, Oracle, NetSuite, Microsoft Dynamics, broker and carrier systems, EDI and ACE, or spreadsheets. We read from the system of record wherever it runs. We deliver the analytics on the Microsoft stack, Fabric, Power BI, and Azure, because it is a strong, governed place to build, but the platform is the how, not the point.

Why only foreign trade?

Because trade analytics fails when it is built by people who do not know trade. Landed cost, duty, incoterms, bonded inventory, HTS classification, denied-party screening, and ACE are not edge cases to us, they are the metrics we model every day. That focus is why we arrive with the trade data model and KPIs ready instead of learning your business on your budget.

Where does the data come from?

From the systems you already run. We land raw data in your tenant, shape it into a governed semantic model, and feed the dashboards from there. Carrier EDI and customs messages are parsed into structured events, so milestones, exceptions, and filings become data you can measure instead of documents you have to read. The data integration doc goes into detail.

How does a project start?

Usually with a trade data assessment: a short, fixed-scope engagement that maps your decisions and data and delivers first dashboards in about two weeks. It de-risks the larger build and produces a scope and a quote grounded in your real data. You leave with working analytics, not a slide deck.

Do you build software too?

Yes, and it grows out of the analytics. Living in a client’s trade data is where our software starts: once we understand the operation, we build the systems that run it, customs filing, trade ERP, inventory, and security vision. Analytics is what we lead with and deliver today; the software is what we build as the relationship deepens.

Do we own the analytics and the data?

Yes. Everything we build is yours: the semantic model, the reports, and the data, all inside your own tenant, with documentation and a full handover. Access is provisioned per engagement against your identity provider and policies. We support and evolve it on a defined agreement after launch, but you are never locked in or dependent on us to keep operating.

Which regions and company sizes do you serve?

We are a US firm serving American importers, exporters, brokers, forwarders, 3PLs, ports, and the manufacturers and distributors that trade across borders. We work with growing operations and established enterprises alike; the common thread is that moving goods across borders is central to the business and the numbers have to be right.

KadmoonINC.

Client sign-in Request a quote

Analytics · Customs Brokers

Entry throughput and clearance-time analytics

A customs broker measured entry volume, clearance time, and exceptions across the team to find where entries stalled.

Microsoft FabricPower BIAzure Data FactoryRow-level security

Clearance time: -22%; illustrative
Entries tracked: All; across ports
Exception reasons: Categorized; and trended
Operating view: Daily; for the team

Illustrative scenario · example figures

The challenge

Volume was growing but the broker could not see clearance time or where entries got stuck, so staffing and problem lanes were managed on instinct.

What we built

We pulled entry and status data from the filing system into a model that tracks throughput, clearance time, and exception reasons by team, client, and port.

Entry volume and clearance time by client, port, and filer.
Exception analysis by reason, with trend over time.
A daily operating view for the clearance team.

Outcomes

Clearance time is measured instead of estimated.
Problem ports and clients are visible and worked down.
Staffing follows real volume and complexity.

Where the data came from

Broker filing systemACE / ABIClient masterPort reference data

Data is drawn from the systems the operation already runs on and delivered in the client’s own tenant.

Want this on your trade data?

Tell us where your numbers live and what leadership needs to see. You get a scoped plan and a quote within one business day.

Request a quote

More case studies

ImportersLanded cost analytics by SKU and supplierAn importer moved landed cost off a monthly spreadsheet into a model that allocates freight, duty, and fees to every unit as goods arrive.ImportersTariff and duty exposure modelingWith tariffs shifting, an importer needed to see duty exposure by product and country and model the cost of a rate change before it landed.ImportersSupplier performance and lead-time analyticsAn importer consolidated supplier data to see lead-time reliability, defect rates, and total cost by vendor in one place.