A divestiture can transfer a business without transferring every promise attached to its gifting program. Invitations may still be redeemable, a seller may own the branded stock, and a buyer may need to support employees without having permission to receive their delivery data. The practical question is not simply who runs the program tomorrow. It is which legal entity may perform each obligation, with which funds, rights, records and evidence. This guide provides an operating register and two hypothetical decisions for corporate development, finance, brand and program owners; it is not legal, tax, accounting or employment advice.
Define the entity boundary before moving the program
Start with the transaction documents, not the platform's administrator menu. Ask transaction counsel to identify the selling entity, acquiring entity, affected subsidiary, effective time, excluded assets and liabilities, and any transitional service arrangement. A share sale, asset sale and internal reorganisation can create different operational questions. The gifting team should not decide their legal effect from the announcement or from the fact that the same employees remain at their desks.
Create a one-page mandate naming the seller's accountable owner and the buyer's accountable owner. Record who can approve spending, brand use, recipient communications, data handling and exceptions. Each owner needs an authorised alternate. A shared transition meeting does not itself grant either side the power to bind the other, and an account administrator is not necessarily a contract signatory.
Separate three dates: the transaction's legal effective time, the program's operational cutover and the end of transitional support. Record the time zone and the evidence that each trigger occurred. A deal can close while the seller continues specified fulfillment work. Conversely, preparation may begin before closing without permitting invitations, address transfers or public use of the buyer's brand.
This is different from an internal program-owner handoff, where the organisation may remain unchanged. It is also different from a program sunset, where the objective is to close obligations. Here the program may continue, but responsibility must be allocated between entities. Use the adjacent guides for their narrower tasks rather than treating a staff handover as a transaction consent.
Build a register that separates ownership from permission
Use one versioned transfer register, with access appropriate to the transaction's confidentiality requirements. Give each obligation a stable identifier. Keep the original order, invitation and support references alongside that identifier so a recipient's history does not disappear when an accounting or organisational label changes. The register is a proposed operating control, not evidence that a transfer is already valid.
The table below is a reusable structure, reviewed for this guide on 27 October 2026. Its blank decisions must be completed from the actual transaction; “unknown” means held, not implicitly approved. Add evidence links, decision dates and named approvers to each row. Keep recipient addresses outside the general transaction register unless their inclusion is necessary and authorised.
| Obligation | Seller-side evidence | Buyer-side decision | Acceptance or hold test |
|---|---|---|---|
| Program contract | Contracting entity, scope and transfer provisions | Assumption, replacement contract or retained seller performance | Required approvals and counterparty confirmations recorded |
| Brand and artwork | Rights owner, approved files and permitted uses | Licensed use, neutral replacement or no use | Exact design, territory, purpose and period authorised |
| Physical inventory | Title evidence, location, quantities and reservations | Receive, leave with seller or resolve separately | Both parties reconcile custody and usable quantity |
| Paid balances | Payer, ledger, currency, commitments and restrictions | Approved allocation and settlement route | Finance agrees liability and cash treatment separately |
| Orders and invitations | Original terms, state, recipient group and dates | Continue, reissue if permitted, or hold | One accountable entity and no duplicate fulfillment |
| Recipient information | Purpose, notices, fields and current access | Approved handling route and permitted users | Privacy decision and necessary controls evidenced |
| Support and exceptions | Open cases, commitments and unresolved outcomes | Named receiving team and escalation authority | Test inquiry reaches an authorised human owner |
Keep four concepts distinct: who owns an asset, who holds it, who may use it and who pays for its use. Stock physically located at the buyer's site may remain seller-owned. A seller-funded balance may be committed to existing recipients rather than available for a new buyer campaign. An approved brand file does not necessarily include permission for a different legal entity to distribute it.
Use a separate exception column for each unresolved issue. Do not compress a disputed balance, missing consent and unknown shipment into one reassuring “transition pending” label. Each needs a responsible owner, next evidence request, review date and safe interim route. That specificity lets authorised work continue without silently clearing the blocked items.
Reconcile funds, invitations and orders as different populations
Freeze a dated reconciliation snapshot while preserving live operational events. Finance should identify the payer, currency, booked amount, actual provider balance, committed orders, potential open invitations, credits, fees and disputed adjustments. Do not assume that invitation face values equal either recognised liabilities or refundable cash. Those conclusions depend on the instrument, contract and applicable rules, and belong to the responsible finance and legal owners.
For an illustrative planning ledger, suppose the seller has funded 20,000 dollars. Confirmed orders reserve 6,000 dollars, unresolved charges reserve 1,000 dollars, and 80 open invitations could each require up to 100 dollars under the hypothetical terms. The conservative operating reserve is 15,000 dollars, leaving 5,000 dollars not allocated by this calculation. That remainder is not automatically transferable or refundable. It is a question for the agreed settlement process, and the calculation excludes any additional taxes, shipping or fees not already included.
Record the assumptions beside the numbers. If invitation values vary, calculate the actual exposure by cohort instead of multiplying a single cap. If an order can still change, state when its reserved amount becomes final. If balances are held in different currencies, keep native-currency ledgers and a separately approved translation method; a convenient exchange rate must not conceal a shortfall.
Reconcile invitation states independently: issued but unopened, viewed but unclaimed, claimed without a confirmed order, confirmed, dispatched, delivered and disputed. A recipient may have more than one invitation legitimately. Deduplication should use the program's entitlement rules and original identifiers, not a blanket rule that deletes repeated names. The purpose is to prevent duplicate execution without erasing valid rights.
At cutover, capture events occurring after the snapshot in a controlled change log. Compare the source system's current state before any replacement invitation or cancellation. If a request timed out, investigate the original transaction rather than issuing another one because the screen looks empty. Reconciliation should include late refunds and failed deliveries after the main handoff has been signed.
Treat brand rights and stock custody as separate release gates
Ask the brand rights owner to identify the precise permission needed for each asset: packaging, garment mark, gift card artwork, invitation sender identity and support signature. Specify legal entity, territory, audience, channel, permitted period and any conditions. An approval for the seller's employee campaign should not be read as an unlimited licence to the buyer.
Inventory review needs a physical count and condition check as well as the ledger. Record usable goods, damaged goods, reserved goods, goods in transit and returns not yet received. Photograph representative packaging and exact artwork versions where permitted. Keep proof of title and custody separate from those images; a photograph shows condition, not the legal right to distribute the item.
Compare three routes. Continued use may preserve recipient continuity but requires the relevant rights and operational approvals. Neutral replacement avoids displaying an unauthorised brand but can add cost, delay and waste; it still needs procurement and recipient-treatment decisions. A no-send hold protects the boundary when neither route is cleared, but requires an honest explanation and an owner for the unresolved obligation.
Do not improvise a sticker, cover-up or donation as an assumed cure. Alteration can affect quality and may not resolve rights restrictions. Donation is a separate disposition decision, not proof that the buyer may use the seller's inventory. Record the approved treatment, quantity and resulting evidence, including retained stock that has not yet been resolved.
Hypothetical decision one: a US unit has open recognition invitations
Assume a US business unit is sold while a seller-funded recognition campaign remains open. There are 120 invitations: 30 have confirmed orders, 10 have a disputed processing state, and 80 are unclaimed. These invented figures illustrate the method, not a customer result. The transaction team has not yet confirmed the required permission for transferring the unclaimed cohort's personal information to the buyer.
The seller's program owner first reconciles all 120 original invitation identifiers with the provider. Finance separately applies the reserve calculation above, checking that the 30 confirmed orders account for the assumed 6,000 dollars and the disputed group for the assumed 1,000 dollars. The buyer's people team confirms which recipients belong to the transferred business; corporate development confirms which obligations the agreement allocates to each entity. None of those confirmations alone authorises a data transfer.
The privacy owner examines the actual notices, purposes, transaction structure and required consent or other lawful route. As a historical caution, the US Federal Trade Commission's April 2014 acquisition notice emphasised that an acquisition does not erase existing privacy promises. That consumer-service example is not a universal rule for employee gifting, but it explains why a corporate announcement cannot substitute for a specific privacy decision.
Until the necessary permission is resolved, the team holds the proposed transfer of that cohort. It evaluates whether the seller can continue fulfilling existing obligations under an authorised transitional arrangement, or whether recipients should receive a separately approved invitation from the buyer. The second route is not automatically better: it can create duplicate entitlements, misleading expiry expectations and unnecessary collection of addresses. The team cannot simply export the old list to make the new process faster.
Suppose a buyer operator prematurely creates a replacement invitation for one recipient, but its send outcome is unknown. Recovery begins by holding further replacement sends for that identifier and inspecting the original request and provider state. The seller checks whether the original invitation was redeemed meanwhile. Only a confirmed state and an authorised decision permit cancellation, reissue or continued performance. An uncertain screen response is not evidence of failure.
Acceptance is a jointly signed cohort record: 30 confirmed orders have a named fulfilling entity, 10 disputed states retain original references and owners, and 80 unclaimed invitations have either an approved route or a clearly documented hold. Finance accepts the reserve and settlement assumptions; privacy accepts the actual handling decision; support tests the recipient-facing explanation. A partial operational handoff is honestly partial, even if the deal itself has closed.
Hypothetical decision two: European logo stock remains with the seller
Assume a European subsidiary is divested, but 600 branded gift sets remain seller-owned under the agreed asset allocation. The rights owner explicitly refuses buyer use of the seller's logo. The buyer has 150 pending recipient commitments associated with the transferred operation. These are hypothetical quantities, and the example makes no claim that one legal treatment applies throughout Europe.
The warehouse owner counts the 600 sets, checks reservations and identifies where they are held. The seller's finance owner confirms their ledger treatment, while the brand owner documents the refusal and its scope. The buyer's program owner compares the 150 commitments with the original recipient terms. The team does not infer that a commitment to provide a gift means a commitment to provide these particular branded sets.
Consider a neutral replacement costing 24 euros per set plus 300 euros in fixed handling. For 150 sets, the illustrative purchase and handling total is 3,900 euros, before any tax, delivery or other excluded charge. Compare that cost with the authorised alternatives, including seller performance where lawful and permitted, or a communicated hold. Do not treat the unused 600 sets as free buyer stock when evaluating the options.
If the buyer approves neutral replacement, procurement obtains an exact specification and sample approval, finance identifies the payer, and support prepares a truthful explanation of any changed timing or selection. The warehouse keeps the seller stock segregated. The recipient data needed for the replacement follows its separately approved handling route; new merchandise does not cure an unresolved data-transfer issue.
Suppose a warehouse mistakenly picks 20 seller-branded sets before the hold is received. First determine whether they are still on site or have left custody. Recover and recount the on-site items under the warehouse's safe procedures; preserve shipment evidence for anything already dispatched. Brand and the responsible legal owner decide the response to any unauthorised use. A new neutral shipment must not be sent until the original recipient and shipment states are reconciled.
Both sides accept a closing stock-and-claims statement: seller stock quantity and location, any actual incident, buyer replacement commitments, payer, approved recipient route and remaining exceptions. The seller signs custody and rights treatment; the buyer signs its accepted obligations. A warehouse dispatch report alone proves neither the legal allocation nor complete recipient resolution.
Use a decision tree for each obligation, not one global switch
Decision tree caption: the following branches are an editorial operating model, reviewed on 27 October 2026. They are not legal determinations or automatic platform behaviour. Apply them to each stable obligation identifier and preserve the evidence behind every answer.
- Is the item within the signed transaction scope? If no, leave it with its existing responsible entity or obtain a separate authorised decision. If unknown, hold the proposed transfer.
- Are the necessary contract, rights, funds and data decisions evidenced for this item? If no, identify the exact missing decision. Do not clear unrelated gates by analogy.
- Can the approved receiving entity actually perform and support it? If no, assess an authorised seller-service arrangement, a permitted alternative or no-send. Do not mark capability testing as acceptance.
- Is the original execution state known and reconciled? If no, investigate that original operation before repeating it. If yes, execute once through the approved route.
- Have both entities accepted the resulting record and remaining exceptions? If no, retain the open handoff. If yes, move to the agreed follow-up checks without deleting history.
Exception: closing is delayed after the operational rehearsal
Preserve the rehearsed register but do not treat its planned timestamp as a completed trigger. The transaction owner confirms the new event; each operational owner checks whether stock, prices, recipient states and notices remain valid. Reverse only reversible preparation that has an approved reversal path. Actual orders, disclosures or dispatches require their own investigation and remedy. Reissue the cutover instruction with a new version and obtain both parties' acknowledgement before execution.
Accept the handoff through tests and named residual owners
Before cutover, run a small authorised rehearsal using non-sensitive test records where possible. Ask the buyer's support team to locate an obligation by its original reference, identify the responsible entity, explain an unresolved hold and route an escalation. Ask finance to trace a sample from payer to reserve to settlement decision. Ask the warehouse to identify which exact goods must not leave. Record observed results rather than attendance at training.
Test excess access as well as missing access. The buyer should not gain visibility into unrelated seller campaigns merely because a shared workspace is convenient. The seller should retain only the access needed for its approved transitional work, for the approved period. Use named roles and permitted accounts rather than sharing an outgoing employee's credentials. Record the actual test outcome and the person authorised to resolve a mismatch.
When a test fails, distinguish a configuration problem from a missing decision. Changing a screen permission cannot provide a counterparty's contractual consent. Moving stock to a different shelf cannot create brand rights. Assign the precise correction, preserve the failed result and repeat only the relevant test after new evidence exists. The aim is a usable, bounded handoff, not a higher count of successful clicks.
Use an acceptance checklist with explicit evidence owners:
- Corporate development confirms scope, effective event and authorised signatories against the controlling agreement.
- Procurement confirms the actual contract route and any required counterparty acknowledgement.
- Brand confirms the permitted artwork version or the no-use instruction.
- Finance signs native-currency reconciliation, reserves, disputes and settlement ownership.
- Privacy confirms the approved purpose, fields, recipients of data and necessary notices or permissions.
- Operations confirms order states, physical counts and protection against duplicate execution.
- Support demonstrates a working contact path for recipients and late-arriving cases.
- Both entity owners sign the same register version and schedule the next exception review.
Set follow-up checks around actual risk, such as the first post-cutover invoice, the last expected shipment and the expiry of a transitional service arrangement. These are operational milestones, not invented statutory deadlines. Keep a residual owner after the transition team disbands. A returned parcel or disputed credit should reopen its original case, not force the recipient to reconstruct the transaction history.
Continue the service without transferring responsibility by assumption
A successful divestiture handoff makes every continuing obligation explainable: which entity owes it, which rights and funds support it, what may happen to its data, and who handles a failed or uncertain operation. Prefer a documented hold over an unauthorised shortcut, and prefer a bounded, jointly accepted continuation over a blanket shutdown. Completion means the two parties accepted the same evidence and the remaining work has real owners, not that every row was coloured green.
Where an approved gifting program needs execution support, Giftpack can be considered for its stated enterprise gifting and fulfillment scope. Confirm the actual service fit, destinations and responsibilities during setup. Contract transfer, brand permission, finance, privacy and employment decisions remain with the organisations and their qualified advisers.