Zilo created a new customer promise. Pidge created the operating layer that made it scalable. Try-and-buy fashion delivery is not a normal last-mile operation. It requires speed, rider discipline, item-level control, customer doorstep coordination, payment closure, partial acceptance handling, reverse pickup, and live visibility. For Zilo, the promise was clear: enable customers to try apparel at their doorstep within a 60-minute delivery window. But making that promise work at scale required more than riders. It required a delivery operating layer that could manage dedicated rider supply, regional deployment, order visibility, doorstep workflows, reverse movement, and operational control. That is where Pidge helped Zilo scale 60-minute try-and-buy delivery across Mumbai regions.

A 60-minute try-and-buy model needs speed and control across both delivery and reverse logistics. Zilo’s model depends on a high-touch customer experience. The customer does not simply receive an order. The customer tries the product, accepts selected items, rejects others, and completes payment only for what is accepted. This means the delivery workflow includes: Fast order movement Rider assignment Store pickup Customer doorstep coordination Product trial support Partial acceptance handling Rejected item return COD or payment closure Proof and status updates Reverse logistics visibility This makes the operating model more complex than standard ecommerce delivery. Zilo needed a partner that could support both speed and workflow discipline.

In try-and-buy fashion, speed matters only when the full doorstep workflow is completed correctly. A 60-minute delivery promise cannot be measured only by rider movement. The order must be picked, packed, assigned, delivered, tried, accepted or rejected, closed financially, and returned where required. If the rider reaches the customer but the accepted and rejected items are not captured properly, the operation is incomplete. If the rejected item return is unclear, inventory visibility suffers. If payment does not match accepted items, reconciliation becomes difficult. If the failed attempt is not genuine or properly recorded, customer experience and operational trust weaken. For Zilo, scaling delivery meant building control across the full try-and-buy journey.

Dedicated rider deployment helps high-touch delivery models maintain better control over speed, reliability, and workflow discipline. Zilo’s 60-minute try-and-buy model needed a delivery layer that could operate with consistency. Pidge supported this through a PDR-led model. This helped Zilo create more dependable execution across active regions. The operating model supported: Dedicated rider deployment Store-level pickup coordination Rider assignment Order movement visibility Customer doorstep workflow Partial acceptance support Reverse pickup handling COD and payment workflow support Operational monitoring Regional scale-up For a specialized fashion delivery model, this kind of dedicated operating control becomes important. It helps reduce dependency on fragmented delivery coordination.

Try-and-buy delivery becomes scalable when the operating layer can support growth without losing workflow control. Zilo’s delivery scale grew from around 70 orders per day to 600–700 orders per day. This growth was not only about adding delivery capacity. It required a system that could support more orders, more riders, more regions, more customer interactions, and more reverse movement. As order volume increased, the operation needed better visibility into: Active orders Rider assignment Pickup status Delivery progress Partial acceptance cases Rejected item movement Failed attempts COD and payment closure Regional performance Exception cases Scaling try-and-buy delivery requires every part of the operation to remain visible and accountable.

Peak-day performance depends on rider readiness, allocation control, monitoring, and exception response. Peak days create pressure on delivery operations. For Zilo, peak execution required the network to handle high order movement without losing control over the try-and-buy workflow. During peak volume, delivery teams need to manage: Rider availability Pickup readiness Allocation speed Delivery timelines Customer coordination Doorstep trial time Reverse item handling Payment closure Failed attempt tracking Operational escalations Zilo reached a peak of 731 orders in a day. This shows the importance of a delivery operating layer that can support both volume and workflow complexity.