Eshopbox now supports

Previously, bulk label generation attempted to create labels only with the . If label generation failed, the shipment was marked as failed without trying any alternate courier.

With this update, Eshopbox will whenever the recommended courier fails, improving label generation success without any manual intervention.

We’ve redesigned the support experience to make raising and tracking issues faster and more convenient.

Open the support widget from anywhere in your Eshopbox workspace. You no longer need to navigate to a separate help console to raise or track tickets.

Find support requests using an or . You don’t need to remember or save a separate Ticket ID.

Select from the order actions. Relevant order and shipment details will be prefilled automatically, reducing manual effort and helping our support team investigate faster.

Don’t want to type a detailed explanation? Use voice input to describe the issue, and it will automatically be converted into text.

The improved support widget keeps help closer to where you work—so you can raise issues faster, provide better context, and track resolutions more easily.

Eshopbox now enables smart bulk dispute creation directly from the “Raise Dispute” of weight discrepancy.

When you initiate a dispute, the system automatically evaluates weight discrepancies having similar SKUs and allows you to raise disputes for multiple weight discrepancies in a single action, instead of submitting them individually.

Delivery timelines may sometimes change after an order has been shipped. In such cases, you did not always have clear visibility into the updated delivery date and the reason behind the change. This could lead to customer confusion, increased support queries, and avoidable escalations.

To improve transparency and delivery communication, Eshopbox has enhanced how revised delivery dates are managed and displayed.

Eshopbox now automatically detects and handles orders that are fulfilled outside Eshopbox (for example, via another 3PL or fulfillment system). Such orders are marked as Externally Fulfilled, ensuring that they are not processed again within Eshopbox.

🎯

🛑 Automatically stops orders already fulfilled outside Eshopbox

⚡ No need to manually hold or manage such orders

🔍 Easily identify externally fulfilled orders using filters

📊 Ensures clean separation between Eshopbox and external fulfillment.

When a return was created via the , it was sometimes appearing in status.

However, the expected behavior is that API-created returns should move to status.

This mismatch caused confusion in tracking and return workflow visibility.

This issue has now been resolved.

Returns created via the Wrapper API will now correctly reflect in status, ensuring accurate status tracking and alignment with the return pickup flow.

Earlier, the Rate Calculator was displaying even when the selected route (pickup and drop pincode combination) was .

This created confusion, as Prime charges were visible for routes where the service was unavailable.

This issue has been resolved.

Eshopbox Prime charges will now be shown

This ensures accurate rate visibility and eliminates confusion during shipping cost estimation.

We’ve improved how business details are captured and validated during KYC to make the process more reliable and reduce errors that previously impacted downstream process.

Eshopbox now shows . You can view the applicable shipping cost before completing the order, ensuring clear cost awareness during processing.

Eshopbox now allows you to directly from the workspace for . You can configure , control what appears on labels, and add branding elements such as your .

Once configured, these settings are automatically applied to all eligible Eshopbox Shipping orders