Skip to content
Heatwave Docs

Spee-Dee Daily Manifest Runbook

Audience: US warehouse / logistics team. Frequency: once per shipping day, end of day, before the Spee-Dee driver pickup. Why: the Manifest Report is the Driver’s Copy Shipping Summary the Spee-Dee driver signs off on for what they are picking up, and Spee-Dee uses it for billing. It is required — Hunter Boelz (Spee-Dee IT) confirmed (2026-07-02) that even once WarmlyYours books all shipments through the API, the daily manifest must still be produced and printed from the ShipIt portal.

Source: Spee-Dee’s “Generate Daily Manifest Report” instructions (Scribe guide, 2026-07-02). This runbook mirrors those steps.

Steps

Section titled “Steps”
  1. Log in to the ShipIt portal: https://speedee.dsapp.io/Account/Login (shared account speedee@warmlyyours.com; credentials in 1Password → the “Speedee Dsapp - speedee@warmlyyours.com” entry).
  2. Click My Orders.
  3. Click Generate Report.
  4. In the report dropdown, select Manifest (not Label / Order Details / Order Export).
  5. Click the date selector in the top right (the Pickup Date field).
  6. Change the date to the shipping date you want to print (i.e. today’s pickup date).
  7. Click Preview to generate the report. It may take a few seconds to pull and compile the day’s shipment data.
  8. Click the printer icon in the top bar to open the browser print dialog. Select the paper printer and print at minimum the 1st page (the summary sheet) for the driver.

What the report shows

Section titled “What the report shows”

The Driver’s Copy Shipping Summary totals the day’s pickup: Regular and Metro shipments (zone / pieces / weight / charges), plus Additional Charges broken out — C.O.D., A.O.D., Hazardous, Oversized, DAS, Unboxed — EZR labels, consignee and stop counts, and the summary barcode / QR the driver scans. The accessorials we book via the API (AOD Direct, Declared Value, Oversized, Unboxed — see the migration task doc) roll up into these totals.

Automation status — what we can and cannot do

Section titled “Automation status — what we can and cannot do”

The manifest is a manual portal step; it is NOT automatable via the Integration API today. The Spee-Dee Integration API (the same one behind Shipping::SpeedeeDispatchScienceClient) exposes order, quote, label, tracking, and subscription endpoints but no manifest / report-generation endpoint (verified against the OpenAPI spec, 2026-07-02). So there is no API call that produces or retrieves this driver summary — it must be generated and printed from the portal by a person.

What this means for our code, by phase:

  • Phase 1 (rating only): no change. Shipments still go out via the legacy path, and the existing automated CSV-over-FTP manifest (app/models/speedee_manifest_shipment.rb, app/services/shipping/speedee_manifest_generator.rb) continues to run.
  • Phase 2 (full API shipping): once orders are created through the API, the portal manifest replaces the legacy FTP manifest — the driver summary is generated from the API-created orders in the portal, so our CSV-over-FTP transmission is no longer the manifest of record. At cutover we must reconcile the two: retire (or stop relying on) the FTP manifest path and make this manual portal print the official end-of-day step.

What we can implement to support the manual step (phase-2 scope, not built yet): an end-of-day operational reminder/checklist in our own CRM/warehouse flow that prompts the team to run this runbook (there is no way to pre-fill or trigger the portal report from our side — the reminder is the extent of what the API allows us to automate). Track this under the migration task doc’s phase-2 plan.

See doc/tasks/202607011617_SPEEDEE_DISPATCH_SCIENCE_MIGRATION.md for the overall migration context.