Ship governed exception and partner workflows beside your TMS and WMS, not inside them

For forwarders and carriers, contract logistics providers, shippers' logistics departments and customs-heavy operations: build claims handling, subcontractor onboarding, pallet account reconciliation, customs clarification and customer-facing portals as production software with review points, traceability and code ownership.

Modernise around TMS, WMS, ERP, telematics and customs software without a single change request to the core system vendor.

Where it runs

Nuclicore-managed single tenant on Hetzner in Germany or Azure in the EU, or your own cloud (BYOC) and on-premise on Enterprise.

What it connects to

TMS and WMS (CarLo, WinSped, Cargosoft, SAP TM and EWM, LFS and others), ERP, telematics exports, customs software and freight platforms via APIs, exports and database views.

What we do not touch

Dispatch and routing, the customs declaration itself, telematics devices and the EDI messages your TMS already exchanges. Those stay where they are.

Who owns the code

You do. Each app is a standard React and Node repository with its own backend, running on a managed, encrypted Postgres database. Export it at any time.

What logistics teams evaluate first

These are the questions the head of operations, the IT lead, the claims manager and the works council ask before a pilot gets a budget line.

Hosting in Germany

Nuclicore-managed on Hetzner in Germany or Azure in the EU, with BYOC or on-premise on Enterprise. No data leaves the EU unless you decide otherwise.

Beside the TMS, not inside it

Every workflow runs as a side-by-side application against TMS and WMS interfaces. No change request to the vendor, no wait for the next release.

Deadlines the system enforces

CMR claim windows, subcontractor document expiry, waiting time approvals and customs response deadlines are fields with escalation, not a note in the mail thread.

Audit trail for customers and insurers

Who raised, who reviewed, who approved, when, with what evidence. Exportable per case for customer audits, liability insurers and internal audit.

Partner access without partner risk

Subcontractors, drivers and customers get their own portal role with exactly the cases and fields they need. Nothing else is visible.

Evidence for NIS2 and customer questionnaires

Dependency scanning, secrets handling, CVE patching and a nightly ZAP scan run on every app. Release gates and logs give you documented technical measures for the security questionnaires your shippers send.

Exit without a rewrite

Standard code, standard database, documented interfaces. Procurement gets an exit path before signature, not after.

Built for real logistics operating models

Align scope, workflow ownership and governance for the segment you operate in.

Forwarders and carriers

Contract logistics and warehousing

Shippers' logistics departments

Customs and cross-border operations

Why delivery models are changing in logistics

The operators that ship fastest keep the TMS standard, move exceptions out of mail and treat compliance as running software.

Common Reality

The TMS handles the standard case. The margin is lost in the exception.

Damage claims, missing pallets, waiting time, address changes and customs questions all leave the TMS the moment they become an exception. From there they live in mail, and nobody can say who owes what to whom until month end.

Common Reality

Three compliance clocks run at once

E-invoice issuance from January 2027 for operators above 800k turnover. eFTI from July 2027, when authorities must accept electronic freight data. NIS2 since December 2025 with transport as an essential sector. Each one needs a process, not a memo.

Common Reality

Shippers push their obligations down the chain

Large customers ask for CO2 per shipment, security questionnaires and subcontractor evidence whether or not you are formally in scope. Answering by mail once is fine. Answering for every tender, every audit and every quarter is a workflow.

What you can build across transport, warehouse and compliance

Deliver governed software around your systems of record, with review points, traceability and code ownership.

Transport and partners

Damage, loss and delay claims

Capture the claim with photos and documents, check it against the CMR deadlines, route to the claims handler, involve the subcontractor and insurer, and close with a decision and a settlement record.

Licence, insurance, minimum wage declarations, driver and vehicle documents collected in a portal, checked, approved and tracked to expiry so no load goes to an unqualified carrier.

Pallet and load carrier accounts

Exchange records per stop, account balances per partner, disputes with evidence and a monthly reconciliation the partner can see.

Waiting time and surcharge approvals

Driver or dispatcher raises the waiting time or surcharge, evidence attached, approval by the right person, record per shipment for the invoice.

Warehouse and customer

Inbound and outbound deviations, wrong quantities, damaged goods and customer complaints in one queue with the customer contact, the deadline and the resolution.

Count results per location, discrepancy thresholds, approval by warehouse lead or customer, and the write-off record for finance.

Returns processing and disposition

Return intake, inspection checklist, disposition decision (restock, repair, scrap), customer notification and the record per item.

Customer status and document portal

Customers see their shipments, documents, claims and open cases in one place, with the fields you decide to expose and nothing else.

Compliance, customs and finance

Customs clarification queue

Questions on classification, origin, value and documents from the customs team or the broker land in one queue with the shipment reference, the deadline and the decision record.

Sanctions and export control checks

