Business Requirements Document (BRD) for Delivery

System
4-6-2024
─

Amr Salah
Project Manager
Aman Holding
 1

Overview
This Business Requirements Document (BRD) outlines the functional and non-functional
requirements for the Delivery System. It includes detailed specifications for order
management, route optimisation, real-time tracking, notifications, reporting, and
integration with existing systems.

Goals
1. Automate Delivery Processes: Streamline and automate delivery workflows to
increase efficiency.
2. Reduce Effort and Save Time: Minimize manual interventions and optimise
processes to save time and reduce operational efforts.

Specifications

Shipping Flows

The Delivery System supports two primary shipping flows:

1. Deliver by Aman
2. Deliver by Seller

Deliver by Aman

1. Order Creation: The sales team creates or reviews an order in the Magento
backend.
2. Operation Team Actions:
○ Reject Order:
■ Action: The operation team rejects the order and provides a reason.
■ Result: The request is returned to the salesman with the rejection
reason.
○ Accept Order:
■ Action: The operation team accepts the order, changing its status to
"Processing."
 2

■ Result: A Bolesa (shipping label) is created, and a request is sent to

the seller dashboard to prepare the order within 48 hours.

Seller Actions:

● Reject Order:
○ Action: The seller rejects the order and provides a reason.
○ Result: The request is returned to the operation team with the rejection
reason.
● Accept Order:
○ Action: The seller accepts the order, changing its status to "Prepare to
Deliver" within 48 hours.
○ Result: The status is updated to "Ready to Deliver."

Operation Team Follow-Up:

● Schedule Pickup:
○ Action: The operation team schedules a pickup date and changes the status
to "Pickup Scheduled."
○ Result: Once the shipping company collects the order from the seller, the
status is updated to "Collected," and the operation team closes the shipment.

Deliver by Seller

3. Order Creation: The sales team creates an order in the Magento backend.
4. Operation Team Actions:
○ Reject Order:
■ Action: The operation team rejects the order and provides a reason.
■ Result: The request is returned to the salesman with the rejection
reason.
○ Accept Order:
■ Action: The operation team accepts the order, changing its status to
"Processing."
■ Result: The request is sent to the seller dashboard to prepare the
order within 48 hours.
○ The seller he would change the status to prepare to deliver then ready to
deliver then close it
 3

Functional Requirements
1. Order Management:
○ Ability to create, view, and manage orders in the Magento backend.
○ Track order status changes and updates.
2. Route Optimization:
○ Automate route planning to ensure timely deliveries and optimal resource
utilization.
3. Real-Time Tracking:
○ Provide real-time tracking of orders for both the operation team and
customers.
4. Notifications:
○ Automated notifications for status changes are sent to relevant stakeholders
(sales team, operation team, sellers, and customers).
5. Reporting:
○ Generate detailed reports on delivery performance, order statuses, and
operational efficiency.
6. Integration:
○ Seamless integration with existing systems, including Magento, seller
dashboards, and third-party logistics providers.

Non-Functional Requirements
1. Performance:
○ The system should handle high volumes of orders and updates without
performance degradation.
2. Reliability:
○ Ensure high availability and reliability of the delivery system to avoid
disruptions.
3. Security:
○ Implement robust security measures to protect sensitive orders and
customer information.
4. Scalability:
○ The system should be scalable to accommodate future growth in order
volume and additional functionalities.
5. Usability:
○ Provide a user-friendly interface for all stakeholders to easily interact with
the system.
 4

Assumptions and Constraints

1. The system will be built on top of the existing Magento platform.
2. Integration with third-party logistics providers will be facilitated through APIs.
3. The implementation will adhere to the project timeline

Glossary
● Bolesa: A term used within the company for a shipping label or delivery note.
● Magento: An eCommerce platform used by Aman Holding for order management.

Stakeholders
● Mohamed Nagy Mohamed
● Moataz Mahmoud
● Hager Saleh