The brief
Enterprise gifting campaigns meant five spreadsheets, three vendor calls, and a guarantee of something going wrong at peak. A company managing hundreds of bulk orders a month needed a single platform that could handle catalogue, cart, bulk checkout, personalisation, and real-time tracking without breaking down when a campaign went large.
Managing at volume
Wraptree's team was managing hundreds of bulk orders a month across disconnected systems. Catalogue data lived in spreadsheets. Shipping was coordinated manually. Personalisation requests arrived by email. Every peak period exposed a different failure point, and order errors were costing the business refunds and client trust.
The failure pattern during peak periods was consistent and costly. A corporate client would place an order for 200 branded gift boxes, each going to a different recipient address, with individual name cards. That single order would touch five internal tools, three email threads, and two members of staff over several hours. When something went wrong, which it did regularly, the error was often discovered at dispatch, too late to fix without expediting a replacement at Wraptree's expense. One bad peak week could erase weeks of margin.
What we built
We built Wraptree end to end: a centralised catalogue with filters and bulk selection, a checkout built for corporate card payments and multi-recipient shipping, real-time order tracking for buyers, and an admin dashboard that gives the Wraptree team full visibility over inventory, dispatch, and analytics. The stack is React, Node, and MongoDB, deployed on a serverless architecture that scales automatically under load.
The decision to go serverless was driven directly by the load profile. Wraptree's demand is not evenly distributed across the year. It spikes hard around Q4, product launches, and company milestones. Provisioning fixed infrastructure to handle those spikes would mean paying for idle capacity for most of the year. Serverless functions scale on demand and cost nothing when idle, which matched the business model exactly. The architecture handles burst traffic without any manual intervention from the Wraptree team.
MongoDB was chosen because the data model for corporate gifting is genuinely document-shaped. A single order can have dozens of recipient records, each with its own address, personalisation fields, and dispatch status. Trying to normalise that into a relational schema adds join complexity without any meaningful benefit. The document model let us store and query orders in the shape the business actually uses them, which simplified both the API and the admin interface.
The bulk checkout was the most technically complex part of the build. Corporate buyers needed to upload recipient lists, assign personalisation at scale, apply a single corporate card charge across the full order, and still get per-recipient tracking links they could forward to gift receivers. We built a recipient import flow that validates addresses inline, flags errors before payment, and generates individual dispatch records from a single checkout action. What used to take hours of email back and forth now takes minutes inside the platform.
The admin dashboard gave Wraptree visibility they had never had before. They can now see inventory levels in real time, view dispatch queues by date and courier, track which orders are pending personalisation versus ready to ship, and pull weekly analytics on order volume, revenue, and error rates. Before the platform, that information was scattered across inboxes, courier portals, and supplier spreadsheets. Now it lives in one place and updates automatically as orders move through the workflow.
The outcome
The 10x capacity figure was validated during a controlled load test before go-live. We simulated peak order volumes at ten times the historical maximum and measured response times, error rates, and database performance under sustained load. The platform held without degradation. In production, Wraptree has since processed peak days that would have been operationally impossible under their previous system, without adding headcount or changing any process.
Wraptree is now in a position to take on corporate accounts they previously would have declined. Large enterprise clients with standing quarterly gift programmes, accounts requiring white-label order portals, and international recipients with complex shipping requirements are all within operational reach. The platform removed the ceiling that manual coordination had placed on the business, and the team is using that capacity to grow.
