Freight Opportunity API
Qualification creates the opportunity map.
The Freight Opportunity API turns customer fulfillment context into a category-level estimate of where Warp can win freight. Order execution is a separate surface; the discovery surface is what makes the network show up.
POST /api/fulfillment/qualify [AVAILABLE]
Submit a qualification payload (company, products, channels, inbound, outbound, systems) and receive a Freight Opportunity Map.
GET /api/fulfillment/opportunity-map/:customer_id [AVAILABLE]
Read the most recent Freight Opportunity Map for a customer.
POST /api/fulfillment/opportunity-map/:customer_id/recalculate [AVAILABLE]
Re-run the opportunity map against the latest submission state. Preserves activated/dismissed cards.
GET /api/fulfillment/opportunities/:customer_id/:card_id [AVAILABLE]
Read a single opportunity card.
POST /api/fulfillment/opportunities/:customer_id/:card_id/activate [AVAILABLE]
Mark an opportunity card as activated. Appends to audit log.
POST /api/fulfillment/opportunities/:customer_id/:card_id/dismiss [AVAILABLE]
Mark an opportunity card as dismissed. Appends to audit log.Qualification API payload
A minimum body that returns a Freight Opportunity Map.
Company + products + channels + inbound + outbound + systems. Sparse payloads are accepted — the engine flags “missing data” instead of failing.
{
"company": {
"name": "Example Home Goods",
"website": "https://example.com"
},
"products": [
{
"sku": "SOFA-01",
"length_in": 72,
"width_in": 35,
"height_in": 30,
"weight_lbs": 120,
"fragile": true,
"expected_units_stored": 50
}
],
"channels": [
"DTC",
"Wholesale",
"Retail"
],
"inbound": {
"imports_inventory": true,
"ports": [
"Port of Los Angeles"
],
"average_containers_per_month": 4,
"vendors_ship_separately": true,
"average_vendors": 8,
"inbound_cadence": "weekly"
},
"outbound": {
"monthly_orders": 1200,
"ships_to_stores": true,
"ships_big_and_bulky": true,
"urgent_local_delivery": true
},
"systems": {
"erp": "NetSuite",
"ecommerce": "Shopify",
"parcel_provider": "Shippo",
"wms": "Existing 3PL"
}
}Freight Opportunity Map (response)
23 freight categories, each with status, size, confidence, activation path, and the reason Warp can win.
{
"customer_id": "01HW7P3J9X3F9DA0Z7K2VEYDN",
"overall_opportunity": "high",
"confidence": "high",
"opportunities": [
{
"category": "Inbound vendor freight",
"status": "detected",
"size": "medium",
"confidence": "medium",
"activation_path": "plug_and_play",
"recommended_first_move": "Issue a vendor routing guide for the top three vendors and tender their next pickup through Warp.",
"why_warp_has_right_to_win": "Warp can route, consolidate, and visibility-track vendor freight before it ever touches the dock.",
"estimated_monthly_volume": "5 vendor pickups"
},
{
"category": "Imported container and drayage",
"status": "detected",
"size": "high",
"confidence": "medium",
"activation_path": "auto_bundled",
"recommended_first_move": "Wire the vessel ETA feed for the top port and pre-coordinate the next container handoff.",
"why_warp_has_right_to_win": "Warp connects port visibility, cross-dock decisions, and downstream fulfillment or freight routing into one event stream.",
"estimated_monthly_volume": "6 containers / month"
},
{
"category": "Port to warehouse drayage",
"status": "detected",
"size": "high",
"confidence": "low",
"activation_path": "auto_bundled",
"recommended_first_move": "Take over the next container drayage leg with port appointment coordination and chassis SLA.",
"why_warp_has_right_to_win": "Warp can dispatch drayage against vessel ETAs and dock availability, avoiding demurrage and detention.",
"estimated_monthly_volume": "6 drayage legs"
},
{
"category": "Transload",
"status": "detected",
"size": "high",
"confidence": "medium",
"activation_path": "auto_bundled",
"recommended_first_move": "Spec a transload SOP at a port-adjacent cross-dock for the next inbound container.",
"why_warp_has_right_to_win": "Warp can transload floor-loaded containers into pallet builds before the long haul, recovering labor and reducing damage.",
"estimated_monthly_volume": "6 containers"
}
],
"missing_data": [
"Vendor origin ZIPs",
"Current vendor freight terms",
"Top three vessels by lane",
"Drayage SCAC",
"Chassis pool",
"Current per-container drayage spend",
"Target transload region",
"Current transload provider",
"Top destination region",
"Inbound cadence",
"Inbound ASN format",
"Dock appointment SLAs",
"SKU velocity by month",
"Seasonal peak factor",
"Average units per order",
"Branded packaging spec",
"Average parcel cost",
"Destination ZIP distribution",
"Current LTL providers",
"Average pallet count per shipment",
"Origin and destination ZIP",
"Frequency target",
"Local origin/destination ZIPs",
"Weekly urgent move count",
"Top retailer list",
"Compliance window specs",
"Store cluster definitions",
"Average B2B order size",
"Delivery window patterns",
"Return rate by SKU",
"Return condition rules",
"SKU bypass eligibility list",
"SKU velocity by region",
"Vendor list",
"Current freight terms",
"Promise breakage rate",
"Top 20 SKU carton dims",
"Damage events sample",
"PO feed payload sample"
]
}Endpoints
Full V1 surface.
Endpoints marked AVAILABLE are live today. Endpoints marked PLANNED are part of the V1 design surface and will return 501 Not Implemented until shipped.
POST /api/fulfillment/blueprints [AVAILABLE]
Create a Fulfillment Blueprint from a structured submission.
GET /api/fulfillment/blueprints/:id [AVAILABLE]
Read a Fulfillment Blueprint by id.
POST /api/fulfillment/orders [AVAILABLE]
Create an order. Optionally route to a specific site_id, allocate inventory by SKU, and auto-purchase cheapest label. Idempotent via external_id.
GET /api/fulfillment/orders [AVAILABLE]
List orders for the merchant. Supports status + service_class filters, pagination via limit/offset.
GET /api/fulfillment/orders/:id [AVAILABLE]
Read an order by id, including its shipment (if a label was purchased) and event log.
POST /api/fulfillment/orders/:id/cancel [AVAILABLE]
Cancel an order. Releases allocated inventory and voids label at carrier if purchased.
POST /api/fulfillment/orders/:id/mark-shipped [AVAILABLE]
Operator action: finalize an order as shipped (decrements on_hand and allocated inventory).
GET /api/fulfillment/sites [AVAILABLE]
List fulfillment sites. ?active=true filters to active only.
POST /api/fulfillment/sites [AVAILABLE]
Create a fulfillment site. Multi-site is supported from day 1; today the network is LA only.
GET /api/fulfillment/sites/:id [AVAILABLE]
Read a site by id.
PATCH /api/fulfillment/sites/:id [AVAILABLE]
Update a site (rename, change address, deactivate).
GET /api/fulfillment/products [AVAILABLE]
List products in the SKU catalog. Filters by sku, active. Paginated.
POST /api/fulfillment/products [AVAILABLE]
Register a product (SKU, dimensions, weight, hazmat/fragile flags).
GET /api/fulfillment/products/:idOrSku [AVAILABLE]
Read a product by id (prod_*) or by SKU.
PATCH /api/fulfillment/products/:idOrSku [AVAILABLE]
Update product fields. Deactivate by setting active=false.
GET /api/fulfillment/inventory [AVAILABLE]
Read inventory levels. Filters by site_id, sku, in_stock_only.
POST /api/fulfillment/inventory/adjust [AVAILABLE]
Adjust a single inventory line. Reasons: received, allocated, released, shipped, returned, damaged, count_correction, transfer_*. Audit-logged.
POST /api/fulfillment/inventory/receive [AVAILABLE]
Receive multiple SKUs into a site in one call (WRO-style). Audit-logged.
POST /api/fulfillment/returns [AVAILABLE]
Create an RMA for an order. auto_generate_label=true uses ShipStation /v2/labels/{outbound}/return to mint a return label. Idempotent via external_id.
GET /api/fulfillment/returns [AVAILABLE]
List returns. Filters by status, order_id, site_id. Paginated.
GET /api/fulfillment/returns/:id [AVAILABLE]
Read a return by id, including return shipment, items, and event log.
POST /api/fulfillment/returns/:id/inspect [AVAILABLE]
Operator action: per-item restock/dispose/quarantine decisions. Restocked items increment on_hand at the return site.
POST /api/fulfillment/returns/:id/cancel [AVAILABLE]
Cancel a return. Voids the return label at ShipStation if generated.
POST /api/fulfillment/freight/quote [AVAILABLE]
Get a freight quote (LTL/FTL/drayage/multistop) via Warp internal API. Carrier-agnostic request, Warp execution under the hood.
POST /api/fulfillment/parcel/quote [AVAILABLE]
Get parcel rates across connected carriers (ShipStation V2 backed). Carrier-agnostic request shape.
POST /api/fulfillment/parcel/label [AVAILABLE]
Purchase a parcel shipping label (from a rate_id or full shipment shape). Idempotent via external_id.
GET /api/fulfillment/parcel/tracking/:carrier/:tracking [AVAILABLE]
Get tracking events for a parcel shipment.
POST /api/fulfillment/parcel/webhook [AVAILABLE]
Webhook receiver for ShipStation tracking updates. Requires X-Webhook-Secret header.
POST /api/fulfillment/skus [PLANNED]
Add or update SKU profiles for a blueprint.
POST /api/fulfillment/activation-path [PLANNED]
Submit or update activation path (starting approach, integration method, decision mode).
POST /api/fulfillment/module-activation [PLANNED]
Set per-module activation mode (auto bundled, plug and play, inactive).
POST /api/fulfillment/system-connections [PLANNED]
Register existing systems Warp should plug into.
GET /api/fulfillment/launch-recommendations [PLANNED]
List activation recommendations (which module to start with, what to integrate first).
POST /api/fulfillment/plug-and-play/configure [PLANNED]
Configure a module in plug-and-play mode against an existing system.
POST /api/fulfillment/auto-bundled/configure [PLANNED]
Configure a module to be auto bundled with Warp execution.
POST /api/fulfillment/upstream/vendor-routing-guides [PLANNED]
Submit vendor routing guide compliance state and generation request.
POST /api/fulfillment/upstream/purchase-orders [PLANNED]
Stream PO data into Warp for upstream freight planning.
POST /api/fulfillment/upstream/inbound-consolidation [PLANNED]
Submit inbound consolidation preferences and thresholds.
POST /api/fulfillment/upstream/inventory-positioning [PLANNED]
Submit inventory positioning preferences (placement, forward deployment, bypass).
POST /api/fulfillment/upstream/packaging-intelligence [PLANNED]
Submit packaging intelligence inputs and flagging preferences.
POST /api/fulfillment/upstream/retail-replenishment [PLANNED]
Submit retail compliance and replenishment planning inputs.
POST /api/fulfillment/upstream/delivery-promises [PLANNED]
Submit delivery promise source and adjustment preferences.
GET /api/fulfillment/upstream/recommendations [PLANNED]
List upstream-control recommendations for a blueprint.
GET /api/fulfillment/upstream/risks [PLANNED]
List upstream-control risks (vendor compliance, promise at risk, packaging gaps).
POST /api/fulfillment/imports [PLANNED]
Submit or update import profile (regions, ports, containers per month, load type).
POST /api/fulfillment/drayage [PLANNED]
Submit or update drayage workflow and port pain points.
POST /api/fulfillment/transload [PLANNED]
Define transload rules per SKU or container type.
GET /api/fulfillment/port-recommendations [PLANNED]
List port-orchestration recommendations for a blueprint.
POST /api/fulfillment/inventory-split-rules [PLANNED]
Define regional inventory split rules applied at port arrival.
POST /api/fulfillment/inbound-transport [PLANNED]
Submit or update inbound transport and origin profile.
POST /api/fulfillment/inventory-positioning [PLANNED]
Submit or update demand region and inventory strategy.
POST /api/fulfillment/receiving-plans [PLANNED]
Submit or update receiving rules.
POST /api/fulfillment/order-rules [PLANNED]
Submit or update order rules.
POST /api/fulfillment/edge-case-policies [PLANNED]
Submit edge case policies and custom rules.
POST /api/fulfillment/rate-estimates [PLANNED]
Generate a pricing estimate from SKU dims and volume.
POST /api/fulfillment/returns-policies [PLANNED]
Submit returns policy.
POST /api/fulfillment/autopilot/rules [PLANNED]
Submit autopilot permissions and thresholds.
GET /api/fulfillment/autopilot/recommendations [PLANNED]
List active recommendations for a blueprint.
POST /api/fulfillment/autopilot/approve [PLANNED]
Approve a pending autopilot recommendation.
POST /api/fulfillment/autopilot/execute [PLANNED]
Execute an approved decision against an order.
GET /api/fulfillment/autopilot/decision-log [PLANNED]
Read the rolling decision log for a blueprint.
GET /api/fulfillment/transport-recommendations [PLANNED]
List transport-before-fulfillment recommendations.
POST /api/fulfillment/cross-dock-bypass-rules [PLANNED]
Define SKU-level cross-dock bypass eligibility.FulfillmentBlueprint
Top-level object.
Includes company, SKUs, inbound transport, inventory positioning, storage, orders, edge cases, returns, outbound modes, autopilot, complexity, risk flags, recommendations, pricing, and the rolling decision log.
{
"id": "01HW7P3J9X3F9DA0Z7K2VEYDN",
"company": {
"name": "Northstar Outdoor",
"contact": "Avery Chen",
"monthlyOrderVolume": 4200
},
"skuCount": 3,
"complexity": "moderate_complexity",
"estimatedMonthlyTotal": 35181.12,
"riskFlags": [],
"fragmentationLevel": "moderate"
}SKUProfile
Product truth, normalized.
{
"id": "sku-1",
"skuName": "Camp Stove Pro",
"skuCode": "NS-CSP-01",
"dimensionsIn": {
"length": 22,
"width": 14,
"height": 6
},
"weightLb": 14,
"expectedUnitsStored": 600,
"flags": {
"fragile": false,
"hazmat": "no"
}
}ActivationPath
Run it with Warp or plug Warp into your stack.
Every module can be auto bundled with Warp execution, or plug and play over the system you already use. Customers can start with one module, one lane, one vendor, one SKU group, one warehouse, or one store region.
{
"startingApproach": "plug_into_existing",
"moduleActivations": {
"fulfillment": "plug_and_play",
"vendor_routing": "plug_and_play",
"po_visibility": "plug_and_play",
"inbound_consolidation": "auto_bundled",
"inventory_positioning": "plug_and_play",
"packaging_intelligence": "plug_and_play",
"retail_replenishment": "auto_bundled",
"delivery_promise": "plug_and_play",
"drayage_port": "auto_bundled",
"freight_autopilot": "plug_and_play",
"returns": "inactive"
},
"systemConnections": [
{
"system": "shopify",
"status": "csv_available",
"notes": ""
},
{
"system": "netsuite",
"status": "api_planned",
"notes": ""
},
{
"system": "shipstation",
"status": "not_connected",
"notes": ""
},
{
"system": "easypost",
"status": "not_connected",
"notes": ""
}
],
"integrationMethod": "csv_upload",
"decisionMode": "recommend_and_request_approval"
}ModuleActivation
A single module’s activation mode.
{
"module": "fulfillment",
"mode": "plug_and_play",
"activatedAt": "2026-05-13T11:39:43.149Z"
}SystemConnection
Existing systems Warp plugs into.
{
"system": "shopify",
"integrationMethod": "csv_upload",
"status": "pending_connection",
"requiredScopes": [
"orders.read",
"inventory.read"
]
}IntegrationMethod
How Warp connects to the systems already in place.
{
"method": "csv_upload",
"activeForSystems": [
"shopify",
"netsuite",
"shipstation",
"easypost"
]
}DecisionMode
How much execution authority Warp holds.
{
"mode": "recommend_and_request_approval",
"appliesToModules": [
"fulfillment",
"vendor_routing",
"po_visibility",
"inbound_consolidation",
"inventory_positioning",
"packaging_intelligence",
"retail_replenishment",
"delivery_promise",
"drayage_port",
"freight_autopilot"
]
}AutoBundledConfiguration
The set of modules Warp will operate end-to-end.
{
"modules": [
"inbound_consolidation",
"retail_replenishment",
"drayage_port"
],
"decisionMode": "recommend_and_request_approval",
"integrationMethod": "csv_upload"
}PlugAndPlayConfiguration
The set of modules Warp plugs into existing systems.
{
"modules": [
"fulfillment",
"vendor_routing",
"po_visibility",
"inventory_positioning",
"packaging_intelligence",
"delivery_promise",
"freight_autopilot"
],
"existingSystems": [
"shopify",
"netsuite",
"shipstation",
"easypost"
],
"integrationMethod": "csv_upload"
}LaunchMotionRecommendation
The safest first move based on the submitted blueprint.
{
"name": "Fulfillment auto bundled with Warp",
"recommendedAction": "Activate the fulfillment module as auto bundled with Warp: Warp receives, stores, picks, packs, ships, and manages exceptions.",
"expectedImpact": "Single contract covers fulfillment plus the freight legs already chosen.",
"confidence": "high",
"requiresCustomerApproval": false
}VendorRoutingGuideProfile
Vendor compliance state.
Routing guide adoption, label and ASN compliance, pallet and carton rules, appointment behavior.
{
"vendorsFollowRoutingGuide": false,
"vendorsShipOnCustomerAccount": false,
"vendorsUseRequiredLabels": true,
"vendorsSendAsns": false,
"vendorsFollowPalletRules": true,
"vendorsFollowCartonRules": false,
"vendorsBookAppointmentsCorrectly": false,
"vendorsConsolidateShipments": false,
"wantsWarpToGenerateRoutingGuide": true
}VendorComplianceRisk
A vendor compliance scorecard you can act on.
{
"vendorComplianceScore": 2,
"totalChecks": 6,
"riskLevel": "high",
"wantsRoutingGuide": true
}PurchaseOrderVisibilityProfile
How early Warp sees POs and what they carry.
PO source, lead time, and content fields (SKU, origin, ship date, delivery date, case and pallet count, vendor contact).
{
"canWarpReceivePoData": true,
"poSource": "shopify",
"poLeadTimeDays": 10,
"poIncludesSku": true,
"poIncludesOrigin": true,
"poIncludesShipDate": true,
"poIncludesDeliveryDate": true,
"poIncludesCaseCount": true,
"poIncludesPalletCount": false,
"poIncludesVendorContact": true
}PurchaseOrderSignal
A single PO event used for upstream capacity planning.
{
"poNumber": "PO-2026-04-0142",
"poSource": "shopify",
"leadTimeDays": 10,
"skuLineCount": 14,
"requestedShipDate": "2026-05-20",
"requestedDeliveryDate": "2026-05-27",
"originType": "vendor",
"palletCountForecast": 8,
"triggeredCapacityReservation": true
}InboundConsolidationProfile
Consolidation preferences and thresholds.
{
"multipleVendorsSameDestination": true,
"vendorsShipSmallLtl": true,
"wantsConsolidationRecommendations": true,
"minPalletsForConsolidation": 6,
"maxDelayForConsolidationHours": 48,
"preferredConsolidationRegions": [
"west_coast"
],
"wantsPooledInbound": true
}PackagingIntelligenceProfile
What you know about packaging, and what you want Warp to flag.
{
"knowsCartonDimsForAllSkus": false,
"knowsParcelDimWeightImpact": false,
"knowsDamageRateBySku": false,
"knowsFreightClassBySku": false,
"usesBrandedPackaging": true,
"usesCustomBoxes": false,
"wantsPackagingRecommendations": true,
"wantsDimWeightFlags": true,
"wantsDamageRiskFlags": true,
"wantsPalletDensityFlags": true
}RetailReplenishmentProfile
Retail compliance, replenishment cadence, and routing preferences.
{
"shipsToStores": false,
"shipsToRetailers": true,
"shipsWholesale": true,
"shipsByStoreCluster": false,
"hasRetailerComplianceWindows": true,
"needsDeliveryAppointments": true,
"needsLiftgate": true,
"needsInsideDelivery": false,
"needsCartonScanVisibility": true,
"needsStoreSpecificLabeling": true,
"wantsReplenishmentCadence": true,
"wantsPoolDistribution": true,
"wantsStoreClusterRouting": false
}DeliveryPromiseProfile
How promises get set today, and what Warp can shape.
{
"showsDeliveryPromises": true,
"whoSetsPromises": "Shopify default rates today",
"promiseSource": "shopify",
"wantsSaferPromises": true,
"wantsCheaperPromises": false,
"wantsFasterPromises": true,
"adjustByInventoryLocation": true,
"adjustByModeAvailability": true,
"adjustByCutoffTime": true,
"escalateWhenAtRisk": true
}DeliveryPromiseDecision
A single promise decision, with the inputs that shaped it.
{
"orderId": "ORD-2026-05-13-001923",
"customerPromise": "Arrives by Thu May 21",
"promiseSource": "shopify",
"inventoryLocationConsidered": true,
"modeAvailabilityConsidered": true,
"cutoffConsidered": true,
"decision": "standard_promise_safe",
"fallbackPromise": "Arrives by Fri May 22",
"riskLevel": "low",
"escalateOnRisk": true
}UpstreamRecommendation
Recommendations generated from upstream control data.
{
"type": "vendor_compliance_risk",
"category": "upstream_control",
"name": "Vendor compliance risk",
"noticed": "4 of 6 vendor compliance checks failing today across labels, ASNs, pallet rules, carton rules, and appointments.",
"recommendedAction": "Issue a Warp vendor routing guide with required labels, ASN format, pallet and carton standards, and appointment SLAs. Score vendor compliance on every inbound.",
"expectedImpact": "Cleaner receiving, fewer chargebacks, fewer dock surprises.",
"confidence": "high",
"requiresCustomerApproval": true,
"dataFields": [
"upstreamControl.vendorRouting"
],
"nextStep": "Generate vendor routing guide template and compliance scorecard."
}ImportProfile
Where inventory enters the country.
Regions, ports, container counts, load type, and the operational pain points that make port arrival a decision point.
{
"imports": "yes",
"primaryImportRegions": [
"china",
"vietnam"
],
"primaryPorts": [
"la",
"long_beach"
],
"averageContainersPerMonth": 6,
"containerTypes": [
"40ft",
"40ft_hc"
],
"containerLoadType": "floor_loaded",
"painPoints": [
"demurrage_fees",
"warehouse_congestion",
"no_visibility",
"fragmented_moves"
]
}ContainerProfile
Container shape, volume, and ports of entry.
{
"averageContainersPerMonth": 6,
"containerTypes": [
"40ft",
"40ft_hc"
],
"loadType": "floor_loaded",
"portsOfEntry": [
"la",
"long_beach"
]
}DrayageWorkflow
How containers move from port to fulfillment.
Transload, cross-dock, overflow, demurrage and detention exposure, and what Warp is asked to orchestrate.
{
"usesDrayageProviders": true,
"usesTransload": false,
"splitsContainersByDestination": false,
"directContainersToFulfillment": true,
"usesCrossDocksAfterPort": false,
"usesOverflowYards": false,
"experiencesDemurrage": true,
"experiencesDetention": true,
"needsPortAppointmentScheduling": true,
"needsLiveContainerVisibility": true
}PortArrivalEvent
Container arrival as a decision point.
Each event carries free-until clocks, drayage status, and the routing decision (store, cross dock, regional split, direct replenishment, overflow yard).
{
"containerNumber": "MEDU-7392418",
"port": "la",
"arrivedAt": "2026-05-13T08:14:00.000Z",
"freeUntil": "2026-05-17T08:14:00.000Z",
"status": "available",
"drayageProvider": "Warp Drayage",
"destinationDecision": "cross_dock",
"containerSize": "40ft",
"loadType": "floor_loaded"
}TransloadRecommendation
When floor-loaded containers should transload at port.
{
"type": "container_transload",
"category": "port_orchestration",
"name": "Container transload recommendation",
"noticed": "Inbound containers arrive floor loaded; floor loaded containers add receiving labor and damage exposure.",
"recommendedAction": "Transload at a port-adjacent cross-dock: depalletize, label, and pallet-build before the cross-country leg.",
"expectedImpact": "Lower devanning labor at fulfillment, faster put-away, and far fewer damaged units.",
"confidence": "high",
"requiresCustomerApproval": true,
"dataFields": [
"imports.containerLoadType",
"imports.averageContainersPerMonth"
],
"nextStep": "Quote a transload SOP for the next inbound container."
}RegionalSplitRecommendation
Split inventory by region at the port.
{
"type": "regional_inventory_split",
"category": "port_orchestration",
"name": "Regional inventory split recommendation",
"noticed": "Demand sits in west_coast, southwest but containers land in one place. Splitting at the port avoids a second cross-country leg later.",
"recommendedAction": "Split each container into regional inventory paths the moment it clears customs. Stage closer to where demand actually lives.",
"expectedImpact": "Faster delivery to the priority region, lower zone freight on outbound, fewer stockouts in peak zones.",
"confidence": "high",
"requiresCustomerApproval": true,
"dataFields": [
"drayage.needsRegionalSplitAfterImport",
"inventoryPositioning.demandConcentrated",
"imports.imports"
],
"nextStep": "Build a regional split plan against the next 90 days of POs."
}StorageBypassRecommendation
Containers that should never touch fulfillment storage.
{
"type": "port_cross_dock_bypass",
"category": "port_orchestration",
"name": "Port to cross-dock bypass opportunity",
"noticed": "Containers move directly into storage today, even when outbound demand is immediate.",
"recommendedAction": "Route eligible containers through a Warp port cross-dock straight to outbound legs without ever staging in fulfillment storage.",
"expectedImpact": "Removes a full receive-store-pick cycle per bypass container; product reaches the customer faster.",
"confidence": "high",
"requiresCustomerApproval": true,
"dataFields": [
"drayage.directContainersToFulfillment",
"drayage.needsBypassStorageAfterImport"
],
"nextStep": "Define bypass eligibility rules by SKU and destination."
}PortRiskAssessment
Demurrage, detention, congestion, and receiving accuracy at a glance.
{
"demurrageRisk": "high",
"detentionRisk": "high",
"portCongestionRisk": "high",
"warehouseBottleneckRisk": "high",
"receivingAccuracyRisk": "medium",
"fragmentedMovesFlag": true,
"activePortOrchestrationOpportunities": 12
}VendorFragmentationProfile
How fragmented the inbound base is.
Vendor count, whether vendors ship separately, the implied small-shipment count, and a fragmentation level the consolidation engine uses.
{
"averageVendorCount": 5,
"vendorsShipSeparately": true,
"smallShipmentCount": 5,
"fragmentationLevel": "moderate"
}InboundConsolidationRecommendation
When fragmented inbound becomes one coordinated wave.
{
"type": "container_consolidation",
"category": "port_orchestration",
"name": "Container consolidation opportunity",
"noticed": "Imports average 6 containers per month, with multiple destinations or vendors.",
"recommendedAction": "Consolidate vendor cartons into mixed-SKU containers at origin; deconsolidate at a transload close to demand.",
"expectedImpact": "Lower per-unit landed cost and a much cleaner inbound wave.",
"confidence": "medium",
"requiresCustomerApproval": true,
"dataFields": [
"imports.averageContainersPerMonth",
"imports.primaryImportRegions"
],
"nextStep": "Run a consolidation model against the next PO window."
}CrossDockBypassRecommendation
When eligible inventory skips storage entirely.
{
"type": "port_cross_dock_bypass",
"category": "port_orchestration",
"name": "Port to cross-dock bypass opportunity",
"noticed": "Containers move directly into storage today, even when outbound demand is immediate.",
"recommendedAction": "Route eligible containers through a Warp port cross-dock straight to outbound legs without ever staging in fulfillment storage.",
"expectedImpact": "Removes a full receive-store-pick cycle per bypass container; product reaches the customer faster.",
"confidence": "high",
"requiresCustomerApproval": true,
"dataFields": [
"drayage.directContainersToFulfillment",
"drayage.needsBypassStorageAfterImport"
],
"nextStep": "Define bypass eligibility rules by SKU and destination."
}InboundTransportProfile
Transport intelligence before fulfillment.
Origin type, inbound mode, cadence, vendor count, dock requirements, cross-dock bypass eligibility, storage bypass, damage and ASN reality.
{
"originType": "vendor",
"inboundMode": "ltl",
"inboundCadence": "weekly",
"averageVendorCount": 5,
"vendorsShipSeparately": true,
"needsCrossDockBypass": true,
"needsStorageBypass": true
}InventoryPositioningProfile
Where demand lives vs where inventory lives.
{
"demandConcentrated": true,
"topDemandRegions": [
"west_coast",
"southwest"
],
"currentInventoryStrategy": "single_warehouse"
}TransportBeforeFulfillmentRecommendation
Inbound consolidation, cross-dock bypass, forward placement, dock coordination.
[
{
"type": "inbound_consolidation",
"name": "Inbound consolidation opportunity",
"expectedImpact": "Lower per-unit inbound cost, fewer receiving touches, fewer dock appointments, cleaner ASN flow.",
"requiresCustomerApproval": true
},
{
"type": "vendor_routing_guide",
"name": "Vendor routing guide opportunity",
"expectedImpact": "Reduces fragmented inbound, improves ASN quality, and pulls inbound onto Warp tender visibility.",
"requiresCustomerApproval": true
}
]AutopilotRule
Policy-controlled execution.
Each rule carries the customer permission (“recommend_only”, “autopilot_with_rules”, “never_automate”, “ask_each_time”) and the thresholds that bound the decision.
{
"key": "route_heavy_off_parcel",
"label": "Route heavy or oversized items away from parcel",
"mode": "autopilot_with_rules",
"thresholds": {
"maxParcelWeightLb": 70,
"maxParcelLengthIn": 36
}
}DecisionLogEntry
Every order decision, logged with its reason.
Each entry carries the available modes, the chosen mode, the rule that fired, and the cost, speed, and risk impact relative to the alternatives. Approval state shows whether the decision ran on autopilot or needed a human.
Sample data. Generated from the preview blueprint above. Live decision logs flow once a blueprint is connected to active orders.
| Timestamp | Order | SKU | Promise | Chosen mode | Why | Cost | Speed | Risk | Rule | Approval |
|---|---|---|---|---|---|---|---|---|---|---|
| 2026-05-12 15:30:00Z | ORD--17500 | NS-CSP-01 | Order by 1pm PT, ships same day | Parcel LTLFTLCargo vanBox truckBig and bulkyB2B | Standard order; cheapest eligible mode under approved rules. | Lowest eligible cost. | On standard delivery promise. | Standard. | cheapest-eligible-mode-v1 | Auto |
| 2026-05-12 15:03:00Z | ORD--17499 | NS-SB-20 | 2-day delivery, signature optional | LTL ParcelFTLCargo vanBox truckBig and bulkyB2B | Standard order; cheapest eligible mode under approved rules. | Lowest eligible cost. | On standard delivery promise. | Standard. | fastest-eligible-mode-v1 | Auto |
| 2026-05-12 14:36:00Z | ORD--17498 | NS-TL-01 | Standard 5-day delivery | Cargo van ParcelLTLFTLBox truckBig and bulkyB2B | Trail Lantern is fragile; cargo van keeps it on a single touch for local delivery. | Higher per-order than parcel; offsets damage cost. | Same-day eligible. | Lower damage risk. | lowest-damage-path-v1 | Auto |