Automate Logistics: Zoho & SRC Integration
Budget: ₹12,500 – ₹37,500 INR
Project Title: Logistics API Integration_SRC & Zoho Inventory
Objective:
Automate the logistics and shipment tracking process between Zoho, and Shiprocket Cargo API, ensuring seamless pickup scheduling, document handling, and error-based escalation.
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: Zoho Projects/Shiprocket Cargo/ Zoho Inventory/ZOHO Flow
• Integrations: - SRC API, Zoho Inventory/ZOHO Projects/ZOHO Flow
• Error Alerts: Zoho Inventory Scheduler or Workflow triggers
Objective:
Automate the logistics and shipment tracking process between Zoho, and Shiprocket Cargo API, ensuring seamless pickup scheduling, document handling, and error-based escalation.
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: Zoho Projects/Shiprocket Cargo/ Zoho Inventory/ZOHO Flow
• Integrations: - SRC API, Zoho Inventory/ZOHO Projects/ZOHO Flow
• Error Alerts: Zoho Inventory Scheduler or Workflow triggers
Related categories:
Software Architecture
CRM
Logistics
Salesforce.com
Zoho
Automation
API Integration