Build the carrier handoff from one warehouse
Start the run from the warehouse already in context
Create Scan Forms does not ask operators to rebuild a package list. It sends the selected warehouse, assigns the next team-wide run number, and opens the generated record while discovery begins.
The run list keeps its number, generated name, status, creator, date, child-form count, and View Scan Form Run action visible.
Scan Form runs
Current warehouse: Dallas Fulfillment Center. Create opens the generated run while package discovery starts.
| Number | Name | Status | Created At | Created By | Scan Forms |
|---|---|---|---|---|---|
| #SF-1042 | Dallas Fulfillment Center / Apr 30, 2026 | Pending | Apr 30, 2026 | Jordan Lee | 0 |
| #SF-1041 | Dallas Fulfillment Center / Apr 29, 2026 | Completed | Apr 29, 2026 | Maya Chen | 4 |
| #SF-1040 | Dallas Fulfillment Center / Apr 28, 2026 | Partially Completed | Apr 28, 2026 | Jordan Lee | 3 |
#SF-1042
Discovering packages to manifest… The create action uses the selected warehouse and opens the generated run.
Find today’s shipped work, then split it where the carrier account or client changes
The warehouse timezone sets the start of the day. Cybership considers packages from that warehouse that have shipped, remain unmanifested, include a shipping label, and have no refund state.
Each unique carrier integration, client or self-fulfilling team, and carrier becomes its own child Scan Form. That keeps credentials and ownership from crossing provider submissions.
Find the eligible package set
Dallas Fulfillment Center · America/Chicago
Warehouse
Dallas Fulfillment Center
Package belongs to the warehouse that started the run
Shipped
Since local midnight
The warehouse timezone defines the start of today
Manifest
Not yet manifested
The package has no manifested timestamp
Label
Present · no refund state
A shipping label exists and refund status is empty
Separate credential and ownership boundaries
Three keys determine which packages can share one provider submission.
- 01
Carrier integration
Keeps provider credentials together
- 02
Client or fulfiller
Uses the client team, or the fulfiller for self-fulfillment
- 03
Carrier
Keeps each carrier submission separate
Create one child form per provider group
Each child carries one integration, one owning team, and one carrier.
Northline / USPS / USPS / 86 packages
USPS credentials · Northline · USPS
Northline / Easy Post / UPS / 51 packages
Easy Post credentials · Northline · UPS
Ridgeline / Easy Post / USPS / 27 packages
Easy Post credentials · Ridgeline · USPS
Keep every child outcome on the run
Each provider request finishes independently. A stored document remains available as View Scan Form, and a later failure can keep its error beside that same link.
When at least one child fails after processing, the run is Partially Completed instead of hiding stored form links or presenting the whole handoff as complete.
Scan Forms
Each child keeps any stored form link and any processing error.
| Name | Outcome |
|---|---|
| Northline / USPS / USPS / 86 packages | Created View Scan Form |
| Northline / Easy Post / UPS / 51 packages | Created View Scan Form |
| Ridgeline / Easy Post / USPS / 27 packages | Failed View Scan FormNetwork timeout |
3
child forms finished
3
documents returned
1
processing error retained
Print every stored form without losing the failed row
After the child requests reach final states, Cybership merges every non-empty stored form URL into one run PDF. A failed child can still contribute its retained link.
Operators can open the merged PDF for the carrier handoff and still see the processing error that followed one stored document.
#SF-1042
Returned form URLs available from one run
Northline / USPS / USPS / 86 packages
Carrier form PDF · included
Northline / Easy Post / UPS / 51 packages
Carrier form PDF · included
Ridgeline / Easy Post / USPS / 27 packages
Carrier form PDF · included
Merged run PDF
3 stored form URLs ready to open and print
Ridgeline / Easy Post / USPS / 27 packages
The stored form remains included; the later processing error remains on the run.
Link and error retained together
Leave the pickup with one record to return to
The merged handoff remains connected to the warehouse run and the child rows that produced it, including any processing error that still needs attention.
- Run detail
- Individual form links
- Merged PDF
- Processing errors
- What stays on the run?
- Its warehouse, creator, date, child-form count, and final status—plus any stored form link and any processing error for each child.
- What enters the merged PDF?
- Every non-empty stored form URL after the children finish processing. Form availability and final child status are separate, so a failed child’s retained link can still enter the merge.
- What can the operator open?
- The run itself, each available View Scan Form link, and View Merged PDF. The current run detail does not expose a retry action.
Trusted by 3PLs and brands
See it in your operation
Bring us the carrier handoff your team still assembles across portals
Show us how today’s shipped packages become pickup paperwork. We’ll map the warehouse boundary, provider groups, stored forms, and failure record against your actual carrier workflow.
No sales call is required to get sandbox access.
Continue exploring
Related workflows
Bulk Ship
Shipping
Group matching orders, pick combined SKU totals, reuse one multi-package plan, and generate the batch’s labels together.
Gaylords
Shipping
Create carrier-specific outbound containers, load labels from desktop or either mobile scan path, then close and export package-item detail.
Shipment Insights
Analytics
Keep one warehouse and filter scope across carrier services, delivery trends, destination-state results, and shipment follow-up.
Shipping Labels
Shipping
Find any purchased or uploaded label, then inspect its package, scan state, carrier movement, decision, and supported actions.