Ending a corporate gifting program is not the same as turning off a campaign. An invitation may still be redeemable, a gift may be in transit, a refund may be owed, a warehouse may hold branded stock, and a recipient record may still have a valid retention purpose. Treat the sunset as a controlled transfer of obligations: identify every open item, assign an owner and a decision, notify the affected person, and retain evidence that the decision was carried out. This runbook is for the business owner, finance, procurement, fulfillment, support, and privacy teams working together. It is an operating framework, not legal, tax, accounting, or employment advice.
Define what is ending, and what is not
Begin with a one-page decision signed by the program sponsor. State which entities, countries, budget codes, campaigns, warehouses, vendors, and recipient populations are in scope. Specify a last invitation date, a last redemption date if one can lawfully and contractually be set, a last fulfillment date, and the owner of exceptions after the project team disbands. Do not collapse those dates into one switch-off time. An invitation can close to new distribution while a previously accepted order remains enforceable or operationally recoverable.
The distinction from adjacent projects matters. A vendor offboarding project changes the execution partner and may leave the program alive; our vendor offboarding guide addresses that handoff. A campaign closeout reconciles one launch. A data deletion request concerns a particular person's information. A program sunset covers the entire obligation ledger across all of these, including money and physical stock. If the business is merely moving to a new platform, first determine whether each entitlement will continue under the successor rather than treating every claim as expired.
Make the exit criteria measurable. The sponsor can accept a sunset only when the register has no ownerless item; every still-open commitment has an approved treatment; stock and money reconcile to signed evidence; data is either disposed of or retained under a documented purpose and access rule; and recipients have a reachable support path. “Portal disabled” proves none of these. Capture the approval of the policy, not just the date an administrator clicked a button.
Build a versioned closure register before changing access
Export or otherwise reconcile the records available to each authorized owner before changing invitations, storefronts, or vendor access. The register needs a stable program identifier, line-item identifier, category, source system, country, legal entity, value or quantity, current state, next action, accountable owner, decision approver, evidence link, due date, and final closure time. Use the least personal information necessary in the working register; keep recipient identifiers in controlled systems and reference them by safe IDs. Version the register by date and preserve who changed each line.
The table below is a field and decision model, not a claim that every company or platform exposes the same states. Map actual source states into it and preserve the original state in a separate column. The operations lead owns the mapping; finance and privacy review the categories that touch their controls.
| Line type | Minimum question | Owner and acceptable evidence |
|---|---|---|
| Invitation or entitlement | Was it delivered, accepted, expired, disputed, or never sent? | Program owner; source event, policy decision, and recipient notice |
| Order or shipment | Is it paid, in production, shipped, returned, or lost? | Fulfillment; order trail, tracking or exception resolution |
| Physical inventory | Where is each stock-keeping unit (SKU), and who owns it? | Warehouse and finance; count, disposition approval, stock movement |
| Funds, credits, or balances | Who owes whom, under which terms? | Finance; ledger reconciliation and signed treatment |
| Recipient data | What purpose still justifies access or retention? | Privacy owner; retention decision, deletion or restriction evidence |
Add a separate exception queue rather than overwriting the source state to make a dashboard green. For each disputed or unclassifiable record, log the evidence gap, person empowered to decide, interim safeguard, next review time, and recipient response channel. Reconcile source totals against register totals by category and by legal entity. If the count differs, pause irreversible disposal or deletion until the difference has an owner. The register is closed only when every item is resolved or explicitly transferred to a named long-term owner with a review date.
Decide claim treatment before sending a final notice
Segment recipients by what they have actually been promised. An unsent draft is different from a delivered invitation; an opened invitation differs from a selected gift; a confirmed order differs from a fulfillment failure. Read the applicable program terms, contract, purchase order, and local rules with counsel before choosing an expiry, refund, substitute, or transfer. Do not assume a single global notice period or that a points balance can simply be erased. Finance should classify the liability or credit treatment under the company's accounting policy; support should test whether the promised remedy is understandable and deliverable.
For each segment, choose a remedy matrix: honor on the original route, honor on a successor route, offer a permitted alternative, refund an authorized payer, or escalate an unresolved claim. Record why an option is unavailable. A new platform may be the best operational path, but only if entitlements, identity matching, budget ownership, and support obligations can be transferred safely. A forced substitute can be worse than a clearly described refund. A quiet expiration can create a dispute even if a backend balance looks small.
Draft notices from the matrix, not from a generic “we are shutting down” template. Include what is ending, what the recipient must do and by when, what happens to an order already placed, how to seek help, and how to challenge a mismatch. Translate and review the message for each market. A test group should be able to use the link, reach support, and receive the remedy stated in the notice. Keep delivery and bounce evidence; an email send count is not evidence that all recipients could act. For unreachable recipients, document a proportionate alternate route under the approved policy.
What if a recipient disputes the ledger?
Freeze the disputed line's irreversible action without freezing unrelated lines. Ask support to capture the invitation identifier, date, communication, and requested remedy through a controlled channel. Have the program owner compare source events and terms; let finance or counsel decide questions in their authority. Record a written outcome and a way to reopen the case if new evidence appears. Never ask the recipient to send sensitive identity data by an unsecured reply.
Hypothetical decision A: unclaimed invitations and funded balances
Imagine a points-based recognition program closing across two business units. At the decision date, some invitations were never opened, some recipients selected a gift that has not shipped, and the budget ledger shows an unused funded balance. These are illustrative facts, not a Giftpack customer case or a tested outcome. The sponsor wants a fast closure, but the claims and accounting positions differ. The operations lead pulls source events and the terms version attached to each invitation; finance pulls funding entries, credits, refunds, and outstanding invoices; support lists open tickets and failed deliveries. The first acceptance test is simple: every source line maps to exactly one register line, and the amounts reconcile to the finance ledger or a named exception.
One option is to honor all valid outstanding claims through the existing route until a controlled final date. This minimizes transition friction but retains support and vendor access longer. Another is an approved transfer to a successor route, which could consolidate operations but requires a verified identity match, equivalent entitlement, funds allocation, recipient notice, and failure route. A third is an authorized refund or other settlement to the actual payer, when terms and accounting treatment permit it. None should be selected merely because it makes the dashboard close faster. The policy approver chooses by entitlement segment, not by average program balance.
Suppose finance approves honoring selected-but-unshipped gifts, offering a defined claim window to eligible unopened invitations, and reviewing remaining payer balances for refunds or other lawful treatment. Operations freezes new invitations but does not cancel accepted orders. Support sends localized, segment-specific notices with a working claim path. Procurement confirms whether the execution partner can maintain the limited tail period. A daily exception review addresses bounces, duplicate entitlements, stockouts, and claims whose source event conflicts with a recipient's evidence. A stockout triggers the approved substitute or refund route, not an improvised gift. A disputed entitlement remains open with a named decision-maker rather than being forced into “expired.”
The case is accepted when no eligible claim is orphaned, every recipient in scope has a recorded notice route or documented exception, accepted orders have fulfillment or remedy evidence, payer balances have a signed finance disposition, and the support owner is reachable after the cutover. If any one of those fails, the program can stop generating new invitations while the sunset itself remains open. This separation lets the business reduce exposure without pretending liabilities disappeared.
Reconcile physical stock, returns, and supplier credits
Inventory is not a single number. Ask each warehouse and supplier for SKU, location, lot or variant if relevant, owned versus consigned status, committed quantity, in-production quantity, damaged quantity, returns in transit, and count date. Reconcile the physical count to the order and finance ledgers. Photographs, signed count sheets, carrier events, and supplier statements may support different questions; none replaces the other. Assign a stock owner even when the vendor holds the goods. Record who pays storage, return freight, repacking, donation, or destruction costs.
Compare dispositions using the same decision fields: whether the goods can lawfully and contractually move, whether brand and recipient promises allow reassignment, the net cost, the lead time, the sustainability implications, and the evidence required. Reassignment to another approved program can preserve value but requires a receiving owner and budget transfer. Donation may be appropriate only after brand, tax, product-safety, and recipient-commitment checks. Supplier return depends on contract and condition, and a credit memo must actually appear in finance records. A write-off or destruction should be an approved last resort with documented chain of custody, not a spreadsheet shortcut.
Close the loop on returns after the visible cutover. A package sent before closure may be returned weeks later; keep an address, support route, and disposition owner for that tail. A supplier credit expected but not received is still open. A warehouse count that excludes goods at a second site is not a final count. Procurement should confirm access to the shipment and invoice evidence before an account or integration is removed. The global gifting operations guide covers continuing operations; here the same data is used to prove a clean exit.
Hypothetical decision B: two-country branded-stock exit
Imagine a multi-country swag program ending with stock in two warehouses and open returns from three employee events. This is a hypothetical planning exercise, not evidence of a company's results. The program owner initially proposes donating all remaining units. The warehouse count, however, reveals one batch reserved for accepted orders, a second batch with outdated branding, and a third held under a supplier-consignment agreement. The first decision is not donation; it is to establish title, commitments, condition, destination rules, and the party authorized to move each batch.
The operations lead creates a SKU-and-location count signed by each site. Fulfillment matches reserved units to accepted orders and holds them until those orders are delivered or remedied. Procurement checks return rights and consignment terms; finance values owned inventory and records expected credits; the brand owner reviews whether reassignment or donation is acceptable; local counsel or specialists review any jurisdiction-specific restrictions. The team compares four routes for each batch: use for existing claims, reassign to a new approved program, return to supplier, or donate/write off under approval. A donated item is not “free” if freight, tax, brand restrictions, or disposal evidence are unresolved.
Suppose the first site reassigns uncommitted current-brand units, while the second returns eligible consigned stock and holds outdated units for an approved disposal decision. The team preserves receiving confirmations, supplier credit notes, signed stock movements, and disposal certificates where applicable. A return arrives after the initial count; instead of treating it as a surprise loss, the return address and owner remain active, the line is added to the versioned register, and finance updates the reconciliation. If the supplier rejects a return, procurement escalates under the contract while the inventory line remains open.
Acceptance is a three-way tie: counted units plus documented movements match the final physical position; order commitments have fulfillment or remedy evidence; and the finance ledger reflects realized credits or an explicitly outstanding receivable. The privacy owner separately verifies that shipping records are retained only for documented purposes. A closed warehouse account is not enough if a delayed return or credit has no owner.
Treat recipient data as a separate workstream
Map data by system and purpose: invitation delivery, order fulfillment, support, tax or accounting evidence, fraud or dispute handling, analytics, and vendor backups. For each dataset, identify controller or business owner, processor or service provider, geography, access group, last necessary use, governing retention basis, deletion method, and proof of completion. Separate production records from exports, shared drives, support attachments, and backups. Disable unnecessary access promptly, but do not promise instantaneous deletion where a documented lawful retention obligation or technically managed backup cycle applies.
Jurisdiction matters. Under the European Union's General Data Protection Regulation, storage limitation, erasure rights, and exceptions require a purpose-specific analysis; they do not supply one universal “sunset day” for all records. Taiwan's Personal Data Protection Act likewise makes purpose expiry and statutory exceptions material. Japan's Personal Information Protection Commission guidance says there is no general fixed retention period in the Act and calls for prompt deletion when use is no longer necessary. Korea's Personal Information Protection Act, Article 21 addresses disposal after the retention period or purpose ends and separate handling where other laws require preservation. Verify the currently applicable law, contract, and local advice for the actual data and entities; this summary is not a legal determination.
Give support an answer that is accurate, not absolute: which records can be deleted now, which must be retained for a stated reason, who can access retained data, and how a request is handled. Ask vendors for contractual deletion or return evidence and subprocessor coverage where relevant. Keep only the evidence needed to demonstrate the action, with its own retention decision. The recipient-data operations guide addresses ongoing controls; a sunset adds the challenge of proving disposal and preserving legitimate dispute records at the same time.
Sequence the 30-, 60-, and 90-day exit
Use the milestones below as planning checkpoints, not universal legal deadlines. A small program may need less time, and a cross-border program with disputed claims may need more. The project manager should publish the register version and exception count at each gate. If an irreversible action lacks evidence, move that action rather than silently changing the policy date.
-
By the first checkpoint, sponsor signs scope, policy authority, dates, and exception owner; operations and finance agree source totals.
-
Inventory owner confirms every warehouse and supplier location, title, committed units, and returns tail.
-
Finance classifies each funded balance, credit, refund, invoice, and expected supplier credit under approved policy.
-
Support tests each localized notice, claim link, escalation route, and failed-delivery fallback before broad sending.
-
At the next checkpoint, operations freezes only the appropriate new activity; accepted orders and authorized claim routes remain serviced.
-
Privacy owner approves the data map, access reduction, retention decisions, vendor requests, and evidence method.
-
At the final checkpoint, each exception is resolved or transferred to a named owner with a dated review; ledgers and stock reconcile.
-
Sponsor signs the closure packet, and support publishes an enduring contact route for late claims and returns.
Keep a single change log for decisions that alter the original plan: what changed, why, who approved it, which recipients or contracts it affects, and what notice is required. Conduct a tabletop test with one claim, one return, one refund, one deletion request, and one disputed balance. If the team cannot locate the owner and evidence for any of those in a few minutes, the exit design is not ready. After cutover, watch the tail queue rather than assuming activity stops on the milestone date.
Choose an execution route without outsourcing accountability
A business can run the tail manually, extend its current vendor for a limited period, or move eligible claims to a successor provider. Compare them against the same criteria: entitlement fidelity, recipient experience, country reach, shipment visibility, financial reconciliation, data-return or deletion evidence, cost of the tail, and support continuity. Manual handling can suit a small low-variance queue but is fragile without dual review and a register. A short vendor extension can preserve order context but may cost more or delay data closure. A successor migration can simplify long-term operations yet creates matching and consent questions. No route is automatically best.
Giftpack may be assessed as a gifting execution option where its verified current service and contractual scope fit the remaining claims. It should be evaluated against the same evidence and test cases as any incumbent or alternative, not ranked first by default. The business sponsor still decides entitlement policy; finance owns balances and accounting; procurement owns contract changes; privacy and counsel decide lawful data treatment. Do not represent an operational gifting tool as a substitute for those decisions, or promise a specific integration, refund function, or compliance certification without verified documentation.
Run one pilot case through the chosen route before broad transfer: a straightforward valid entitlement, a disputed claim, a cross-border shipment if in scope, and a late return. Confirm the actual recipient message, funds movement, fulfillment trail, support handoff, and data records. Record failed tests and a rollback or alternate remedy. The strongest option is the one that can close the actual obligations with verifiable evidence, not the one with the most reassuring sales language.
Close only when the obligations have owners and evidence
A defensible sunset ends with a signed closure packet: scope and terms versions; final register and exception transfers; invitation and order disposition; inventory counts and movements; finance reconciliation; recipient communications; data-retention and disposal decisions; vendor confirmations; and a support path for late claims. The packet should tell a future reviewer where the source evidence lives and who may access it. It need not include unnecessary recipient details in a broadly shared folder. Reopen a line when a late return, credit, or recipient claim shows the prior closure was incomplete; preserve the original decision history instead of quietly rewriting it.
If the team is considering Giftpack for any remaining gifting execution, use the same closure register and a bounded pilot to test its fit. Giftpack can support an operational discussion; it does not decide refunds, legal retention, tax treatment, or employer obligations. The durable result is not a disabled portal. It is a program whose commitments can still be explained, honored or resolved, and evidenced after the original team has moved on.