Peptide Preorders and Shipping Delays: When to Get Consent or Refund

For your covered U.S. online merchandise orders, use the applicable delay-consent procedure or cancel and promptly refund unshipped merchandise. In the hypothetical launch, a supplier slips its release date four days before 120 paid peptide orders are due, and the store's chosen plan cancels and refunds 45. Changing the product page protects neither paid buyers nor parcels already in the packing queue. A properly disclosed short first delay may use silence as consent; a further delay past an agreed definite date generally requires express agreement. The dates and exceptions matter, so classify the order before choosing a message. FTC business guide.

This guide covers shipment timing, buyer choices and refund handling for covered orders, not whether a peptide or sale is lawful. The worked examples are hypothetical. Suggested records, staff assignments and tests are operating recommendations; the cited rule supplies the requirements. State and local obligations also need consideration.

Which delay-consent procedure applies?

The first question is which deadline controls this buyer's order. The second is which kind of delay you are proposing. Classify both before selecting a customer message.

The first four branches come from the delay provisions in 16 CFR 435.2(b)(1)-(2). The prior-indefinite-consent exception is in paragraph (b)(2)(iii). These are different procedures; changing the subject line of one old email does not make it suitable for every branch.

Count an extension from the correct deadline

For a first delay, the 30-day distinction measures the proposed extension beyond the original applicable shipment deadline. It is not 30 days from the date your team sends the notice.

For example, assume a hypothetical order promised shipment by October 20. A first revised date of November 19 is 30 days later. November 20 is 31 days later. Those proposals fall on different sides of the first-delay distinction even if the notices are sent on the same day.

The usual 30-day default for an order with no stated shipment time is a separate rule. Do not combine the two into a general “60 days for every preorder” policy. A buyer given a shorter shipment promise does not lose that promise because the default period would have been longer.

Give the notice while the buyer can act

Offer the required choice within a reasonable time after discovering that you cannot meet the applicable deadline, and no later than that deadline. Explain the revised date, or the inability to give one, the right to cancel for a full and prompt refund, and a way to exercise the choice at the seller's expense. FTC business guide, delay notices.

If you have neither shipped nor provided the required notice on time, the FTC guide calls for cancellation and a prompt refund. Do not treat a late progress email as permission to keep the order open.

You can also choose cancellation and refund instead of requesting a delay. The FTC guide says to notify the buyer and send the refund within the period in which the required delay notice would otherwise have been sent.

Choose an explicit-choice policy deliberately

A store may request affirmative agreement for every delay, including a short first delay. That is an available operating approach, rather than a claim that the rule always requires affirmative consent.

Decide what non-response will do before sending the notice. State the response cutoff, its time zone and the cancellation/refund outcome. Set that cutoff to fit the applicable branch; an internal preference cannot extend a legal deadline. If you promise earlier cancellation for non-response, carry out that promise consistently.

Store the response alongside the exact notice, affected items and proposed date. A note saying “customer agreed” is not enough for the next employee to know which commitment controls. When a reply is ambiguous, ask a short follow-up while preserving the applicable deadline.

The worked launch later in this guide uses explicit choices and an earlier store-selected cancellation cutoff. It does not use the short first-delay silence provision.

Build a decision card before drafting the email

Create one short decision card for each group of orders sharing the same facts. Put the original promise at the top, followed by the properly completed order date, current carrier-custody status, notice history and proposed new shipment date. Use the buyer's purchase record as the source of the original promise. A supplier's latest forecast belongs elsewhere on the card.

Next, write the exact branch in ordinary language. For example: first delay, definite date eight days after the original deadline, store chooses affirmative agreement and earlier cancellation for silence. Another group might be further delay after a definite date the buyer expressly accepted. Those labels help staff understand why two customers receiving similar stock information need different notices.

Include the unresolved question that could change the branch. A replacement order may already carry a later agreement. A warehouse manifest may show physical carrier possession despite a stale store status. A buyer may have cancelled through support without the update reaching the order. Check those questions before a bulk send. Grouping is an efficiency choice; it does not remove the need to retain the controlling facts for each order.

Then name the person who will confirm the branch and the person who will reconcile its outcome. A founder can do both jobs in a small store. The written distinction still matters: selecting a lawful notice is a different task from checking that forty-five cancellations actually stopped forty-five shipments.

Let one fact change one conclusion

