Shipments

In PrepFlow, a shipment is a collection of orders grouped together with defined quantities for dispatch to a specific destination or integration (e.g., FBA, WFS, FBM).

Shipments are the bridge between inventory and outbound fulfillment — they track what’s being sent, through which integration, and at what stage of completion.

What Is a Shipment?

A shipment represents a group of orders that share a common destination or integration workflow.
Each shipment contains:

• The list of orders or inventory items included
• Quantities of each item being shipped
• The assigned client
• A status (Requested, Working, or Shipped)
• A linked workflow (e.g., FBA, WFS, FBM)

Shipments act as the operational container that moves your prep center’s work from “ready to send” → “in progress” → “completed”.

How Shipments Are Created

Shipments can be created in three ways:

1. From the Inventory Page

Admins can manually create shipments using existing inventory.

• Go to Inventory
• Select the items you want to include
• Click Actions → Create Outbound Shipment
• Enter the quantities per item and optionally a shipment name
• Click Create Shipment

This method is most common for controlled, staff-created outbound workflows.

2. Automatically (via MOQ Settings)

If a client has a Minimum Order Quantity (MOQ) rule set, PrepFlow can automatically create a shipment request when the threshold is met.

For example:

If a client’s MOQ is 100 units, and their inventory reaches that amount, PrepFlow will automatically group those items into a Requested Shipment.

This helps automate recurring fulfillment cycles for clients who send predictable volume.

3. Client-Initiated (Manual Requests)

Clients can also manually request shipments directly from their dashboard.
They can select their available orders or inventory, define quantities, and submit a shipment request for your team to process.

Client-created and MOQ-created shipments both start in the Requested status.

Shipment Statuses

Each shipment progresses through a clear, three-stage lifecycle:

Requested → Working

When a shipment is first created, it sits in Requested status.
At this point:

• It’s not yet billed
• You can review or delete it if it was created in error
• The client can still unrequest or modify it

As soon as you open the shipment to start processing:

• The status automatically changes to Working
• The client is blocked from unrequesting or changing it
• The integration workflow tools become active

Working → Shipped

Once you’ve completed the shipment’s workflow — for example:

• Finished an FBA inbound plan
• Completed an FBM order

—you’ll be prompted to mark the shipment as shipped.

Doing this will:

• Move the shipment to the Shipped status
• Transfer it from Worklist → Shipments to the Outbound page
• Trigger any billing or post-shipment workflows (depending on your settings)

Where to Find Shipments

Worklist → Shipments

This is where you’ll find all active shipments:

• Requested and Working shipments appear here
• Used daily for operational management
• Allows filtering, searching, and integration-specific actions

Outbound

Once shipments are marked as Shipped, they move to the Outbound page.
This acts as your historical record of completed shipments, including:

• Shipment names
• Integration type
• Completion dates
• Linked tracking or documentation

Finishing a shipment

Once a shipment is created, you’ll proceed with the integration-specific workflow (e.g., FBA flow).

For details, see the guides for your integration in Integrations → Fulfillment Type.