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.

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.

Data integration | Docs

Q: 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.

Trade data is scattered by nature: an ERP, a broker portal, carrier feeds, a warehouse system, and spreadsheets each hold part of the picture. We bring them into one governed model without asking you to replace any of them.

Sources we connect

Data can originate anywhere your operation already runs. We read from the system of record rather than asking teams to rekey anything.

ERP: SAP S/4HANA and ECC, Oracle, NetSuite, Microsoft Dynamics 365, Infor.
Customs and trade: ACE and ABI, broker filing systems, HTS and duty schedules, denied-party lists.
Logistics: TMS and WMS, ocean and air carrier EDI, tracking APIs, freight invoices.
Finance and other: accounts payable, treasury and FX feeds, Salesforce, and spreadsheets where they are still the source.

How ingestion works

We land raw data in your tenant, then shape it in layers: a raw copy for lineage, a cleaned and conformed layer, and a semantic model the reports read from. Pipelines run on a schedule or near real time where the source and the decision justify it.

EDI and ACE

Carrier EDI and customs messages are parsed into structured events so milestones, exceptions, and filings become data you can measure, not documents you have to read. We map the message types your partners actually send and validate against them.

The delivery platform

We deliver analytics on the Microsoft stack, Fabric, Power BI, and Azure, inside your own tenant. The platform is the how, not the point: the goal is one trusted set of numbers, and the sources above feed it whatever tools they run on.