Kandiantong: The yearly fee is written on the order page by plan

Start with the conclusion: when a clerk places an order on a member's behalf, performance goes either to the guide the member belongs to or to the clerk who operated. Only one may be chosen, and it must be written into policy. The order must record the operator.

How to use the conclusion

Laws and platform rules change. This article gives handling principles for implementation. It is not legal advice.

The service guide on the member master record is the usual owner of the sale. An order placed on someone's behalf must not change that owner unless there is an approval. Payment should be completed by the member when possible. If a clerk pays instead, it has to follow payment rules and keep a voucher. Internal purchases and retail must not use the same assisted-order entrance.

Easy mistakes

Giving the sale to whoever placed the order leads to people grabbing orders. There is no operation log. The assisted order used the clerk's own member price. Kandiantong records the operator and the member. The performance-owner field is configured to your policy.

What to check before go-live

In implementation, credit the person the operating rule names, and keep a log. Confirm the boundary with the monthly fee on a list: copy changes and listing or delisting go through support, and state machines and integrations go through a project. Acceptance uses one operation that should succeed and one that should fail. The item counts as landed only when the two results are opposite.

Kandiantong does not build features that bypass review, pay on three levels, list goods without a license, or exaggerate treatment effects. What cannot be done is removed at review, rather than left for after go-live and handled with a note.

Source: https://www.kandiantong.com/answers/agent-order-performance.html