These terms explain the basic rules for MainwinERP. The mutually confirmed contract and applicable platform requirements govern specific scope, fees, rights and obligations. Browsing or generating a requirement summary does not activate service or create a purchase obligation.
01 / Service scope
MainwinERP provides catalog, order, inventory, fulfillment and finance collaboration. The contract specifies entities, accounts, marketplaces, modules and implementation, activated according to account authorization and platform eligibility.
02 / Account authorization & eligibility
Users must hold lawful authorization for the relevant accounts and follow Amazon and other applicable platform rules. For different group legal entities, each entity’s use and data authorization scope must be confirmed. The provider does not request seller passwords or offer services to hide account relationships or bypass platform restrictions.
03 / Restricted features
Direct shipping, tax invoicing and other restricted-data features require API support, role approval and customer program eligibility. Purchasing service or accepting terms does not grant additional Amazon data access.
04 / Fees & payment
Software package prices appear on the plans and pricing page. This website offers no online purchase or payment. Implementation, migration, support, third-party costs, taxes, term, renewal and refunds are specified in written quotations and contracts before service begins. Generating a requirements brief creates no purchase obligation.
05 / Data & confidentiality
Data use is limited to authorization and service necessity under the privacy policy, processing agreements and applicable law. Both parties protect credentials and non-public business information. See the Privacy policy。
06 / Support & changes
Support channels, hours, response targets and maintenance require separate confirmation. No unwritten SLA or round-the-clock support is guaranteed. Material changes to scope, features or fees should be confirmed as agreed before implementation.
07 / Suspension & termination
Access should be suspended as formally agreed if authorization is revoked, the contract ends or security risks arise. Data export, cleanup and necessary statutory retention must be clarified. Stopping use and deleting historical data are separate processes requiring individual verification.
08 / Liability & disputes
Responsibility for API changes, third-party interruptions and operational risks follows the contract and applicable law. These terms do not limit rights that cannot lawfully be excluded.
09 / Contact & version
Business and policy enquiries: a958965018@gmail.com. You can also use the requirements page to generate local discussion materials. This website does not automatically send requirements or create service accounts.