Feature Requests

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

Hi Team, Currently we or brand are cancelling the orders (B2C) one by one. Can we develop a new feature through which we can cancel the orders in bulk.

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.

Objective: To automate the end-to-end processing of FBA (Fulfilled by Amazon) orders by eliminating manual intervention, thereby improving efficiency, reducing errors, and accelerating order fulfillment. Current Process: FBA orders are manually created on Workspace. These orders are then manually processed for RTS (Ready to Ship) from the backend. There is no automated integration between Workspace, Eshopbox, and SAP for FBA orders. Proposed Solution: FBA orders should be automatically pushed from Workspace to Eshopbox as soon as they are created or confirmed. Eshopbox should then automatically sync these orders with the SAP system. The entire workflow should require no manual handling unless exceptions or errors are encountered.

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.

Combining multiple orders from the same customer into a single package.

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.