Let a helper prepare an employee gift order, but give them only the authority the recipient actually granted. Explaining a size chart, entering a selected item and committing an order are different jobs. A practical assisted-order program separates them, preserves the employee’s own choice and leaves a clear record of who approved the final details.
This matters when employees cannot conveniently complete checkout themselves: a deskless team member may need a scheduled support session, someone may want help navigating the store, or an employee may explicitly ask a coordinator to submit a particular selection. None of those situations automatically authorizes a manager to choose a gift, spend a balance or reuse an old home address.
Brand Sauce publishes this guide from a company-store provider’s perspective. The workflow below is our recommended operating model, not a claim that every platform—or Brand Sauce implementation—includes delegated ordering. Official platform examples were checked October 20, 2026. Confirm the configured behavior and service scope with your provider.
Choose the assistance level before opening the order
The useful question is not simply whether an administrator can place orders. It is which decisions remain with the employee, which actions the helper can perform and where the process must pause. Use three assistance levels rather than a single “order on behalf” permission.
| Mode | Helper’s job | Employee’s role | Release condition |
|---|---|---|---|
| Guided self-service | Explain options and navigation | Select, enter private details and submit | Employee completes the normal confirmation |
| Prepared order | Build a draft from the employee’s instructions | Review, correct and complete it | Recipient confirms the final version |
| Delegated submission | Submit a specifically authorized order | Approve the item, variant, destination and funding terms | Authorized helper submits within that scope |
Start with the least authority that solves the problem. Someone who needs help finding the measurement guide may still prefer to enter their address and complete the purchase privately. A helper should not take over the whole transaction merely because the first step was difficult.
Assistance is also not a replacement for a usable storefront. If several people repeatedly need help with the same inaccessible control, log and fix that problem. Our accessible employee gift-selection guide covers testing the broader journey; this guide focuses on the boundary between helping and acting for someone.
Create a short, order-specific authority record
Before a helper submits anything, establish who asked for assistance through the organization’s normal verified support route. A forwarded screenshot of a gift invitation is not a complete instruction. Nor is a manager’s statement that a team member “will probably want a large.”
Use a restricted support record with the following fields. Keep sensitive fulfillment details in the approved order system where possible, and reference that record instead of duplicating addresses across spreadsheets.
- Recipient and campaign: the intended employee and the specific gift entitlement.
- Named helper: the person allowed to prepare or submit the order.
- Permitted action: guidance, preparation only, or final submission.
- Approved selection: exact item, color, size, quantity and personalization, if any.
- Destination confirmation: reference to the delivery details reviewed for this order.
- Funding boundary: employer-funded amount, any employee-paid difference and who completes payment.
- Validity and changes: when the authorization ends and which changes require another review.
- Outcome: final order reference or a clear not-submitted status.
This is an operational record, not a request for an employee’s medical history or a legal template. “Requested assistance with checkout” can describe the service need without collecting a diagnosis. Your organization’s privacy and retention rules should govern access and deletion.
For a recurring program, do not turn one successful order into permanent permission. A winter jacket authorization does not authorize the helper to choose next year’s gift, spend unused funds elsewhere or update the employee’s account profile.
A draft is a handoff tool, not proof of recipient approval
Some commerce platforms have useful preparation tools. Shopify’s draft-order documentation describes creating an order on a customer’s behalf, including products and customer information, and saving it as a draft or sending an invoice. That establishes a preparation capability; it does not establish an employee-gifting permission model or entitlement control.
Ask your provider to demonstrate the actual employer-funded path. Can a coordinator prepare an order without consuming the employee’s allowance? Can the recipient change it before approval? Does the final record distinguish the recipient from the administrator who performed the action? If the answers depend on a manual support process, name that process and its owner.
Shopify’s invoice guidance also describes handing a checkout link to the customer to complete the order. Treat this as a platform example, not a recommendation to send an employee a payable invoice for a fully funded gift. Test the wording, amount due and confirmation path in your configuration before using it.
The recipient should understand whether they are looking at a proposed selection or an accepted order. Suggested draft wording is: “We prepared the item you requested. No order has been submitted. Please review the selection and delivery details before confirming.” Use that wording only when it is factually true.
Review the exact version that will be submitted
Build one final summary with the product name, variant, quantity, decoration or personalization, destination, amount due from the employee and any relevant fulfillment estimate. Let the employee correct it before release. A photograph of a navy jacket is not enough if the underlying order says black, medium.
W3C’s review-and-correct technique G98 describes providing a way to review information before committing a transaction, including a summary and correction mechanism. It is an example technique, not the only way to meet accessibility requirements. We recommend the same review pattern for assisted gift orders because the helper may have misunderstood an instruction.
Keep the approval attached to that version. If the size becomes unavailable after review, stop and request a new choice; do not silently substitute a different fit. If the employee changes the delivery destination, recheck the applicable shipping service and total. For personalization, show the literal spelling, including punctuation and capitalization, rather than asking whether “the name looks right.”
An employee-paid upgrade needs a separate payment boundary. The helper can prepare the choice, but the employee should complete any required personal payment through the approved secure flow. Do not ask them to send a card number or account password to the coordinator.
Keep assistance from creating a second redemption
A prepared order creates a coordination problem: the employee may still have an active invitation and may continue shopping independently. Before submission, check the campaign record for an existing order and any other open assistance request. Use the same recipient-and-campaign reference throughout, rather than treating the helper’s email address as a new gift recipient.
Agree with the provider how the final submission updates the entitlement. If a helper’s administrative order bypasses normal redemption controls, a manual reconciliation step may be necessary. Do not assume the presence of a draft means the invitation has been disabled or that funding has been reserved.
After successful submission, record the order reference, close the preparation request and explain what the original invitation now does. If submission fails, record whether no order exists or the outcome is still unknown. An uncertain result is a reason to investigate before trying again, not to create another order immediately.
For the underlying identity and repeat-import problem, see our duplicate employee-gift prevention guide. The additional issue here is that a human helper and the recipient can act on the same entitlement at the same time.
An illustrative handoff with a deliberate stop
Consider a hypothetical employee who asks a coordinator to order a navy fleece in medium, delivered to the office. The employee authorizes that exact selection and asks for no personal spending. The coordinator prepares a draft and sends a private summary through the approved support route.
Before release, the supplier reports that medium navy is unavailable but large navy is available. The correct status is “awaiting a new selection,” not “equivalent item approved.” The employee’s original authorization covered a specific size, not any available fleece.
The employee then chooses a backpack within the funded allowance. The coordinator replaces the draft item, rechecks the total and obtains confirmation of the revised summary. Only then is the order submitted and its reference attached to the assistance record. These are invented circumstances to illustrate the decision rule, not a client story or measured result.
The useful control is the pause between a material change and submission. It protects choice without requiring the employee to repeat the entire support conversation.
Apply the same authority boundary to bulk and on-demand
On-demand production may suit individual assisted orders arriving throughout the year, but it does not remove the need for exact variant approval or make a decorated item easy to change after release. The helper must know the agreed change cutoff, not infer it from an editable screen.
Bulk or hybrid programs can be more appropriate when a team has a fixed distribution date, approved finished stock or consolidated delivery. A coordinator can collect individually confirmed selections and release a batch. Keep the employee-level choice records connected to the batch so that a total of 40 jackets does not erase who approved each size.
If stock is scarce, explain whether a prepared selection is actually held. If it is not, prepare a route for fresh choices before the batch closes. Never use the convenience of one bulk purchase to turn unconfirmed selections into recipient-approved orders.
Run five handoff tests before offering the service
- Preparation-only test: a helper creates a draft but cannot accidentally describe it as submitted. The employee can review the exact proposed details.
- Material-change test: change a size or destination after approval. The process requires a fresh review rather than reusing the old confirmation.
- Parallel-order test: let the employee submit while the helper has a draft open. Confirm that the second attempt is caught or routed to review before another release.
- Privacy test: verify who receives messages and sees the address. A manager should not become the default recipient of private fulfillment details merely because they requested help.
- Failure test: interrupt the final handoff. Staff can determine whether an order exists and recover without spending the entitlement twice.
Record observed outcomes, the responsible owner and any unresolved limitation. A documented manual procedure can be acceptable for a small program; an untested promise of automatic delegation is not a substitute.
Frequently asked questions
Can a manager choose for an employee who has not responded?
Not merely because the invitation is unanswered. Treat nonresponse separately from permission to act. Offer the campaign’s normal reminder or exception path. Our unredeemed gift playbook covers that decision without treating silence as a selection.
Does assistance require sharing the employee’s login?
No. Use guided self-service, a properly permissioned administrative path or an approved support workflow. Sharing credentials makes it harder to distinguish the helper’s actions from the employee’s and is not necessary to define a delegated order.
Who receives the confirmation?
Set this explicitly. The employee should have an accessible way to receive the outcome and request help. The coordinator may need a restricted operational reference, but that does not mean every manager needs the full order or address.
What if the platform cannot separate preparation from submission?
Use a reviewed support record and a named release step outside the platform, if your program owner approves that workflow. For larger volumes, evaluate whether a more suitable configuration is needed. Do not call the process recipient-controlled unless the employee really has an opportunity to approve the final choice.
The release rule: one recipient, one current authorization, one confirmed selection and one traceable order. Assistance should remove friction from employee choice—not quietly transfer that choice to someone else.
