Skip to content
Bitween AI is on the way

Logistics & supply chain

Track every shipment event from carrier to customer, and prove it arrived.

Logistics integration is high-volume, event-shaped and unforgiving: a lost status update is a missed delivery window. Bitween receives events from carriers, warehouses and customers, routes them by content, and keeps each shipment’s full trail one search away.

Talk to an architectRead the docs

The challenge

What makes logistics & supply chain integration hard.

01

Every carrier is different

Webhooks from one, XML files on SFTP from another, a queue from a third, and all of them change without notice.

02

Status storms

Tracking updates arrive in bursts of thousands. They must not starve billing, customs or proof-of-delivery flows.

03

Customers want events in their systems

Shippers expect updates published to their own brokers and APIs, with retries when their side is down.

Flows you can run today

How Bitween handles it.

Each flow below uses capabilities that exist in Bitween now, with links into the documentation that describes them.

Flow 1

Carrier status events, routed by content

Carriers call an async API gateway and get a 202 with an exchange id immediately. Bitween promotes the tracking number and status, and bus gateway routes with match expressions send exceptions to operations and deliveries to billing.

  1. 1Async API gateway
  2. 2Promote trackingNo
  3. 3Publish by type
  4. 4Match status
  5. 5Deliver per route

Flow 2

Warehouse outbox to customer brokers

A scheduled job drains the warehouse's outbox table in marker mode, turning each shipment notification into an exchange and marking the row. Deliveries publish to each shipper's own RabbitMQ or Amazon SQS queue.

  1. 1Scheduled job
  2. 2Marker mode
  3. 3Map per shipper
  4. 4Publish to customer queue

Flow 3

Proof of delivery from inboxes

A POP3 receiver turns emailed proof-of-delivery scans into exchanges, carrying the attachment base64-encoded, and an upload handler files each one in S3 or Azure Blob Storage.

  1. 1POP3 receiver
  2. 2First attachment · base64
  3. 3Upload handler
  4. 4Archive by exchange

Controls that matter here

Capabilities behind the flows.

Follow one shipment end to end

Exchanges created from responses share a correlation id, so one search shows the whole chain of a shipment across flows.

Docs

Lanes for tracking storms

Work groups give high-volume tracking its own RabbitMQ queues, so billing and customs flows keep moving.

Docs

Deduplicated intake

A redelivered broker message with the same key is acknowledged without creating a second exchange.

Docs

A map of every route

The Flow map draws gateways, message types and subscriptions, and warns about loops and messages nobody listens to.

Docs

Good to know about formats and scope

JSON and XML are mapped natively. Carrier CSV or EDI 214 status messages need a custom adapter to translate them before mapping.

Related use cases

Go deeper on the patterns.

Event-driven integration

Consume from RabbitMQ and Amazon SQS, route by content and chain flows by message type.

File & mailbox automation

Pick up files from S3, Azure Blob, SFTP and mailboxes; transform and deliver them safely.

API gateway for partners

One HTTPS endpoint per business process: sync when partners need an answer, async when they need speed.

Plan your logistics & supply chain integrations with us.

Share your partners, systems and volumes. We'll show you how the flows would run on Bitween in your own environment.

Talk to an integration architectRead the docs