The multi recipient swag drop playbook

The multi recipient swag drop playbook

The single hardest thing about running a company merch programme at a distributed company is not the catalogue. It is not the budget. It is the post office.

By "the post office" we mean the work of getting one order, with one approval, dispatched to forty seven different addresses across eleven countries, in five to ten working days, without an internal team standing over a printer assembling shipping labels by hand.

This is a working playbook for that work, written for People Ops and procurement leads who have inherited a distributed merch programme and are trying to make it not be the worst part of their week.

Phase one: the recipient list

The recipient list is the engine of the whole programme. Get it right once and the rest of the programme runs on it.

The fields that matter on a recipient list:

• Full legal name (for international shipping documents).
• Email address (for delivery notifications).
• Phone number (for couriers in countries where SMS is the default delivery touch point).
• Address line 1, line 2, city, region or county, postcode, country (ISO 3166-1 alpha-2).
• Garment size if apparel is in the kit.
• Cost centre or budget code if your finance team needs it on the invoice.

Most People Ops teams collect this in a one off Google Form per cohort. Better: collect it once on the new starter onboarding flow and reuse it across every merch drop. A column in the People Ops system, accessible to the merch workspace via export, removes the friction.

Address quality is the single biggest predictor of delivery success. A 200 unit drop with a 5 percent invalid address rate generates 10 failed deliveries, which generates a week of recovery work and a per recipient delivery cost that doubles or triples for the failed recipients. Address validation up front matters more than any other quality control in the programme.

Phase two: the kit specification

A multi recipient drop should ship a single kit shape to every recipient. Variation creates work; work creates errors.

The minimum spec for a recurring kit:

• One apparel item (tee or hoodie) with a size variant.
• One stationery item (notebook or card).
• One drinkware or bag item.
• The packaging (kraft mailer, paper wrap, branded thank you card).

Six items is the upper end of a recurring kit before the per recipient cost gets noticeable. Three items is the lower end where the kit still reads as a kit and not a single product. A four item kit at £45 to £85 per recipient lands at the sweet spot for most B2B programmes.

The kit specification should be locked at the workspace level, with a version number. When the spec changes (new cohort, new season, new product line), the version increments. Every order references a spec version, which gives finance and procurement an audit trail.

Phase three: the production run

A 47 recipient drop in a typical workspace runs as a single order with 47 line items, each line item being one full kit destined for one recipient address.

The production decisions to make at order time:

• Print method per item. DTG for apparel; foil stamp for stationery; engrave for drinkware where applicable. The workspace should pre select these per SKU.
• Personalisation, if any. Most recurring kits are not personalised; the cost and complexity rises sharply when each kit carries a different name.
• Garment size split. Sized from the recipient list, not estimated. A 47 unit drop with size estimates will misfit roughly 6 to 12 units.
• Single dispatch window or batched. Single dispatch keeps the order auditable; batched dispatch fits cohorts that hire on a rolling basis.

Production lead time for a 47 unit drop in the UK and EU sits at five to seven working days end to end (two to three days production, two to four days transit). Plan the trigger date back from the recipient delivery date with a working day buffer for international shipping.

Phase four: the dispatch

Multi address dispatch is where the platform earns its place in the programme. The work to dispatch 47 parcels manually is roughly four to six hours; the work to dispatch them through a workspace that prints labels in batch and hands the parcels to the courier in a single drop off is roughly twenty minutes.

The dispatch should produce, per recipient:

• A tracked label with the correct carrier service for the destination country.
• A delivery notification email when the parcel ships.
• A second notification when the parcel is out for delivery.
• A failure notification, with a clear recovery path, when delivery fails.

The dispatch should produce, per order:

• A single order page showing the status of every recipient parcel.
• A consolidated invoice with the kit line items and the per recipient shipping line items.
• An audit trail of the approval, the production sign off, and the dispatch.

Norma orders with multi address shipping produce all of this on one screen.

Phase five: the recovery

Failed deliveries are a normal part of distributed shipping. The recovery process matters more than the failure rate.

The recovery shape for a Norma order:

1. The courier reports a failed delivery (recipient not in, address invalid, recipient declined).
2. The workspace receives an event with the failure reason and the parcel reference.
3. The People Ops or procurement lead sees the failure on the same order page that everything else lives on.
4. They contact the recipient via the email address on the recipient list.
5. They either correct the address (rare) or trigger a re ship to a corrected address.

The re ship is a one click action; the cost lands on the same invoice as the original order. The recipient gets a delivery notification when the re ship dispatches.

A 47 unit drop in a typical month sees one to three failed deliveries on first attempt and a 100 percent recovery rate within five working days when the workspace has the recipient list and the failure events in one place.

Phase six: the post mortem

After the drop, the data the workspace produces is the input for the next drop. Three numbers to track:

• Delivery success rate first attempt. Target: 95 percent or higher. Below that, address quality needs work.
• Per recipient landed cost. Includes kit, packaging, dispatch, and the proportional ops time. Useful for finance.
• Recipient response rate. A short post delivery survey link in the dispatch email. Optional, but worth doing once per quarter.

The post mortem closes the loop. The next drop's recipient list is cleaner, the spec is tuned, the lead time is right, and the failure rate drops. By the third drop in a workspace, the programme runs itself.

What to ask a supplier before you commit

If you are evaluating a supplier for a multi recipient programme, ask in writing for:

• A worked example of a 47 recipient order through their platform.
• The address validation step, the print method per SKU, the dispatch lead time per country.
• The failure recovery workflow.
• The invoice format (single invoice with per recipient line items, or many invoices, or something else).
• The per recipient shipping cost across the destinations you ship to.

If the supplier cannot answer those five questions in writing within a working day, the supplier is not set up for distributed dispatch. That is not a bad supplier; it is a different supplier. Pick the one that is set up for the shape of the work you actually do.

The post office should not be your job. Pick a supplier that has built the post office.