Feature Requests

Hi Team, This is regarding an ongoing issue that is causing significant discrepancies across multiple processes. We are observing that shipments are being created even after an order has already been dispatched from the warehouse and subsequently cancelled in-transit. A new shipment gets generated for the same order, which then gets stuck in Flex due to a duplicate tracking ID error. In such cases: The original shipment reflects “Return on the way” in the workspace The newly created shipment shows “Processing” or “Ready to Ship” Since the order has already been dispatched against the original tracking ID, the system rightfully flags the new shipment as duplicate. Additionally, in cases where a shipment contains multiple items and one item is cancelled during in-transit, the system is following an RTS cancellation flow, which is not operationally feasible. As both items are packed in a single shipment, partial delivery is not possible, leading to further discrepancies. Key Issues: Operational Blockage in Picklist Processing If one shipment in the picklist faces an issue, the entire process gets blocked. Even after applying temporary fixes via support tickets, discrepancies persist. In some cases, this has resulted in duplicate deliveries, as orders already dispatched are processed again under a new shipment ID. Incorrect Status Handling Orders marked via temporary fixes as RTO are getting restocked under a different shipment ID. Meanwhile, the original dispatched shipment reflects “customer cancellation” with a putaway option, creating further confusion. Suggestion / Recommendation: A new shipment should not be created if the order is already: Dispatched in Flex Marked as “handover done” in the workspace Instead, the system should follow the RTO flow for such cases. Additionally, we suggest evaluating whether it is feasible to fetch pickup/handover status from Flipkart API, to ensure: Once the shipment is handed over to the courier, no new shipment is created The shipment is correctly processed through the Return (RTO) lifecycle This will help eliminate duplicate shipments, prevent operational delays, and ensure process accuracy. Please review this and let us know if the proposed solution is feasible or if any alternative approach can be implemented to address these issues.

Hi Team, Nykaa Marketplace is introducing Tagloop for their orders. Which will enhance accurate deliveries and avoid any fraud by customer. They are constantly asking for confirmation on tagloop. Please what we can do in this scenario.

Dear team, We have been facing recurring challenges in tracking denied orders, making it difficult to identify the actual reasons for denials from the courier’s end. This has been causing unnecessary confusion for both our team and the brands, as we currently have to share manual remarks against denied orders on a daily basis. To streamline this process and improve visibility, we would like to propose the following enhancements: Add a “Reason for Denial” Column: This column should allow warehouse teams to mark a reason whenever a shipment is denied. Common predefined options can include: NSZ (Non-Serviceable Zone) AWB Not Existing Shipment Showing as Cancelled During Scan Tracking ID Not Assigned Others – with a mandatory remarks field for specific details. These reasons should be visible on the workspace as the “Reason for Failed Handover.” This feature will bring greater transparency and reduce daily follow-ups or confusion regarding pending or denied shipments. Enable Bulk Sidelining of Orders: Allow the warehouse team to select multiple tracking IDs with similar reasons and mark them as sidelined in one go, against each manifest. This will significantly reduce manual effort and processing time. We believe that implementing these improvements will greatly enhance operational efficiency and provide clearer visibility to both internal teams and brand partners. Please advise if these requirements can be taken forward for development. @Mayur Karwa sir, Please suggest.

better pickup service and train your staff to better served

Hi Team, Objective: Implement a system that automatically cancels unfulfilled orders meeting the following criteria, to improve order management and customer experience. Scope: Applies to orders in unfulfilled status for more than 48 hours. Includes orders marked as: Out of Stock Pin Code Not Serviceable Business Rules: If an order remains in the unfulfilled state for 48 hours from creation, and the reason is either Out of Stock or Pin Code Not Serviceable, the system should automatically cancel the order. Brand - Benetton

Virtual KIT Sales & Sales return posting in ERP is not getting posted for Being Human. They want us to make discount & price available in API at component level for which attached is the requirement, check & confirm on feasibility with ETA.

Auto-Sync of Order Cancellations from Eshopbox to Unicommerce Brand: Portronics Reported by: Portronics Team Date: [Insert Date] Current Scenario When an order is cancelled on Eshopbox, the cancellation is not reflected on Unicommerce. This results in the need to manually cancel the same order in Unicommerce, which is time-consuming and leads to redundant efforts and operational inefficiency. Current System Limitation As per existing behavior: Eshopbox does not support pushing cancellation events to Unicommerce. There is no sync mechanism between the two systems for order status updates, specifically cancellations. Proposed Requirement To improve operational efficiency and reduce manual intervention, the following functionality is proposed: Feature Requirement Implement a provision in the integration where order cancellations initiated on Eshopbox are automatically synced to Unicommerce. The cancellation status should be updated in real-time or near real-time on Unicommerce once the order is cancelled on Eshopbox.

We propose introducing an option that allows brands to manually put an order on hold directly from the Eshopbox workspace. This functionality would empower operations, support, and order management teams to temporarily pause order processing under specific scenarios — without needing backend intervention or raising support tickets.

The system should ensure that the latest error message is always updated and displayed in the Workspace and Process All Orders tab. If an initial error (e.g., product verification issue) is resolved and a new error occurs (e.g., pincode not serviceable while generating the label), the latest error should be reflected in the interface. The error message should dynamically update to provide real-time visibility of the current issue. Reference Bug Id - https://auperator.atlassian.net/browse/BUGS-20763

We would like to request the addition of a feature to mark internal remarks/comments in orders under the "Take Action" tab , these remarks should be downloadable in the Sales Order Report. This feature is essential for us to add and track key comments related to orders, helping us analyze the order journey performance on average basis and refer to historical data for better insights. It will significantly improve our ability to monitor and optimize operations. Please let us know if this can be implemented and the expected timeline.