If your gifting platform was acquired, nothing breaks immediately — and that is exactly why it is worth thinking about now rather than later. Sendoso acquired Alyce in February 2024 and Postal in April 2025, and both continue to operate as named product lines. There is no announced sunset for either. What there is, publicly, is a commitment to unify the Sendoso, Alyce and Postal experiences under one interface over time.
That is a normal and reasonable thing for an acquirer to do. It is also the thing worth planning around, because "unified over time" eventually means one product, and the one that survives is usually the acquirer's.
We build a competing product, so read this with that in mind. It is written to be useful anyway — including the parts where the answer is stay where you are, which for most teams reading this it will be.
What actually happened
- February 2024 — Sendoso acquires Alyce, adding AI-driven gift personalisation built on recipient interest data.
- April 2025 — Sendoso acquires Postal, adding a simpler interface aimed at SMB and People Ops, plus branded swag and company-store capability.
- Since — both run as "Alyce by Sendoso" and "Postal by Sendoso". Integration is rolling out gradually. No end-of-life date has been announced for either.
Worth saying plainly: this is category consolidation, not a company in trouble. Sendoso bought capability it did not have. If you are a Sendoso customer, you got more product.
What acquisition actually means for you
The honest version, without the churn-marketing framing:
In the first year, usually very little
Contracts are honoured, support continues, the product you bought keeps working. Teams that panic-migrate in month three generally spend more on the migration than they would have on another year of the contract.
In the second and third, the roadmap is the tell
Watch where new features land. When the acquired product stops getting meaningful releases and everything ships on the parent platform first, the direction is set — regardless of what anyone has announced. That signal usually arrives twelve to eighteen months before a formal migration notice.
Renewal is the real decision point
Not the acquisition announcement. If your renewal is nine months out, you have time to evaluate properly rather than under pressure. That is the whole reason to think about it early: so the evaluation happens on your schedule.
When you should stay
Most teams should, and it is worth being specific about who:
- Your use case is what the acquirer is good at. If you run CRM-attributed gift sends tied to sales campaigns, consolidation makes Sendoso stronger at that, not weaker. Leaving would be a downgrade.
- Migration cost exceeds the risk. If you hold inventory with them, have deep CRM integration, and it is working — the expected cost of moving today is higher than the expected cost of moving later, if you ever have to.
- Your renewal is far out. Re-evaluate three months before it, not now.
When it is worth looking
- You were on Postal specifically for the simpler UX. That was the reason to pick it, and it is the thing most likely to change when interfaces unify.
- Your use case drifted. Plenty of teams bought a gifting tool and now run onboarding kits, event shipments, an internal store and client gifting through it. That is not gifting any more — it is a merch program, and it is a different category of tool.
- Your buyer changed. Gifting platforms are bought by revenue teams. If the program has migrated to People Ops, Brand or Procurement, they will ask questions — who can order, from which budget, using which logo — that a campaign-attribution tool answers awkwardly.
- Renewal is inside six months. Look now, while you still have leverage in the conversation.
Five questions worth asking your rep
These are fair questions and a good rep will answer them straight:
- Which platform will new features ship on first over the next twelve months?
- Is there a committed support timeline for the product I am actually on?
- If interfaces unify, what specifically changes in my day-to-day workflow?
- What happens to inventory I currently hold with you if I move?
- Can I export my recipient data and gift history, in what format, today?
The last one matters most and is the one people leave until it is urgent. Ask it while nothing is at stake.
Where to look, honestly
Stay with Sendoso if the job is CRM-attributed sends inside sales campaigns. Consolidation strengthens exactly that.
Reachdesk is the closest like-for-like if you want to remain in the gifting category with a different vendor.
Brandmerch if what you are actually running is a merch program rather than a send, and you want control over it. Gifting platforms broker third-party suppliers and warehouses, which buys reach. We source, decorate, hold and ship the goods ourselves, which buys control — over which products exist at all, over quality when a run comes out wrong, over how and when it ships, and over who can order what against which budget. Branded storefronts, procurement, stockroom inventory, approvals and fulfillment run on one permission model, with budget caps enforced at checkout rather than reported afterwards. Existing inventory can come into the system rather than sitting invisible beside it, which is usually the deciding practical detail when moving. The honest cost: an integrated catalog lists fewer SKUs than a brokered one.
Sends are programmable — the REST API creates a send, checks ready-to-ship inventory and emits send.created, send.shipped and send.delivered webhooks, so a CRM workflow can trigger merch directly. What we do not ship is a prebuilt Salesforce or HubSpot app, or attribution reporting inside the CRM.
So: we are the wrong choice if the thing you are buying is that attribution dashboard — gifts mapped to opportunities and influenced pipeline, reported where your sales team already works. That is Sendoso's centre of gravity and we do not compete with it.
If you do move
- Ask about held inventory first. It is the single most common source of migration friction and the thing people discover last.
- Export recipient and gift history before you give notice, not after.
- Map every automated trigger. If a send fires from a CRM workflow today, something has to replace it. Map it before migration, not during.
- Do not migrate mid-campaign. An overlapping month costs less than the reconciliation.
For the fuller category comparison, see Sendoso alternatives, and merch program management software covers what the governance category has to do that gifting tools do not.
