1 Implementation Overview

The purpose of this document is to provide administration tasks and integration information for Oracle Retail Collect and Receive Foundation Cloud Service.

This cloud service provides premier delivery options, bringing together Oracle’s industry IP and cloud infrastructure with Uber’s extensive network of drivers and cutting-edge logistics technology to offer reliable and cost-effective same-day delivery services. Whether bookings are taken on the website, contact center, or in the retail store, Collect and Receive facilitates the booking of the Uber courier for the delivery of the package to the consumer or for pickup up of a return from the consumer to deliver to the drop off location. Same Day Delivery and Same Day Returns transform the Omnichannel experience by providing businesses with a fast, efficient, and cost-effective way to meet customers’ growing demand for faster delivery options.

Collect and Receive Technical Overview

Collect and Receive is a cloud native solution leveraging the most recent and advanced technologies used in Oracle Cloud applications architecture including Autonomous Database. 

Collect and Receive is a Java-based application deployed on Oracle Cloud Infrastructure. The application is deployed in a highly available, high performance, scalable architecture.

Key technical features include the following:

• Browser-based User Interface for scheduling and managing deliveries 

• Application APIs for external systems

• Same Day Delivery services using Uber's Delivery as a Service (DaaS) API

• OAuth 2.0 based authentication via Oracle Cloud Infrastructure Identity and Access Management (OCI IAM)

• Internal Job Scheduler

• Event-driven webhook notifications to receive near real-time deliver status notifications

Collect and Receive Functional Integration

The diagrams below provide a sample functional overview for how Collect and Receive integrates with other systems. These diagrams highlight just one example of how these journeys can be architected, though there are other possible journeys and touch point considerations to craft the desired customer experience. The first diagram illustrates a Same Day Delivery journey (Store to Customer) and the second illustrates a Returns journey (Customer to Store). The accompanying explanations are written from a system-to-system perspective, noting steps in the process and the movement of data associated with those steps.

Figure 1-1 Functional Integration — Store to Customer

Store to Customer (Same Day Delivery)

Use Case: Customer purchases via Website for Same Day Delivery, fulfilled from nearby Store

1. Customer browses items on the Website and adds them to the cart.

2. Website checks item availability and fulfillment rules with Order Management System.

3. Order Management System determines the nearest fulfillment location to the Customer.

4. Website displays the fulfillment options, including Same Day Delivery.

5. Customer selects Same Day Delivery.

6. Website calls Collect and Receive, which calls Uber, to check eligibility of delivery between Store and Customer locations.

7. Eligibility is confirmed to the Customer.

8. Customer places the order.

9. Website books order with the Order Management System, which includes fulfillment type.

10. Order Management System creates the order.

11. Point of Sale System requests orders to fulfill from Order Management System.

12. Point of Sale System notifies Store Associates of Same Day Delivery orders.

13. Store Associate picks and packs the order.

14. Point of Sale System calls Collect and Receive, which calls Uber, to book the delivery.

15. Delivery is created successfully.

16. Uber dispatches Courier to Store to pick up the order and then deliver to the Customer.

17. Customer receives delivery.

Figure 1-2 Functional Integration — Customer to Store (Returns)

Customer to Store (Returns)

Use Case: Customer initiates request for Return Authorization (RA) via Website

1. Customer initiates request for a Return Authorization for their order on the Website.

2. Website calls the Order Management System to get back the eligible return items on the order.

3. Item(s) eligible for return are displayed on the Website to the Customer.

4. Customer selects item(s) to return and elects for a Courier to pick up their return item(s).

5. Website requests a Return Authorization to be created by the Order Management System.

6. Order Management System creates the Return Authorization and determines the Store nearest to the Customer’s address.

7. Order Management System calls Collect and Receive, which calls Uber, to check eligibility of a delivery between the Customer and Store locations.

8. Eligibility is confirmed and the Website offers the option to schedule a courier to pick up the return items.

9. Customer schedules a courier pickup.

10. The Website calls the Order Management System, which calls Collect and Receive, which calls Uber to book the return pickup.

11. Returns pickup is confirmed. Confirmation displays on Website to the Customer.

12. Uber dispatches Courier to the Customer to pick up the Returns and then deliver to the Store.

13. On receipt, the Store Associate scans the package label (Delivery ID) at the Point of Sale to look up the Return Authorization and order.

14. The Point of Sale System calls the Order Management System to request the Return Authorization details.

15. The Point of Sale System displays the Return Authorization details to the Store Associate.

16. Store Associate confirms receipt of return item(s) into Point of Sale.

17. The Point of Sale System sends a message to the Order Management System that the Return Authorization items have been received.

18. Customer receives confirmation of processed return.