Automate Logistics: Zoho, Porter & SRC Integration

Project Title: Logistics API Integration with Porter, SRC & Zoho Inventory

Objective:
Automate the logistics and shipment tracking process between Zoho, SRC, and Porter Logistics API, ensuring seamless pickup scheduling, document handling, and error-based escalation.

Part-A: Porter Integration
1) Scope of Work
A) Trigger Conditions –
• Sales Order reference number does not contain “OC” & “TM”.
• Customer name is not “Recruiter Bdesir”.
• Distance between pickup and delivery pin-codes ≤ 120 km
• Appointment Date is not empty. (Shipment section under Inventory (ZOHO Inventory).

B) Porter API Pickup Automation –
• Schedule pickup at 9:30 AM on the Appointment Date.
• Pickup category: 3-wheeler only
• API request sent to Porter Logistics per their latest API Contract also check every 5 min whether trip is active/live it should stop if order status is “delivered”.

C) Data Sync and Pull from Porter –
• Tracking Number (CRN Number -It should be the last one referring to a successful delivery)
• Tracking Link
• POD Link
• Courier Partner Name should be update as “Porter”.
• Tracking Status (Real time) (Open, Accepted, Live, Ended, Cancelled as per Porter API)

D) Proof of Delivery & Escalation Logic –
• 11:30 AM Alert: If status ≠ “In Transit” and Appointment Date is today.
• 6:00 PM Alert: If status is 'Delivered' and 'POD Missing' at after 5 PM - Create Issue in Zoho Projects.


Part-B: ShipRocket Cargo Integration
1) Scope of Work
A) Trigger Conditions –
• Sales Order reference number does not contain “OC” & “TM”.
• Customer name is not “Recruiter Bdesir”.
• First Priority will be given to “Movin” if not serviceable then “Delhivery”.
• Order status on Maven should be “WH-Packed”.

B) Push to SRC –
• Box Quantity Calculation: 1 Box = 300 units (rounded up)
• Push “From” and “To” address and generate one LR and multiple AWB depending on the number of boxes to be shipped.
• Create E-Way bill in ZOHO Inventory basis selected transporter in SRC.
• Merge and push a single PDF to SRC from ZOHO Invoice attachments.
• Push E-way bill pdf to SRC.


C) Update to/from SRC –
• Push Appointment date from ZOHO Shipments to SRC (check every 2 min driven by webhook).
• Pull Shipment status/Tracking URL/Tracking No./Courier Partner Name from SRC to ZOHO Shipments. (check every 2 min driven by webhook).
• Pull proof of delivery (POD) pdf file from SRC to ZOHO Shipments attachment section


D) Proof of Delivery & Escalation Logic –
• 09:00 AM Alert: If status ≠ “Reached at Destination” and Appointment Date < 48 hours.
• 6:00 PM Alert: If status is 'Delivered' and 'POD Missing' after 24 hours –
• Status should be “Out for Delivery” at 11:00 AM on the Appointment Date.
• Create Issue in Zoho Projects.

2) Technical Implementation –
• Platform: Porter/Zoho Projects/Shiprocket Cargo/ Zoho Inventory/ZOHO Flow
• Integrations: - Porter API, SRC API, Zoho Inventory/ZOHO Projects/ZOHO Flow
• Error Alerts: Zoho Inventory Scheduler or Workflow triggers