Skip to main content

Discharge Notifications

Container discharge events are critical milestones in the supply chain. Dockflow's automation system allows you to automatically flag containers when they're discharged at terminals, enabling immediate visibility and proactive logistics management.

Overview​

Discharge notification automation:

  • Monitors discharge events - Tracks when containers are unloaded at terminals
  • Automatically flags containers - Marks discharged containers for visibility
  • Triggers downstream actions - Enables follow-up automation and notifications
  • Provides real-time alerts - Stay informed as soon as discharge is confirmed
Common Applications
  • Alert logistics teams when containers are available for pickup
  • Trigger customs clearance processes
  • Notify warehouse teams to prepare for arrival
  • Track dwell time starting from discharge
  • Coordinate ground transportation

Understanding Discharge Events​

What is a Container Discharge?​

A container discharge occurs when:

  • A container is unloaded from a vessel at a terminal
  • The terminal registers the discharge event in their system
  • The discharge information is transmitted to Dockflow

Why Track Discharges?​

Discharge events are important because they:

  • Indicate availability - Container is physically at the destination terminal
  • Start the clock - Dwell time and demurrage periods begin
  • Enable pickup - Container can be retrieved (subject to customs/release)
  • Require action - Customs clearance, pickup coordination, delivery scheduling
Data Sources

Discharge events are detected from multiple sources:

  • Terminal APIs (most accurate, real-time)
  • Carrier data feeds (scheduled discharge times)
  • Port community systems
  • Manual entry by your team

Setting Up Discharge Notifications​

Follow these four steps to create an automation that flags containers when they're discharged at terminals.

Step 1: Create a Flag​

First, create a flag to mark discharged containers.

  1. Log in to your Dockflow account
  2. Go to Automations in the main navigation
  3. Click the Flags tab
  4. You'll see a list of existing flags

Create the Flag​

  1. Click the Create Flag button
  2. Enter flag details:
    • Name: "Discharge Event" (or your preferred name)
    • Color: Choose a color (e.g., blue for informational, orange for action required)
    • Description: "Automatically set when container is discharged at terminal"
  3. Click Save
Flag Naming Best Practices
  • Use clear, descriptive names: "Discharged at Terminal," "Arrived and Discharged," "Ready for Pickup"
  • Be specific if you have multiple discharge-related flags
  • Consider including location if you track multiple terminals differently
  • Use consistent naming conventions across all flags

Alternative flag names:

  • "Discharged - Awaiting Customs"
  • "Terminal Discharge Confirmed"
  • "Available for Pickup"
  • "Unloaded at POD"

Step 2: Build the Automation​

Create an automation rule that monitors discharge events and applies your flag.

Create New Automation​

  1. Navigate to Automations → Overview
  2. Click the Create Automation button
  3. Give your automation a descriptive name:
    • "Flag Discharged Containers"
    • "Auto-Flag on Terminal Discharge"
    • "Discharge Event Notification"

Add Trigger: Milestone Change​

  1. Click Add Trigger
  2. Select Milestone Change from the trigger types
  3. Configure the milestone:
    • Type: Notice (0 hours)
    • Milestone: Container Discharge at Terminal
  4. Click Save Trigger
