Design a Gift Wrapping & Personalization Service

Problem statement

Design a gift wrapping and personalization service that lets customers add gift-wrap packaging, handwritten-style notes, custom gift tags, and uploaded images or logos to any eligible order at checkout. The system must calculate additional fees, persist personalization data, generate print-ready instructions for the fulfillment center, and ensure the correct wrapping and note are applied to the correct item.

This is not a standalone product. It is a cross-cutting fulfillment concern that intersects with the shopping cart, checkout flow, pricing engine, order management system, warehouse management system, and the physical packing line. A gift-wrap option selected at 11:58 PM on December 23 must produce a correctly labeled box on the packing floor by 6 AM on December 24. The system must survive the holiday peak, handle personalization data that is sensitive (names, messages, sometimes images of people), and degrade gracefully when the print service or warehouse API is unavailable.

Why the problem is distinctive

A generic order system processes items by SKU. A gift-wrapping service adds a per-item or per-order overlay that changes the physical fulfillment path. The warehouse worker does not just pick and pack; they must select the correct wrap paper, print a note card, attach a tag, and verify the personalization matches the order. If the note says "Happy Birthday, Grandma Rose" and it lands on the wrong box, the customer experience is ruined and the return cost is high.

The design therefore separates order intent (what the customer selected and paid for) from fulfillment execution (what the warehouse actually does). Order intent is durable, strongly consistent, and customer-facing. Fulfillment execution is eventual, idempotent, and warehouse-facing. The bridge between them is a work-order event that carries all the information the packing station needs, including rendered note text, wrap style code, and any custom image reference.

Public operating baseline versus design assumptions

Amazon publicly offers gift wrapping on eligible items, typically charging $3.99 per item, and processes the wrapping at fulfillment centers using automated and manual packing lines. Etsy built its entire marketplace around seller-level personalization, where each listing can define custom text fields, image uploads, and per-unit pricing. Walmart offers gift wrapping and gift messages at checkout, integrated with both online fulfillment and in-store pickup.

For capacity planning, this answer explicitly assumes a mid-size e-commerce platform with 200,000 orders per day at baseline, a 10% gift-wrap uptake rate during non-holiday periods, a 25% uptake rate during the November-December peak, and a 4x event multiplier for Black Friday and Cyber Monday. Unless a number is tied to a citation, it is a stated design assumption.

The three architectural planes

1. Checkout and pricing plane: gift-wrap option selection, fee calculation, cart-level and item-level personalization, and payment capture.
2. Fulfillment plane: work-order generation, print-queue management, warehouse instruction delivery, and physical verification.
3. Customer experience plane: order tracking with personalization status, preview rendering, modification windows, and post-delivery proof.

A strong interview answer keeps these planes separate. The checkout plane can degrade (show a stale wrap catalog) without affecting the fulfillment plane (which must never lose a work order). The customer experience plane can show a cached preview while the fulfillment plane re-renders the note from the durable source of truth.