AWBack is a hosted bridge between your ERP and the airlines. Send shipments in your own JSON. We check them, turn them into electronic air waybills, deliver them to the carrier and send every acknowledgement and status update back to your system.
One shipment, out and back. The AWB number is an example.
For forwarders who run their own systems
If your operation runs on an in-house or smaller ERP, sending electronic air waybills usually means moving to a large forwarding suite or retyping data into airline portals. AWBack connects the system you have to the airlines you book, and tells it what happens next.
Airlines increasingly charge extra for paper air waybills. Sending complete e-AWB data electronically avoids those fees and the manual corrections that follow incomplete data.
How it works
1
Onboard
We set up your account, record your e-AWB activations with each airline, load your AWB stock and agree the webhook endpoints that will receive updates.
2
Connect your ERP
Your ERP posts shipments in its own JSON, or in our standard schema if you build against it. We build and test the mapping with you before anything goes live.
3
Send shipments
Each shipment is validated, converted to the format its airline accepts and sent over our messaging channel.
4
Get answers back
Acceptances, rejections and status updates are pushed to your webhooks as they arrive, and show up in your client portal.
What's included
Messages
Your format, or ours
Keep the JSON your ERP already produces, or send our documented standard schema.
Cargo-XML and ONE Record
XFWB, XFZB and XFHL through a cargo messaging network, and IATA ONE Record for carriers that are ready for it.
Answers as signed webhooks
Accepted, rejected, received, departed, arrived and delivered events, each signed so your system can verify it came from us.
Control
AWB stock
Your airline number ranges in one place, with check-digit validation before a number is used.
Checks before sending
Missing or invalid data is reported back in your own field names, before an airline can reject it.
Isolation and allowlists
Each client’s data is kept separate, and API access can be limited to your own IP addresses.
Visibility
Client portal
Transaction history, current status of every shipment and reporting across your airlines.
Complete audit trail
Every message in and out is kept exactly as sent and received, for disputes and corrections.
Talk to us about onboarding
Tell us which ERP you run and which airlines you book. We'll explain what onboarding involves and what we need from you to get your first e-AWB out.