Suppose an illustrative order promised shipment on October 20 and the proposed date is November 19. That is a thirty-day extension. Move the proposed date to November 20 and the first-delay consent treatment changes. Move the notice date earlier while keeping November 20 and the extension remains thirty-one days. An earlier email does not shorten the proposed delay.

Now suppose the buyer had already agreed to October 28 after an earlier notice. A newly proposed November date is a further delay, even though it is fewer than thirty days after October 28. Counting the days correctly cannot turn a renewed notice into a first notice. Preserve the sequence of agreements so the team can explain which event controls.

Finally, suppose the warehouse prints a label on October 20 but the carrier takes possession on October 21. The label does not establish shipment on October 20 under the definition. Check physical handoff evidence. The examples isolate three different facts because each changes a different part of the decision.

Establish the dates that control each order

Treat order receipt, shipment and delivery as separate events.

A properly completed order generally combines the required payment or charge authorization with the information needed to process and ship it. A qualifying partial payment can count. Shipment means physically placing the merchandise with the carrier; creating a shipping label alone does not complete that event. 16 CFR 435.1(c), (e).

Use distinct fields for the original shipment deadline, each revised deadline and actual handoff. Preserve the original value when an order changes. Otherwise, a team member looking at the latest date may be unable to tell whether it came from checkout, a supplier estimate or a buyer's agreement.

Also distinguish the estimated delivery date shown by the carrier. An order still sitting in your warehouse needs a different response from a parcel already moving through the carrier's network. Combining both under “shipping delayed” makes it harder to assign the next action.

A limited exception changes the unstated-time default from 30 to 50 days when the buyer applies to the seller for credit at ordering. It is not a general extension for ordinary card payments. 16 CFR 435.2(a)(1)(ii).

The practical lesson is to record the actual transaction. Do not infer the applicable timing from a payment button's name or from the date money reaches a bank account.

If the order is missing information, identify the missing item precisely. A support note such as “waiting on customer” is too broad. State what the team needs, when it requested it and what happened next. Keep that record separate from an inventory delay so the business can explain the sequence accurately.

Work through the 120-order launch

Return to the hypothetical launch in the opening. All 120 orders carry an October 20 shipment promise. On October 16, the business learns that document review will prevent release on time.

Suppose the supplier provides enough information for the team to support shipment by October 28. The business decides to use an explicit-choice notice and an earlier response cutoff of October 19 at 5 p.m. Eastern. In this example, it will cancel and refund unshipped orders whose buyers do not choose to wait by that cutoff.

These dates describe a chosen operating plan. The earlier reply cutoff is not presented as a deadline set by the FTC.

October 16: establish one affected-order list

The operations lead confirms the 120 orders and checks that none has already shipped. Support removes orders already cancelled and verifies the remaining contact information.

The warehouse places the affected allocations on hold. Marketing pauses the offer displaying October 20. Finance receives the order list and the amounts that could require refunds.

Use order identifiers across departments; one email address may belong to a buyer with several purchases.

October 17: communicate the actual choice

The notice identifies the items, the original shipment promise, the revised date and the store's response cutoff. It explains how to keep the order or cancel it, and what will happen if the buyer does neither.

Support checks delivery failures rather than assuming every sent email reached a working address. It also reviews incoming replies for choices made in plain language. The customer should not need to repeat an unambiguous cancellation through a second channel merely to satisfy an internal preference.

October 19: reconcile every order

Assume 75 buyers elect to wait, 30 cancel and 15 do not respond. Those figures total 120 orders.

Under the store's stated procedure, 45 orders now enter cancellation and refund handling. The remaining 75 stay on hold for shipment by October 28, subject to the internal product-release decision.

Reconcile the counts with order identifiers. A total of 45 refund tasks is useful only if the same 45 orders are blocked from warehouse release. Check that a duplicate reply has not created a second refund task for one customer while leaving another customer's request unresolved.

Before October 28: confirm the remaining commitments

If the lot clears review, the warehouse checks which of the 75 waiting orders remain active before packing. Any later cancellation must reach that check.

If the date becomes unsupported, the operations lead reopens the affected orders. The team uses the applicable renewed-consent process for the definite revised date, rather than sending a generic progress report and leaving the prior choices unchanged.

The example illustrates a useful management habit: close the incident by reconciling orders, inventory and money. “We emailed everyone” describes an activity. It does not establish the outcome of each purchase.

What if you cannot give a shipment date?

