Arub Shipping - Carrier & Order Integrations
Worked on carrier APIs, order synchronization, shipment processing, label generation, reconciliation, idempotency, retries, and recovery handling.
- External shipping connectivity
- Carrier APIsExternal shipping connectivity
- Synchronized processing workflow
- Order → shipmentSynchronized processing workflow
- Retry and recovery handling
- IdempotentRetry and recovery handling
Arub Shipping connects order processing with carrier services. Tijani's documented integration experience includes carrier API connectivity, order synchronization, shipment processing, label generation, transaction reconciliation, idempotency, retries, and recovery handling.
The problem
Shipping workflows need to carry order data into carrier services and bring shipment status and labels back into the originating operation. This becomes fragile when API requests are retried, events are duplicated, or the carrier and order systems temporarily disagree.
Engineering constraints
- Carrier services are external dependencies with their own request and response lifecycle.
- Order and shipment state must remain synchronized across systems.
- Retries and recovery need protection against duplicate processing and inconsistent records.
Tijani's role
Tijani worked on the shipping integration layer, covering carrier APIs, order synchronization, shipment processing, label generation, and transaction reconciliation. The documented reliability mechanisms include idempotency, retries, and recovery handling.
- Connected shipping workflows to external carrier APIs.
- Synchronized order information with shipment processing.
- Supported label-generation workflows.
- Worked on reconciliation and safe retry/recovery behavior.
Carrier lifecycle and recovery
The engineering scope follows a shipping operation from order synchronization through carrier processing and label generation. Idempotency and recovery behavior are important because a repeated request should not create duplicate shipment actions or leave the order and carrier states out of sync.
Technologies & implementation areas
- Carrier APIs
- Order Sync
- Shipment Processing
- Label Generation
- Reconciliation
- Idempotency
- Retries
Role & ownership
Tijani participated in developing and deploying Arub Shipping integration workflows, including carrier APIs, order synchronization, shipment processing, label generation, idempotency, retries, and reconciliation. This does not imply ownership of the wider Arub platform or carrier relationships.