Multi-Carrier Shipping Software Development

Real-time rate quotes from all your carriers in a single API call -- parcel carriers (FedEx REST API, UPS OAuth API, USPS Web Tools, DHL Express API), regional carriers, and LTL carriers where applicable. For carriers without direct API access, EasyPost, ShipStation, or Shippo aggregation APIs provide normalised rate access to 100+ carriers under a single integration contract, eliminating the need to build and maintain individual carrier API connections for lower-volume partners.

Dimensional weight calculation is applied automatically per carrier rules -- each carrier uses a different dimensional factor (typically 139 or 166 cubic inches per pound for US domestic parcel), and the system calculates both actual weight and dimensional weight, billing at the greater of the two as the carriers do. Zone-based pricing optimisation identifies where rate arbitrage exists across your carrier network for the same origin-destination zone. Rate normalisation presents comparable service levels across carriers so ground, 2-day, next-day, and equivalent regional services are compared on an apples-to-apples basis. Negotiated rate application uses your account-specific contracted rates, not published list rates. The rate comparison your warehouse team currently does manually across carrier portals, automated to a sub-second response time.

Rule-based carrier selection engine that picks the right carrier for each shipment automatically, without requiring a human to review rates. The rules engine evaluates each shipment against a configurable priority-ordered rule set: cheapest rate meeting the required service level, preferred carrier for specific weight breaks or zone ranges, carrier weight and dimension limits, delivery date commitment requirements, product type restrictions (hazmat, lithium battery, alcohol -- each carrier has different acceptance rules), and customer-specified carrier preferences or carrier exclusions.

Weight break optimisation is built into the rules: for shipments near a carrier's weight tier boundary, the engine calculates whether upgrading to the next service tier on a cheaper carrier beats the cheapest option at the actual weight. This is the kind of optimisation your most experienced shipping team member does manually and everyone else skips. Carrier selection rules are managed via an admin interface so your operations team can update zone preferences, add weight break rules, or adjust service level priorities without a developer involved. The automation removes carrier selection from your per-shipment workflow, which scales linearly -- the same platform handles 50 shipments a day and 5,000 shipments a day without adding headcount.

Label generation via carrier API for all your carriers -- FedEx REST API, UPS OAuth 2.0 API, USPS Web Tools, DHL Express API, and regional carrier APIs. Bulk label generation allows your warehouse team to print a full wave of outbound shipment labels in a single batch operation rather than booking each shipment individually, which is the workflow required when processing high-volume daily outbound manifests. Label format handling covers thermal label formats (ZPL for Zebra printers, EPL for older Eltron hardware), standard PDF, and PNG for browser-based printing.

Carrier-specific required fields, package types, service codes, and ancillary service indicators -- signature required, adult signature, Saturday delivery, insurance -- are handled per carrier within the same label request API call. Domestic and international label generation includes required customs documentation: CN22 and CP72 customs declarations for postal channels, commercial invoice generation, and electronic export filing (EEI) for US exports above the $2,500 filing threshold. The returns management portal generates pre-paid return labels on demand -- either included in the outbound shipment or sent by email when the customer requests a return, with the returns carrier and service level configurable independently from the outbound carrier selection rules.

Tracking event ingestion from all carriers via API polling and webhook subscription where carriers support push notification. EDI 214 (Transportation Carrier Shipment Status) processing for carriers that deliver tracking updates via EDI rather than REST API, which covers the majority of LTL and regional freight carriers that have not yet built modern API tracking endpoints. This means the unified tracking timeline works for your full carrier mix, not just the carriers that have invested in modern APIs.

Normalisation of carrier-specific tracking status codes into a consistent status model -- picked up, in transit, out for delivery, delivered, exception -- removes the need for your customer service team to understand FedEx's 37 status codes versus UPS's different set. Unified tracking API and customer-facing tracking page show all shipments regardless of carrier in a single view, accessible from the order confirmation notification link. Delivery performance analytics track on-time delivery rate, average transit time, and exception rate by carrier and by origin-destination lane, so carrier performance is measured continuously rather than at quarterly business reviews. Carbon footprint calculation per shipment uses carrier-reported emissions factors (where published) or distance-based emissions modelling per shipment mode, supporting Scope 3 Category 4 emissions reporting under the GHG Protocol.

Automated customer notifications triggered by normalised tracking events: shipment booked, picked up, in transit, out for delivery, delivered, and exception. Email and SMS notification options, with SMS delivery handling via Twilio or a comparable messaging API so delivery is not dependent on email inbox filtering. Branded notification emails match your company identity -- carrier branding is not exposed to the customer unless you choose to show it. Customers interact with your brand throughout the shipment journey, not the carrier's.

Customer tracking page is accessible from the notification link without requiring a carrier portal account or a tracking number lookup on the carrier's website. The tracking page shows the unified status timeline, the estimated delivery date, and proof of delivery when available -- pulling from the same normalised tracking data used internally. Delivery exception notifications for delayed or returned shipments include the specific exception reason where the carrier provides it, giving customers context rather than a generic "delay" message. Delivery performance analytics record on-time delivery rates by carrier and by service level so your customer service team has data to work from when a customer raises a late delivery complaint.

Automated matching of carrier invoices against the rates quoted and booked at shipment time, identifying overbilling, incorrect surcharge application, address correction charges applied to addresses that were valid at booking, and accessorial fees not covered under your rate agreement. Industry benchmarks suggest 2-5 percent of carrier invoices contain billing errors; at meaningful shipment volume, the freight audit pays for itself in recovered charges.

Carrier invoice ingestion handles EDI 210 (Freight Invoice) for freight carriers and standard carrier billing file formats for parcel carriers. Each line on the invoice is matched to the corresponding shipment booking record and the rate-shopped rate at time of booking. Discrepancies above a configurable threshold are flagged to the exception queue rather than auto-approved. Exception workflow records the dispute, tracks the carrier's response, and logs the credit or adjustment when received. Recovery tracking reports the total disputed amount, recovered amount, and recovery rate by carrier over rolling periods so you can see whether a carrier has a systematic billing accuracy problem. Cost-per-shipment analysis by carrier, service level, and origin-destination zone feeds the carrier selection rules engine so zone-level rate performance is visible alongside theoretical rate comparisons.