SaaS integration
Your SaaS Doesn't Ship Freight. It Should.
Every WMS needs outbound shipping. Every marketplace needs carrier rates. Every ERP needs freight tracking. Warp's API adds quoting, booking, and tracking to your product in one afternoon. Your users get freight capabilities. You get a new revenue stream.
One afternoon integration · New revenue stream · 20,000+ carriers · All modes
Why your SaaS should ship freight
Adding freight to your platform is not a feature request. It is a business model expansion with four compounding advantages.
Revenue expansion
Take a margin on every shipment your users book through your platform. Freight becomes a revenue line, not a cost center.
Stickier product
Shipping is a daily workflow. Once users are booking freight inside your product, switching costs go through the roof.
Competitive moat
Your competitor does not have embedded freight. You do. That is a differentiator prospects can see in the first demo.
User value
Your users stop switching between your app and carrier portals. Everything lives in one place. That is the experience they want.
Shopify added shipping and it became a multi billion dollar revenue line. The B2B freight version of this play is wide open.
What kind of SaaS products add freight?
WMS / warehouse systems
Outbound shipping from pick/pack. When an order is staged, your WMS calls Warp and books the shipment automatically.
ERPs
Purchase order fulfillment. When a PO is approved, your ERP triggers a freight quote and books the cheapest option.
Marketplaces
Connecting buyers with shipping. Your marketplace gives sellers embedded freight rates at checkout.
Order management
Auto ship when an order is ready. No manual carrier selection, no copy pasting tracking numbers.
Inventory management
Replenishment triggers shipping. When stock hits reorder point, your system books the freight to refill.
E-commerce platforms
B2B wholesale shipping. Your merchants ship pallets, not parcels. Warp handles the freight side.
How to integrate in one afternoon
Three integration points. Three API calls. Your product goes from zero freight capability to full quoting, booking, and tracking.
1. Quoting: get rates
Your product calls POST /api/v1/freights/quote, gets rates back, and displays them in your UI. Your users never leave your product.
POST /api/v1/freights/quote
// Your product calls Warp for rates
const response = await fetch(
"https://api.wearewarp.com/api/v1/freights/quote",
{
method: "POST",
headers: {
"Content-Type": "application/json",
"apikey": "YOUR_API_KEY"
},
body: JSON.stringify({
pickupDate: ["2025-03-15"],
pickupInfo: {
zipCode: "90001",
city: "Los Angeles",
state: "CA"
},
deliveryInfo: {
zipCode: "85001",
city: "Phoenix",
state: "AZ"
},
listItems: [{
name: "Pallet",
length: 48, width: 40, height: 48,
sizeUnit: "in",
totalWeight: 800, weightUnit: "lb",
quantity: 2, packaging: "pallet"
}]
})
}
);
const { data } = await response.json();
// data.quoteId, data.totalCost, data.transitDays2. Booking: confirm the shipment
User selects a rate in your UI. Your backend calls POST /api/v1/freights/booking. Shipment is confirmed, tracking number returned.
POST /api/v1/freights/booking
// User selects a rate, your backend books it
const booking = await fetch(
"https://api.wearewarp.com/api/v1/freights/booking",
{
method: "POST",
headers: {
"Content-Type": "application/json",
"apikey": "YOUR_API_KEY"
},
body: JSON.stringify({
quoteId: data.quoteId,
pickupInfo: {
zipCode: "90001",
city: "Los Angeles",
state: "CA",
street: "123 Warehouse Blvd",
contactName: "Dispatch Team",
phone: "3105551234"
},
deliveryInfo: {
zipCode: "85001",
city: "Phoenix",
state: "AZ",
street: "456 Distribution Dr",
contactName: "Receiving Dock",
phone: "6025551234"
},
listItems: [{ /* same items from quote */ }]
})
}
);
const shipment = await booking.json();
// shipment.data.shipmentId, shipment.data.trackingNumber3. Tracking: real time updates
Webhook events flow from Warp to your platform. Display shipment status inside your UI. Your users never open a carrier portal.
Webhook handler
// Warp pushes status events to your webhook URL
// Register your endpoint in the Warp dashboard
app.post("/webhooks/warp", (req, res) => {
const event = req.body;
// event.status: "PICKED_UP", "IN_TRANSIT", "DELIVERED"
// event.trackingNumber, event.location, event.timestamp
// Update your UI, notify your user
await updateShipmentStatus(
event.trackingNumber,
event.status,
event.location
);
res.status(200).send("ok");
});The revenue model
You get Warp's all inclusive rate via API. You add your margin: 10%, 15%, whatever you want. You charge your user. You keep the difference.
$500 LTL shipment
With 15% margin, that is $75 per shipment. Pure incremental revenue on freight your users are already moving.
100 shipments/month
At $75 per shipment, that is $7,500 in new MRR from one customer. And it compounds: more users shipping more frequently.
Your price, your brand
Your users see your rates, not Warp's. The API is invisible. You control the margin, the presentation, and the experience.
What your users get
- -Instant rates across LTL, truckload, box truck, and cargo van.
- -Real time tracking inside your product. No separate carrier portals.
- -All inclusive pricing with no surprise fees.
- -20,000+ local 3rd party carriers dispatched through the Warp driver app.
- -Every mode from a single API. One integration covers all freight types.
Add freight to your SaaS
One API key. One afternoon. New revenue on every shipment your users book through your platform.
The infrastructure your users ship on
When your users book freight through your product, they are shipping on Warp's network. That means 20,000+ local 3rd party carriers, 50+ cross dock facilities, and our AI backbone, Orbit, managing every shipment from pickup to proof of delivery. All inclusive pricing means no accessorial surprises. Every rate your users see is the final price.
Frequently asked questions
Most teams integrate in one afternoon. The API is standard REST with JSON. No EDI, no VAN providers, no carrier specific integrations.
Yes. You get Warp’s all inclusive rate and add whatever margin you want. Your users see your price, not Warp’s.
Not unless you want them to. The API powers everything from your backend. Your users see your brand, your UI, your pricing.
LTL (1 to 12 pallets), truckload (dry van, reefer, flatbed), box truck (26 foot, liftgate equipped), and cargo van (cartons, cases, parcels, or up to 3 pallets).
No minimums. Your users can ship one pallet or a hundred. The API handles any volume.
One afternoon. New revenue. Every shipment.
Your SaaS already has the users. Warp's API gives them freight. You keep the margin.
One afternoon integration · New revenue stream · 20,000+ carriers · All modes