CROP
ProjectsDelivery Services

CROP Delivery Services - Stakeholder Documentation

Welcome to the CROP Delivery Services documentation. This documentation is designed for business stakeholders, managers, and decision-makers who need to...

CROP Delivery Services - Stakeholder Documentation

Welcome to the CROP Delivery Services documentation. This documentation is designed for business stakeholders, managers, and decision-makers who need to understand the capabilities, value, and business impact of the delivery service platform.

Documentation Overview

This documentation package provides comprehensive information about the CROP Delivery Services platform:

Quick Start

What is CROP Delivery Services?

CROP Delivery Services is a unified delivery management platform that integrates multiple shipping providers (UPS and Clinton Tractor) into a single, easy-to-use API. It enables businesses to:

  • Get shipping rates from multiple providers instantly
  • Create and manage shipments across different carriers
  • Track packages in real-time
  • Validate delivery addresses automatically
  • Access advanced shipping features (pickup scheduling, location finder, etc.)

Key Benefits:

Unified Interface - One API for multiple delivery providers
Cost Optimization - Compare rates across providers automatically
Real-Time Tracking - Automatic updates on shipment status
Flexible Options - Choose from standard, express, or premium delivery
Automated Workflows - Reduce manual work with automated processes

Who Should Read This Documentation?

  • Business Owners - Understand the strategic value and capabilities
  • Operations Managers - Learn about operational benefits and workflows
  • E-commerce Teams - Discover how to integrate shipping into your platform
  • Customer Service - Understand tracking and shipment management features
  • Decision Makers - Evaluate the platform for your business needs

Getting Started

Start with the Overview to understand the platform at a high level, then explore specific topics based on your role and interests.


For technical implementation details, please refer to the main README.md file in the project root.

On this page