Integrations

Keep your systems.
Connect the operation.

An integration is more than a connector. It needs clear ownership, authorized access, validated mappings and a reliable response when something goes wrong.

Discuss a connection
What connects

What Intelicargo connects to

Confirmed per implementation

Accounting & ERP

NetSuite and other accounting systems

Decide who owns customers, items, invoices and journals, then let them flow both ways automatically. Your finance team validates the transaction rules before anything goes live.

Confirmed per implementation

Operational systems

QuickBase and partner applications

Map the specific records and events that need to move between your operational tools and the shipment record, so nobody re-keys the same job twice.

Confirmed per implementation

EDI & trading-partner feeds

Orders in, status and paperwork out

Where a partner can send EDI or API data, orders land in Intelicargo directly and status updates and paperwork go back automatically. Message types are agreed with each partner.

Confirmed per implementation

Customs & regulatory filings

Puerto Rico e-manifest · AES/EEI

Generate the filing files and track the workflow from the same shipment record, so the paperwork matches the cargo that actually moved.

Confirmed per implementation

Customer channels

Portals, websites and notifications

Design the handoff between customer self-service and your operations team, including escalation and communication rules.

Confirmed per implementation

Custom API workflows

Your approved integration contract

Agree authentication, identifiers, mappings, retries, reconciliation and monitoring before any live write is enabled.

These are integration pathways, not a list of switched-on connections. Provider capabilities, customer permissions and testing are verified for each implementation.
Payment gateways

Get paid where
the work happens.

Connect your card processor and take payment on bookings, invoices and counter sales. The gateway confirms the payment, the booking is marked paid and the ledger entry follows, without anyone typing a receipt number.

  • Hosted checkout and pay-by-link invoices, so card details go straight to the gateway and not through your servers
  • Gateway confirmations mark the booking paid and post to the ledger automatically
  • Refunds issued from the same record and reflected in your books
  • Customer wallet and prepaid credit applied at booking alongside card payments

Which gateway you use, and its fees and settlement terms, are between you and your processor. We connect to it and keep the records consistent.

StripeCard payments with signed webhook confirmation.
PowerTranzHosted payment page, callback confirmation and refunds.
Wallet & creditPrepaid balances and credit limits checked at booking.
Other gatewaysConnected on request and confirmed for each implementation.
Build on what already works

One shipment record.
Every system around it.

Your accounting, partner and customs systems still matter. Define clear data ownership and connect the right information to the right workflow.

  • ERP & accounting
  • Payment gateways
  • Customer portal
Intelicargo One connected workflow
  • Carriers & partners
  • APIs & EDI
  • Customs filings

Integration architecture illustration. Available connections are confirmed for each implementation.

For your technical team

Settle the contract
before you connect.

Most integration pain comes from unspoken assumptions. We write down identifiers, direction of data, timing, retries and who is paged when a message fails, then test with real records.

Open the developer hub 
// Illustrative example only, not a public API specification
{
  "event": "shipment.status_changed",
  "reference": "IC-10482",
  "status": "Customs Staged",
  "occurred_at": "2026-01-14T09:42:00-04:00",
  "idempotency_key": "evt_7f3a…"
}

Your operation has enough moving parts.
Your technology shouldn’t add more.

Let’s map the workflow, find the friction and build the right connection.

Talk to Intelicargo