🚛 How to Prevent Duplicate Listings on Central Dispatch

(Cronetic + CD Integration Workflow Guide)

Why This Matters

Central Dispatch counts every new listing toward your Tier usage. If a listing is removed and recreated, CD interprets this as a brand-new posting. This can inflate Tier usage and create duplicates.

The key: Use “Repost” instead of “Remove” whenever you want to refresh or update a load.

---

1. Load Creation & Dispatch Flow

(See diagram below)

Cronetic only creates a listing under two conditions:

1. When a new load is posted to the load board.

2. When a load is dispatched and no active listing exists.

---

2. Correct vs Incorrect Workflows

✅ Correct Workflow (Preserves Tier Count)

• Step 1: Post to Load Board → creates a listing.

• Step 2: Need to update or refresh? → Use Repost (updates existing listing).

• Step 3: Dispatch → assigns existing listing to the carrier.

Result:

• No duplicate entries.

• Tier usage does not increase.

• Listing ID remains the same.

---

❌ Incorrect Workflow (Inflates Tier Count)

• Step 1: Post to Load Board → creates a listing.

• Step 2: Remove the listing.

• Step 3: Dispatch again → system doesn’t detect an active listing, so it creates a new one.

Result:

• CD counts it as a new posting.

• Tier usage increases unnecessarily.

• Appears as duplicate activity.

---

3. Side-by-Side Example

Action	Repost Workflow	Remove Workflow
Post Load	Listing created (Tier +1)	Listing created (Tier +1)
Update Load	Repost updates existing listing (Tier +0)	Remove deletes listing (Tier stays same, but no listing exists)
Dispatch Load	Existing listing assigned (Tier +0)	New listing created (Tier +1)
Total Tier Impact	1	2

---

4. Best Practices

• Use Repost, not Remove, when you want to refresh or update a load.

• Only Remove if the load is fully canceled.

• When dispatching:

  • If a listing exists → Cronetic assigns it to the carrier.

  • If no listing exists → Cronetic creates a new one.

---

5. Compliance Note

Cronetic is built to align with Central Dispatch’s policies. Listings are only generated when:

• A user explicitly posts a new load, or

• A dispatch occurs without an active listing.

By following the Repost Workflow, your team will:

• Avoid duplicate entries,

• Prevent inflated Tier usage, and

• Stay compliant with Central Dispatch standards.
  
  
  
  Contact [e-mail] if you have any questions, comments or concerns.