An unknown date is an operating fact to explain, not a blank to fill with an optimistic estimate. Record which event prevents a supportable forecast and who can confirm its completion.

A supplier might be awaiting a result, replacement material or another unresolved release step. Ask what remains unfinished and when the next useful information will be available. Keep that update appointment separate from the shipment date. A review scheduled for Friday does not make Friday a shipping commitment.

For an indefinite-delay notice, explain the reason, say that you cannot provide a definite revised shipment date, and explain the continuing right to cancel before shipment if the buyer agrees to wait. The notice also needs the applicable consent and automatic-cancellation information. FTC business guide, first and later notices.

Keep indefinite consent distinct from an unanswered notice

For a first unknown-date delay, silence does not authorize an unlimited hold. Without the required express consent within the applicable 30-days-after-original-deadline window, an order still unshipped at that point must be cancelled and refunded.

A properly obtained agreement to an indefinite delay is different from agreement to one definite date after another. The FTC guide says additional delay notices are not required after an appropriate timely notice and agreement to an indefinite revised shipment date. The rule specifically exempts qualifying prior consent to an indefinite extension beyond the first revised date from the renewed-option paragraph. 16 CFR 435.2(b)(2)(iii).

Keep the wording and evidence of the consent. Do not infer it from a buyer accepting an earlier definite date or opening a status email. If you cannot establish what the buyer agreed to, resolve that uncertainty rather than marking the order “approved to wait indefinitely.”

Keep a review appointment and cancellation route

Even when another delay notice is not required under that indefinite-consent treatment, schedule an internal review. Check whether new information supports shipment, whether the buyer has cancelled, and whether the business should continue the order. A review reminder is useful management; it is not a new shipment promise.

Give the employee receiving a cancellation access to the warehouse status and the person who can stop dispatch. Keep the continuing cancellation right effective in the actual workflow. An order should not stay in the packing queue simply because the request reached a different inbox.

During the hold, remove automated delivery countdowns that assume carrier possession. Check that restock campaigns cannot sell inventory already allocated to waiting buyers. If your store sends a voluntary progress update, keep it accurate about what changed and what remains unknown.

Finally, name the person who can decide to cancel on the business's own initiative. An unresolved supplier problem should not leave paid orders open merely because no one owns the decision.

Calculate and complete the refund

A cancellation has both a money amount and a required payment action. Track them separately so “order cancelled” cannot hide a refund that remains unfinished.

For most payment methods, including credit where a third party is the creditor, the prompt-refund period is seven working days after the buyer's right to a refund arises. Where the seller is the creditor, the specified credit-account provision uses one billing cycle. That is a particular seller-credit situation, not an extension for every ordinary card refund. 16 CFR 435.1(b), (d).

The regulation also defines what constitutes a refund for each payment type. For third-party credit, it describes the appropriate instruction to the creditor and the required buyer communication; other payment methods have their own instruction, return or no-charge provisions. Match the action to the actual payment arrangement.

The rule contains a separate provision when the seller cannot refund by the method originally tendered: it specifies cash, check or money order sent by the required means within seven working days after discovering that inability. An account restriction therefore needs a named resolution owner. It should not turn a failed button click into an indefinite “refund pending” status. 16 CFR 435.1(b)(1).

Work out the whole-order or partial-shipment amount

If nothing ships, refund the entire amount paid, including shipping, handling and other charges. If part of the order ships, refund the difference between the total paid and what the shipped items alone would have cost under the ordering terms. The FTC guide also says required refunds cannot be replaced with credit for future purchases or vouchers. FTC business guide, refund amounts.

For a hypothetical whole-order cancellation, assume two items at $80 each plus $12 shipping, with no taxes, discounts or other fees. The buyer paid $172. Because nothing ships, the refund is $172.

For 45 cancelled orders with those same illustrative amounts, the refund outflow is $7,740: 45 multiplied by $172. These numbers are planning assumptions, not a report of a business's revenue or refund rate.

Now assume a different hypothetical purchase contains an $80 item and a $120 item, plus $12 flat shipping. The buyer paid $212. The ordering terms would charge the same $12 shipping for the $80 item alone. That item ships; the $120 item is cancelled before shipment.

The shipped-only amount under those terms is $92. The refund is therefore $212 minus $92, or $120.

Different ordering terms can change that answer. If shipping is based on quantity or order value, calculate the amount properly attributable to the shipped portion under those terms. Check actual discounts, taxes, other charges and previous refunds before confirming the final number; the simplified examples exclude them.

