What the documents look like
For after-sales questions in Group-buy presale orders, this page examines FastGPT HTTP integrations. Pre-sale cancellation and refund inquiries separate demand, applications and actual handling. Reading consolidated orders cannot establish returned funds. The examples are hypothetical.
Constraints at the HTTP integrations step
A proposed customer wants an added product withdrawn. Prior output retains only a consolidated product name without current confirmation scope. Inspect how the real contract distinguishes demand from orders instead of using a product list as order identity. A cancellation application or procurement-plan change supports its own stage, not executed refunds. A cut-off notice covering original items cannot decide treatment of the addition.
Configuration and implementation checks
| Pre-sale withdrawal reading | Proposed identity gap | Actual need |
|---|---|---|
| Consolidated product | Name is not order identity | Confirmed relationship |
| Added scope | Original notice does not cover | Applicability evidence |
| Cancellation request | Not executed refund | Actual handling |
| Request conditions | Distinguish under real contract | Compare transmitted subject |
| Subsequent action | Amendments and refunds separate | Query does not decide for parties |
Documented conditions
| Documented item / implementation check | Condition |
|---|---|
Request address and method | The request address and method follow the external contract. |
Params and Headers | Inspect parameters, headers and authentication separately. |
| Body | Where a JSON body is used, validate its structure against the external contract. |
Variable references | Variables can come from global, system or upstream outputs. |
Debug identity fields | Test mode lacks chatId and responseChatItemId. |
Three common errors
Demand promoted to an order needs original-demand and actual-order correspondence. Cancellation promoted to refund needs real fund-processing evidence. A notice extended beyond its scope requires applicability wording beside returned coverage. These inspect identity relationships, execution stage and scope despite a nonempty response.
How to verify the setup
Retain conditions and actual response. Add demand confirmation and inspect the transmitted subject and coverage of this addition. Empty output does not establish no application; check permissions and scope. Procurement amendments, cancellation confirmation and refund writes need separate receipts. Inspect parameters and headers separately under the real contract. Reading supplies evidence without deciding for suppliers, customers or the platform.
| Material context | Scope |
|---|---|
| Document types | Pre-Sale Product List, Consolidated Order Results, Procurement Plan and Order Cut-off Notice |
| Candidate sources | Mini Program Orders, Supplier Inventory, Group Leader Feedback and Warehouse and Distribution Route Planning |
| Technical baseline | FastGPT v4.17.2 |