What the documents look like
Tmall flagship store daily operations center on brand authorization, flagship store identity, and Tmall points compensation rules. Working materials include the product publishing page, brand authorization letter, delivery commitment record, and after-sales ticket. These materials come from the Tmall merchant backend, the Tmall rules center, ERP order tables, and customer service chat records, and they update daily and per order. Typical operators are the brand e-commerce department, the Tmall store manager, and agencies running the store.
For order fulfillment and after-sales answering, the shared access step carries fulfillment status and after-sales positions into an external entry point. The brand authorization letter defines what the store may publish and answer, the delivery commitment record shows what was promised and what was shipped, and the after-sales ticket shows where a case stands. A link identifier, a retrieval score, or a form field does not carry any of that business authority. The task here is to keep those identities, stages, and scopes straight when a no-login share window is used to receive after-sales questions.
Constraints at the shared access step
The no-login window creates a temporarily reachable address that any internet user can open, and the resulting charges fall on the team that owns the application, so the link is not meant to be shared freely. The system generates a localId for each user to identify that user and pull conversation records from the cloud. This arrangement only holds when the user stays on the same device and the same browser; switching devices or clearing browser cache loses those records. The system allows pulling only the most recent 30 days and 20 records.
Identity verification is a POST request root address. Once filled in, share-link initialization, conversation start, and conversation end each send a request to a specific endpoint under that address. The server only needs to return whether verification succeeded. The response uses success, message and msg, and data.uid. FastGPT reads success to decide whether the user may continue. The uid is required, must not contain the characters "|", "/", or "\", and must be a string no longer than 255 bytes; otherwise an Invalid UID error is returned. The uid is then used to pull and save conversation records. In the share link, an extra query parameter authToken is appended, and FastGPT carries token=[authToken] in the body of the authentication request. The conversation result reporting endpoint has no required return value; its response matches the chat interface format plus a token field, and totalPoints and token are the fields of note. Identity verification is available only in the commercial edition, and some parameters are likewise limited to that edition.
A hypothetical paper exercise sample is used below only to check whether a draft sentence matches the source wording. The source text reads: "This store's brand authorization letter number is A-2024-001, valid until December 31, 2025, and its authorized scope covers Tmall flagship store product publishing and after-sales answering. The delivery commitment record shows order 20240601-001 shipped on June 2, 2024 at 10:00, logistics number SF1234567890." The draft sentence to be judged reads: "This order has completed fulfillment, and after-sales answering may directly cite authorization letter number A-2024-001." This sample exists only to compare subject, object, status, and valid scope between the source wording and the draft sentence.
Configuration and implementation checks
| Configuration item | Hypothetical trial starting value for this page | How to check |
|---|---|---|
| Expiration time | Set to December 31, 2025 | Compare against the authorization letter validity; after that time the link cannot be used |
| QPM | Set to 10 | Maximum visits per user per minute; check against the actual edition |
| Points cap | Set to 1000 | Maximum billing data produced by this link; check cost ownership |
| Identity verification | Fill in the POST root address | Judge by the official success value and uid |
| View quote snippet | Enabled | Check against the system introduction |
| View full quote text | Enabled | Check against the system introduction |
These starting values are hypothetical for this page, chosen so the share entry aligns with the authorization letter period and stays within a small internal trial scope; they are not official defaults. Identity verification is bounded by the commercial edition. QPM means maximum visits per user per minute. The points cap is checked against the usage limit and cost ownership of the share entry, and some parameters are edition-limited. Conversation record boundaries depend on the same device and same browser; cross-device records require separate identity and session design. A retrieval similarity value is not a category, entity, or permission filter, and retrieval does not perform authorization.
Three common errors
- Treating a link identifier as business authorization. The input is the shareId in the share link, the comparison object is brand authorization letter number A-2024-001, and the observable result is that the link opens while the authorization letter does not cover that entry; subject and object do not match.
- Treating an after-sales ticket awaiting review as approved. The input is an after-sales ticket status of "awaiting review", the comparison object is the shipment time in the delivery commitment record, and the observable result is that the ticket is unsigned and not in effect, so completed fulfillment cannot be derived.
- Treating a retrieval result as a permission filter. The input is a similarity score of 0.83, the comparison object is the success value returned by uid verification, and the observable result is that retrieval matched while identity verification did not pass; retrieval does not isolate permissions.
How to verify the setup
- Input the hypothetical source text "This store's brand authorization letter number is A-2024-001, valid until December 31, 2025", compare the draft sentence "This order has completed fulfillment, and after-sales answering may directly cite authorization letter number A-2024-001", and observe whether the draft sentence exceeds the validity period and scope stated in the authorization letter. The expectation is that the draft sentence is unsupported and needs evidence of completed fulfillment.
- Input the hypothetical source text "The delivery commitment record shows order 20240601-001 shipped on June 2, 2024 at 10:00, logistics number SF1234567890", compare the draft sentence "This order has completed fulfillment", and observe whether a shipment record equals completed fulfillment. The expectation is that the shipment record shows only the shipment action, and the fulfillment completion status remains to be verified.
- Input the identity verification response "success: true, data: {uid: 'user1'}", compare whether the uid format excludes the specified characters and stays within 255 bytes, and observe whether an Invalid UID error is returned. The expectation is that a uid meeting the format requirement passes verification, and a uid that does not meet it records the actual error.