Shipment Completion Automated Workflow

What Is Shipment Completion Automation?

Shipment Completion Automation eliminates manual completion tasks by triggering automatic actions based on real-world shipment events. Instead of checking every shipment manually, you define conditions like "complete when package is opened" or "complete when shipment reaches destination," and the system handles the rest.

Why Automation Matters

Before Automation:

• Team members manually checked and marked shipments as complete

• Delays in completion affected downstream reporting

• Human error sometimes marked shipments as complete prematurely

• No standardized completion criteria across shipment lanes

With Automation:

• Shipments auto-complete when business logic is satisfied

• Instant completion reflects real-world events (delivery, opening, etc.)

• Consistent rules applied across all shipments

• Reduced manual workload

Who Should Use This?

Any organization that:

• Manages high-volume shipments with predictable completion events

• Wants to reduce manual data entry

• Needs consistent completion criteria across shipment lanes

• Uses device sensors (light, temperature, etc.) for package monitoring

Main Concepts

Triggers: Events that can initiate a workflow action

• Shipment State Change — Triggered when shipment moves to a specific state (e.g., "At Destination" or "Delivered")

• Light Sensor — Triggered when package is opened or light is detected

Nodes: Points in a workflow where actions or decisions occur

• Trigger nodes — Detect events (State Change or Light Sensor)

• Action nodes — Complete the shipment or perform other operations

• Delay nodes — Wait a specified time before proceeding (e.g., 24 hours)

Lanes: Groupings of shipments with shared rules

• Workflows are configured per lane

• Each lane can have different completion criteria

• Example lanes: "Domestic Ground," "International Air," "Cold Chain"

Pre-Built Templates

Workflow Builder v1.2 includes three pre-built templates for common scenarios:

Template 1: Light Sensor → Completion

Use When: You want to auto-complete shipments upon package opening

Workflow:

1. Light Sensor detects package opening

2. Shipment automatically completes

3. Notification sent to team

Best For: Samples, perishables, time-sensitive shipments

Template 2: State Change → Light Sensor Check (with 24hr Fallback)

Use When: You want confirmation that a package was opened after delivery, with a safety timeout

Workflow:

1. Shipment enters "Delivered" state

2. System waits for Light Sensor trigger

3. If light detected within 24 hours → Shipment completes (package opened)

4. If 24 hours pass without light → Shipment auto-completes anyway (fallback)

Best For: High-value shipments, samples requiring signature confirmation

Main Workflow: Creating a Shipment Completion Automation

Step 1: Navigate to Workflow Builder

1. Go to Settings or Administration

2. Click Workflow Builder

3. Select Shipment Completion Automation or Create New Workflow

Step 2: Choose Your Lane

1. Select the shipment lane you want to configure (e.g., "Domestic Ground")

2. If this is your first workflow for this lane, start with a template

Step 3: Select a Template (or Build Custom)

1. Click on a template that matches your requirements

2. Or click Custom Workflow to build from scratch

Step 4: Configure Trigger Values

1. Each trigger node shows user-configured values by default

2. Click the node to edit

Step 5: Set Optional Delays

1. If your template includes a delay node (like the 24-hour example):

2. Click the delay node to set duration

Step 6: Review and Activate

1. Review your complete workflow diagram

2. Verify all trigger and action nodes

3. Click Activate Workflow or Save & Enable

4. The workflow is now active for this lane

Node Configuration Display

When you open a workflow, all nodes show their configured values immediately:

You don't need to click each node to see the configuration — it's visible in the node label itself.

Workflow History and Monitoring

Viewing Workflow Runs

1. Open the workflow in Workflow Builder

2. Click History or Workflow Runs

3. A table shows all executions of this workflow

Workflow Run Status

Dynamic Run Duration

• Running workflows display elapsed time (e.g., "Running for 2 hours 15 minutes")

• Completed workflows show total duration (e.g., "Completed in 47 seconds")

• This helps you verify workflows are executing on expected timelines

Tips and Best Practices

• Start with templates — Pre-built templates are battle-tested; customize only if needed

• Test on one lane first — Deploy to a low-volume lane first to verify behavior

• Monitor history regularly — Check workflow history weekly to ensure triggers are firing as expected

• Set realistic timeouts — If using delays, factor in carrier transit times and weekends

• Define clear lane criteria — Each lane should have a single, well-defined purpose

• Document your triggers — Note why each trigger was chosen; it helps when troubleshooting later

• Adjust sensitivity carefully — If using Light Sensor, test sensitivity settings in a staging environment first

Troubleshooting Workflows

Advanced: Custom Workflows

If the three templates don't meet your needs:

1. Click Create Custom Workflow

2. Drag and drop trigger, delay, and action nodes

3. Connect nodes in sequence

4. Configure each node with your specific values

5. Save and activate

Custom workflows support:

• Multiple triggers in parallel (e.g., "Light OR State Change")

• Conditional branching (e.g., "If light AND temperature > 25°C, then complete")

• Multiple actions per workflow

• Nested delays and retry logic

Permissions & Access Control

Contact your administrator if you need workflow creation rights.

Need Help?

• How do I know if a workflow triggered? — Check Workflow History; look for entries matching your shipment IDs and dates

• Can I run a workflow manually? — Templates don't support manual triggering; set a custom workflow with a manual trigger if needed

• What if I deactivate a workflow? — Active shipments aren't affected; only new shipments skip that workflow

• Can I use multiple workflows on one lane? — Yes; they execute in parallel if conditions are met

• How long does workflow history keep data? — History is retained for 12 months; contact your administrator for archival options

Summary

Shipment Completion Automation removes manual completion tasks by automatically marking shipments as complete based on real-world events. Pre-built templates, real-time workflow monitoring, and clear node configuration make deployment fast and reliable.

Deploy your first workflow in minutes, monitor progress in the Workflow History table, and enjoy reduced manual workload while maintaining consistent completion criteria across all shipment lanes.