Solution Provider Program
Effective Date: October 15, 2026 Version: 1.0 Applies to: All firms enrolled in the Solution Provider Program and the Sellers and Brands they serve.
Article 1: Introduction and Scope
1.1 This document states the program terms for a Solution Provider: a firm that builds on, integrates with, or implements the Platform for a Seller, a Brand, or another merchant. It governs enrollment, standing, duties in client work, and removal. It incorporates the Developer Agreement as the master developer instrument; this document states program terms only and does not restate that agreement.
1.2 If a provision of this document conflicts with the Terms of Use, this document controls for program participation. If a provision of this document conflicts with the Developer Agreement, this document controls for program matters and the Developer Agreement controls for all other matters. Policies and help pages explain this document; they do not amend it.
Article 2: Definitions
2.1 In this document, terms defined in the Developer Agreement have the same meaning, and Client: a Seller, a Brand, or another merchant the Provider serves. A reference to a Seller in this document includes a Brand client where the context requires.
Provider: a firm enrolled in the Solution Provider Program under this document. The Provider is the Developer for purposes of the Developer Agreement in respect of the Provider's own developer access.
Responsible Individual: a named individual with authority to answer for the Provider's Platform work, reachable within two (2) business days.
Article 3: Eligibility, Application, and Enrollment
3.1 The Provider is the Client's contractor, never the Client's substitute. The Provider shall not accept Platform terms on a Client's behalf, shall not hold a Client's session or credentials, and shall not speak for a Client in an enforcement proceeding. The Client's relationship with the Company is direct and is governed by the Client's own agreements.
3.2 This program is not a reseller program. The Provider shall not resell Platform access, shall not hold Platform credentials for resale, and shall not interpose itself between the Client and the Company's billing, enforcement, or support.
3.3 An application is submitted through the partner-application intake for the trade the Provider serves, subject to the rate discipline for that intake; an attempt to defeat an intake limit by rotating addresses or by repeated automated submission is Circumvention under the Scraping Prohibition. The application shall state plainly that the applicant is a solution provider and not a merchant, and shall identify the trade served. An acknowledgment of receipt is not an approval. Initial review is targeted within ten (10) business days of a complete application. An incomplete application is returned once for completion and is closed if not completed within thirty (30) days.
3.4 To enroll, a Provider shall: (a) submit a complete application under clause 3.3; (b) accept §Developer Agreement–2.7.25 in full; (c) demonstrate one delivered merchant implementation on the Platform, reviewed by the Company for compliance with §Developer Agreement–2.7.25; and (d) name a Responsible Individual.
3.5 The Company shall not enroll: a firm currently suspended or terminated under the Partner Suspension, Termination and Appeals; a firm whose principals were barred for scraping, data sale, or credential collection; a firm that cannot identify a Responsible Individual; or a firm whose business model requires holding Client credentials or pooling Client sessions.
3.6 Enrollment is per firm. Staff and subcontractors of the Provider act under the firm's enrollment, and the firm is answerable for their acts on the Platform as its own.
Article 4: Standing
4.1 Registered. Requirements: a complete provider profile, acceptance of §Developer Agreement–2.7.25, and one delivered merchant implementation reviewed under clause 3.4(c). Benefits: a directory listing when the directory is available, and use of the Registered badge in accordance with the Developer Brand and Trademark Use (Developer Brand and Trademark Use Policy).
4.2 Certified. Requirements: Registered standing for six (6) months, certification of at least one connector under the Integration Certification Policy, two Client references the Company may contact, and support responsiveness that meets the standard for the second priority class in the Partner Support and Incident Escalation Policy. Benefits: the Certified badge, lead referrals where the Company operates a referral procedure, and co-marketing eligibility under Article 6.
4.3 Premier. By invitation only. Requirements: Certified standing for twelve (12) months, five (5) Client references, a dedicated support contact at the firm, and an annual business review with the Company. Benefits: the Premier badge, priority lead flow, advance briefings under a confidentiality agreement, and Elevated Tier under the API Access Tiers for the firm's implementation work.
4.4 A badge or standing is a statement about program participation only. Standing does not entitle the Provider to a Client's business, and the Company does not warrant the Provider's work to a Client. The Provider's contract with the Client governs the Provider's work for that Client. The Company is not a party to a Provider–Client contract, is not liable for performance under it, and does not mediate a fee or scope dispute under it, except as Article 9 provides for a program violation.
Article 5: Duties in Client Work
5.1 Credentials. The Provider holds the credentials of the Provider's own Developer account only, never a Client's. The Provider shall not ask a Client for the Client's password and shall not pool Client sessions across the Provider's client base. A violation of this clause is also a violation of the Scraping Prohibition.
5.2 Compliance of implementations. Every implementation the Provider delivers for a Client shall comply with §Developer Agreement–2.7.25, including: data duties under the Data Use, Retention and Deletion, where the Provider's retention statement shall cover Client data the Provider touches; disclosure under the Automated Access and Agent Disclosure where an automated agent is deployed for a Client; rate discipline under the API Rate Limits and Quotas; and security under the Partner Security Requirements.
5.3 Flow-down of data duties. The data duties of the Provider's Clients under the Data Use, Retention and Deletion flow down to the Provider for every item of Client data the Provider receives, stores, or processes. The Provider shall impose the same duties in writing on each subprocessor the Provider uses for Client data, shall keep the Client's data use within the purpose the Client authorized, and shall not use Client data for the Provider's own advertising, profiling, or model training. A Provider breach of a flowed-down duty is a breach of this document and of the Data Use, Retention and Deletion.
5.4 Return of data. On termination of the Provider–Client relationship, the Provider shall: transition or return all Client data within thirty (30) days; delete Provider-held copies in accordance with the Data Use, Retention and Deletion; and not condition return of data or of credentials the Client owns on payment of a disputed fee. Retention of a Client's catalog or records to compel payment is cause for immediate removal under Article 7.
5.5 Compensation disclosure. The Provider shall disclose to the Client, in writing before contract signature: any compensation the Provider receives that is tied to Platform fees or application revenue; and any addition the Provider applies when reselling a Platform-billed service. The Company does not set the Provider's prices; the duty is that the Client sees the amounts described in this clause before signing.
5.6 Support continuity. The Provider shall maintain the support responsiveness of its standing for the life of each Client engagement and for sixty (60) days after the engagement ends.
Article 6: Badges, Marketing, and Referrals
6.1 A Tier badge may be used only while the standing is held and only in accordance with the Developer Brand and Trademark Use (Developer Brand and Trademark Use Policy). A Provider that loses Certified standing shall remove the Certified badge within fifteen (15) days.
6.2 A program status: including "partner," "certified," and "premier": is not an endorsement of the Provider's work outside the Platform. Marketing that implies the Company guarantees the Provider's results, or that the Provider speaks for the Company, is prohibited.
6.3 A case study naming the Company or a Client requires written consent of the named party. Publication of a Client's Order volumes or revenue figures without consent violates this article and the Data Use, Retention and Deletion.
6.4 Co-marketing: including a joint presentation, a featured listing, and event presence: is available to Certified and Premier Providers by proposal. The Company may decline a proposal without stating a reason; co-marketing is a benefit, not a right.
6.5 Where the Company operates a lead-referral procedure: the Company routes a merchant inquiry to Providers matching the trade and standing; the Provider shall acknowledge a referral within two (2) business days and shall report the outcome (engaged, declined, or closed); a Provider that disregards a referral or reports an outcome falsely loses referral eligibility. Referral fees, revenue share, and lead payments, if any, are governed by the Partner Revenue Share Policy. A referral is a lead, not an assignment: the merchant chooses the Provider, and a Provider shall not pay for placement in a referral procedure.
Article 7: Review, Downgrade, and Removal
7.1 Standing is reviewed annually against Article 4 and Article 5. Failure to meet the requirements for the standing held results in downgrade on thirty (30) days' written notice stating the reasons.
7.2 Cause for removal includes: a material breach of §Developer Agreement–2.7.25 in Client work; retention of Client data contrary to clause 5.4; fraud or misrepresentation in the application or in Client dealings; loss of the Responsible Individual without replacement within thirty (30) days; and a violation for which no cure period applies under Article 9, including scraping under the Scraping Prohibition and sale of data under the Data Use, Retention and Deletion. Removal follows the Partner Suspension, Termination and Appeals; cause described in the preceding sentence as carrying no cure period permits immediate removal.
7.3 On removal, the Provider shall transition each affected Client within sixty (60) days: hand over documentation, credentials the Client owns, and data in accordance with clause 5.4; cooperate with a successor provider the Client names; and delete Provider-held Client data with certification in accordance with the Data Use, Retention and Deletion. The sixty (60) day period protects the Client; delay in transition is a separate violation.
Article 8: Liability
8.1 Exclusion of certain damages. To the fullest extent permitted by law, neither party is liable to the other for indirect, incidental, special, punitive, or consequential damages, or for lost profits, lost revenue, or loss of goodwill, arising out of or relating to this document, even if the party has been advised of the possibility of those damages.
8.2 Cap. To the fullest extent permitted by law, the Company's total liability arising out of or relating to this document shall not exceed the greater of (a) the amounts the Provider paid to the Company under this document in the twelve months before the event giving rise to the claim, or (b) one hundred dollars ($100).
8.3 Carve-outs. This article does not limit (a) a party's indemnification obligations under this document; (b) liability for fraud or willful misconduct; (c) amounts the Provider owes for Orders, fees, chargebacks, or refunds under this document; or (d) liability that cannot be limited under applicable law.
8.4 Essential purpose. The parties agree that this article allocates risk between them, that it is an essential part of the basis of their bargain, and that it applies even if a limited remedy fails of its essential purpose.
Article 9: Indemnification
9.1 Duty. The Provider shall indemnify, defend, and hold harmless the Company and its members, managers, employees, and agents from and against every claim, demand, action, loss, liability, judgment, settlement, cost, and expense (including reasonable attorneys' fees) arising out of or relating to: (a) the Provider's breach of this document; (b) the Provider's implementations, services to a Client, and content; (c) the Provider's violation of any law or of the rights of any person, including a Client whose data the Provider held; and (d) taxes for which the Provider is responsible under this document.
9.2 Procedure. The Company shall give prompt written notice of a claim under this article. The Provider shall control the defense with counsel reasonably acceptable to the Company. The Company may participate in the defense at its own expense. The Provider shall not settle a claim in a manner that imposes any obligation or restriction on the Company, or that does not release the Company fully, without the Company's prior written consent.
9.3 Survival. This article survives the termination of this document.
Article 10: Enforcement and Appeals
10.1 Investigation. The Company may investigate any suspected violation of this document. The Provider shall cooperate with an investigation and shall produce the records this document requires the Provider to keep, including application records, disclosure records under clause 5.5, and transition records under clause 7.3.
10.2 Notice. If the Company determines that the Provider has violated this document, the Company shall give written notice stating the provision violated and the facts relied on, except where notice would compromise an investigation of fraud, a safety risk, or a legal obligation.
10.3 Opportunity to cure. Where a violation is capable of cure, the Provider has ten (10) business days from notice to cure it and to confirm the cure in writing. No cure period applies to retention of Client data contrary to clause 5.4 after a demand for return, to scraping, to sale of data, to fraud, or to a violation that by its nature cannot be cured.
10.4 Measures. If a violation is established and is not cured within the period allowed, the Company may, proportionate to the violation: (a) issue a written warning; (b) downgrade standing under clause 7.1 or remove the Provider under clause 7.2, with the transition duties in clause 7.3; (c) require removal of a badge under clause 6.1; (d) suspend or revoke a Credential; (e) suspend the Account or program participation, in whole or in part; (f) terminate this document and the Account; and (g) exercise any other right or remedy available under this document or at law. Procedure is further governed by the Partner Suspension, Termination and Appeals.
10.5 Appeal. The Provider may appeal a measure under this article by written notice to legal@aapawz.com within thirty (30) days of the measure, stating the grounds and attaching the records relied on. The appeal is decided by a person who did not make the original decision. The Company's decision on appeal is final. A measure remains in effect during an appeal unless the Company directs otherwise in writing.
10.6 No waiver by delay. The Company's delay in acting on a violation is not a waiver of the violation or of any later violation of the same kind.
Article 11: Term and Termination
11.1 Term. This document takes effect when the Provider is enrolled and continues until terminated under this article or until the Developer Agreement terminates, whichever occurs first.
11.2 Termination by the Company. The Company may terminate this document on thirty (30) days' written notice for any reason, and immediately on written notice if the Provider materially breaches this document, engages in fraud, or becomes ineligible to participate. Removal for cause under clause 7.2 is a termination under this clause.
11.3 Termination by the Provider. The Provider may terminate this document on thirty (30) days' written notice to support@aapawz.com, provided the Provider has no investigation outstanding and has completed the transition duties in clause 7.3 for each Client affected.
11.4 Effect of termination. On termination: (a) enrollment and standing end and badge use shall cease in accordance with clause 6.1; (b) the transition, return, and deletion duties in clauses 5.4 and 7.3 apply to every Client; (c) obligations that arose before termination survive until satisfied; and (d) the Company shall pay amounts owed, less amounts the Company may set off under this document, within thirty (30) days, except amounts held in connection with an open investigation or dispute.
11.5 Survival. The Definitions, Liability, Indemnification, Enforcement and Appeals (for measures taken before termination), Dispute Resolution, and General Provisions articles survive termination, together with clauses 5.3, 5.4, and 7.3 until satisfied.
Article 12: Dispute Resolution
12.1 Any dispute arising out of or relating to this document, or to the relationship it governs, is governed by the Dispute Resolution Policy, which is incorporated into this document by reference.
Article 13: General Provisions
13.1 Amendments. The Company may amend this document by posting the amended document in the Document Center and giving notice to the Provider at the email address in the Account. An amendment that materially increases the Provider's fees or obligations takes effect thirty (30) days after notice; other amendments take effect on posting. Continued use of the Platform after the effective date of an amendment is acceptance of it. If the Provider does not accept an amendment, the Provider's remedy is to terminate under Article 11 before the amendment takes effect.
13.2 Notices. Legal notices under this document shall be sent to legal@aapawz.com. Operational notices and all other communications shall be sent to support@aapawz.com. A notice to the Company is effective when the Company acknowledges receipt or, for email, one business day after sending, whichever is earlier. Notices to the Provider are effective when sent to the email address in the Account or posted to the Account's notice facility in the portal, whichever occurs first. The Provider shall keep the email address in the Account current. DMCA notices are given as provided in the DMCA and Copyright Policy, to the designated agent at legal@aapawz.com.
13.3 Governing law. This document is governed by the laws of the State of Tennessee, without regard to its conflict-of-laws rules. Subject to the Dispute Resolution Policy, any proceeding arising out of this document shall be brought in the state or federal courts located in Shelby County, Tennessee, and the parties consent to personal jurisdiction there.
13.4 Severability. If any provision of this document is held unenforceable, the provision shall be enforced to the fullest extent permitted, and the remaining provisions continue in full effect.
13.5 Entire agreement. This document, together with the documents it incorporates by reference, is the entire agreement between the Company and the Provider for the subject it governs and supersedes every prior or contemporaneous statement, communication, or agreement on that subject, whether written or oral. This clause does not make the Company a party to a Provider–Client contract.
13.6 Assignment. The Provider shall not assign this document or any right or obligation under it without the Company's prior written consent, and an assignment without consent is void. The Company may assign this document to an affiliate or in connection with a sale of all or part of its business, on notice to the Provider.
13.7 Waiver. A waiver of any provision of this document is effective only in writing and only for the instance stated. No waiver is a waiver of any other provision or instance.
13.8 Interpretation. Headings are for convenience only. "Including" means "including without limitation." This document shall not be construed against a party on the ground that the party prepared it. The English-language text controls over any translation.