What the documents look like
Dealer rebate calculation happens after sales close. The working materials come from ERP sales records, dealer remittances, the contract ledger, and the finance system. Day-to-day documents include the rebate policy, the volume achievement table, the reconciliation statement, and red-letter invoices. This shapes what a shared access step has to align: order fulfillment status, after-sales question records, and the rebate basis need to refer to the same entity and the same period. Rebate calculation updates monthly and quarterly. A share link configuration does not synchronize with those updates on its own, so material versions require manual comparison.
Constraints at the shared access step
The no-login window is created from Application Details - Publish Channels, and the complete system-generated link is copied. The link identifier only controls access. It does not serve as business authorization. Expiration time and QPM are set for the intended scope of use, where QPM is the maximum number of 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 restricted by edition. Identity verification is limited to the commercial edition scope and follows the official interface return of success and uid, where uid is a string that excludes specific characters and does not exceed 255 bytes in length. The anonymous localId depends on the same device and the same browser. Records across devices require separately designed identity and session management. Retrieval and similarity do not carry permission or entity isolation.
Hypothetical paper exercise sample. Rebate policy text supplied for comparison: "For Q3 2025, dealer rebates in the East China region are accrued at 2% of remittance amount, and return amounts are deducted from the achievement basis." Reconciliation statement text: "As of September 30, 2025, Dealer A remitted 1.2 million yuan and returned 80,000 yuan." Draft sentence to be assessed: "Dealer A's Q3 rebate is accrued in full on 1.2 million yuan." The comparison objects are Dealer A, Q3 2025, and the rebate accrual field. The draft sentence conflicts with the policy text's deduction of returns, and it does not state an authorization status.
Configuration and implementation checks
| Configuration item | Relevant setting or check on this page | Hypothetical trial starting value and comparison method |
|---|---|---|
| Link name | Used only for record display | Enter "Rebate Q&A - East China" and compare with the display name in the publish channel list |
| Expiration time | The link cannot be used after this time | Assume 2025-10-01 to 2025-12-31 and compare with the period covered by the materials |
| QPM | Maximum visits per user per minute | Assume a starting value of 10 and compare with concurrent access from dealer finance staff |
| Points cap | Maximum billing data produced by this link | Assume a starting value of 5000 and compare with the expected number of Q&A rounds |
| Identity verification | POST root address returning success and uid | Check the return values of /shareAuth/init and /shareAuth/start |
| Conversation record boundary | localId depends on the same device and browser | Check whether cross-device records have separately designed identity management |
Three common errors
- Treating the link identifier as rebate calculation authorization. The input is the share link, and the comparison object is the authorization credential field. Link accessibility does not mean Dealer A holds rebate accrual permission.
- Treating pending review as approved. The input is the reconciliation statement status, and the comparison object is the approval field. Pending review does not show an absence of operating permission, and it does not equal approval.
- Treating retrieval similarity as entity filtering. The input is the similarity value, and the comparison object is the dealer entity field. Similarity does not exclude unrelated business records.
How to verify the setup
- Input the policy text, reconciliation statement text, and draft sentence from the hypothetical sample. Compare whether the draft sentence deducts the return amount. The draft sentence accruing in full on 1.2 million yuan conflicts with the policy basis, so it is assessed as unsupported.
- Input the token and authToken in the /shareAuth/init request body. Compare the returned success and uid. The condition is met only when success is true and uid satisfies the character and byte length requirements.
- Input a cross-device access scenario. Compare whether localId can retrieve records. The same device and same browser can retrieve the most recent 30 days and 20 records. Missing records across devices are an expected boundary, and identity management requires separate design.