Keep one refund task until the required action is complete

Use an order-level record containing the cancelled items and quantities, refund amount, payment method, date the right arose, due date, owner and action reference. Preserve the assumptions behind a partial refund so another employee can reproduce it.

Before sending an instruction, check for an earlier refund or cancellation on the same order. If a transaction has another unresolved payment event, reconcile the actual payment record before issuing overlapping instructions. A spreadsheet total alone cannot tell finance which buyer has already received money.

After the action, save the result and the required customer communication. Describe an instruction sent as an instruction sent. Do not promise that funds have appeared in the buyer's bank account merely because the seller completed its own action.

Keep failures visible. Assign a next step to a rejected request, investigate the actual cause, and check the payment service's response. Support can answer the customer while finance still has work to finish; those events need separate statuses.

Close the refund group by matching the completed actions to the cancelled order identifiers and quantities. A balanced total is necessary, but a duplicate refund and a missing refund can offset each other. Reconcile the individual purchases as well as the sum.

Use customer notices that lead to an action

Write each notice around a specific order and choice. A customer should be able to identify the affected items, understand the proposed timing and act without searching through an unrelated policy page.

The following examples use a store-selected explicit-choice procedure. They are illustrative wording for the stated situations, not universal legal forms. Replace every bracketed field, check the applicable deadlines and make sure your operation can carry out the promised response.

First delay with a definite revised date

> Subject: Choose a revised shipment date or refund for order [number]

>

> We cannot ship [affected items] by the shipment date we gave you, [original date]. Our revised shipment date is [new date].

>

> Please choose one option at [order link]:

>

> Keep my order: I agree to wait for shipment of the listed items by [new date].

>

> Cancel my order: Cancel the listed unshipped items and provide the applicable full, prompt refund.

>

> There is no charge to make your choice. If we have not shipped and receive no choice by [store-selected response cutoff and time zone], we will cancel the affected unshipped items and issue a full, prompt refund for those items.

>

> You may also contact [support method] to make your choice or cancel before shipment.

For a whole-order delay, identify the whole order. For a mixed order, say which items are affected and make the available choices understandable. Avoid sending a notice that says “cancel my order” when the business intends to cancel only one line.

A further delay after the buyer agreed to a date

> Subject: A new decision is needed for order [number]

>

> You previously agreed to shipment of [items] by [agreed date]. We cannot meet that date. The new shipment date we can support is [new date].

>

> Please tell us at [link] whether you agree to this further delay or want to cancel the affected unshipped items for a full, prompt refund.

>

> If we have not shipped and do not receive your agreement by [applicable cutoff and time zone], we will cancel those unshipped items and issue their full, prompt refund.

>

> Make your choice or contact us at [support method]. There is no charge to respond.

Set the further-delay response cutoff no later than the existing definite revised shipment deadline. The second message refers to that agreement so the buyer can understand what changed. Keep the notice attached to the response it generates.

A cancellation and refund confirmation

> Subject: Cancellation and refund update for order [number]

>

> We have cancelled [unshipped items]. The refund amount is [amount and currency].

>

> We [sent the refund instruction / completed the applicable refund action] on [date] through [payment method]. Your reference is [reference].

>

> [Describe any items already shipped, if applicable.]

>

> If you need help with this refund, contact [support method] and include your order number.

Choose the refund-status wording that matches what actually happened. A prepared refund request and a completed payment action are different events.

The FTC permits a seller to cancel and refund instead of requesting a delay. Its notice guidance also explains the information needed when seeking consent. Use that guidance to check the actual communication before sending it. FTC business guide, notices and cancellation.

Test the response path

Open the message on a phone and a desktop. Check that the order link points to the right purchase, the dates match the order record and the support method works.

Have a colleague choose cancellation in a test order. Follow that choice through the support record, warehouse hold and refund task. Then repeat the exercise with an acceptance.

Give the buyer a confirmation of the choice recorded. That confirmation lets support resolve a later question without asking the customer to reconstruct an earlier conversation.

Resolve conflicting replies without losing the deadline

A launch response inbox will rarely arrive as a clean spreadsheet. A buyer may click keep, reply cancel an hour later and then ask whether cancellation succeeded. Another buyer may accept a date while asking a question about a second item. Treat the messages as instructions to interpret, not as votes to count independently.

