Kandiantong: The basic monthly plan is for a single shop starting out

The conclusion first: products, the cart, WeChat Pay, regular members, coupons, and standard shipping use the monthly fee. Write-off rollback, order review, a split-warehouse source of truth, and staged payments are custom.

How to use the conclusion

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

Judge it in one sentence: does the order end as "signed for by courier after payment"? If not, write the fulfillment states first, then decide whether it is a template.

Custom work is quoted from a list. Integrations that are not written down are not included in the monthly fee. Standard transactions use the monthly fee. Changing the state machine is custom.

Easy pitfalls

Sales may say verbally that anything can be changed. The monthly fee may be assumed to include Kingdee. Only at acceptance does it turn out that the state machine must change.

A requirements review marks each item as template, configuration, or custom. Only items marked custom enter person-days.

What to check before go-live

Fix the conclusion first: products, the cart, WeChat Pay, regular members, coupons, and standard shipping use the monthly fee. Write-off rollback, order review, a split-warehouse source of truth, and staged payments are custom.

During implementation, hold to "standard transactions use the monthly fee; changing the state machine is custom." Put that sentence where the user can see it before payment, not only in an internal group. For acceptance, run one operation that should succeed and one that should fail. The item counts as implemented only when the two results are opposite.

Kandiantong does not build features that bypass review, pay three levels of compensation, list goods without a license, or exaggerate efficacy. What cannot be done is removed at review, not left for a note after go-live.

Source: https://www.kandiantong.com/answers/saas-custom-boundary.html