Project

General

Profile

Edit Copy Actions

Feature #11354

open

Return process for online orders

Added by Yalavarthi Thriveni 16 days ago. Updated 10 days ago.

Status:
Feedback
Priority:
High
Start date:
10/07/2026
Due date:
% Done:

90%

Estimated time:
Spent time:

Add

Subtasks


Add

Related issues

Updated by Teja Sriram Sangani 15 days ago

  • % Done changed from 0 to 10

- Conducted an end-to-end review of the FedEx shipping integration and identified gaps in multi-tenant caching, residential routing, customs handling, cancellation, and webhook security.
- Implemented multi-tenant FedEx OAuth token caching using client ID, account number, and base URL to prevent token conflicts across tenants.
- Added automatic FedEx service resolution between FEDEX_GROUND and GROUND_HOME_DELIVERY based on delivery address and added international customs support with weight conversion and commodity declarations.
- Implemented and verified FedEx shipment cancellation and strengthened webhook HMAC signature validation using the raw request body with Base64 and Hex support.
- Enhanced multi-package order tracking and the Dropper Dashboard with parcel-level statuses, tracking timelines, carrier filters, and live carrier tracking.
- Added 4×6 label preview/printing, parcel status simulation, and customer Email/SMS notification triggers to support end-to-end FedEx sandbox testing.

Updated by Teja Sriram Sangani 14 days ago

  • Status changed from New to In Progress
  • Start date changed from 10/06/2026 to 10/07/2026
  • % Done changed from 10 to 40

- Enhanced the Dropper Manifest to display complete customer shipping addresses, recipient names, and phone numbers in a multi-line format.
- Validated dynamic shipping rate calculations based on dimensional weight, actual weight, packaging type, and sender/recipient ZIP codes.
- Designed the Return and Replacement (RMA) workflow to support refunds, replacements, exchanges, and store credits.
- Updated backend return request and order schemas to manage replacement details, return shipping methods, and item disposition statuses.
- Implemented automatic replacement order creation with original shipping details, zero-dollar payment handling, and warehouse fulfillment integration.
- Implemented return inventory disposition logic to restock sellable items and record damaged or scrapped items without affecting available inventory.
- Updated the customer return request modal with Free Replacement and Cash Refund options and dynamic pricing summaries.
- Enhanced customer order details with return/replacement actions, linked replacement order information, return label downloads, and replacement status indicators.
- Fixed FedEx Sandbox tracking fallback issues and implemented multi-package order status synchronization while preserving existing tracking statuses and manual events.
- Integrated return and replacement requests into the customer tracking screen and continued preparing the admin workflow for replacement approvals, return label handling, and inbound inventory disposition.

Updated by Teja Sriram Sangani 13 days ago

  • % Done changed from 40 to 60

- Implemented the merchant/admin return and replacement tracking portal with dynamic status timelines, replacement approval options, return waiver functionality, and inbound item inspection.
- Added return item disposition options to restock products into inventory or scrap/discard damaged items, along with return type filters, KPI cards, and parent-to-replacement order navigation.
- Enhanced backend return management APIs with resolution type filtering, aggregation metrics, and automatic disposition handling.
- Integrated replacement orders into the Warehouse Dropper and Packer dashboards with replacement badges, parent order references, and replacement-specific filters.
- Updated thermal 4×6 shipping labels with the “REPLACEMENT ORDER - NO CHARGE (WARRANTY)” banner for warranty replacement shipments.
- Automated carrier handoff processing to update linked RMA status, record replacement tracking numbers and carrier details, and send shipment notification emails to customers.
- Streamlined warehouse role responsibilities by separating order assignment, picking, packing, shipping label generation, and carrier handoff operations across the respective dashboards.
- Implemented automatic email notifications and persistent in-app reminders for Warehouse Managers when new customer orders arrive, including order details and direct navigation links.
- Restored real-time header notification bell updates using the merch-alerts API and Socket.IO, and enforced role-based notifications so new orders are visible only to Warehouse Managers and Admins while floor workers receive alerts for their assigned tasks.
- Successfully validated the frontend production build using npm run build with zero compilation errors and prepared the next development task for FedEx reverse logistics and return shipping label generation.

Updated by Teja Sriram Sangani 10 days ago

  • % Done changed from 60 to 80
  • Implemented FedEx reverse logistics integration to support return shipments from customers to the designated warehouse, including shipment creation and return tracking.
  • Developed return shipping label generation functionality for approved RMAs, supporting FedEx 4×6 thermal labels with shipment details, tracking numbers, and return addresses.
  • Integrated FedEx return rate calculation APIs to estimate return shipping costs based on package weight, dimensions, origin, and destination.
  • Automated reverse shipment tracking updates to synchronize carrier statuses with RMA records and provide real-time visibility into returned shipments.
  • Added customer email notifications for return label generation, pickup scheduling, in-transit updates, and successful delivery to the warehouse.
  • Implemented error handling and sandbox testing for FedEx return shipment creation, label generation, tracking synchronization, and failed shipment requests.

Updated by Teja Sriram Sangani 10 days ago

  • Status changed from In Progress to Feedback
  • % Done changed from 80 to 90

- Fixed the return request validation error by making the `returnShippingMethod` field dynamic in the backend RMA model

Edit Copy Actions

Also available in: Atom PDF