What if delivery does not go to plan?

Start with what your Deal shows: the agreed delivery arrangements, whether receipt was code-confirmed, the review deadline, and any active Dispute or return. These details determine which action is available. A message outside SHYLDA does not complete a receiving step or open a Dispute.

Respond through the delivery-claim or problem step shown in the Deal and say that you did not receive the item. Do not reveal a delivery code for an item that is not present. A Seller delivery claim alone does not confirm receipt or start the ordinary review-and-release window.

Check the response deadline and provide relevant facts, such as the agreed destination and what happened at the expected handoff. If the item is missing or the delivery cannot be completed, use the available Dispute path. Ignoring a delivery claim does not turn it into confirmed receipt, but responding keeps the problem explicit.

Describe that situation accurately through the delivery-problem response shown in your Deal. Do not invent an earlier confirmation or use an unrelated completion action just to make the status look correct.

For example, a parcel may have been left at a reception desk while you were unavailable. The Seller's statement that it was left there is different from completing the agreed handoff. Follow the next step in SHYLDA and request support if the correct receiving action is unclear. The time of a delivery claim is not the start of a code-confirmed review window.

Record the recipient or representative in the Delivery Plan and make sure they know what is being received. The Buyer account holder performs the SHYLDA actions and may reveal the delivery code remotely when the item is present for handoff.

Arrange how the item will be checked within the applicable review window. Having someone else receive it does not automatically extend that window. Never give them or the Seller your private release passcode as a substitute for the receiving code; those codes have different purposes.

Compare the item with the accepted description and record the difference with clear evidence. If you are meeting to inspect, raise the concern before final release. If you are receiving for later review, open a Dispute within the verification window shown in the Deal.

The current receive-and-review goods journey gives 24 hours after successful delivery-code confirmation to check the item and raise a Dispute. Use the actual remaining deadline shown. A separate message to the Seller does not pause release, and a change-of-mind return depends on whether the agreed policy includes that reason.

Keep the item with the Seller or carrier while the required receiving actions remain incomplete. Agree a new delivery or meeting arrangement through the steps available in the Deal. A missed meeting, failed connection, or arrival estimate is not proof of receipt or permission to release funds.

Check that the other participant accepted any replacement arrangement. If the delivery cannot be completed or there is a safety concern, use the problem or Dispute path rather than pretending the handoff succeeded. SHYLDA does not operate the delivery itself.

Check whether funds have already been released. If the code-confirmed review window ended without a Dispute, the accepted automatic release rule can apply. A later complaint cannot reverse that final release through a new Dispute.

Create a Support Request to understand any available assistance, while being clear that it is not a promise of a refund. If a Dispute or return is already active, read its current deadline instead: ordinary release may be paused while separate return conditions still require you to act.

Use Forgot passcode? where it is available in your Deal and follow the recovery instructions. The Buyer may need to wait for the stated recovery period and sign in again before setting a replacement. Check the status shown rather than assuming the request is an immediate reset.

Setting a replacement passcode does not itself authorize release. Review the intended next action after recovery, and keep the new passcode private. Support can help you understand recovery, but it cannot complete the Deal or move the funds on your behalf.