What buyer protection helps with
The product title, price, description, delivery method, included and excluded items, selected add-ons, and support period are saved with the order. Later listing edits do not rewrite those order terms.
If a seller updates a listing while checkout is open, Mehor stops the purchase and asks the buyer to review the latest information before placing the order.
ZIP files, the required README or setup guide, purchased add-ons, and GitHub ownership-transfer activity stay connected to the order so the buyer can verify what was delivered.
After delivery, the buyer receives a review window to inspect the product. If more time is needed, the available extensions can be requested. If the delivery does not match the order, the buyer can open a dispute before the review window ends.
When the order is completed, the support period saved with the purchase begins. It covers questions and defects in the delivered product, but not new features, customization, deployment work, or problems caused by later buyer changes unless those services were included.
What buyers should do
Read the complete listing, including limitations, excluded items, delivery method, add-ons, and support period.
Ask the seller about unclear requirements, setup needs, third-party services, or licenses before ordering.
If Mehor says the listing changed, review the refreshed checkout before trying again.
Use the correct GitHub username when repository ownership will be transferred.
Inspect every delivered item and test the product during the review window.
Keep order questions, delivery confirmations, and problem reports inside Mehor so the record is available if help is needed.
Open a dispute promptly and explain the specific difference between the order and the delivery, with useful evidence when available.
What buyer protection does not cover
A change of mind after the seller delivered the product described in the order.
Features, files, services, deployment, customization, or support that were never included in the saved order.
Problems caused by the buyer, later code changes, unsupported hosting, or third-party services after delivery.
Promises, payments, files, or conversations moved outside Mehor that cannot be verified through the order record.
A complaint raised after the applicable review or support period when no earlier issue was documented.
How buyer protection works during a dispute
A dispute is for a meaningful problem with the purchased product or delivery, not a general request for extra work. Open it during the active review window, describe what does not match the saved order, and attach evidence when it helps explain the issue.
The buyer selects a reason and explains what was expected, what was received, and what is not working or missing.
The saved order terms, messages, delivery activity, files, add-ons, deadlines, and submitted evidence can be reviewed.
The seller can respond, and the buyer can add relevant information while the dispute remains open.
Based on the order record, the order may be completed, canceled with a full subtotal refund, or resolved with a partial subtotal refund.
Review the complete product before you place an order.
Compare the scope, delivery method, support period, and seller information, then ask questions about anything that is unclear.