Screening results, dual-use questions and end-use declarations as a checklist per consignment with the approver on record.

Freight invoice audit and disputes

Carrier invoices checked against rates and approved surcharges, disputes with evidence, and e-invoice rejections handled in one workflow.

CO2 per shipment data collection

Collect distance, mode and load data per shipment from TMS and telematics exports, apply your factors, and hand the result to the customer or the reporting tool with a record of the inputs.

Fits your systems of record

Most ROI comes from removing manual handoffs between dispatch, warehouse, claims, customs and finance, and from connecting to the TMS and WMS with clear ownership of every interface.

We build governed workflows around TMS, WMS, ERP, telematics, customs software and freight platforms. We read what these systems expose and write back through their supported interfaces. We do not replace dispatch, routing or the customs declaration itself.

What we need from you

Integration patterns supported

Governed releases, stable production

Security and data controls for logistics

Each application runs its own backend, with a managed, encrypted Postgres per environment. Single-tenant infrastructure, BYOC and on-premise on Enterprise. Hosting in Germany or the EU by default.

RBAC, audit logs and monitoring keep access controlled per site, role and partner. Dependency scanning, secrets handling, CVE patching and a nightly ZAP scan run on every app, which gives you documented technical measures for NIS2 and for your customers' security questionnaires. Your workspace content is not used to train models.

Security controls in practice

What a first logistics pilot looks like

We align on one approval-heavy workflow and deliver reviewable increments with clear governance.

Scope, acceptance criteria, architecture outline

Pick one workflow (for example claims handling, subcontractor onboarding or pallet accounts). Define roles, approval matrix, the TMS fields to read and the records to write back.

First working version in Preview

Forms, routing, deadlines, approvals and the read integration to your TMS or WMS exports. Dispatch, claims and warehouse users click through and comment in the task.

Test environment with real roles and real data

Site and partner roles, SSO if applicable, write-back to TMS or DMS, audit trail export. Your IT reviews the interface and the access concept.

Production release and handover

Approval, release to Production, redeploy of an earlier version verified. Documentation for IT, operations and the works council. Decision on the next workflow.

Success criteria examples

Logistics & Supply Chain FAQ

Answers for operations, IT, claims and customs teams.

What does "governed" mean for logistics workflows?

Work is organised into reviewable tasks with acceptance criteria. Releases move through Preview, Test and Production with approval, and any earlier release can be redeployed. Every case carries who raised, reviewed and approved it, with timestamps and evidence. That is the trail customers, insurers and auditors ask for.

Our TMS already has a claims module. Why build beside it?

Because the module covers the standard case and the exception leaves it: the subcontractor's reply, the insurer's questions, the photos from the driver, the customer's credit note. Nuclicore builds the workflow around the module and writes the result back, so the TMS stays the system of record and the mail thread disappears.

Do you replace dispatch, routing or telematics?

No. Dispatch, routing, telematics and EDI stay in the systems you have. Apps consume their exports and interfaces and handle what happens around them.

Can subcontractors and customers log in?

Yes. Partner and customer portal roles see only their own cases and the fields you expose. Subcontractors upload documents and answer claims, customers see status and documents. Nothing else is visible, and every access is logged.

Does this cover eFTI and e-invoicing?

It covers the processes around them. eFTI submissions run through a certified platform and e-invoices through your invoicing system; Nuclicore handles the clarification, approval and dispute workflows that feed and follow both, with a record per case.

Does this help with NIS2 and customer security questionnaires?

The apps themselves run with dependency scanning, secrets handling, CVE patching, nightly ZAP scans and audit logs, which gives you documented technical measures for the applications you build. Subcontractor onboarding with evidence tracking is one of the first workflows operators build for the same reason.

Can it run on-premise or in our own tenant?

Yes. BYOC and on-premise deployment are available on Enterprise. The default is Nuclicore-managed single tenant on Hetzner in Germany or Azure in the EU.

We have twelve sites with different approval rules. One app or twelve?

One app, one codebase, one release. Site-specific fields, approvers and thresholds are configuration, not code. Deployment labels let you release per site or legal entity when a site needs a different cutover date.

Who owns the code and the data?

You do. Each app is a standard React and Node repository with its own backend, running on a managed, encrypted Postgres database. You can export the code and the data at any time and run it yourself. Procurement gets the exit path before signature.

Who maintains the app after the pilot?

Your team, through the same platform: describe the change, review the task, approve the release. Security patches to dependencies are applied by the platform. If you want to take the code and maintain it in-house, you can.

What is not a fit?

Dispatch and route optimisation, telematics, customs declarations themselves, EDI message processing and replacing the TMS or WMS. Nuclicore builds the governed workflows around these systems, not the systems.

Move claims, partners and exceptions out of mail and into governed software.

Ship beside your TMS and WMS, with audit trail, partner portals and code you own.