When the person running your company store leaves, transfer the decisions and unfinished work—not just the login. Name an accountable successor, confirm the provider recognizes their authority, reconcile open commitments, and have the successor run a realistic handover exercise before treating the transition as complete.
A storefront can keep accepting orders while its operating knowledge disappears. The missing detail may be who can approve a replacement jacket, which invoice is disputed, or whether a holiday campaign has already committed its budget. Those gaps are easy to miss in a folder of product images.
This guide answers a specific continuity question: how can a new owner operate the existing program without relying on the previous owner? It is not a provider migration or a platform rebuild. The objective is to preserve normal service while changing who is responsible.
Publisher perspective: Brand Sauce publishes this suggested operating framework as a company-store provider. The handover records and exercises below are recommendations, not claims about included platform features or service levels. Confirm transition support, permissions and any fees with your provider. Primary references were checked October 26, 2026.
Separate four kinds of ownership
“The new store owner is Maya” sounds clear until Maya discovers that she can edit products but cannot authorize spending. Write down the four responsibilities separately, even if a small team assigns several to the same person.
| Responsibility | What must transfer | Evidence of acceptance |
|---|---|---|
| Program ownership | Purpose, eligibility, campaign calendar and exceptions | Successor can explain what is active and what is deliberately paused |
| Commercial authority | Budget approval, contract contact, billing escalation and renewal decisions | Finance and provider recognize the new approval route |
| Day-to-day operation | Order support, artwork routing, assortment changes and reporting | Operator completes representative tasks using their own access |
| Technical custody | Domain, integrations, account recovery and protected configuration | IT confirms named custodians and a working support route |
A provider may handle production and fulfillment while your company still decides who is eligible and what a campaign may spend. Conversely, an internal coordinator may own the calendar without being authorized to amend the contract. Do not infer authority from job title or familiarity with the supplier.
Give each responsibility a primary owner and an available alternate. An alternate does not need unrestricted access to everything; they need a documented way to cover the relevant work. Use our company-store permissions guide for the separate question of what each account should be allowed to do.
Decide what must keep moving
Start the handover with a short continuity brief. List the next campaign, the next payment decision, the oldest unresolved order, and the next contractual or domain-related date that requires action. Ask what happens if each is ignored for one working day, one week and one month. These are discussion intervals, not promised service targets.
NIST's contingency-planning guidance describes evaluating systems and operations to establish contingency requirements and priorities. We apply that general planning principle here to a narrow merchandise-program handover; this checklist is not a NIST certification or a substitute for your organization's continuity plan.
Put time-sensitive recipient problems ahead of optional improvements. An address correction before production or a replacement needed for a scheduled induction may deserve immediate attention. Redesigning the collection page usually does not. Record the actual provider cutoff and escalation route instead of assuming the new owner has time to learn it later.
Build a handover packet people can use
A useful packet is a small index linking to controlled records, not a giant export of every employee's information. Include an owner, last-checked date and authoritative location for each section. Where sensitive records are necessary, link to the restricted system instead of copying them into the general handover document.
- Program rules: eligible groups, allowance logic, campaign dates, permitted exceptions and the person authorized to change each rule.
- Approved assortment: current products, decoration approvals, pending substitutions and items scheduled for retirement.
- Commercial record: current agreement, renewal notice requirements, approved purchase orders, payment route and unresolved charges.
- Service route: provider contacts, support entry point, escalation sequence and the information required to investigate an order.
- Decision log: open choices, who must decide, deadline, supporting evidence and what happens if no decision arrives.
- System map: store address, reporting locations, integration owners and organization-approved access-recovery process. Do not put passwords or recovery codes in the packet.
For example, an artwork file called “final-logo-new” is not enough. Link the approved version to the affected product and record whether the approval covers placement, thread colors, print size or all three. The successor should not have to reconstruct a production decision from informal messages.
Choose an organization-controlled document location. Google explains that files in Workspace shared drives belong to the team rather than an individual and remain when members leave. That is a useful ownership distinction, not a requirement to use Google. Check the access and licensing arrangements of your chosen repository, and verify the actual files are available to the successor—not merely shortcuts to material they cannot open.
Reconcile unfinished work at a defined cutoff
Take a dated snapshot of commitments immediately before the handover. The snapshot is a starting balance, not a replacement for live order records. Orders may continue changing while you review it, so keep a small change log for activity after the cutoff.
| Queue | Handover record | Question the successor must answer |
|---|---|---|
| Orders in progress | Order reference, current stage, next action and responsible party | Which orders need a decision rather than passive monitoring? |
| Recipient support | Case reference, latest promise and next contact date | What have we already told the recipient? |
| Money | Approved commitments, unpaid invoices, disputed items and expected credits | What is available to spend without counting pending credits as cash? |
| Campaigns | Invitations issued, deadlines, unredeemed eligibility and outstanding exceptions | Which promises remain valid after the owner changes? |
| Physical stock | Location, custodian, approved artwork version and usable quantities | What can actually be issued, and who can release it? |
Illustrative example—not client data: a program has an approved $8,000 campaign budget and $5,200 in committed orders. A $300 credit is expected but not yet posted. Its uncommitted amount is $2,800 before any other obligations, not $3,100. Finance should confirm how taxes, shipping and cancellations affect that record. The point is agreement on the starting position, not a universal accounting method.
Have the outgoing and incoming owners review exceptions together where possible. A supposedly duplicate order may be an approved replacement. A low redemption count may reflect a deliberately staggered invitation schedule. Preserve the reason, not just the number. For the underlying financial check, see our invoice reconciliation guide.
Transfer authority through the proper channels
Ask the provider what evidence it requires to change the authorized contact. Complete that process before relying on the successor's first urgent request. Confirm who may approve product changes, incur charges, request reports and authorize a pause. Keep written confirmation in the packet.
The successor should use their own authorized account. Do not make continuity depend on the former owner's email session, personal phone or shared password. IT should coordinate identity changes, recovery arrangements and any integration dependencies under the organization's normal process. A working login proves access; it does not prove that billing notices or support escalations now reach the right person.
For planned departures, schedule a short overlap and a clear transfer time. For unexpected absence, name an interim decision-maker and use established account-recovery and provider-verification routes. Do not postpone required access removal simply because the handover is incomplete. Restrict optional changes until authority and records are established, while keeping essential recipient support moving.
Run a successor-led continuity exercise
The outgoing owner should observe rather than drive. Use a test environment or safe read-only walkthrough where possible. If a live test would place an order, spend funds or contact a recipient, arrange the appropriate internal authorization first. A hypothetical case can test judgment without creating an actual shipment.
- Find an approved item. The successor locates its artwork decision and identifies who can approve a requested change.
- Trace an unfinished order. They identify the current stage, next action and provider support route without asking where the record lives.
- Handle a hypothetical exception. A recipient requests an alternative after a product disappears. The successor identifies the decision-maker and the rule, rather than inventing a new promise.
- Explain the budget. They reconcile one commitment and one unresolved credit to the handover snapshot.
- Find the next deadline. They locate the next campaign close, invoice action or renewal decision and identify an alternate if unavailable.
- Recover the operating instructions. They open the packet from their own account and demonstrate that the necessary linked documents are accessible.
Record each result as passed, blocked or not applicable, with evidence and an owner for any repair. “We walked through it together” is weaker than “the successor found the order, explained the next step and identified the authorized approver.” Repeat only the failed steps after fixing them.
Adapt the packet to on-demand, bulk or hybrid programs
On-demand fulfillment removes some finished-stock counting, but it does not remove artwork, spending or service decisions. Transfer which products are approved for individual ordering and which exceptions require separate quotes. Do not assume all products or destinations share the same arrangement.
A bulk program may be the practical choice for a known event quantity and fixed distribution date. Its handover needs warehouse contacts, stock counts, reserved quantities and release instructions. A spreadsheet balance without a physical custodian is not sufficient. For hybrid programs, label which items are made after selection and which ship from existing inventory; otherwise the new owner may promise the wrong lead time or reorder stock that already exists.
The handover should preserve the program's chosen operating model until there is evidence to change it. An ownership change is not, by itself, a reason to replace bulk with on-demand or move providers. If a provider change really is necessary, use a separate store migration plan.
Close with acceptance, not a farewell meeting
Use a short acceptance note: effective date; named program owner and alternate; provider acknowledgment; location of the packet; cutoff for the commitment snapshot; exercise results; and unresolved items with owners and due dates. A handover can be accepted with a clearly bounded exception, but an unknown budget or unverified authority should not be waved through.
Schedule the first review around meaningful events: the next order-support case, next invoice and next campaign decision. Check that notices arrived correctly and that open issues actually moved. Update the packet after those events so it reflects how the program works, not only how it was described during the transition.
Questions about company-store handovers
Does a managed store eliminate the need for an internal owner?
No. Confirm the provider's responsibilities, but retain an internal authority for eligibility, budgets, brand approvals and exceptions. Outsourcing tasks does not tell the provider who can make your company's decisions.
What if the outgoing owner is already unavailable?
Appoint an interim owner, establish authority through existing organizational and provider processes, and reconstruct the current state from authoritative records. Start with open orders, money and upcoming deadlines. Mark unknowns explicitly rather than presenting assumptions as settled history.
Should every handover trigger a store shutdown?
No. If authorized support, funding and fulfillment remain intact, routine ordering may continue. Pause only the affected activity when a material dependency is unresolved, such as a campaign without an authorized budget owner. Explain the pause to the relevant internal stakeholders.
What is the simplest test of a successful transfer?
The successor can handle the next ordinary decision using their own access and the documented rules, while the alternate knows how to cover an absence. The program no longer needs the previous owner to explain where everything is.
