Fulfillment in Pipe17 represents the physical process of completing an order: picking, packing, and shipping items to the customer. It’s the final step in the order lifecycle, where the promise made at checkout becomes a delivered experience.
Fulfillments are automatically created in the app once a connected fulfillment provider (such as a 3PL, WMS, or in-house warehouse) confirms shipment data. Each fulfillment record in Pipe17 captures shipment details, ensuring your operations, sales channels, and customers stay synchronized in real time.
What is a Fulfillment?
A Fulfillment is a record that documents the successful processing of a Shipping Request. It includes essential data such as:
- Tracking number(s)
- Carrier and service type
- Shipment date and status
- Items shipped and quantities
- Warehouse or fulfillment location
- References to the related order and shipping request
In short, while a Shipping Request is an instruction to fulfill, a Fulfillment is proof that the fulfillment was completed.
Fulfillments in Pipe17 are immutable (once created, they cannot be modified), meaning once they are created, they cannot be modified. This ensures historical accuracy and compliance for audit, reporting, and customer service use cases.
How Fulfillment Works in Pipe17
The fulfillment process in Pipe17 connects all your systems to deliver a complete post-purchase experience:
- Shipping Request Sent: Once the Order Routing Engine determines the optimal fulfillment location, a Shipping Request is generated.
- Fulfillment Partner Action: The connected 3PL or warehouse system processes the shipment.
- Fulfillment Record Created: When the shipment is confirmed, Pipe17 receives fulfillment data and creates a Fulfillment record linked to the Shipping Request.
- Status Updates Synced: The fulfillment status (e.g., Shipped, Partially Fulfilled, Delivered) is updated in real time across all connected channels.
- Customer Visibility: Tracking numbers and shipment details are pushed back to your selling channels for customer notifications and order status updates.
Example Scenario
A customer orders three items through your online store. Pipe17 routes the order to your 3PL warehouse. Once the warehouse picks and ships two of the three items, the system creates a Partial Fulfillment record.
When the final item ships later that day, Pipe17 automatically adds a second Fulfillment record. The order then transitions to the Fulfilled status, with tracking information and carrier data synced back to Shopify.
Fulfillment Lifecycle States
| Status | Meaning | Triggered By |
|---|---|---|
| Pending | Fulfillment expected but not yet created | Shipping Request generated |
| Partially Fulfilled | Only some line items have shipped | Partial shipment confirmation |
| Fulfilled | All line items have shipped | Final shipment confirmation |
| Cancelled | Fulfillment was voided or returned by partner | Connector or warehouse system |
| Rejected | Fulfillment was voided or returned by partner | Connector or warehouse system |
| Delivered | Shipment delivered to customer | Carrier tracking event |
Why Fulfillment Matters
Accurate, automated fulfillment updates are critical to:
- Customer satisfaction: Provide real-time visibility and tracking.
- Operational efficiency: Eliminate manual reconciliation between sales and warehouse systems.
- Inventory accuracy: Automatically decrement stock and prevent overselling.
- Data integrity: Keep your ERP, WMS, and selling channels synchronized without duplication or delay.
Pipe17’s fulfillment automation ensures that every shipment, from warehouse to doorstep, is visible and verifiable, reducing customer support tickets and fulfillment errors.
Relationship to Other Objects
| Object | Relationship to Fulfillment | Purpose |
|---|---|---|
| Order | Parent transaction | Defines what is being fulfilled |
| Shipping Request | Precedes Fulfillment | Specifies the fulfillment instruction |
| Inventory | Updated by Fulfillment events | Adjusts stock levels accurately |
| Return | May be created after delivery | Manages reverse logistics workflows |
Together, these relationships form the post-purchase data network within Pipe17’s Commerce Data Model, ensuring that your entire fulfillment process remains transparent, accurate, and automated.
Troubleshooting
If a Fulfillment record is missing or incorrect:
- Verify the fulfillment connector (e.g., ShipBob, Logiwa, ShipHero) is connected and synced.
- Check that the Shipping Request has been successfully sent and acknowledged.
- Review the Order Details Page for any open exceptions or error messages.
- Confirm that the fulfillment partner is sending complete shipment data (including tracking numbers).
Need Help?
If you need additional assistance:
- Use Ask Pippen, our AI agent, located at the top of the app page.
- Submit a support request with as much relevant detail as possible. Learn how to submit a request.
- For urgent issues, email us directly at support@pipe17.com.
We're here to help you succeed with your operations.
Comments
0 comments