What is an Order?

An order in Pipe17 represents a confirmed purchase transaction captured from a selling channel such as Shopify, Amazon, or BigCommerce. It acts as the core record that connects commerce, fulfillment, and financial operations across your connected systems. Each order includes details such as line items, quantities, prices, shipping addresses, payment information, and the channel source that originated it.

Pipe17 treats orders as dynamic operational objects—not static records. This means an order evolves as it moves through your connected network, updating automatically based on fulfillment, shipment, and return activities received from your 3PLs, WMS, or ERP systems.


Order Structure

Orders are part of Pipe17’s Commerce Data Model, which provides a single, consistent schema for all entities (e.g., orders, products, inventory, fulfillments, returns). This ensures error-free handoffs and synchronized data across channels and systems.

Each order object contains key relationships with:

  • Products and inventory – SKUs, bundles, and stock levels tied to the transaction.
  • Fulfillment and shipping requests – the actions that move goods to customers.
  • Returns and exchanges – post-fulfillment activities tied to customer satisfaction.
  • Settlements – financial reconciliation with selling channels or partners.

Order Lifecycle in Pipe17

An order’s lifecycle reflects the real-world process from capture to delivery and reconciliation. The major stages include:

  1. Order Creation – Orders are imported from sales channels via managed connectors or APIs.
  2. Order Validation – The Automation Engine verifies address, quantity, and line-item data; applies holds or rules as needed.
  3. Routing – The Order Routing Engine evaluates business rules to select the optimal fulfillment location(s).
  4. Fulfillment – Shipping requests are generated and sent to fulfillment partners or warehouses.
  5. Status Updates – Real-time tracking and status changes (e.g., Ready for Fulfillment, Sent to Fulfillment, Partially Fulfilled, Fulfilled).
  6. Closure or Exception Handling – Orders are closed, archived, or flagged for review depending on fulfillment outcomes.

Check the order lifecycle overview here.


Why Orders Matter

Orders form the operational heartbeat of your business. Through Pipe17’s Order Operations Platform, every order triggers a series of automated workflows that ensure:

  • Real-time visibility into order progress and fulfillment status.
  • Intelligent routing and exception detection.
  • Synchronization across sales, fulfillment, and financial systems.
  • Consistency of data across multiple channels and back-office applications.

This unified approach helps ecommerce retailers, brands, and 3PLs reduce manual effort, eliminate data discrepancies, and accelerate fulfillment.


Troubleshooting

If an order does not appear or behaves unexpectedly:

  • Confirm that the selling channel connector is active and authenticated.
  • Check the Order Details Page in the app for status and routing errors.
  • Review any active automation rules or holds applied to the order.
  • Verify that your fulfillment partner has acknowledged the shipping request.

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.