FedEx
FedEx software-provider onboarding and the customer’s own shipping account are required. Authorization testing is separate from enabling shipping operations.
Carrier integrations
Connect each carrier account to the right company.
AFilipTrans is built for separate customer workspaces. Carrier access is authorised per company, so one customer cannot see or use another customer's credentials, shipments or tracking data.
Who does what
A clear split between platform and customer.
- 01
RoadTech Logistics maintains the AFilipTrans integration and completes any software-provider approval required by the carrier.
- 02
The customer company holds the commercial carrier account and requests access where the carrier requires an account-holder application.
- 03
A Super Admin connects the carrier inside that company's isolated workspace. A Transport Manager can review operational status without seeing secrets.
- 04
The system stores encrypted credentials, records supported authorization tests and keeps an audit trail. Job or shipment synchronization requires a separately implemented and tested carrier interface.
Provider routes
One integration screen, provider-specific onboarding.
Carrier availability, API approval and commercial terms remain subject to each provider and the customer's carrier agreement.
UPS
UPS issues application credentials for approved accounts. Multi-customer authorization needs the appropriate provider-approved flow; a normal UPS password is not an API connection.
Amazon Shipping
A public software application needs approved roles and customer authorization. The issued refresh token is used for authorization testing; operations depend on the implemented adapter.
DHL Express, DPD & Evri
Availability depends on the customer contract. The carrier or account manager issues the required credentials to the account holder.
Before connecting
What the customer should have ready.
An active carrier contract or shipper account in the customer company's name.
Authority from the account owner to connect the service.
The carrier account number and approved API credentials or OAuth access.
A named office owner for connection failures and operational exceptions.
Secrets entered only in the secure integration form—not by email, chat or shared documents.
Know the difference
Sending a shipment is not the same as hauling for a carrier.
If your trucks transport freight for DHL or another carrier, ask for its approved carrier/subcontractor API or EDI interface. A public shipping API does not automatically give access to allocated haulage jobs.
We first confirm the carrier division, existing job portal, customer consent and supported operations: order receipt, acceptance, milestones and proof of delivery.
Honest availability
Credentials secured. Operations verified separately.
Available today: workspace-isolated credential storage and authorization testing for supported OAuth providers.
Automatic carrier-job import, shipment booking, labels, provider webhook delivery and POD synchronization are not enabled simply by saving credentials. Each needs the correct approval, an implemented adapter and sandbox acceptance testing before live use.
Check your integration requirementsPLAN THE CONNECTION
Request a guided demo