Starshipit
Carry orders through dispatch

Build Starshipit fulfillment workflows that prepare orders, verify labels, and follow shipment exceptions. Validate destination, package, and customs details before dispatch work begins. Create approved labels and manifests with exact order and shipment identifiers.

Yes. Start with a mission such as 'Build the dispatch readiness desk'. SPIRITT builds the application, source mappings, validation, and operations queue around the connected account. Use carrier tracking events and warehouse evidence to keep delivery exceptions moving.

SPIRITT retrieves each approved Starshipit order before creating its labels, records the returned shipment and tracking identifiers, and inspects the label files against the order manifest. Because label creation is irreversible, uncertain results go to reconciliation rather than an automatic repeat. The warehouse receives only the verified batch; later carrier progress is checked through tracking records, not inferred from a printed label.

Connect Shopify to supply fulfillment orders, Google Drive to archive verified label files and manifest PDFs from approved dispatch runs, and Slack to resolve dispatch exceptions. SPIRITT verifies each Drive file and links its ID to the order and warehouse batch. Archiving uses a separately authorized Drive connection; a missing file does not authorize creating another label or manifest.

SPIRITT creates and updates eligible orders, quotes rates, creates labels and manifests, and reads tracking and WMS data. Label creation creates shipments and can incur charges; manifesting is irreversible, and label generation does not prove carrier pickup or delivery.

Open a SPIRITT workspace, connect Starshipit, and hand over a mission such as 'Build the dispatch readiness desk'. Name the target account or records, the outcome, and the companion apps involved. Set the approved scope for changes and customer-facing actions before the workflow runs.