What is a Shipping Request?

A Shipping Request in Pipe17 represents the actionable instruction to fulfill an order. Once an order has been validated and routed, a Shipping Request tells a fulfillment location or partner (such as a 3PL, warehouse, or internal distribution center) what to ship, where to ship it, and when.

It acts as the bridge between an order and its fulfillment, ensuring that each line item is assigned to the correct fulfillment source based on business rules, inventory availability, and location setup.

Shipping Requests are automatically created and managed by the app’s Order Routing Engine and are essential to maintaining operational accuracy across multiple sales and fulfillment channels.


How Shipping Requests Work

When an order is received into Pipe17, either from a connected sales channel or via API, it goes through several automated steps before fulfillment begins:

  1. Order Routing: The Order Routing Engine evaluates each order against routing rules you’ve defined (e.g., location proximity, inventory availability, order type, or sales channel).
  2. Shipping Request Creation: Once a routing decision is made, Pipe17 automatically generates a Shipping Request for the designated fulfillment location.
  3. Fulfillment Handoff: The Shipping Request is sent to your connected fulfillment system (3PL, WMS, or in-house warehouse) via a built-in or custom connector.
  4. Fulfillment Updates: As the fulfillment partner processes the shipment, status updates flow back into Pipe17: tracking numbers, carrier details, and fulfillment confirmations are all synced in real time.

Each Shipping Request contains detailed information, including:

  • Destination address
  • Order reference and line items
  • Fulfillment location
  • Shipping method and carrier preferences
  • Tracking and package information

Why Shipping Requests Matter

Shipping Requests are the operational link that allows Pipe17 to:

  • Split or combine orders across multiple fulfillment centers.
  • Ensure inventory is reserved and decremented at the correct source.
  • Maintain synchronization between your sales channels, warehouses, and carriers.
  • Provide real-time visibility into fulfillment progress and exceptions.

For eCommerce retailers, brands, and 3PLs, Shipping Requests eliminate manual handoffs, reduce errors, and ensure on-time and accurate delivery.


Example Scenario

A customer places a three-item order on Shopify:

  • Item A and Item B are available in your East Coast warehouse.
  • Item C is stocked only in your West Coast warehouse.

Pipe17’s routing logic automatically creates:

  • Shipping Request 1: For the East Coast warehouse (Items A & B).
  • Shipping Request 2: For the West Coast warehouse (Item C).

Each fulfillment partner receives only the relevant line items, ensuring both warehouses act independently while Pipe17 maintains full visibility into the order’s complete lifecycle.


Relationship to Other Objects

Object Relationship to Shipping Request Purpose
Order Parent object that triggers one or more Shipping Requests Defines what needs to be fulfilled
Fulfillment Resulting record once the shipment is processed Tracks shipment details, carrier, and delivery status
Inventory Determines routing and fulfillment eligibility Ensures products are available at assigned locations
Exception Flags issues during the fulfillment process Enables proactive resolution before customer impact

This relationship structure makes Shipping Requests central to the Commerce Data Model, ensuring all fulfillment data flows cleanly between systems and stays consistent across your network.


Troubleshooting

If a Shipping Request does not appear or is not updating as expected:


Need Help?

If you need additional assistance:

We're here to help you succeed with your operations.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.

Have more questions?
Submit a request
Share it, if you like it.