Keep a chronological history with the order identifier, the exact buyer language, its receipt time and the staff decision. Identify the currently effective instruction and communicate that outcome to the buyer. When an available pre-shipment cancellation is received, route it immediately to the person able to stop the parcel. A previously recorded acceptance should not make a later cancellation invisible.

If the instruction is genuinely ambiguous, ask a focused question about the affected items and quantities. Keep the applicable response cutoff visible during that clarification. The absence of a clear answer does not authorize staff to invent express consent or extend a deadline. Escalate unresolved cases to the incident owner in time for the required outcome.

Do the same for duplicate orders and changed contact details. Two purchases using one email address remain two purchases. Link the response to the relevant order and ask if its scope is unclear. Give the buyer a useful confirmation that identifies the items and date, rather than an automated message saying only that the ticket is closed.

Reconcile quantities and dollars independently

The hypothetical launch later in this guide contains 120 orders, with 75 buyers waiting and 45 entering cancellation. That order count is not an inventory count if quantities differ. Export affected quantities beside each order before releasing stock or estimating what can be resold.

Similarly, a count of completed refunds needs a defined meaning. One report might count refund requests; another might count successful payment instructions. Keep the required amount, action reference and observed status together. A matching batch total can conceal a duplicate refund and a missed customer.

Use a second comparison at the end of the day: the same order identifiers should appear in the cancellation list, warehouse stop record and finance work queue. Investigate disagreements individually. This check makes the incident manageable without making a promise that every payment service or warehouse supports the same automation.

Coordinate suppliers and fulfillment partners before reopening sales

The FTC's business guide places responsibility for rule violations caused by a fulfillment house or drop-shipper on the seller. FTC business guide, fulfillment houses and drop-shippers.

Build the partner relationship around the information you need to manage that responsibility. Ask for product-specific availability, the meaning of each warehouse status and a contact who can act on a stop request.

A supplier may use “released” to describe approval for its own dispatch. Your warehouse may use the same word for permission to pick an order. Define these terms in your working instructions so employees do not mistake one event for the other.

Agree how cancellations reach the packing queue

Choose a clear stop procedure with the fulfillment partner. State where the instruction is sent, who acknowledges it and how the sender checks whether picking or carrier handoff has already occurred.

Test a cancellation after a pick task has been created. That is a more informative test than cancelling an order that has never entered the warehouse system.

If your store sends orders automatically, check what happens after cancellation. Does an update reach the partner, or does it merely change the status visible in your own dashboard? If a temporary manual list is needed during the incident, assign someone to reconcile it against new activity.

Reopen against a fresh allocation

Once inventory becomes available, calculate the active commitments again. Some customers will have cancelled; others may have agreed to wait. Avoid reopening the entire original quantity simply because it appeared in the initial launch plan.

Review the supplier documents and warehouse release through your normal product process. Then confirm how much inventory remains available for new orders after the waiting buyers are accounted for.

Before releasing waiting orders, trace one purchase across the systems your team actually uses. Compare its current buyer instruction, affected quantities, lot-release decision and warehouse allocation. Confirm which person can stop the parcel before carrier handoff and which person owns any required refund action. If the records disagree, assign the mismatch to a named owner and check the corrected outcome before relying on that handoff for the remaining group.

Plan cash and capacity for the refund branch

Use the cancelled-order scenario when planning a preorder, even if the preferred outcome is to ship everything on time.

List the money already committed to the supplier, expected fulfillment costs and the amount that would need to be returned if the release failed. Keep the assumptions visible. A forecast based on every buyer choosing to wait leaves the business with no plan for customers who choose cancellation.

Assign someone to monitor available funds and the practical route for issuing refunds. If a payment service has a reserve, restriction or rejected transaction, record the observed issue and contact that service about the actual account. Avoid assuming that an internal cancellation has moved money.

Capacity also matters after buyers agree to wait. Releasing an entire delayed group at once may collide with new orders already in the packing queue.

For illustration, suppose a team can complete 40 orders per working day under a particular packing plan. A group of 75 waiting orders would use almost two such days before adding other work. That arithmetic does not establish your team's capacity. Measure your own process, including checks and carrier cutoffs.

Before choosing a revised shipment date, compare the waiting group with the existing queue. Decide which work is assigned to each day and who will notice if the plan slips. A revised date becomes more useful when the person running fulfillment can explain how the orders will reach carrier handoff.

