ABM gifting platforms compared — no vendor is complete.

The short version

One line per vendor, before the detail. “The motion” below means API-triggered 1:1 sends to sender-supplied office addresses, with shipped/delivered events available to automation.

The six capabilities that matter

The fulfillment chapter makes the argument in full: for this motion, the vendor requirement is a status API, not a gift catalog. That translates into six concrete capabilities — true 1:1 physical personalization per package (merge-field note cards, per-package unique QR codes), programmatic send triggering, shipped/delivered status events, direct-to-address shipping without a recipient confirmation flow, friendliness to a 25-50 package pilot, and pricing you can see before a sales call. The matrix scores all ten vendors on exactly those six.

The capability matrix

Alyce — historically the strongest 1:1-personalization brand in the category — no longer appears as a row because it has been absorbed into Sendoso. Zest and Imprint Engine were screened out as category mismatches (white-label e-commerce gifting infrastructure and a full-service swag agency, respectively).

Goody — the motion’s best API, with a physical gap

Goody is the surprise of the field. Known mostly as a consumer-grade “send gifts as easily as a text” product, its business arm ships the most complete developer surface we verified anywhere: an order-batch API with a sandbox, a documented direct_send method that takes a sender-supplied mailing address per recipient — the researched-office-address motion, natively — and a webhook catalog that fires on order shipped, delivered, opened, accepted, canceled, and refunded, delivered through Svix with logs and replay. No platform fee, no minimums, pay per gift accepted. For the trigger-orchestration architecture in the orchestration chapter, that is the entire wish list.

The gap is physical. Goody’s greeting cards are digital — they render in the recipient’s unwrapping experience, not on paper in the box — and there is no printed merge-field note card, no per-package QR insert, and no bespoke sourcing service. Its catalog is strong on brand-name gifts and on-demand branded swag, and weaker internationally than Reachdesk. The practical pattern: use Goody as the programmable fulfillment rail, and solve the note-card-and-QR layer with a print vendor or a custom-packed gift shipped into its flow. For campaigns where the landing page (reached from the digital card or a follow-up email) carries the personalization instead of a printed insert, Goody alone may be enough.

&Open — the bespoke leader, with a redemption-shaped core

&Open’s reputation is earned at the high end: it built Airbnb’s custom gift collection, fulfilled Granola’s much-posted spoon and OpenAI’s custom gifts, and ran Clay’s 600-package ABM campaign — including building a mail-merged 1:1 note card format that didn’t exist in its lineup until Clay asked. That willingness to build is the differentiator, and it lives in the managed “Super-Served” tier: off-catalog sourcing, creative briefs to an in-house gift-design team, complex bundles, a dedicated account manager.

The important nuance for this motion: &Open’s default machinery is redemption-shaped. Its API takes a recipient name and email and returns a redemption URL; its on-demand catalog charges per redemption (gift price plus a service fee plus shipping, only when the recipient claims). Direct-to-address shipping — the thing the surprise-at-the-office motion requires — is supported, but for stocked, pre-ordered gifts. Practically, that means the pilot conversation with &Open is a stocked-gift conversation: you commit inventory up front and they ship to the addresses you researched. Pricing for all of it is custom-quoted; nothing is published.

Sendoso — the automation platform with a human gate

Sendoso has the broadest platform footprint — marketplace, Amazon sourcing, custom items, deep CRM integrations with status mapping across processing, shipped, delivered, and undeliverable — plus whatever remains of Alyce’s 1:1 personalization capability, which it acquired. It is one of only three vendors in the field with confirmed status webhooks. Two gates temper the story: the webhooks are support-enabled per organization rather than self-serve, and sends triggered programmatically from data tools land in a “pending approval” queue that a human must clear before anything ships, with no documented bypass.

Whether the approval queue is a dealbreaker depends on who is running the campaign. For a lean in-house team chasing full automation, it breaks the loop. For an agency-operated motion with a human already reviewing every send, it’s a step that was going to happen anyway — which makes Sendoso considerably more attractive in practice than it looks on an architecture diagram.

Reachdesk — the programmatic pick, minus the push events

Reachdesk comes closest to the programmatic ideal on the trigger side: a campaign-trigger API that any HTTP client can call, with per-send custom attributes that flow into gift notes and gift emails as merge variables. That is the closest match in the field to Clay-style 1:1 campaigns, where a data tool computes the personalization and fires the send. It also owns the strongest international story — in-region warehouses across the US, Canada, UK, Europe, and Australia, shipping to 180+ countries.

The two catches. First, no outbound webhooks: the API beyond triggering is read-only, so shipped/delivered-driven automation must poll the send-records endpoint on a schedule or lean on the native Salesforce/Marketo status sync. Second, its default physical-gift flow is address-confirmation — the recipient picks a delivery address on a landing page — which is the inverse of the researched-address motion. Sender-supplied addresses at trigger time need explicit validation in the sales process.

The rest of the field, briefly

Postalresolved worse than its positioning suggests for this specific motion. The physical operations are real — curated marketplace, branded swag store, handwritten notes at scale, international warehousing, and an enterprise integration list (Salesforce, HubSpot, Marketo, Outreach, 6sense, Demandbase) with logos like SAP and Uber. But there is no public developer portal at all, and the Zapier app’s trigger list contains no shipped or delivered event — order status lives in the reporting dashboard. If your campaign is driven from a CRM by marketers, Postal works; if it’s driven from code by engineers, it doesn’t.

Loop & Tieis Postal’s mirror image: the best incumbent developer experience we verified — clean REST API, sandbox keys, an atomic bulk-send endpoint, and ten webhook events including both shipped and delivered — at a $0 entry price. But it is structurally a choice-based redemption platform: the API’s delivery methods are email and link only, and the recipient enters their own address at redemption. It cannot ship to an address you supply, which rules it out for the surprise-at-the-office motion, while making it excellent for code-triggered gifting where recipient choice is a feature.

CorporateGift supports the address motion well operationally — CSV multi-address upload, ship-to-many in one transaction, CRM sync, handwritten cards from selected sellers — and runs real Salesforce and HubSpot apps. The caution flags: its marketing claims an “open API” but no public documentation exists, no delivery webhooks are documented, marketplace fulfillment is effectively US-only, and cards carry per-product setup fees. SnackMagic/Stadium is the cheapest way to test the channel at all: no minimums, published pricing (boxes from $45 plus a 15% pay-as-you-go fee), and “surprise” orders that ship to sender-supplied addresses — with personalization capped at a custom note and a branded sticker. Printfection remains disqualified for automated 1:1 sends. Giftpackis the watch row: AI-matched per-recipient gifts across a claimed 3.2M-SKU catalog and 220-country delivery, with real customer logos but seed-stage funding and thin public API documentation — take the demo, don’t build on it yet.

The recommendation matrix

Design for polling anyway

Three vendors have real status webhooks (Goody, Sendoso, Loop & Tie); the rest are poll-only or worse, and one of the three gates webhooks behind a support request. The architectural conclusion stands: build the campaign’s nervous system around a status poller — every 30 minutes is plenty for physical mail — writing changes to the CRM status field that drives the triggers in the orchestration chapter. That design works against every vendor in the matrix and degrades gracefully when an API has a bad day. Where webhooks exist, treat them as a latency optimization layered on top, never as the only path.

Where this fits

This page scores the vendors; the fulfillment chapter explains the requirements behind the scorecard, and the orchestration chapter covers what the status events drive once you have them. If you’re starting from zero, the end-to-end playbook sequences all of it.