Trigger Types
  • Notice (0 hours): Triggers immediately when discharge is confirmed
  • Before: Not applicable for discharge (can't predict exact discharge time)
  • After: Use if you want delayed actions (e.g., flag 2 hours after discharge)

Why use Notice type? Setting the trigger to "Notice" with 0 hours ensures the automation fires immediately upon discharge confirmation, providing real-time visibility without delay.

Configure Conditions (Optional)​

Add conditions if you want selective flagging:

Examples:

Only flag high-value shipments:

Condition: Shipment Value > $50,000

Only flag specific destinations:

Condition: Destination Port = Rotterdam

Only flag for specific customers:

Condition: Customer Name = "Acme Corporation"

Only flag reefer containers:

Condition: Container Type = Reefer
When to Use Conditions

Use conditions if:

  • You don't need to flag all discharges
  • You want different flags for different scenarios
  • You're managing high volumes and need to focus attention
  • Different teams handle different types of shipments

Omit conditions if you want to flag all discharge events universally.

Step 3: Apply the Flag Action​

Configure the automation to set your flag when the trigger fires.

Add Action Step​

  1. In the automation builder, click Add Step
  2. Select Set Flag for Container from the action types
  3. Choose your flag:
    • Select "Discharge Event" (or whatever you named your flag)
  4. Configure options:
    • Apply to: Current container
    • Remove after: Leave blank for permanent flag, or set duration
  5. Click Save Action

Optional: Add Additional Actions​

You can add multiple actions to the same automation:

Send email notification:

  1. Add Step → Send Email
  2. Select recipients (lead contact, team, specific users)
  3. Customize email template

Create task:

  1. Add Step → Create Task
  2. Assign to user or team
  3. Set due date (e.g., 24 hours after discharge)

Update field:

  1. Add Step → Update Field
  2. Select field (e.g., "Status")
  3. Set new value (e.g., "Ready for Pickup")

Chain to another automation:

  1. Add Step → Trigger Automation
  2. Select follow-up automation (e.g., customs clearance workflow)
Multi-Action Workflows

Create comprehensive workflows by chaining actions:

  1. Set flag (for visibility)
  2. Send email to logistics team
  3. Create pickup task
  4. Update status field
  5. Log activity to notes

Step 4: Activate the Automation​

Enable the automation to start monitoring discharge events.

Activate Toggle​

  1. In the automation builder, locate the activation toggle in the upper right corner
  2. Click to toggle from Inactive to Active
  3. The automation immediately begins monitoring discharge events
Test Before Activating

Before activating:

  1. Review all trigger settings
  2. Verify flag selection is correct
  3. Check any conditions you've added
  4. Confirm actions will behave as expected
  5. Consider testing with a sample shipment first

Verify Activation​

Confirm the automation is running:

  • Status shows "Active" (usually indicated by green color)
  • Toggle is in the "on" position
  • Automation appears in your active automations list

Testing Your Automation​

After activation, test to ensure proper functionality.

Manual Test​

  1. Find a test container that's approaching or at discharge
  2. Wait for discharge confirmation in Dockflow
  3. Check for the flag on the container
  4. Verify timing - Flag should appear immediately or within minutes

Check Automation Logs​

  1. Navigate to Automations → Activity Log
  2. Filter by your automation name
  3. Review:
    • Trigger events (when discharge was detected)
    • Actions taken (flag applied)
    • Any errors or failures
  4. Confirm successful execution

Verify Flag Appearance​

  1. Go to your Dashboard
  2. Find containers with the discharge flag
  3. Confirm flag appears correctly
  4. Check flag timestamp matches discharge time
Troubleshooting Failed Tests

If the automation doesn't fire:

  1. Check activation status - Ensure it's truly active
  2. Review discharge data - Confirm discharge event was registered in Dockflow
  3. Verify conditions - Ensure test container meets any condition criteria
  4. Check data sources - Terminal data may be delayed
  5. Wait longer - Some data sources have sync delays (up to 8 hours)

Configuring Notifications​

Flags provide visibility, but notifications ensure your team is actively alerted.

Enable Email Notifications​

  1. Navigate to Automations → Flags
  2. Find your "Discharge Event" flag
  3. Click Configure Notifications
  4. Select notification method:
    • Direct Email: Immediate alert for each discharge
    • Daily Report: Consolidated summary once per day
  5. Choose recipients:
    • Never: No notifications
    • Lead Contact: Notify shipment lead
    • Team: Notify entire team
    • Always: Notify specified users for every occurrence
    • Backup Contact: Fallback if no other recipient configured
  6. Click Save

Notification Delivery Methods​

Direct Email (Real-time):

  • Sent immediately when flag is set
  • Separate email for each container
  • Ideal for time-sensitive discharges requiring immediate action

Daily Report (Consolidated):

  • Single email with all flagged containers
  • Sent at specified time each day
  • Better for high-volume operations where immediate action isn't required
Choosing Delivery Method

Use Direct Email when:

  • Immediate action is required (pickup, customs clearance)
  • Low discharge volume (won't overwhelm inboxes)
  • Multiple stakeholders need separate alerts

Use Daily Report when:

  • Managing high container volumes
  • Recipients prefer summary views
  • Immediate action isn't critical
  • Reducing email noise is important

Advanced Configuration​

Multi-Tier Flagging​

Create different flags based on urgency or characteristics:

Immediate Action Required:

Flag: "Discharged - Reefer" (orange/red)
Condition: Container Type = Reefer
Notification: Direct Email to operations manager

Standard Processing:

Flag: "Discharged - Standard" (blue)
Condition: Container Type ≠ Reefer
Notification: Daily Report to logistics team

High-Value Shipments:

Flag: "Discharged - High Value" (yellow)
Condition: Shipment Value > $100,000
Notification: Direct Email to account manager + operations

Location-Specific Automations​

Create separate automations for different terminals or ports:

Rotterdam Terminal:

Automation: "Discharge - Rotterdam"
Trigger: Container Discharge at Terminal
Condition: Destination Port = Rotterdam
Flag: "Discharged - RTM"
Action: Email Rotterdam operations team

Los Angeles Terminal:

Automation: "Discharge - LA"
Trigger: Container Discharge at Terminal
Condition: Destination Port = Los Angeles
Flag: "Discharged - LA"
Action: Email LA operations team + create pickup task

Time-Based Follow-Up​

Combine discharge flags with time-based automations:

Initial discharge:

Automation: "Discharge Event"
Trigger: Container Discharge at Terminal
Action: Set flag "Discharged"

24-hour follow-up:

Automation: "Pickup Overdue"
Trigger: Time-based (24 hours after discharge)
Condition: Flag = "Discharged" AND Status ≠ "Picked Up"
Action: Set flag "Pickup Overdue" + Send escalation email

72-hour escalation:

Automation: "High Dwell Alert"
Trigger: Time-based (72 hours after discharge)
Condition: Flag = "Discharged" AND Status ≠ "Picked Up"
Action: Set flag "High Dwell - Action Required" + Email senior manager

Integration with Other Systems​

Chain discharge notifications with external actions:

Update ERP system:

Action: Webhook to ERP
Payload: Container number, discharge timestamp, location

Trigger customs broker API:

Action: API call to customs system
Payload: B/L number, discharge confirmation

Update warehouse management system:

Action: WMS notification
Data: Container number, estimated arrival at warehouse

Best Practices​

Flag Management​

  1. Clear naming - Use descriptive flag names that indicate purpose
  2. Consistent colors - Assign colors meaningfully (e.g., blue for info, orange for action needed)
  3. Regular review - Periodically audit flags to remove or archive completed ones
  4. Documentation - Maintain a flag reference guide for your team

Notification Strategy​

  1. Target appropriately - Send notifications only to those who need to act
  2. Balance frequency - Avoid notification fatigue with too many alerts
  3. Escalation paths - Define who gets notified when issues aren't resolved
  4. After-hours handling - Consider weekend/holiday notification policies

Automation Maintenance​

  1. Monitor performance - Regularly check automation logs for failures
  2. Update conditions - Adjust as business rules change
  3. Archive old automations - Deactivate and archive obsolete automations
  4. Version control - Document changes to automation logic

Integration with Workflows​

  1. Map complete process - Discharge is one step in a larger workflow
  2. Coordinate teams - Ensure all stakeholders understand their roles
  3. SLA tracking - Use discharge flags to measure performance against SLAs
  4. Continuous improvement - Analyze flag patterns to optimize operations

Troubleshooting​

Flags Not Being Set​

If discharge flags aren't appearing:

  1. Check automation status - Verify it's active, not paused
  2. Review discharge data - Confirm discharge events are being registered
  3. Test trigger conditions - Ensure containers meet condition criteria
  4. Check data sources - Terminal data may be delayed or unavailable
  5. Review automation logs - Look for errors or failed executions
  6. Verify flag still exists - Ensure flag wasn't accidentally deleted

Delayed Flag Assignment​

If flags appear later than expected:

  1. Check data sync schedule - Terminal data typically syncs every 4-8 hours
  2. Review carrier data timing - Some carriers report discharges with delay
  3. Verify trigger type - Ensure "Notice (0 hours)" is selected
  4. Check system performance - During peak times, slight delays can occur
  5. Contact support - Persistent delays may indicate integration issues

Duplicate Flags​

If the same container gets multiple discharge flags:

  1. Review automation logic - Multiple automations may be triggered
  2. Check for duplicate events - System may receive discharge confirmation multiple times
  3. Add de-duplication conditions - Use "Flag not already set" condition
  4. Audit active automations - Disable redundant discharge automations

Missing Notifications​

If flags are set but notifications aren't sent:

  1. Verify notification configuration - Check settings in Flags section
  2. Confirm recipient email addresses - Ensure contacts have valid emails
  3. Check spam filters - Notifications may be blocked
  4. Review recipient selection - Ensure appropriate option is chosen (not "Never")
  5. Test with sample - Manually assign flag to test notification delivery

Frequently Asked Questions​

Q: Can I flag discharges at specific terminals only? A: Yes, add a condition like "Terminal Name = [specific terminal]" or "Destination Port = [specific port]" to your automation.

Q: What's the difference between discharge and arrival? A: "Arrival" typically refers to the vessel arriving at port. "Discharge" is when the container is physically unloaded from the vessel. Discharge is the more actionable milestone for logistics teams.

Q: Can I automatically remove the flag after pickup? A: Yes, create a second automation:

  • Trigger: Milestone Change = "Full Gate Out POD"
  • Action: Remove Flag "Discharge Event"

Q: How quickly are discharge events detected? A: This varies by data source:

  • Terminal APIs: Real-time to 15 minutes
  • Carrier data: 1-8 hours
  • Manual entry: Immediate Most discharges are flagged within 1 hour of occurrence.

Q: Can I set different flags for discharge at different ports? A: Yes, create separate automations with location conditions and different flags for each port or terminal.

Q: Will I be notified about discharges that happened in the past? A: No, automations only trigger on events that occur after the automation is activated. Historical discharges won't generate flags or notifications.

Q: Can partners see my discharge flags? A: Only if you explicitly share the flag. By default, flags are private to your organization. See Sharing Flags with Partners for details.

Q: How many containers can be flagged simultaneously? A: There's no limit on the number of containers that can have the same flag or the number of discharge events the automation can process.

Support​

Need help setting up discharge notifications?