On this page
Black Friday is Friday, November 27, 2026. Cyber Monday is Monday, November 30. Use the dates below as completion deadlines, subject to your store’s earlier freeze.
By Nov 6: agree the warehouse release rule
Ops/fulfillment owns the warehouse agreement. Get the import trigger and the last point for stopping a pick in writing. Record the final inbound receiving date, the same-day dispatch cutoff and the treatment of orders above the daily cap. Ask the 3PL to name its weekend escalation contact and agree a response deadline for each physical stage. Base the customer promise on the 3PL’s written deadlines.
Ecommerce/dev owns the release condition and agency owns the connector wiring. Use the 3PL edit-window implementation guide to establish whether the warehouse waits for a Shopify hold to lift or for a release tag.
CX owns the wording sent to customers. Promise a completed correction only after the corrected order is released to the warehouse. Give requests outside the edit window to the named ops operator.
Ecommerce/dev audits every hold-release automation. Shopify’s fulfillmentOrderReleaseHold mutation releases every hold on that fulfillment order when holdIds is omitted. Identify the hold each automation releases, and its owner, before approving it for peak.
If you are reading after November 6, ops must document the existing release behavior before accepting change promises. If your freeze has started, route configuration changes through the Level 3 freeze exception. Keep uncertain orders in the manual warehouse-stop process.
Set Revize’s edit deadline before peak
Ecommerce/dev configures Revize with ops/fulfillment’s approval. Open Order editing > Editing policy > Edit deadline and choose a timed window that fits the warehouse agreement and your dispatch commitment. Decide before peak orders are placed, because each order keeps the deadline it got at creation. A metafield-date deadline is the exception, since it can refresh while editing remains open. Record which mode you use before an incident.
For context, among committed address, contact and delivery edits from Revize customers, the median interval from order placement to edit commit is 4.6 minutes (Revize, 2026). On the same basis, 80.6% land within the first hour and 90.4% within 24 hours (Revize, 2026).
Under Fulfillment while editing, choose Hold orders for a warehouse that respects Shopify holds, or Skip hold with Add release tag for one that picks only orders tagged revize:order_released, as the setup guide explains.
A stop tag registered under Settings > Order editing > Editing restrictions > Order tags closes customer editing and can release Revize’s own fulfillment hold. During an incident, ops pauses warehouse work through the warehouse’s agreed process.
Check plan entitlements before setup. The per-order rules engine requires Pro or above, and shipping and tax recalculation on address edits requires Pro. For a peak-only rule, tag peak orders and match that tag in a rule, because the rules engine has no calendar date-range criterion. Build and test the Shopify Flow workflow that tags peak orders before the freeze. Tag-based rules re-match when tags change.
Nov 13-20: rehearse the handoff
Agency and ops/fulfillment jointly own the rehearsal. Follow the four ingest tests with the current admin paths above. Inspect the warehouse record at import, after the change and at release. Save the Shopify order and the warehouse record at each point.
Add a cancellation request after the fulfillment service accepts the original request. Ops records whether the service accepts the cancellation and whether warehouse work stops. Shopify says requesting fulfillment blocks order edits and item refunds. After the warehouse reports a physical stop, CX still waits for the fulfillment service to resolve the request and for Shopify to permit editing before changing the order, even for a simple size swap.
Ecommerce/dev owns the additional-payment rehearsal. Add an item to a test order through Revize (adding products is a Pro feature), leave the balance unpaid, and include that order in the warehouse’s release checks.
CX rehearses the declined-change response. Load the native Shopify editing limitations into the support reference instead of promising that every unfulfilled order is editable.
If you are reading after November 20, rehearse the existing route before expanding self-service. If a change type has no proven warehouse route, CX sends it to ops for manual handling. Respect any freeze already in force.
Change type and warehouse state
CX owns intake. Ops owns warehouse instructions once the order is released to the warehouse. Use this table during peak, including for requests that arrive after the customer window closes. This table covers unfulfilled orders only. Before editing, resolve any fulfillment request and confirm Shopify permits the change. For orders not yet sent, ops blocks export until the change is finished.
| Change type | Unfulfilled, not sent to 3PL | Sent to 3PL, not picked |
|---|---|---|
| Address | CX corrects the shipping address; ops releases the corrected order. | Ops blocks the imported job. CX edits once any fulfillment request is resolved, and the warehouse updates its destination before release. |
| Variant swap | CX checks replacement stock and swaps the variant before export. | Ops stops the job. CX edits once any fulfillment request is resolved, and the warehouse replaces its line. |
| Quantity down/remove | CX reduces the line and handles any refund; ops releases the corrected order. | Ops blocks the job. Once any fulfillment request is resolved, CX edits and refunds, and the warehouse removes the units. |
| Add item | CX adds the item and collects any balance; ops releases the corrected order. | Ops asks whether the warehouse can amend the job. If it can, CX edits once any fulfillment request is resolved, and ops reconciles units and payment before release. If it declines, CX offers a separate order. |
| Cancel | CX cancels the eligible order and handles the refund; ops prevents export. | Ops requests cancellation and waits for service acceptance plus a warehouse stop. CX then completes the cancellation and refund. |
Once picking starts, ops takes the case and follows the warehouse stage procedure for Picking, Packed and Shipped orders, including its stop request and reconciliation checklist. Agree provider-specific exceptions before peak.
Nov 23-26: assign alerts and freeze changes
Ecommerce/dev owns integration alerts, with agency as the named backup. Track orders held beyond their deadline, unpaid balances, unexported orders and failed webhook deliveries. Give each queue a named responder and an escalation deadline agreed with ops.
For HTTPS webhooks, Shopify fails a delivery if the app does not respond within five seconds. Shopify retries failed deliveries up to eight times over four hours, and persistent failures remove subscriptions configured through the Admin API. Agency records how each subscription is configured and how missing orders are recovered.
If an integration depends on orders/edited for address-only changes, agency must inspect its API version. Before API version 2026-10, an order-edit commit containing only a staged shipping-address update does not emit orders/edited. From 2026-10, that edit fires orders/edited with shipping_address.changed in the payload. Use the order-management guide for reconciliation and handler design.
Ops/fulfillment reconfirms pick waves and weekend coverage. CX publishes the actual editing cutoff and the staffed route for late requests. Ecommerce/dev freezes the rehearsed configuration, including Flow workflows that tag, hold or cancel orders, as Taylor Sicard’s freeze guidance recommends.
If you are reading after November 26 and a failed delivery or unexported order has no responder, assign ecommerce/dev and an agency backup to that queue now. Route any wiring or release-condition change through the Level 3 freeze exception.
Nov 27-30: run each request against the table
CX checks the requested change and current edit eligibility. Anything outside the open, protected window goes to ops/fulfillment, which checks the physical stage. Keep one ops operator responsible for each warehouse case. Use one incident record.
At each pick wave, ops reviews unresolved stop requests and orders held past their deadline. Ecommerce/dev checks the export queue and failed deliveries on the same schedule. Agency handles connector failures that the on-call developer escalates. CX sends the customer the outcome recorded by ops.
A rejected cancellation does not stop the parcel. Shopify documents that a fulfillment service can continue creating fulfillments after rejecting a cancellation. If the response is rejected or missing, keep the warehouse-stop request open until ops establishes the parcel’s position or moves the case to recovery.
If you are reading after November 30, use these rules for the remaining peak orders. Apply the December reconciliation step before returning those orders to the normal queue.
Warehouse escalation and acceptable proof
Ops/fulfillment owns the escalation roster, with a name and backup phone number at each level and the response deadlines agreed by November 6. Escalate unanswered stop requests.
| Level | Trigger and caller | Required proof and next action |
|---|---|---|
| 1: one order | CX calls the assigned ops operator. Ops calls the warehouse shift lead. | Warehouse identifies the Shopify order and WMS job, records its physical stage, and states that affected units or parcels are stopped. Ops records the responder and timestamp. Resume only against the agreed final order. |
| 2: repeated failure | Ops calls ecommerce/dev and agency on call when held orders import, release tags fail, or export failures recur. Ops also calls the warehouse supervisor. | Before clearing the incident, ecommerce/dev compares the recovered Shopify orders with the warehouse’s affected-job list and connector delivery logs. The warehouse supervisor records which jobs remain blocked and which corrected records are approved for release. |
| 3: freeze exception | Ecommerce/dev or agency calls the named ecommerce approver when recovery requires a configuration change. Ops calls the 3PL account escalation contact. | The approver records the exact change, affected orders and rollback. Ops authorizes warehouse resumption only after the changed release behavior matches the agreed process. |
Promise no change until the warehouse confirms a stop. An acknowledgment that a message arrived does not count. Record the refund decision separately from the stop evidence in the incident record. If the agreed response deadline expires, ops calls the backup contact. If the warehouse cannot stop the parcel before handoff, CX gives the customer recovery options under the store’s policy.
Dec 1-7: reconcile before reopening configuration
Ops/fulfillment and ecommerce/dev own the remaining-order review. Match unexported orders against warehouse receipts. Inspect overdue holds and unresolved cancellation requests.
CX checks that each case has a customer response and an owner for any refund or return. Agency reconciles orders missed during connector failures before declaring the queue cleared. Do not bulk-release holds to make the queue disappear.
Ops reviews cancellations alongside peak sales with the cancellation reporting guide before reporting results.
If you are reading after December 7, reconcile the remaining exceptions before scheduling deferred configuration work. Preserve the original incident record alongside the financial outcome.
Support replies for peak
Can we change Revize’s edit window in the middle of peak?
Treat it as a Level 3 freeze exception. CX checks each order’s assigned deadline before promising an earlier release.
A customer added an item but hasn’t paid the difference. Will the order ship?
Revize sends the customer to Shopify checkout to pay the difference, and unpaid additions remain on fulfillment hold until Shopify confirms payment. Cash-on-delivery orders are the exception. The hold stops shipment only if the warehouse respects Shopify holds.
Why do Shopify reports show more orders than we took during peak?
Shopify lists an edit made after the order-placement day as a separate order in reports, even though no new order was created. Account for those late edits before comparing report order counts with warehouse shipments.
The order is partially fulfilled. Can CX still cancel it?
No. Shopify does not allow canceling a partially fulfilled order. Route the unfulfilled units through ops and the service’s supported process, and tie any return or refund to the units involved so CX does not promise to cancel a parcel already handed to the carrier.