Close a company-store campaign at a specific instant, not at an unexplained “midnight.” Choose either one shared cutoff or separate recipient-group cutoffs, state the date and time zone, and test what happens when a checkout crosses the boundary. The invitation, storefront, benefit rules and order records should all describe the same decision.
This matters when employees work across regions, travel during a campaign or select a gift near a daylight-saving change. A clear deadline can still fail if a banner uses headquarters time while a discount uses another setting. The operational question is not simply when to close. It is which event counts as on time, which clock decides, and how to resolve a disputed order.
Brand Sauce publishes this guide and provides company-store services. The controls below are recommended acceptance criteria, not a statement that every platform or Brand Sauce configuration supports them automatically. Confirm implementation and any additional service costs in your scoped proposal. Official sources were checked October 24, 2026.
Choose one shared instant or a local deadline for each group
A shared instant is usually the simpler operating model for a single production batch. Everyone loses access to the campaign benefit at the same moment, although their local clocks show different times. A group-local deadline gives employees the same wall-clock closing time in their assigned region, but the campaign remains open across multiple instants.
| Model | Good reason to use it | Control you need |
|---|---|---|
| One shared cutoff | One consolidated approval or production handoff | Clear headquarters-zone wording and accurate local equivalents |
| Separate regional cutoffs | Comparable local access windows for distributed teams | Fixed group assignments and a separate closing record per group |
| Individual rolling windows | New-hire invitations issued throughout the year | A defined start event, duration rule and individual deadline |
Do not promise “Friday evening for everyone” while configuring one global Friday deadline. Conversely, do not assume a local display changes the underlying rules: showing an employee a converted time is different from granting that employee a different closing instant.
For a regional model, assign the group from an agreed program record, such as the employee’s work location at invitation. Decide how a transfer will be handled. Avoid silently changing eligibility because a traveler opens the store from a hotel or their browser reports a different zone. The local display can follow their device; the entitlement should follow the published policy.
For rolling windows, settle another ambiguity: does “seven days” mean exactly 168 hours from invitation, or the same local clock time seven calendar dates later? Around clock changes, those definitions can diverge. Either may suit a program, but the system, reminder and support team must use the same definition.
Create one deadline record that every message uses
Give each campaign a compact closing record. It should contain the campaign identifier, eligible group, named time zone, human-readable deadline, equivalent UTC instant, completion event, exception owner and production-release dependency. Treat the UTC value as an implementation and audit reference; employees should not need to understand it to select a gift.
The IANA Time Zone Database maintains location-based time-zone rules and is updated for changes to boundaries, offsets and daylight-saving arrangements. Ask the provider to use maintained time-zone data for conversions. A fixed offset copied from last season is not a substitute for the rules that apply on this campaign’s actual date.
NIST’s daylight-saving guidance explains that, in U.S. locations observing the change, the autumn transition repeats an hour and the spring transition skips an hour. Its published 2026 dates are March 8 and November 1. Our operational recommendation is to avoid scheduling a closing boundary inside a clock-change hour. A well-supported afternoon cutoff is easier to explain and troubleshoot.
Use a named location-based zone in the setup record, such as America/Chicago, rather than relying only on an abbreviation. In recipient copy, spell out the date and identify the reference location. If you include a numeric UTC offset, calculate it for the deadline date, not the day you draft the email.
Illustrative campaign wording: “Complete your gift order before 5:00 p.m. Chicago time on November 6, 2026. That is 23:00 UTC. Adding an item to your cart does not complete your order. Contact the program help desk before the deadline if checkout is not working.” This is example copy, not a live Brand Sauce campaign or a delivery promise.
Specify what closes: the store, the benefit or the batch
These are different switches. A store may remain available for employee-paid purchases after an employer-funded selection campaign ends. A benefit can expire while product pages remain visible. A batch can stop accepting orders while a separate on-demand assortment continues operating.
Shopify’s official discount FAQ, for example, says a configured discount expiry uses the end date and time in the admin’s displayed time zone. It also describes rollout settings that can affect a discount’s effective status. This is a specific platform example, not a claim about every company-store system. Check the effective behavior of the complete configuration, not just one field labeled “end date.”
| Boundary | Decision to document | Recipient experience to test |
|---|---|---|
| Campaign benefit | When employer funding stops applying | Expired funding is explained before any employee-paid order is confirmed |
| Ordering access | Whether products remain orderable afterward | Closed selection does not look like a broken store |
| Production batch | Which accepted orders enter the export | On-time pending orders have a stated review route |
| Support exception | Who may approve a late selection | Help instructions remain available after closing |
A funded cart must not become an unexpected personal purchase. If your program permits employee-paid orders after closing, make the changed total and payment responsibility unmistakable and require the normal explicit checkout confirmation. Test a cart created before closing and reopened afterward, not only a fresh visit.
This is a campaign-operations guide, not a rule for expiring purchased gift cards, earned compensation or other regulated balances. Keep those instruments out of the campaign-code design until their applicable terms have been reviewed separately.
Define the event that counts as on time
Choose an event your system can actually record and your operations team can verify. “Started shopping” is difficult to adjudicate. “Order accepted with an order identifier before the cutoff” is more concrete, but still requires a policy for payment delays, manager approvals and failed submissions.
For an employer-funded order with no personal payment, order acceptance may be enough. For a paid upgrade, decide whether the relevant event is submission, payment authorization or another documented status. Do not announce that payment must be complete if the system grants eligibility at submission. Do not promise that a submitted order is secure if a later payment failure can remove it.
Ask the provider to explain boundary precision. Does an end time of 17:00 mean closing at the start of that minute, or after it? Is the comparison inclusive? Write the employee instruction to match the observed rule. A countdown reaching zero is not evidence that the checkout engine enforces the same boundary.
Use the authoritative order or eligibility record to adjudicate timing. An email arrival time can be later than order acceptance, and a screenshot of a cart does not establish a completed order. Retain enough timestamp detail to distinguish the original acceptance from a later status update or retry.
For approvals, separate recipient timeliness from internal processing. An employee should not be classified as late merely because their manager reviewed an otherwise valid submission the next morning, unless the program clearly requires completed approval before closing. Set an internal review deadline and keep the affected order visible until resolved.
Run a boundary test, not just a normal test order
Set up a short test campaign or equivalent safe test environment with the same eligibility and closing configuration. Record expected and actual outcomes. Do not change production clocks or live employee entitlements to simulate the test.
- Before closing: an eligible test recipient completes an order and receives the correct funded total and order identifier.
- Across closing: a cart opened before the deadline is submitted afterward. The result matches the written rule.
- At the boundary: the provider demonstrates the configured precision and inclusive or exclusive comparison.
- After closing: a fresh visit and a saved direct checkout link both receive the intended outcome. A stale banner does not restore eligibility.
- Different display zones: the same shared deadline appears as equivalent local times without changing eligibility. Regional campaigns follow their assigned groups instead.
- Unfinished processing: a pending payment or approval is classified correctly without granting another benefit or dropping a valid order.
- Reopening: an approved exception works only for its intended scope and does not reset completed recipients’ usage limits.
Test mobile as well as desktop. Keep the closing date in ordinary readable text; do not make a countdown the only source of information. Check the final reminder against the actual configuration and cancel reminders for people who have already completed their selection.
Keep exceptions separate from reopening the whole campaign
Plan for a verified checkout outage, an accessibility barrier or an employee who was added to the wrong group. Those are different from a routine late request. Give support a small classification list and an owner who can approve the appropriate remedy.
Before issuing an exception, check for an accepted order and any unresolved transaction. Then record the original deadline, reason, affected recipient, approved remedy and new deadline. Use a narrowly scoped extension or replacement invitation where supported. A global extension may be necessary after a broad outage, but it should be a deliberate program decision with a duplicate-order check.
Do not reopen a production batch by implication. If the batch has been released, a late order may need a separate production route, a different delivery estimate or a substitute assortment approved by the employee. Explain that before accepting the selection. Our delivery-deadline planning guide covers the separate work of checking production and transport commitments.
On-demand production can make an individual late order operationally feasible, but it does not remove funding, availability or delivery constraints. Bulk remains useful when a fixed group and shared event justify one committed batch. A hybrid program can keep a small late-selection assortment open without changing the main batch. Compare the actual extra production, shipping and handling charges; do not assume that a second route is free or cheaper.
Close with a reconciliation, not a screenshot
At closing, reconcile accepted orders, pending transactions, unresolved approvals and approved exceptions. Save the configured cutoff and its zone alongside the export time. An export created at closing is only a snapshot; determine how later status changes will be added without duplicating orders already sent downstream.
Use a simple release gate: the campaign owner confirms eligibility, support classifies unresolved cases, and the production owner accepts the final order set or documented pending list. Leave the help route accessible even when the gift-selection route closes.
If you are still deciding whether the store should close at all, start with preorder versus always-on company stores. If the problem is a large unresolved recipient list, use the unredeemed employee gifts playbook to diagnose the cause. Neither problem is solved merely by changing a timestamp.
Frequently asked questions
Should we close at midnight?
Only if midnight has a clear date, zone and tested meaning in the platform. A staffed closing time can make last-minute support and reconciliation easier. Choose around the audience and production handoff, not an unexplained default.
Should every employee receive the same local deadline?
That can be appropriate for regional campaigns, but it creates multiple closing instants. Use fixed group rules and do not release a consolidated batch until all included groups have closed or their orders are explicitly excluded.
Does a saved cart preserve the employee’s gift allowance?
Do not assume so. Document and test the actual eligibility event. Tell employees whether a completed order is required and how to get help if checkout fails before the cutoff.
Can we extend the deadline after the campaign closes?
Only after checking the platform’s behavior, original usage records and production status. Record the extension’s scope and confirm that already completed orders cannot claim the same benefit again. A support exception and a reopened production batch are separate approvals.
