# What a Platform Order Protects | Cheery Supply Chain

> A marketplace order page is not a guarantee. The six fields to read before you confirm, and why the platform's own terms have to be read.

Source: https://luressource.com/insights/what-a-platform-order-protects/

Direct answer. A marketplace order is a contract with a platform's dispute process behind it, not a blanket refund promise. What it covers depends on the terms in force for your order, the time limits for raising a problem, and the evidence you keep. Before confirming, read six fields - entity and account, specification version, price and scope, delivery basis, acceptance method, and the payment route - and confirm that the order page reflects what you agreed. Key facts. 1) The order page and the approved attachments together form the agreement; neither alone does. 2) Coverage, time limits and exclusions sit in the platform's current terms, which are versioned and can change. 3) A platform dispute process is not a substitute for an agreed acceptance method. 4) Entering the order through a known address is part of the control, not a courtesy. Frequently asked questions. Q: Does a marketplace order guarantee I get my money back if the goods are wrong? A: No platform can promise that, and any supplier who says otherwise is describing something they do not control. What a platform provides is a documented order, a payment route and a dispute process. Whether a particular claim succeeds depends on the terms in force, the deadline for raising it and the evidence you hold. Q: What is the most common mistake when placing a first order? A: Treating the order page as a summary of a conversation rather than as the agreement. Specifications, tolerances and approval samples mentioned in chat but not attached to the order are, in practice, not part of it. Q: Should I use the platform's payment route or pay directly? A: Paying outside the platform usually removes the platform from the transaction, which means the dispute process is no longer available for that payment. If a supplier pushes hard for an off-platform route, that preference is itself information worth weighing. Q: How long do I have to raise a problem? A: That is set by the platform's terms for your order type and, separately, by any inspection or acceptance window you agree with the supplier. The two are different clocks. Read both, and record the date the goods were received, because every window starts from a date and the wrong date ends the argument before it starts. Q: What evidence should I keep from an order? A: The approved specification and its version, the sample approval record, the order confirmation, the packing list, the shipping documents, the inspection record and photographs taken at unboxing. This is the same file you would need for a quality claim, so it is worth building once and keeping together. Sources (9). 1) Alibaba.com Trade Assurance overview - the platform's own explanation of its order protection — https://tradeassurance.alibaba.com/ 2) US consumer product safety requirements that can affect what may be imported - CPSC — https://www.cpsc.gov/ 3) Harmonized System heading 9507 for fishing tackle - US HTS lookup — https://hts.usitc.gov/ 4) Our editorial rules on claims we will not make — /opportunities/editorial-rules/ 5) Harmonized System heading 9507 (rods, hooks, reels, lures) — US HTS lookup — https://hts.usitc.gov/ 6) US consumer product safety requirements — CPSC — https://www.cpsc.gov/ 7) Incoterms rules — FOB, EXW and who carries cost and risk — https://iccwbo.org/business-solutions/incoterms-rules/ 8) Chinese business registration lookup — National Enterprise Credit Information Publicity System — https://www.gsxt.gov.cn/ 9) ISO standards catalogue — quality and testing frameworks — https://www.iso.org/ A marketplace order is a good thing to have. It is not a guarantee, and the difference matters most on the order where something goes wrong. This page is about reading the order before you confirm it, rather than reading the terms afterwards. What an order actually is Three things sit behind a marketplace order, and they do different jobs. A contract. The order page plus its attachments is the agreement. What is not attached is, in practice, not part of it. A payment route. Money moves through the platform's process, which creates a record that a direct transfer does not. A dispute process. A defined way to raise a problem, with its own deadlines, evidence requirements and exclusions. None of those three is a promise about outcome. The platform's own overview of its order protection describes the shape of the service; the terms that apply to your order are the ones to read, and they are versioned, so a page read last year may not describe the order you are placing today. Where a claim matters commercially, record the date you read the terms, the version and where you found them. The six fields to read before confirming Field What correct looks like What to do if it is wrong Entity and account The seller entity matches the contract and the beneficiary Stop. Do not pay until the three names agree Specification The approved spec and sample are attached, with a version Attach them, or the order does not describe your product Price and scope Unit, quantity, currency, and what is included Ask for the scope in writing; an unclear scope is a future dispute Delivery basis Incoterm, named place, and who carries what Compare with what the term actually covers Acceptance method How the goods will be checked, against what rule Agree it now; see the QC record fields Payment route Paid through the order, not around it Treat an off-platform request as a decision, not a convenience The third row is where most arguments start. A price is agreed in a chat, the order page carries a different figure or a different unit, and by the time anyone notices, the goods exist. If the order page and the conversation disagree, the order page wins, which is a good reason to make sure they agree before confirming. The acceptance clause is the one people skip Platform dispute processes ask a version of the same question: did the goods match what was agreed? That question is unanswerable unless the agreement says how the goods would be checked. A specification without an acceptance method is a description, not a standard. So the order should say three things about checking: what rule applies, who applies it, and what happens to goods that fail. This is the same territory as sampling and the QC record , and it belongs on the order rather than in a side conversation. An agreed inspection method turns a disagreement into a measurement. Two clocks, not one When something goes wrong, two deadlines run at once. The platform's window for raising a dispute starts from a date defined in its terms. Any inspection or acceptance window you agreed with the supplier starts from delivery. They are not the same clock, and buyers who only know about one of them routinely discover the other has already expired. Write both down when the order is placed, and record the actual receipt date when the goods arrive. It sounds bureaucratic until the first claim, at which point it is the difference between a process and a complaint. Getting to the order safely A small habit with a large payoff: reach the order through an address you already know, or through the platform's own navigation, rather than through a link in an email. Check the domain and the order number before entering payment details. Never share passwords, one-time codes or access keys with anyone who asks for them, whatever the reason given. This is the same control as the one described in payment safety on a first order , applied to the platform side of the transaction. It costs a few seconds and removes an entire class of incident. What to keep afterwards The file you want after delivery is the same file you would want for a quality claim: the approved specification with its version, the sample approval record, the order confirmation, the packing list, the shipping documents, the inspection record, and photographs taken as the cartons were opened. Build it once, keep it together, and the question of what was agreed stops being a matter of memory. Related reading: what documents travel with a shipment and carton data before you book freight . Frequently asked questions Does a marketplace order guarantee I get my money back if the goods are wrong? No platform can promise that, and any supplier who says otherwise is describing something they do not control. What a platform provides is a documented order, a payment route and a dispute process. Whether a particular claim succeeds depends on the terms in force, the deadline for raising it and the evidence you hold. What is the most common mistake when placing a first order? Treating the order page as a summary of a conversation rather than as the agreement. Specifications, tolerances and approval samples mentioned in chat but not attached to the order are, in practice, not part of it. Should I use the platform's payment route or pay directly? Paying outside the platform usually removes the platform from the transaction, which means the dispute process is no longer available for that payment. If a supplier pushes hard for an off-platform route, that preference is itself information worth weighing. How long do I have to raise a problem? That is set by the platform's terms for your order type and, separately, by any inspection or acceptance window you agree with the supplier. The two are different clocks. Read both, and record the date the goods were received, because every window starts from a date and the wrong date ends the argument before it starts. What evidence should I keep from an order? The approved specification and its version, the sample approval record, the order confirmation, the packing list, the shipping documents, the inspection record and photographs taken at unboxing. This is the same file you would need for a quality claim, so it is worth building once and keeping together.