Can customs software connect through API and ERP?
Yes. ERP integration is possible when the customer system integrates into the Declarium API. Declarium provides the API-based handover point; the connection from ERP, SAP, WMS, TMS, shop, or fulfillment systems is implemented on the customer side. A full integration project is not required to start.
- REST API as the handover point for customer systems
- ERP, SAP, WMS, TMS, shop, and fulfillment integration by the customer team or integration partner
- Quick start through email, upload, Excel, CSV, or PDF
What data does a customs API need?
Customs workflows often need more than an order number and recipient address. Depending on the procedure, shipment, item, value, origin, weight, package, address, and document data may be required. Declarium helps turn this information from systems or documents into a usable customs process.
- Order, shipment, SKU, and item data
- Value, origin, weight, quantity, Incoterms, and addresses
- Invoices, packing lists, tracking references, and supporting evidence
What comes back from the customs process?
Integration does not end when data is submitted. Operations teams need feedback to continue shipping, warehouse, customer service, and finance workflows. Declarium can return status, references, documents, questions, and errors in a structured way.
- Status, MRN, references, and process information
- Export accompanying documents, customs documents, and archive data
- Questions, error messages, and exceptions
Email, upload, or API: which start fits?
Not every company needs to start with a deep API integration. Many teams can begin with email, upload, Excel, CSV, PDF, or structured files and gain operational experience quickly. When volume and process maturity increase, the customer system can later integrate directly into the Declarium API.
- Email and upload for a quick operational start
- API for recurring and time-sensitive volume
- Step-by-step integration instead of a big-bang project
Integration from ERP, SAP, WMS, TMS, shop, and fulfillment
Customs data originates in different systems: purchasing and order management in ERP, goods and picking data in WMS, transport data in TMS, customer data in shop or fulfillment workflows. In a full integration, the customer system sends this data to the Declarium API and can process feedback from Declarium.
- Data transfer from ERP, SAP, or adjacent systems into the Declarium API
- Integration by the customer team or integration partner
- Customs workflows closer to the operational data source
From PDFs and documents to system-ready customs data
Not all relevant information is cleanly available in the ERP. Commercial invoices, packing lists, and supporting documents often remain part of the workflow. Declarium can turn document data into structured customs information and combine it with system data.
- Data intake from trade documents
- Combination of document and system data
- Less manual preparation before customs processing
Validation, errors, and exception handling
A customs integration also has to work when data is missing, values conflict, or a process should not continue automatically. Declarium makes these cases visible and supports question and clarification workflows instead of pushing incorrect data forward.
- Plausibility checks before further processing
- Clear questions for missing or contradictory data
- Documentation of status, errors, and decisions
When Declarium is a fit
Declarium fits especially well when customs workflows recur, several systems are involved, or teams want to reduce manual broker, email, and Excel workflows. The start can intentionally be simple; full system integration is most useful when volume, repetition, and IT resources are available.
- Recurring import, export, transit, or parcel volume
- Quick start without full ERP integration
- Later API integration by the customer team or integration partner
