APPLYING CLAIMS IN SHIPFAST (VELOCITY DASHBOARD) SOP

Created by Level 2, Modified on Thu, 8 Jan at 6:12 PM by Level 2

Aggregator: Shipfast

Portal: https://dashboard.velocity.in/
Department: Operations / Logistics


Purpose: Raise forward & return claims correctly with zero rework

Claim Types in Ship fast (NON-NEGOTIABLE)

Ship fast has TWO main claim flows. Choose correctly or the claim will be rejected.

A. Forward Claim

Used when the issue happens before delivery to customer

Examples:

  • Lost in transit (Forward)
  • Damaged before delivery
  • Shipment not delivered but marked delivered

? Login Email: contact@bluetyga.com

B. Return Claim

Used when the issue happens after delivery attempt

Return claims are of TWO sub-types:

  1. RTO (Return to Origin)
    • Customer refused / undelivered
    • Returned item is damaged / wrong / missing
  2. Customer Return
    • Customer initiated return after delivery
    • Returned item damaged / used / missing

Login Email: retun@bluetyga.in

Do NOT use forward login for return claims or vice versa

This is the #1 reason Ship fast silently rejects claims.

  2️ Login Rules (STRICT)

Portal Login

  1. Open: https://dashboard.velocity.in/
  2. Click Login
  3. Use area-specific email ID only

Claim Type

Login Email

Forward Claim

contact@bluetyga.com

Return / RTO Claim

retun@bluetyga.in

Never raise:

  • Forward claim from return email
  • Return claim from contact email

Ship fast tracks this internally.



2 SOP – RETURN CLAIM (RTO / CUSTOMER RETURN)

Step 1: Login

  • Login using retun@bluetyga.in

Step 2: Go to Support

  • Click Support
  • Select Raise Ticket / Claim

Step 3: Select Return Claim Type

Choose Return Shipment Issue

Then choose:

  • RTO Claim → undelivered return
  • Customer Return Claim → post-delivery return

Do NOT mix these.

Step 4: Enter Return Details

Mandatory:

  • Return AWB
  • Order ID
  • RTO / Return received date
  • Product value

Step 5: Issue Selection (VERY IMPORTANT)

Choose one:

  • Other Product
  • Missing
  • Damaged
  • Lost

Issue must exactly match QC finding.

Step 6: Upload Proof (MANDATORY)

Upload:

  • Outer packet images
  • Inner packet images
  • Product images
  • Damage / mismatch close-up
  • Invoice

Best practice: upload Google Drive link if multiple files.

Step 7: Submit Claim

  • Submit ticket
  • Note down Ticket ID
  • Mark claim as OPEN in tracker

Post-Submission Process (Must Follow)

Day

Action

Day 0

Claim raised

Day 3

First follow-up via portal

Day 7

Escalation

Day 10+

Final follow-up / closure


No follow-up = delayed pay-out.


                          SOP – FORWARD CLAIM (Step by Step)

Step 1: Login


Step 2: Navigate to Support

  • Click Support

  • Select Raise Ticket / Claim


Step 3: Select Claim Category

Choose Forward Shipment Issue

Then select correct issue:

  • Lost in transit

  • Damaged in transit

  • Not delivered but marked delivered

⚠️ Choose ONE issue only.


Step 4: Enter Shipment Details

Mandatory:

  • AWB Number

  • Order ID

  • Product value (invoice value only)


Step 5: Upload Proof

Upload:

  • Invoice copy

  • Product images (if applicable)

  • Any internal proof

❌ No proof = no claim.


Step 6: Submit & Record

  • Submit ticket

  • Copy Ticket ID

  • Update internal claim tracker

4  Internal Recording (MANDATORY)

Immediately update Claim Master Sheet with:

  • Ticket ID
  • Claim type (Forward / RTO / Customer Return)
  • Proof link
  • Submission date
  • Current status

One AWB = One claim row only.

Common Mistakes (DO NOT REPEAT)

Using wrong login email
Raising RTO under forward claim
Missing QC images
Claim value higher than invoice
Late submission (after SLA)

Any one of these = valid rejection.

Control Checklist (Before Clicking Submit)

  • Correct login email?
  • Correct claim type selected?
  • QC completed within 24 hrs?
  • Proof uploaded and clear?
  • Invoice attached?

If all YES, submit.
If even one NO, STOP.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article