Set up the next paid preorder before accepting money

A preorder creates an operating commitment before the product is ready for immediate dispatch. Start by deciding what has to be true for your team to keep that commitment.

Separate three situations. You may have finished inventory already assigned to your business. You may have a confirmed incoming lot with receiving work outstanding. Or you may still be testing interest in a product that has no dependable release plan. Those situations deserve different checkout decisions.

An unpaid availability list can help with the third situation. Tell people what the list means, what information they will receive and whether joining reserves anything. Avoid presenting an expression of interest as a completed purchase. Keeping payment out of this early stage also gives your team time to settle the shipment plan before taking paid orders.

For a paid preorder, write down the route from supplier to carrier. Include the steps your own operation actually uses: supplier release, transport, receiving, review of the lot documents, inventory allocation, picking, packing and carrier collection. Assign a person to confirm the completion of each step.

The supplier's estimated arrival date is only one input. If goods are expected on Tuesday but your team cannot complete receiving until Thursday, Tuesday is a poor basis for a customer shipment promise. If your carrier collects once daily, a late packing finish may miss that day's handoff.

A clearly disclosed shipment period longer than 30 days still needs a reasonable basis. FTC rule summary.

Make the launch quantity an explicit decision

Choose a preorder limit from the quantity you expect to be able to release and the number of orders you can fulfill within the promised period. Leave room for the actual exceptions your process must handle.

For illustration, suppose you expect 300 units. You allocate 20 for an existing commitment and hold 10 for an internal review decision. That leaves 270 units available for the proposed release. If the average hypothetical order contains two units, 135 orders would consume that allocation. This arithmetic is a planning example, not a demand forecast or a recommended stocking ratio.

A sales cap should also reflect fulfillment capacity. Having enough units will not help if the launch produces more parcels than the team can prepare before collection. Decide who can stop checkout when the allocation is exhausted, and test that control before the launch opens.

Keep every buyer's shipment promise

Save the wording shown at purchase. Include the product page, the relevant checkout message and the confirmation. Record any more specific shipment representation given while taking that order.

For new purchases, clear updated shipment information can supersede earlier advertising. Communicate that update before the order is placed. A later website edit does not retroactively complete the delay process for existing buyers. FTC prompt-delivery guidance.

A useful check is to ask someone outside the launch team to make a test purchase. Have that person state the shipment expectation using only the information they saw. If their answer differs from the warehouse plan, revise the offer before taking live orders.

Decide whether waiting is still a useful offer

A consent option is useful only if the business can explain what the buyer is agreeing to. Repeatedly offering another date without reviewing supply and capacity can produce orderly emails around a plan that remains unsupported. Ask what has changed since the previous forecast and which unfinished step determines carrier handoff.

If the only update is that the supplier hopes to know more next week, use that as an information appointment. Do not convert it into a definite shipment date. If the business cannot support even the proposed path to shipment, consider its option to cancel and refund rather than leaving the decision unowned. Use the required notice and refund timing for the branch actually taken.

A buyer's agreement also does not settle the release status of the material. Keep that review with the responsible product owner. Pressure to reduce refund outflow should not change whether the lot may be released. Finance can plan cash while technical work remains unresolved, and support can describe the uncertainty without promising the eventual finding.

For a future launch, compare a paid preorder with an unpaid interest list. The interest list can answer whether people want updates while the shipment plan is still being built. Explain whether it reserves anything and avoid suggesting that signing up guarantees access to stock. Once the evidence supports a paid promise, decide the sale quantity against both released availability and packing capacity.

Before reopening, choose one earlier order that waited and one that cancelled. Trace the first to its active commitment and the second to its stop and refund action. Then test a new checkout against the fresh promise. These three paths reveal whether the business has repaired the actual handoffs that failed.

What closes an individual decision card?

Close the card with one observable order outcome. For a shipped purchase, identify the active customer instruction and the actual carrier-handoff evidence for the relevant items. For a cancellation, identify the stopped unshipped quantities, the refund amount, the required payment action and its reference. Where an order still validly waits, retain the agreement, current uncertainty and next review owner rather than marking shipment work finished.

If a required action remains unresolved, transfer it by name and due time. A payment error needs a finance owner even when the warehouse stop succeeded. A split order needs its remaining line linked to the original purchase. Give the next operator the evidence needed to act without treating a closed supplier ticket as proof of a completed customer outcome.